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

Aberta
#2,760 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
30/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
postgresql, python
Domínio
cli, devops

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Rust
Estrelas
2
Forks
0
Merge médio
9h 48min
PRs com merge (30d)
151

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de registrystack/registry-stack

Todas as issues de registrystack/registry-stack

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.