You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The outcome of #4536 was that there's no easy automated way for us to monitor GCP disaster recovery backups.
Let's design a manual process that we can do every month instead.
The outcome of this should be:
Definition of done
A document that any engineer can follow to check if backups are being performed correctly, and old backups are being deleted correctly.
This process should not take more than a total of 30min for the engineer to perform.
Design options
There are three ways to do this:
Document how you would look at this in the GUI
Document what set of gcloud commandline commands should be run and how to verify them
Add a command to deployer to do this
Whoever is doing this task can decide which of these three approaches to take. Take whatever is the easiest for you to implement, so we can mark move forward in this EPIC.
The text was updated successfully, but these errors were encountered:
The outcome of #4536 was that there's no easy automated way for us to monitor GCP disaster recovery backups.
Let's design a manual process that we can do every month instead.
The outcome of this should be:
Definition of done
Design options
There are three ways to do this:
gcloud
commandline commands should be run and how to verify themdeployer
to do thisWhoever is doing this task can decide which of these three approaches to take. Take whatever is the easiest for you to implement, so we can mark move forward in this EPIC.
The text was updated successfully, but these errors were encountered: