Imagefactory is now deployed on prod-machine, as well as on the dev machine. Prod and stg take images from prod, dev keeps to itself.
For the prod(/stg) master branch of the tools repo is used, develop for dev.
tflink | |
mkrizek |
Imagefactory is now deployed on prod-machine, as well as on the dev machine. Prod and stg take images from prod, dev keeps to itself.
For the prod(/stg) master branch of the tools repo is used, develop for dev.
None, as it goes with ansible..
Lint Skipped |
Unit Tests Skipped |
Looks good, one suggestion though.
roles/taskotron/imagefactory-client/tasks/main.yml | ||
---|---|---|
16 | You can put the branch name into variable and avoid having separate tasks for dev and stg/prod, no? Unless you are expecting more differences. |
I'll echo @mkrizek's suggestion to make the branch a variable unless you're expecting it to always be develop but otherwise, looks good to me
I'll rephrase a little bit.
Unless there are other differences you expect between dev and stg/prod, please use a variable instead of conditionals in the tasks file
Just realized that one more thing is needed, in playbooks/groups/taskotron-client-hosts.yml there is a line:
- { role: taskotron/imagefactory-client, tags: ['imagefactoryclient'], when: deployment_type == 'dev' }
The condition needs to be removed.
note that change to taskotron.yaml will be needed in order to actually enable using the images built by imagefactory on prod/stg, but I'd rather do this in a second step, after we successfully build the ones currently needed
Yeah, I'll be changing taskotron.yaml when updating to the latest libtaskotron on stg and prod anyway.
ACK
You can put the branch name into variable and avoid having separate tasks for dev and stg/prod, no? Unless you are expecting more differences.