Jean-Philippe Evrard 50f3fd6df7 Ensure the user_secrets file is updated ... We shouldn't allow any arbitrary secret file to be updated in the leap process, but instead ensuring the file present in J/K/L will be properly updated to the end of the process. If you had set the variable in those playbooks, you would naturally CREATE a new file, alongside the existing user_secrets, with the risks of: - Having different values - Having precedence issues depending on the file name Change-Id: I2873318e2f1fd34673e95f8eb77a0001d649df1e		2017-08-31 09:27:55 +00:00
..
ansible_fact_cleanup-newton.yml	Added leap upgrade tooling	2017-02-01 14:27:07 +00:00
aodh-api-init-delete.yml	Added leap upgrade tooling	2017-02-01 14:27:07 +00:00
ceilometer-api-init-delete.yml	Added leap upgrade tooling	2017-02-01 14:27:07 +00:00
deploy-config-changes-newton.yml	Added leap upgrade tooling	2017-02-01 14:27:07 +00:00
galera-cluster-rolling-restart.yml	Added leap upgrade tooling	2017-02-01 14:27:07 +00:00
lbaas-version-check.yml	Update URLs in documents according to document migration	2017-07-14 13:54:50 +08:00
memcached-flush.yml	Added leap upgrade tooling	2017-02-01 14:27:07 +00:00
old-hostname-compatibility-newton.yml	Added leap upgrade tooling	2017-02-01 14:27:07 +00:00
user-secrets-adjustment-newton.yml	Ensure the user_secrets file is updated	2017-08-31 09:27:55 +00:00