You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Container instances behave as described in the documentation. Although not explicitly mentioned in that section of the documentation, it’s also possible to place software system instances within a deployment node.
I’ve observed the following behavior when using the snippet below:
deployment softwareSystemName deploymentEnvironmentName {
include *
autolayout lr
}
The software system referenced by name does not appear in the diagram. Its containers, components, and relationships with other elements are also absent.
All other software system instances are included along with their direct and implied relationships.
This was confusing at first, especially since I wasn’t yet familiar with how deployment views are intended to be used.
Would it be possible to document this behavior or adjust the logic so that the referenced software system is also included in the resulting diagram? Either of those would have been very helpful for a newcomer like me. If a change is considered, perhaps the behavior for non-referenced software system instances should be updated to align with how container instances are handled?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Container instances behave as described in the documentation. Although not explicitly mentioned in that section of the documentation, it’s also possible to place software system instances within a deployment node.
I’ve observed the following behavior when using the snippet below:
This was confusing at first, especially since I wasn’t yet familiar with how deployment views are intended to be used.
Would it be possible to document this behavior or adjust the logic so that the referenced software system is also included in the resulting diagram? Either of those would have been very helpful for a newcomer like me. If a change is considered, perhaps the behavior for non-referenced software system instances should be updated to align with how container instances are handled?
Beta Was this translation helpful? Give feedback.
All reactions