-
Notifications
You must be signed in to change notification settings - Fork 440
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: fix container names annotations for sdk, apache, nginx #3307
Conversation
Found through code inspection, the ApacheHttpd, Nginx and SDK injectors do not honor their container-names annotations. This is a breaking change if anyone is using the enablement flag with container names for these 3 injectors, which I believe would work as truthy would treat a list of container names as true. Signed-off-by: Alan Clucas <alan@clucas.org>
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.
Good catch!
Please, could you add a changelog?
@Joibel Thanks for the fix, I'll update the tests after this fix. |
What I find worrisome is that changing this doesn't fail any tests. Could you add a unit test? Ideally, we'd also have an e2e test exercise this function. |
Yes, I will do. |
Signed-off-by: Alan Clucas <alan@clucas.org>
I've added a changelog. I'm not that familiar with the tests - I could possibly write one but it looks like @IshwarKanse has offered so I'll leave it with them. |
Found through code inspection, the ApacheHttpd, Nginx and SDK injectors do not honour their container-names annotations.
I have changed the annotation used for the container list to match the expected annotation constant which already existed in each case but was unused in the code base.
This is a breaking change if anyone is using the enablement flag with container names for these 3 injectors, which I believe would work as truthy would treat a list of container names as true.