Repository navigation
Replies: 1 comment
|
I'm looking into this issue myself, since I'm wondering why the auto-discover feature doesn't work lately for my new repos. The helm variable module.exports = {
...
"autodiscoverFilter": ["ops1/*", "org2/*"]
};I'm not sure how to configure it as the owner intended; but I think for helm deployment (container in general), I would convert my vars into JS configs (maybe with kustomize) |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I was initially testing out a POC of renovate with the CLI tool, but have moved to a renovate-ce helm installation as I begin to finalize the deployment.
I had been using this configuration for autodiscovery:
I chose to use the
autodiscoverNamespacesfeature overautoDiscoverFilterbecause the documentation says the namespace filtering is done server-side:This seems to be also confirmed based on autodiscoverFilter using renovate's custom string match logic, which would imply its client-side filtering.
However,
autodiscoverNamespaces/autodiscoverProjectsdoesn't seem to work with the helm installation (and possibly also the Docker image, I haven't used that). Reviewing the values file documentation, it says we must use theautodiscoverFilter, which should support my use case, but wouldn't it be incorrect to sayautodiscoverFilteris server-side filtering?If the values documentation is incorrect, I'm happy to open a PR, but I'm also curious why the more-efficient filtering option is not supported by the helm installation, as I haven't found an explanation for that.
All reactions