Since https://github.com/openstack/heat/commit/8a56cafe2b99b39d1ad5705b9ad1a85b4781f76e we validate that the server id is correct for various resources, and in particular SoftwareDeployment now validates the server property.
This works OK when the deployment and server exist in the same stack, but in the event you want to abstract the server configuration by putting SoftwareDeployment(s) into a provider template, we eagerly validate and fail because prior to creating the provider resource, the server doesn't exist so the default resource name is passed instead.
This is breaking a pattern TripleO wish to adopt where SoftwareConfig and SoftwareDeployment resources are abstracted via provider templates to enable alternate impementations to be easily substituted.
Reproducer:
$ cat example-script-provider.yaml
heat_template_version: 2013-05-23
parameters:
key_name:
type: string
default: default
flavor:
type: string
default: m1.small
image:
type: string
default: fedora-software-config
resources:
config:
type: My::Config
properties:
server: {get_resource: server}
server:
type: OS::Nova::Server
properties:
image: {get_param: image}
flavor: {get_param: flavor}
key_name: {get_param: key_name}
user_data_format: SOFTWARE_CONFIG
$ cat example-script-env.yaml
resource_registry:
My::Config: example-script-config.yaml
$ cat example-script-config.yaml
heat_template_version: 2013-05-23
parameters:
server:
type: string
resources:
config:
type: OS::Heat::SoftwareConfig
properties:
group: script
inputs:
- name: foo
- name: bar
outputs:
- name: result
config:
get_file: config-scripts/example-script.sh
deployment:
type: OS::Heat::SoftwareDeployment
properties:
config:
get_resource: config
server:
get_param: server
input_values:
foo: fooooo2
bar: baaaaa34
$ heat stack-create sc2 -f example-script-provider.yaml -e example-script-env.yaml
ERROR: Failed to validate: Property error : deployment: server Error validating value u'server': The server (server) could not be found.
Fix proposed to branch: master
Review: https:/