Allow jinja templates while provisioning

[eedgar]

I used this to dynamically set the hostname based on templates. instead of having to create a file for every vm etc.
This should work for all provisioning cases I found.

you should be able to set additional template args as well .. name is implied.

"provision": [
{
"type": "shell",
"inline": "echo {{name}} > /tmp/out2",
"template": "True"
},
{
"type": "shell",
"path": "./salt-minion.sh",
"template": "True"
},
{
"type": "file",
"source": "./temporary.txt",
"destination": "/tmp/temporary.txt",
"template": "True"
}
]

more temporary.txt
{{name}}

more salt-minion.sh
#!/bin/bash
sudo mkdir -p /etc/salt

Set the minion id

sudo sh -c "echo {{name}} > /etc/salt/minion_id"
sudo wget -O - https://repo.saltstack.com/py3/ubuntu/20.04/amd64/latest/SALTSTACK-GPG-KEY.pub | sudo apt-key add -
sudo sh -c "echo 'deb http://repo.saltstack.com/py3/ubuntu/20.04/amd64/latest focal main' > /etc/apt/sources.list.d/saltstack.list"
sudo apt-get update
sudo apt-get -y install salt-minion

Set the hostname

sudo salt-call --local network.mod_hostname {{name}}

Restart the salt-minion service

sudo service salt-minion restart

[mkinney]

I am so sorry. I thought I had notifications enabled, but I must not have it set correctly or something. I just stumbled on this PR. I'll take a look at this soon. Thanks for the contribution.