Reference operator: adopt-restored does not support a physical restore

Ouverte
#2,760 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
30/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
postgresql, python
Domaine
cli, devops

Piste de recherche

Start with the adopt-restored command in deploy/stack_operator.py and follow how it treats a matching BReg instance claim with no Helm release as a post-claim-adopt adoption. Read deploy/OPERATIONS.md for the logical-restore path it currently documents, and the BReg security guide's bregctl instance-claim adopt requirement. The open design question (an explicit --physical-copy flag versus refusing an ambiguous matching claim) has to be settled before coding; done means adopt-restored handles the physical path and the guide describes it, including fencing the original first.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

area:breg enhancement

The reference operator's adopt-restored command (deploy/stack_operator.py) supports logical restores only, which is the path deploy/OPERATIONS.md describes. It does not yet support a physical restore: a base backup, point-in-time recovery, a storage snapshot or a promoted replica.

A physical copy keeps the cluster's system identifier and the database OID, so the BReg instance claim already names the copy. adopt-restored reads a matching claim with no Helm release as an adoption that stopped after claim-adopt, and it resumes by serving. For a physical copy, claim-adopt never ran. The BReg security guide asks for bregctl instance-claim adopt before a physically restored copy serves, because that step supersedes the import authorities the restore reopened.

To support physical restores, adopt-restored could take an explicit option such as --physical-copy that always runs claim-adopt, or refuse a matching claim unless the operator says which kind of restore it is. The guide would then describe the physical path, including fencing the original first.

Until then, restore with deploy/state_bundle.py as the guide describes.

Langage dominant
Rust
Étoiles
2
Forks
0
Merge moyen
9 h 48 min
PR mergées (30 j)
151

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de registrystack/registry-stack

Toutes les issues de registrystack/registry-stack

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.