Currently all our data is volatile or generated by Puppet, but when U2F support is added there will be some data worth backup up (and there's probably more, needs a closer investigation)
The data to be backed up can then be defined in a backup set and added to our backups.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Add IDP device data to backups | operations/puppet | production | +7 -0 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T233921 Further steps for CAS/web SSO | |||
| Resolved | MoritzMuehlenhoff | T233936 Integrate CAS into backup infrastructure |
i think ultimately all the none volatile data like u2f registration and audit data should live in one of the supported storage backends
Change 553058 had a related patch set uploaded (by Muehlenhoff; owner: Muehlenhoff):
[operations/puppet@production] Add IDP config to backups
Change 553058 merged by Muehlenhoff:
[operations/puppet@production] Add IDP device data to backups
I'm closing this, the U2F meta data is backed up and the rest comes from Puppet or is volatile.