We currently use the master/minion setup even for a single server. But recently we've noted problems with either the Salt Master consuming too much memory or the minion falling over and not restarting. When the minion isn't up the deploy doesn't fail but it doesn't work either. It just does nothing.
Salt-SSH uses the developer's local machine as a temporary master and runs the states on the remove machines: http://docs.saltstack.com/en/latest/topics/ssh/ There is no master and no minion so this is more like Ansible without having to rewrite all of our states. Unclear how the GPG secrets could work here but worth an investigation.
We currently use the master/minion setup even for a single server. But recently we've noted problems with either the Salt Master consuming too much memory or the minion falling over and not restarting. When the minion isn't up the deploy doesn't fail but it doesn't work either. It just does nothing.
Salt-SSH uses the developer's local machine as a temporary master and runs the states on the remove machines: http://docs.saltstack.com/en/latest/topics/ssh/ There is no master and no minion so this is more like Ansible without having to rewrite all of our states. Unclear how the GPG secrets could work here but worth an investigation.