Resource Group Index
Resource groups need a psudo param that allows the nested/iterated templates to know their position.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Steve Baker
Related branches
Related bugs
Sprints
Whiteboard
For example, consider the following psudocode:
"Parameters": {
"BaseIp": {
Default: "10.0.101."
}
"Ip0": {
Default: "10"
}
"Ip1": {
Default: "11"
}
"Ip2": {
Default: "12"
}
}
"Resources": {
"0": {
"Properties": {
"Ip": { "Join": [ "", [ {"Ref": "BaseIP"}, {"Ref": "Ip0"}] }
...
}
},
"1": {
"Properties": {
"Ip": { "Join": [ "", [ {"Ref": "BaseIP"}, {"Ref": "Ip1"}] }
...
}
},
"2": {
"Properties": {
"Ip": { "Join": [ "", [ {"Ref": "BaseIP"}, {"Ref": "Ip2"}] }
...
}
}
}
With a Resource Group and a psudo param, you should be able to do something like:
"Resources": {
"configcluster": {
"type": "OS::Heat:
"properties": {
"count": 3,
"Ip": { "Join": [ "", [
}] }
...
}
}
-------
There seems to be a duplicate blueprint now:
https:/
Addressed by:
https:/
That seems to solve this.
s/{"Ref": "OS::ResourceGr
Work Items
Dependency tree
* Blueprints in grey have been implemented.
