-
Notifications
You must be signed in to change notification settings - Fork 43
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
Retry update with latest secret if plan still matches the applied plan #114
Retry update with latest secret if plan still matches the applied plan #114
Conversation
Signed-off-by: Chris Kim <[email protected]>
Tested through the integration framework for etcd restore on the etcd node:
|
} | ||
// If we get a conflict, we can retrieve the latest secret and compare plan data to see if the plan changed. | ||
latestSecret, getErr := core.Secret().Get(secret.Namespace, secret.Name, metav1.GetOptions{}) | ||
if getErr == nil { |
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.
we could avoid nesting if we invert the condition, but this is more of a nit as the current nesting doesn't significantly impact readability
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.
yeah... this was a little hasty in an attempt to fix this, I can come back and fix this later on.
#113