chef / chef/knife-ec-backup

knife-ec-restore can't restore backups that don't include public_key_read_access group

Open
#84 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Ruby
Stars
32
Forks
28
PR merge metrics
No merged PRs in 30d

Description

Specific Issue

We now expect a backup to contain the public_key_read_access group for an organization. If it doesn't we can't restore it.

General Issue

Over the last few Chef Server releases a number of changes have been made to the default layout of an organization and default ACLs. If we don't account for these changes on restore, it is very unclear what the restored state of the organization is. This needs to be investigated.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the knife-ec-restore restore path and inspect how organization groups and default ACLs are reconstructed from backups. Compare backups with and without the public_key_read_access group and document the expected restored organization state; done means older backups restore with defined, predictable defaults.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.