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
{{ message }}
This repository has been archived by the owner on Dec 12, 2021. It is now read-only.
we had an accident where I accidentally deployed from the master branch instead of our personal branch, which ended up resetting SANTA_DEFAULT_CLIENT_MODE. I would have imagined this would have only affected new hosts, however ALL hosts ended up getting reset to lockdown mode triggering a lot of unhappiness :)
I think for hosts that are in the datastore should not be affected by a change to this variable.
The text was updated successfully, but these errors were encountered:
Yeah, that definitely should not happen. Sorry for the trouble this caused. Can you tell if the new deployment somehow resulted in multiple SantaHost entities being created for a single device?
Yeah this should not have happened. Looking at the code, it doesn't look like a change in this constant should have changed the settings of existing hosts. Are there other changes you've made on your branch that could have made the server think that it hadn't seen the host before?
I don't see how any of the other changes could have caused it. Unfortunately we wiped the DB. I'm working on enabling backups so we can do rollbacks instead of wipes
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
we had an accident where I accidentally deployed from the master branch instead of our personal branch, which ended up resetting
SANTA_DEFAULT_CLIENT_MODE
. I would have imagined this would have only affected new hosts, however ALL hosts ended up getting reset to lockdown mode triggering a lot of unhappiness :)I think for hosts that are in the datastore should not be affected by a change to this variable.
The text was updated successfully, but these errors were encountered: