-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
feat(manager/flux): support chartRef in HelmRelease resources #31962
base: main
Are you sure you want to change the base?
Conversation
conflicted |
…renovatebot#32532) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Michael Kriese <[email protected]>
…#32538) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…ot#32541) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Rhys Arkins <[email protected]>
…renovatebot#32548) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…enovatebot#32554) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…#32553) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…renovatebot#32557) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…enovatebot#32816) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…2820) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…v13.0.23 (renovatebot#32824) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovatebot#32826) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovatebot#32827) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Michael Kriese <[email protected]>
…32831) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…novatebot#32837) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
unfortunately a lot of commits were introduced accidentally on this branch when merging with |
@@ -102,6 +106,39 @@ function resolveGitRepositoryPerSourceTag( | |||
} | |||
} | |||
|
|||
function resolveHelmRepository( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same, extract to refactor pr. can combined with comment above
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry, but I cannot really follow this. the extracted code in this function is literally identical to what was previously within the switch statement, and I need the exact same logic in the new case (as it's just about resolving the details of the referenced repository, properly supporting OCI repos etc). If I don't extract this into a function, I'd have to duplicate the whole block, copy+paste it down into the new case. which causes test coverage to decrease, and forcing the addition (and duplication) of test cases just to test the same code again in the other context - and to remove all of these additional tests again right afterwards in yet another PR too? that doesn't make sense.
I've removed the other refactoring as requested though, as that was in a part that is now mostly unchanged again after working on the various topics. but I really don't see how the second one here could be avoided without creating more questionable quality issues.
Changes
Adds support for
chartRef
fields withinHelmRelease
resources in the flux manager, as described in #31945.Context
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: