-
Notifications
You must be signed in to change notification settings - Fork 13
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
Adds an overwrite flag to force annotation updates #70
Adds an overwrite flag to force annotation updates #70
Conversation
efdce21
to
ddd8b71
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.
LG, a few questions. Also, think we'll want a parallel change made in restore?
0e4c26f
to
f7c4e7b
Compare
@@ -53,15 +53,19 @@ pgo backup hippo | |||
# Update the 'backups.pgbackrest.manual.repoName' and 'backups.pgbackrest.manual.options' fields | |||
# on the 'hippo' postgrescluster and trigger a backup | |||
pgo backup hippo --repoName="repo1" --options="--type=full" | |||
|
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.
Not your change, but can you look at line 40 -- I don't like that it uses the word "overwrite" when that's not what we do unless you use the overwrite flag
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.
Does the new text work?
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 think there's ~3 cases here that we (maybe) want to cover:
a) take a backup with the settings already in the spec
b) take a backup with new settings that you write to the spec
c) take a backup with new settings that you write to the spec -- even if someone else owns those settings.
Maybe something like (but better than):
Backup allows you to take a backup of a PostgreSQL cluster, either using
the current "spec.backups.pgbackrest.manual" settings on the PostgreSQL cluster
or by writing those settings using the flags (potentially overwriting them with the
`--force-conflicts` flag).
(I don't think we actually want parentheses in our docs. Maybe we just want to say "you can take backups with the settings that are there or write those settings" and mention the overwrite situation in the flag description? No, I think people will run into that, we probably want to bring it up in this summary.)
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.
What about this?
bbdcd72
to
7cec13c
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.
Looks good over all, just need to remove one file.
7cec13c
to
3f35acf
Compare
190e814
to
677c983
Compare
9b476ce
to
fe4e162
Compare
Issue: PGO-39