resource validation fail due to dependency
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Vijendar Komalla |
Bug Description
resource/property validation fails if a resource depends on other resource. For example, template given below results in stack creation failure with following error message
"ERROR: Property error : service_db: users Property error : users: 0 Property error : 0: password "" does not match pattern "[a-zA-
Below given is an example template to reproduce the problem:
resources:
database_
type: "OS::Heat:
properties:
length: 16
sequence: lettersdigits
service_db:
type: OS::Trove::Instance
properties:
name: app_db
flavor: { get_param: db_flavor }
size: { get_param: db_size }
databases:
- name: app_data
users:
- name: { get_param: db_user }
password: { get_attr: [database_password, value] }
databases: [ app_data ]
Changed in heat: | |
assignee: | nobody → Vijendar Komalla (vijendar-komalla) |
description: | updated |
Changed in heat: | |
status: | New → In Progress |
Changed in heat: | |
importance: | Undecided → High |
Changed in heat: | |
assignee: | Vijendar Komalla (vijendar-komalla) → Clint Byrum (clint-fewbar) |
Changed in heat: | |
assignee: | Clint Byrum (clint-fewbar) → Vijendar Komalla (vijendar-komalla) |
Changed in heat: | |
milestone: | none → juno-3 |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | juno-3 → 2014.2 |
As we discussed, maybe this can be solved by a new concept of property dependencies (on other resources). Then, validation can only be done if the property has no dependencies. Sounds tricky to implement though.