Closed deinspanjer closed 1 year ago
There are two problems here:
staff
before it's been created (as always, order is important with the DSL).staff.vpn
inside the deployment node dc
, which doesn't exist. prod.staff.vpn
will work though.Urgh. that first issue was purely a mistake on my part. My original example had staff at the top and the problem was the same.
I think your second point is the source of my issue. I thought that it would look for items that were at the top level of the environment. I should have tested referencing the environment itself. :/
I’ve hit something that feels like a bug to me. If I try to make a forward or backward relationship inside a container instance or an infrastructure node, I get a syntax error saying the far-end node doesn’t exist. However, if I put the relationship outside the creation, it works fine. The docs say that both containerInstance and infrastructureNode blocks allow relationships as children, so I’m not sure what’s going on exactly. Here is an example DSL that demonstrates the problem. You can flip the commented lines to see it work properly.