-
Notifications
You must be signed in to change notification settings - Fork 261
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 webhook changes to OpenStackCluster.Spec.Bastion #1070
✨ Allow webhook changes to OpenStackCluster.Spec.Bastion #1070
Conversation
✔️ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready! 🔨 Explore the source changes: ab690e0 🔍 Inspect the deploy log: https://app.netlify.com/sites/kubernetes-sigs-cluster-api-openstack/deploys/61af34d309b6db0007ad5eb2 😎 Browse the preview: https://deploy-preview-1070--kubernetes-sigs-cluster-api-openstack.netlify.app/print |
ad684bc
to
301d7b8
Compare
9a56fa2
to
aea3643
Compare
e6d66f4
to
8810b36
Compare
Signed-off-by: Tobias Giese <tobias.giese@daimler.com>
c68b89e
to
5be9181
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.
Thanks for the unit tests! Couple of discussion points.
6c2b7f4
to
a32fe32
Compare
a32fe32
to
f81ecbf
Compare
Signed-off-by: Tobias Giese <tobias.giese@daimler.com>
f81ecbf
to
ab690e0
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.
/lgtm
Thanks for the extra test. As discussed in Slack, I was worried that allowing changes to the spec before the bastion had actually been removed could potentially introduce a race which somebody might hit if, e.g. they scripted it. This approach feels simple and correct.
wantErr: true, | ||
}, | ||
{ | ||
name: "Disabling the OpenStackCluster.Spec.Bastion while it's running is allowed", |
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.
👍
@tobiasgiese Tests are all passing. Do you want to remove the hold? |
I‘m still waiting for the approve of a CAPO maintainer. Prow won‘t merge until it‘s approved. |
ptal @hidekazuna @jichenjc 🙂 thanks |
That's ok. If you remove the /hold it will merge immediately after it's approved. |
I know that 🙂 we're using Prow at work. Edit: and it removes the chance to get reviews from more people. If someone approves and lgtm this PR without my hold it's going to be merged, no matter if other people have findings/concerns or not :) |
/LGTM |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hidekazuna, mdbooth, tobiasgiese The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@tobiasgiese You can remove /hold if you want 😃 |
thx @hidekazuna :) /unhold |
What this PR does / why we need it:
This PR allows
OpenStackCluster.Spec.Bastion
to be updated (i.e., to be mutable).Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #1054
Special notes for your reviewer:
TODOs:
/hold
Tobias Giese tobias.giese@daimler.com, Daimler TSS GmbH, legal info/Impressum