Skip to content

fix: set resolver in jsonnet vm #442

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

Merged
merged 3 commits into from
Aug 26, 2024
Merged

Conversation

tompizmor
Copy link
Contributor

Since kubecfg version 0.29.1 (more precisely since this commit IIFNM) the resolve-images feature stopped working since the resolver was not set.

I noticed the flagResolver and flagResolvFail flags were simply ignored and I also saw the existing WithResolver function was not used at all.

I tested this MR in my environment and it works fine. Please let me know I case I have not considered something important.

Signed-off-by: Tomas Pizarro Moreno <tpizarro@vmware.com>
Signed-off-by: Tomas Pizarro Moreno <tpizarro@vmware.com>
@tompizmor
Copy link
Contributor Author

@mkmik in the name of Bitnami, would you be so kind to take a look at this? 😄

Copy link
Contributor

@jotadrilo jotadrilo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@mkmik mkmik merged commit 05c77cf into kubecfg:main Aug 26, 2024
6 checks passed
@tompizmor tompizmor deleted the fix-resolve-image branch August 26, 2024 14:52
@tompizmor
Copy link
Contributor Author

@mkmik could you release a new version to include this fix?

@mkmik
Copy link
Contributor

mkmik commented Oct 16, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants