Alex Schultz 1f9942fd75 Always clear cached facts first ... Because you could be running against different clouds or hosts, we need to always clear the facts at the start of the deployment playbook to ensure we aren't using incorrectly cached facts. That being said, the caching mechanism should persist between the plays in the overall deployment. Change-Id: I5992edf43bf1995eebdf401c6bd886e77e528695 Closes-Bug: #1884654		2020-07-05 20:20:49 +00:00
..
services	Add global groupvar to set the ansible async dir	2020-01-29 10:10:48 -06:00
container-puppet.sh	Exclude /etc/hostname	2020-06-29 13:43:11 -06:00
container_startup_configs_tasks.yaml	Cleanup all container startup configs before generating the new ones	2020-07-02 21:04:07 +00:00
deploy-steps-playbooks-common.yaml	Always clear cached facts first	2020-07-05 20:20:49 +00:00
deploy-steps-tasks-step-0.j2.yaml	Deprecate EnablePaunch and remove Paunch support	2020-06-03 17:53:40 +00:00
deploy-steps-tasks-step-1.yaml	deploy-steps-tasks-step-1: update startup-configs with latest hashes	2020-04-17 15:54:28 +00:00
deploy-steps-tasks.yaml	Deprecate EnablePaunch and remove Paunch support	2020-06-03 17:53:40 +00:00
deploy-steps.j2	Collapse deploy steps	2020-07-03 13:12:31 +00:00
generate-config-tasks.yaml	Deprecate EnablePaunch and remove Paunch support	2020-06-03 17:53:40 +00:00
hiera-steps-tasks.yaml	Add ansible hieradata file	2020-04-24 19:02:06 +00:00
host-container-puppet-tasks.yaml	Deprecate EnablePaunch and remove Paunch support	2020-06-03 17:53:40 +00:00
post.j2.yaml	Consolidate puppet/docker deployments with one deploy steps workflow	2017-08-11 17:25:02 +00:00