-
-
Notifications
You must be signed in to change notification settings - Fork 318
-
Description
Relations may or may not exists depending on factors like deployment environment.
For example, in case od load balancing:
- In VM environment, VM may include software load balancer
- In Kubernertes, client will use Kubernetes Service, which is stand-alone entity.
It is also needed for re-arhitecting projects where compnents may be removed od replaced and one want to show both states.
Only way that I am aware of is to create as superset of relations in the model, and then to exclude them one-by-one, which is time-consuming and error prone.
Priority
Low (I have no budget and there's no rush, please add this feature for free)
More information
No response
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 2 comments 1 reply
-
It would be much simpler to just add tags to relations while designing the model and filter them by tags later on.
Beta Was this translation helpful? Give feedback.
All reactions
-
I don't think I understand what you are after from your post above, but maybe this helps?
e g
container springPetClinic "All_Containers_tag1_expectation2" {
include "element.tag==tag1"
exclude * -> *
include "relationship.tag==tag1"
autoLayout
}
(Just browsing after some solutions today, this caught my eye)
Beta Was this translation helpful? Give feedback.
All reactions
-
May solve
structurizr/dsl#303
structurizr/dsl#306
Beta Was this translation helpful? Give feedback.