-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add code to remove legacy validation_marker
file that created by etcd-custom-image on the filesystem
#38
base: main
Are you sure you want to change the base?
Conversation
…cd-custom-image on the filesystem
/invite @ishan16696 |
Hey Shreyas, etcd-wrapper/internal/app/app.go Lines 96 to 100 in d3b0f82
May be what you have seen could be some edge cases in which etcd-wrapper failed to remove old // Delete legacy validation marker after etcd starts successfully
// TODO: To be removed in next release
if err = bootstrap.CleanupExitCode(types.LegacyValidationMarkerFilePath); err != nil {
a.logger.Warn("failed to clean-up legacy exit code file", zap.Error(err))
} |
@ishan16696 that code cleans up the new So deletion of |
I'm saying can we reuse the same func and just pass the old path of exit code file (i.e validation_marker file). // Delete legacy validation marker after etcd starts successfully
// TODO: To be removed in next release
if err = bootstrap.CleanupExitCode(....); err != nil {
a.logger.Warn("failed to clean-up legacy exit code file", zap.Error(err))
} |
@ishan16696 not really. etcd-wrapper is designed to delete the I've pushed the change as requested. PTAL. |
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 @shreyas-s-rao for PR.
LGTM!!
How to categorize this PR?
/area compliance security
/kind task
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #37
Special notes for your reviewer:
Release note: