Vaults

A vault is how a repository is shown to projects. It has a name, a description and the terms for manual backups taken there. The terms say how long a manual backup may be kept, whether it may be kept until deleted, and how many may be taken a day. A policy keeps its backups in the vault of its backup repository. A manual backup outside any plan names a vault directly. Operators write vaults. A project sees the public ones and those of the policies it is offered.

📄️ List vaults

A project sees the vaults offered to it: the public ones and those its policies keep backups in. An operator sees every vault with its repository and terms as written. Vaults are listed by name.

📄️ Create a vault

Gives a repository the name, description and terms that projects see. The terms say how long a manual backup may be kept there, whether it may be kept until deleted, and how many may be taken a day. A vault on a locked repository is immutable. A repository has at most one vault.

📄️ Delete a vault

Withdraws the vault. Backups already kept in it keep their dates.

📄️ Show a vault

Any reader of the project the token is scoped to.

📄️ Change a vault

Fields left out are kept. A vault stays on its repository.