You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
@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?
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.
The text was updated successfully, but these errors were encountered: