openstack/openstack-ansible
Code Issues Proposed changes

Allow for skipping custom env.d file checks

Browse Source 
Currently if the env.d check fails and halts the upgrade, re-running
the run-upgrade.sh script doesn't pass the skip-tags flag to
Ansible.  This prompts the user to set the env variable if they want
to further skip checks and then passes the skip-tags as necessary.

Change-Id: Ic62887c7d8faa6a7a95021c012b1bf4f733edc33
This commit is contained in:
Antony Messerli 2019-04-23 16:22:06 -05:00
parent e837d2a8fa
commit 85981996c4
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
scripts/upgrade-utilities/deploy-config-changes.yml
View File

@ -56,9 +56,11 @@
layout in {{ repo_root_dir }}/inventory/env.d. The difference between these files layout in {{ repo_root_dir }}/inventory/env.d. The difference between these files
should be carefully reviewed to understand whether the changes are still necessary should be carefully reviewed to understand whether the changes are still necessary
and applicable to the environment. If all the user-space env.d files are necessary, and applicable to the environment. If all the user-space env.d files are necessary,
then please re-run this playbook with the CLI option '--skip-tags custom-envd-file-check'. then please export SKIP_CUSTOM_ENVD_CHECK=true and re-run the playbook or
run-upgrade.sh script.
when: when:
- _envd_dir_contents.matched > 0 - _envd_dir_contents.matched > 0
- not(lookup('env', 'SKIP_CUSTOM_ENVD_CHECK') | bool)
tags: tags:
- custom-envd-file-check - custom-envd-file-check