For folks who manage their infrastructure via salt deploys via manual machine updates can be tedious and error prone. I initially met this need with a terribly hacky bash script that would prompt the developer to figure out what needed to be done. After some exploration I was able to come up with a better setup below:
Configuration
salt 2015.5.3 (Lithium) with reactor configured running SSL and the hook api configured to not require auth. Note that this means that you need to secure your request or only support requests that don’t harm your environment bitbucket (web-based) 2.0 API
Gather environmental variables
You’ll need the following details from your environment
#Project Full Name We use this to build out the git config and identity config
FULLNAME=testteam/testrepo
# Project shortname This should be a unique alphanumeric name to allow salt to act on the right state.
SHORTNAME=testrepo
#Project UUID you can find it with this curl -u '$USERNAME:$PASSWORD' "https://api.bitbucket.org/2.0/repositories/$FULLNMAE"
UUID={800736ea-fc3c-430b-8c26-8f3f81037e9c}
#Salt hook endpoint
SALTHOOK=https://$SALT:8000/hook # or similar
Setup webhooks
Bitbucket will notify salt via a webhook that a change has been made to a repo. I explicitly use the bitbucket/request resource to help target and allow more granular changes in the future. You can do this on any major state you prefer. I use an accepted merge here but you can find out all of your options at
https://confluence.atlassian.com/bitbucket/webhooks-resource-735642279.html Also note you may need to change SSL cert recognition for the created webhook if you have self-signed certs or certs bitbucket can’t find a trust chain for.
curl -u '$USERNAME:$PASSWORD' -s -d '{
"description" : "SaltPush",
"url" : "https://$SALTHOOK/bitbucket/request",
"events" : [
"pullrequest:fulfilled"
],
"active": "true" } ' https://api.bitbucket.org/2.0/repositories/$FULLNAME/hooks
Setup reactor config
You’ll need to add the following to your salt-master config to support the new bitbucket config
reactor:
- 'salt/netapi/hook/bitbucket/*':
- /etc/salt/reactor/bitbucket.sls
Restart your salt master and you’ll now have the ability to recognize the incoming bitbucket requests. Inside the bitbucket.sls you’ll need to drop in the following data. Modify the tgt command to match the nodes you need the state to run on in your environment.
{% set build = data.get('post', {}) %}
{% if build.repository.uuid == "$UUID" %}
pull_$SHORTNAME:
local.state.sls:
- tgt: 'I@gitrepos:$SHORTNAME and I@gitenv:{{ build.pullrequest.destination.branch.name }}'
- expr_form: compound
- arg:
- git.$SHORTNAME
{% endif %}
This file is the equivalant of all requests that match the repo $UUID run this command
salt -C 'I@gitrepos:$SHORTNAME and I@gitenv:{{ build.pullrequest.destination.branch.name }}' state.sls git.$SHORTNAME
Once you’ve added the sls file you should be ready to start deploying the state defined. If you have any troubles stop the master and minion on the target host and restart them in debug mode and look for issues.