Boundaries with same name are grouping together

[mikicho]

I'm not sure if it's by intent or not, but if I have two boundaries with the same name the components rendered into one boundary.
i.e:

dbVpc = Boundary("VPC")
serviceVpc = Boundary("VPC")

...

db = Datastore("Postgres Aurora")
db.inBoundary = dbVpc
server = Server("Server")
server.inBoundary = serviceVpc

Generates the following:

[lfservin]

That might be more of a graphviz problem. Have you looked at the dfd output? does the dot command complain about something?

[redshiftzero]

hmm I just ran into this too, it looks like what is happening is that the truncated hashes used as the node ID for graphviz (e.g. fedfcbcecdeaaeefcdaefdb) are derived only from the name (see the _uniq_name() function). As such, if the names are equal, the hashes will collide, and graphviz will then only render a single instance of the node.

Here's a self-contained reproducer:

#!/usr/bin/env python3
from pytm.pytm import Actor, Boundary, TM, Server

tm = TM("test")
tm.description = "test"

server_rack = Boundary("bar")

app_server = Server("foo")
app_server.inBoundary = server_rack

mon_server = Server("foo")
mon_server.inBoundary = server_rack

admin = Actor("beep")
admin.inBoundary = server_rack

tm.process()

Even though there are two Server objects called foo, only one renders: