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
fix(applicationset): support webhook with matrix interpolation (#9931) #10236
fix(applicationset): support webhook with matrix interpolation (#9931) #10236
Conversation
Codecov Report
@@ Coverage Diff @@
## master #10236 +/- ##
==========================================
- Coverage 46.18% 46.10% -0.08%
==========================================
Files 226 228 +2
Lines 27581 27956 +375
==========================================
+ Hits 12737 12889 +152
- Misses 13124 13321 +197
- Partials 1720 1746 +26
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
ac4e88d
to
d3294c2
Compare
@sboschman can you resolve the conflicts? |
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.
@sboschman can you describe (or add as comments) what the changes in shouldRefreshMatrixGenerator
do? I need to read this more in-depth, but I think a quick description will help a lot. :-)
I'm a little worried that the temporary generators don't include matrix and merge generators. Is this solution expected to work with nested matrix generators, or matrix generators that contain nested merge generators?
No not expected in its current form, as for some reason I was under the impression nesting those two generators was not allowed. After checking the docs again, I see you are allowed to nest them just once. So, will have to do some changes to support that. |
Even before interpolation the webhook code didn't support nested matrix/merge generators. Do we silently fix this as part of the interpolation fix, or do you want me to open a new issue for changelog purposes @crenshaw-dev ? Talking about changelog, should this fix be added to the changelog or not? As it fixes something that is not yet released, the interpolation feat is part of the upcoming 2.5 release... Might be a bit strange to have fixes in the changelog for 2.5 release for features introduced in that same 2.5 release? |
d3294c2
to
09b8ff1
Compare
Signed-off-by: Sverre Boschman <1142569+sboschman@users.noreply.github.com>
09b8ff1
to
c71ea2d
Compare
Signed-off-by: Sverre Boschman <1142569+sboschman@users.noreply.github.com>
I'm okay with just adding the support here, rather than with a new issue.
I think it's fine to include in the changelog. Folks will probably mostly look at the "features" section. Might be a little surprised to see this in the "bug fixes" section, but I don't think that will be a huge problem. |
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.
Fantastic. Thanks @sboschman!
Moved the webhook code to its own 'webhook' package, otherwise go ends up in a cyclic dependency error.
fixes #9931
Note on DCO:
If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.
Checklist: