Closed qtzar closed 1 year ago
When using hierarchical identifiers with deployment groups it is possible to add a deployment node with no reference but doing so breaks the hierarchy and causes the nested elements to have a hierarchy reference of null.
DSL Included below to highlight the issue
No response
workspace { !identifiers hierarchical model { DEPLOY = deploymentEnvironment "Deployment" { deploymentNode "Node1"{ IN1 = infrastructureNode "Node1" IN2 = infrastructureNode "Node2" IN3 = infrastructureNode "Node3" } NODE2 = deploymentNode "Node2"{ IN1 = infrastructureNode "Node1" IN2 = infrastructureNode "Node2" IN3 = infrastructureNode "Node3" } null.IN1 -> null.IN2 null.IN2 -> null.IN3 DEPLOY.NODE2.IN1 -> DEPLOY.NODE2.IN2 DEPLOY.NODE2.IN2 -> DEPLOY.NODE2.IN3 } } views { deployment * DEPLOY { include * autolayout } } }
Minor
Low
I have no budget, please fix this for free
Description
When using hierarchical identifiers with deployment groups it is possible to add a deployment node with no reference but doing so breaks the hierarchy and causes the nested elements to have a hierarchy reference of null.
Steps to reproduce
DSL Included below to highlight the issue
Screenshot
No response
Code sample
Configuration
No response
Severity
Minor
Priority
Low
Resolution
I have no budget, please fix this for free
More information
No response