From 9ce99ce5617116b76843dfb67b137e0e83b12dde Mon Sep 17 00:00:00 2001 From: Steven Hardy Date: Wed, 15 Nov 2017 14:59:08 +0000 Subject: [PATCH] Add noop-deploy-steps.yaml environment The I2c12255fce11a8f6976fe5afc76357446c1e32aa patch adds an option to disable deploy steps, but with hard-coded resources in tripleoclient. This instead provides an environment file, which can be modified for each version as the resource interfaces evolve and/or be backported to old versions where we need this functionality, e.g for fast-forward upgrades Change-Id: Iff19de020e6cc7f3eee9a0b8091454d71dc7f889 --- environments/noop-deploy-steps.yaml | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 environments/noop-deploy-steps.yaml diff --git a/environments/noop-deploy-steps.yaml b/environments/noop-deploy-steps.yaml new file mode 100644 index 0000000000..8a5c0dfbab --- /dev/null +++ b/environments/noop-deploy-steps.yaml @@ -0,0 +1,6 @@ +# Disable deploy steps, useful for upgrades where we want to disable +# deploy steps and run them for each role manually +resource_registry: + OS::TripleO::DeploymentSteps: OS::Heat::None + OS::TripleO::Tasks::*PreConfig: OS::Heat::None + OS::TripleO::Tasks::*PostConfig: OS::Heat::None