-
-
Notifications
You must be signed in to change notification settings - Fork 15
[Merged by Bors] - Separate operator and controller names #492
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
Conversation
src/builder/meta.rs
Outdated
operator_name: &str, | ||
controller_name: &str, | ||
app_role: &str, | ||
app_role_group: &str, |
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.
This triggers a cargo warning due to #491, not sure if we want to tackle that in this PR...
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.
I'd be fine with munging it together but I'd appreciate it if you could bring it up at the daily or arch meeting to see if there are any objections (I don't expect any tbh.).
If you decide to let me know please.
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.
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.
Updated to account for #491 being merged.
## Description Hopefully this should help clarify how the different names hold together, and help make it clearer how to adjust for later changes going forward. This doesn't cover `role_group_selector_labels` or `role_selector_labels` since they have a more obvious inherent structure to them, and I don't see them changing as much (especially since they are effectively part of the public API). This is kind of coupled to #492, do we want to merge that into this PR or do that one on top of this afterwards? Fixes #491. Co-authored-by: Teo Klestrup Röijezon <teo.roijezon@stackable.de>
bors r+ |
## Description Fixes #482 Co-authored-by: Teo Klestrup Röijezon <teo.roijezon@stackable.de>
Pull request successfully merged into main. Build succeeded: |
Description
Fixes #482
Review Checklist
Once the review is done, comment
bors r+
(orbors merge
) to merge. Further information