-
Notifications
You must be signed in to change notification settings - Fork 26
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
labeller: make component labels more descrete #182
Conversation
35ce5a0
to
8558e48
Compare
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.
Since those names of resources and labels are kinda part of our public API (some users might write scripts expecting them) and if we don't want to break it now or in the future it would be wise to first make a PR with test for this values. I think ComponentManager constructor should be split in two parts, where first one is about creating components and not interacting with k8s — so that constructor can be used in such test and we call GetMetaLabelMap
for all components and canonize the result.
After that this PR will introduce change and we can be sure if nothing is broken and new changes are intended.
8558e48
to
374c322
Compare
2303234
to
01c315d
Compare
1b14641
to
3336916
Compare
I guess this one also not actual now after labels refactoring. |
No description provided.