-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support helm chart placeholder repositories #4681
Comments
@bastianeicher @gordonbondon @srueg @BugRoger appreciate your inputs here if you have any |
This is repo alias(helm/helm#2174) and it works when helm repo was added locally with Tools like helmfile in your example provide options to do this You can get a list of name-url pairs after they were added by doing |
Ideally we want to do this without shelling out to third party binaries. Being able to scan/parse in a browser or pass unit tests without installing a dozen binaries is important to the project. In the AXOOM example the placeholder definition is in |
Hi @rarkins, first of all, thanks for taking a look at our GitHub projects. :) In Helm, in order for a repository to be usable it must always be registered first with Even when you don't intend to use the alias name, you still need to perform the This works well enough if there's a How about adding a new config option to Regards |
🎉 This issue has been resolved in version 19.69.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
What would you like Renovate to be able to do?
Support placeholders like this:
Also support
alias:axoom-github
too as allowed in helm/helm#2174Describe the solution you'd like
It seems we need to check other
yaml
files within the repo for placeholder values. Is the location deterministic?Describe alternatives you've considered
Currently we just skip placeholders, so they're not updated.
Additional context
Example source: https://github.com/AXOOM/Templates.WebService/blob/b7fca8e6a8aa94283a4aa4a1a98c92d77d6d4f55/content/helmfile.yaml#L6-L8
The text was updated successfully, but these errors were encountered: