-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Select resources by UUID label #2609
Select resources by UUID label #2609
Conversation
) | ||
|
||
// DefaultLabeller adds K9 style managed-by label |
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.
hahaha, we had k9 style labels? 🐶
Codecov Report
|
hey @corneliusweig this looks good, I think you just need to rebase! |
ping @corneliusweig, if you rebase we can merge! |
I'm still traveling, but I'll get to it by tomorrow evening. |
Signed-off-by: Cornelius Weig <[email protected]>
Signed-off-by: Cornelius Weig <[email protected]>
2e02db0
to
591d813
Compare
Before, these were selected based on the managed-by label, which caused interferences in tests. Using the UUID label avoids these problems. Signed-off-by: Cornelius Weig <[email protected]>
- use idiomatic go names - make sure the runID remains identical, even if multiple labeller instances are created Signed-off-by: Cornelius Weig <[email protected]>
…he same runID Signed-off-by: Cornelius Weig <[email protected]>
591d813
to
9a37620
Compare
@nkubala rebase is done! |
For details see #2496.
As described there, I added a new label which is specific to each skaffold run. When selecting resources, only resources created by the exact same skaffold run will be found.
Fixes #2496