Saltstack: Pass jinja variable from a salt state file to an included salt state

Pete,

So there are some things to beaware of with having your configs and code together. Lets say you deploy using git this means all your code and config files are sent to each server. If your git is not setup for readonly then someone that gets into one of your machines can edit the configs with a small exploit that will help them access all your machines.

I have known people that put there ssh keys in there deploy repo so they can easily spin up a new salt server or puppet or what ever they use. Again the issue with deploying both your app and configs to each server would mean you have given the keys to the kingdom again this depends that your doing it pull on all your servers and the ssh key is there also.

I have setup deploy systems where i use a readonly git user for deploying code and keep my configs away from all my servers only giving each server the config files that it needs. Each server does have the private key to the readonly git account. I have also been in a setup that on every deploy i automatically roated the public key of all my servers.

You can set a grain on the minion that indicates if the MySQL-State has run before. Just add this to your State:

mysql_master_status:
  mystate.query:
    - query: SHOW MASTER STATUS
  grains.present:
    - name: mysql
    - value: master

Then you can wrap things in your State you only want to run once between an if Statement:

{% if salt['grains.get']('mysql') != 'master' %}
...
{% endif %}

The advantage of this method is that you can now also keep track of your Minions who are MySQL-Masters. The downside is that you have to keep an eye on your grains so that the information won't get lost.