Jiri Stransky 6d9560e177 Respect tags in upgrade tasks ... There seems to be a difference between how include_tasks and import_tasks work. `include_tasks` applies properties on the inclusion itself, and if we want to apply something on the included tasks, we need to use `apply` dict. We previously had to add `always` tag onto `include_tasks` to make the inclusion happen when we ran upgrade with `--tags`. `import_tasks`, on the other hand, is processed more like a block than an individual task, and all its properties get applied on the tasks inside. This meant that the `always` tag got applied on all tags in the upgrade playbook, instead of on the import itself, which broke use of tags in `upgrade_tasks`. This is now fixed by removing the tags from `import_tasks`. The import should happen always regardless if there are any `tags` on the import. Change-Id: I66a4ed99f9e0cc199899494813073b4a085d99e7 Closes-Bug: #1830892		2019-05-30 07:35:27 +00:00
..
services	Introduce scale_tasks	2019-04-24 11:07:53 -04:00
container-puppet.py	Gracefully handle empty config json data	2019-05-08 14:33:06 -06:00
deploy-steps-tasks.yaml	Evaluating ansible_check_mode as a boolean	2019-04-17 16:55:40 -04:00
deploy-steps.j2	Respect tags in upgrade tasks	2019-05-30 07:35:27 +00:00
post.j2.yaml	Consolidate puppet/docker deployments with one deploy steps workflow	2017-08-11 17:25:02 +00:00