-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
Add support for the registry value in the autodiscovery for helm #1346
Milestone
Comments
mavimo
added a commit
to mavimo/updatecli
that referenced
this issue
May 26, 2023
…ry feature for helm
mavimo
changed the title
Feature Request:
Add support for the registry value in the autodiscovery for helm
May 26, 2023
mavimo
added a commit
to mavimo/updatecli
that referenced
this issue
May 26, 2023
…ry feature for helm
mavimo
added a commit
to mavimo/updatecli
that referenced
this issue
May 26, 2023
…ry feature for helm
mavimo
added a commit
to mavimo/updatecli
that referenced
this issue
May 26, 2023
mavimo
added a commit
to mavimo/updatecli
that referenced
this issue
May 26, 2023
olblak
pushed a commit
that referenced
this issue
May 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem?
I'm experimenting the auto-discovery feature
helm
.I see that work fine using the
tag
andrepository
entry but only if the repository include also theregistry
entry, when they are defined in different entries (that seems to be the most used approach) is not able to work.E.g.:
work fine, but:
fail since use the default registry (
hub.docker.io
) instead the one specified in the registry.Solution you'd like
Add support also for the
registry
entryAlternatives you've considered
Do some manipulation in the yaml before and after using updatecli to woraround the problem
Anything else?
I already have some code working, I'll open a PR soon
The text was updated successfully, but these errors were encountered: