-
-
Notifications
You must be signed in to change notification settings - Fork 162
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
Allow setting controller block owner deletion false #858
Allow setting controller block owner deletion false #858
Conversation
980ded5
to
1ebaaf2
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.
Would it also make sense to add these same-named arguments to kopf.adopt()
— an aggregate on top of all these ownership/hierarchy functions? For consistency of the interfaces. Wdyt?
Please rebase on |
eefe7df
to
f491fe8
Compare
I considered that and decided probably not. As per the comment you left on the issue I referenced I think adopt means that the child is under full control of the parent. If I'm adding an owner ref explicitly then I may well want to have multiple, if I'm adopting then I want that as the only owner |
d2aece4
to
eddb1b4
Compare
I've rebased against main but am still getting the |
eddb1b4
to
735c4c4
Compare
Signed-off-by: Anthony Nash <anthony.nash@du.co>
Signed-off-by: Anthony Nash <anthony.nash@du.co>
Signed-off-by: Anthony Nash <anthony.nash@du.co>
Signed-off-by: Anthony Nash <anthony.nash@du.co>
Signed-off-by: Anthony Nash <anthony.nash@du.co>
controller/block_owner_deletion kwargs only Co-authored-by: Sergey Vasilyev <nolar@nolar.info> Signed-off-by: Anthony Nash <anthony.nash@du.co>
controller/block_owner_deletion kwargs only Co-authored-by: Sergey Vasilyev <nolar@nolar.info> Signed-off-by: Anthony Nash <anthony.nash@du.co>
Signed-off-by: Anthony Nash <anthony.nash@du.co>
735c4c4
to
4eec6f9
Compare
Ok, I've re-rebased against your main (forgot I had accidentally pushed to my main) and commits are now clean, but still the same test failures |
@nolar what would you prefer? |
What do these changes do?
This will allow setting controller and blockOwnerDeletion from both build_owner_references and append_owner_references
Description
Previous behaviour:
Error from trying to set multiple owner controllers
New behaviour:
Allow explicitly setting
controller=False
, so no errorDoes the change affect end users?
Only if they choose to use it
Issues/PRs
Type of changes
Checklist
CONTRIBUTORS.txt