-
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
[0.6] Make sure to update the name in the mutator #535
[0.6] Make sure to update the name in the mutator #535
Conversation
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.
Idea looks ok to me (assuming that if you set both name and generate name k8s won't just re-make the name based on generate name, though I would test that). I would definitely add a test for this overall logic if we can.
dcfc231
I have tested the generateName vs name, and as long as name is populated, k8s won't use generate name to overwrite it |
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.
👍 Tests look like they'd cover the documented business requirements for the generative name prefix.
Fixes an issue with #532 where the name wasn't being updated