39321cca71
We inherit the `prepare` commands from deploy, in Rocky we will automatically get config-download env file there so no need to explicitly disable DeploymentSteps in *-prepare.yaml files too. We should also disable the WorkflowSteps in config-download environment, as they too aren't meant to be used with config-download. Similarly, for `converge` commands in the *-converge.yaml files we shouldn't re-enable the DeploymentSteps and WorkflowSteps, as that would go against using config-download. Change-Id: I89f54ba9a0a15afd26da4d4b26aba8ef09ebf04b
15 lines
586 B
YAML
15 lines
586 B
YAML
# DEPRECATED: these mappings are now the default in
|
|
# overcloud-resource-registry-puppet.j2.yaml. This environment file will be
|
|
# removed during the Stein release.
|
|
resource_registry:
|
|
OS::TripleO::SoftwareDeployment: ../config-download-structured.yaml
|
|
|
|
OS::Heat::SoftwareDeployment: ../config-download-software.yaml
|
|
OS::Heat::StructuredDeployment: ../config-download-structured.yaml
|
|
|
|
OS::TripleO::DeploymentSteps: OS::Heat::None
|
|
OS::TripleO::WorkflowSteps: OS::Heat::None
|
|
|
|
OS::TripleO::Ssh::KnownHostsDeployment: OS::Heat::None
|
|
OS::TripleO::Ssh::HostPubKey: OS::Heat::None
|