knife-ec-restore can't create backups of Servers that don't have public_key_read_access group (< 12.5.0)
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 the Chef Server to contain the public_key_read_access group for an organization. If it doesn't we can't back it up.
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 all of the possible past structures of the Chef Server groups, then knife-ec-backup can not be used reliably facilitate migrations from old servers to new.
Similar in nature to https://github.com/chef/knife-ec-backup/pull/79
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the knife-ec-restore and knife-ec-backup handling described here, then compare the related changes in pull request #79. Determine which older Chef Server group layouts need support; done means backups work when public_key_read_access is absent and migrations from older server structures remain reliable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100