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
Similar problems for other removed states/pillars. Just because you remove the worker state doesn't mean the Supervisor config and the currently running service will be removed. You have to go back and do a one off clean up.
Maybe when we want to remove a user from the system, instead of removing the user from our list, we could add a "state: removed" or something like that, then look for it when processing the user entries?
Activity
mlavin commentedon Aug 7, 2014
No obvious solution to this problem. There isn't a Salt state to assert the entire contents of the authorize keys. Only that single keys are present or absent. http://docs.saltstack.com/en/latest/ref/states/all/salt.states.ssh_auth.html#module-salt.states.ssh_auth
Similar problems for other removed states/pillars. Just because you remove the
workerstate doesn't mean the Supervisor config and the currently running service will be removed. You have to go back and do a one off clean up.daaray commentedon Aug 7, 2014
Fair enough. That one off would look something like (or just ssh to the machine and ✂️ it).
fab [env] salt:'ssh.rm_auth_key [user] [key]
mlavin commentedon Aug 7, 2014
Let's not close this. It is a problem. As you said it just needs some docs or a fab shortcut to help with it.
dpoirier commentedon Aug 11, 2015
Maybe when we want to remove a user from the system, instead of removing the user from our list, we could add a "state: removed" or something like that, then look for it when processing the user entries?
vkurup commentedon Aug 28, 2015
Margarita portion tracked in caktus/margarita#66. We would then need some docs/examples over here on how to use it.