Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bootstrapping a Chef server should not delete databases #79

Closed
glasschef opened this issue Feb 3, 2015 · 2 comments
Closed

Bootstrapping a Chef server should not delete databases #79

glasschef opened this issue Feb 3, 2015 · 2 comments
Labels
Type: Enhancement Adds new functionality.

Comments

@glasschef
Copy link
Contributor

It's far too easy to delete the bootstrap sentinel file, and accidental wipes of production data happen entirely too often. It would be delightful if the cookbook detected existing data and refused to remove it, but instead required the user to manually delete the files with a warning and suggestion for backups.

@sdelano
Copy link
Contributor

sdelano commented May 13, 2015

@glasschef - Can you provide a bit more detail here about the version of the Chef Server and what exactly it is that you're seeing? In older versions with CouchDB, the first part of executing the bootstrap was (unfortunately) a force-delete of the authorization database here.

Is this related to Enterprise Chef 11, or does a similar bit occur during a Chef 12 bootstrap?

@marcparadise
Copy link
Member

Confirmed in that Chef Server 12.6, a 'reconfigure' run will fail non-destructively if the sentinel file is deleted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement Adds new functionality.
Projects
None yet
Development

No branches or pull requests

4 participants