Skip to content

Filter relations by tags #405

@zeljkot

Description

@zeljkot

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions