Closed ghost closed 8 years ago
This is going to be a bit painful to update but definitely for the best. @vkurup @dpoirier do you have any strong objection? This would enable us to get back to easy branch deployments as @rebecca-caktus has already proven on Hosted Tracpro.
Maybe mention this in the developer docs, with a link to https://docs.saltstack.com/en/latest/topics/tutorials/pillar.html#setting-pillar-data-on-the-command-line and an example of using it to override the branch name on the fab command line?
I made a couple of comments but like the idea overall.
Interesting note: an alternative to this change would be to change the pillar merging strategy: https://docs.saltstack.com/en/latest/ref/configuration/master.html#pillar-source-merging-strategy
See changes here: https://github.com/caktus/django-project-template/pull/251
@dpoirier This is ready for re-review.
Let's update http://caktus.github.io/developer-documentation/margarita/states.html#project-repo along with this.
@dpoirier Updated.
Related pulls: https://github.com/caktus/developer-documentation/pull/44 https://github.com/caktus/django-project-template/pull/251
:+1:
There's a nifty command line trick for salt to pass in pillar data. If we break apart this pillar then we can easily override the branch in the
deploy
Fabric command.See also: https://github.com/caktus/django-project-template/pull/251 https://github.com/caktus/developer-documentation/pull/44