This message was deleted.

Hi @incalculable-dream-27508, can you please thread your messages to make it easier for others to follow and not interfere with other conversations? https://slack.com/help/articles/115000769927-Use-threads-to-organize-discussions-

Certainly, apologies.

Can you share a more complete version of your code? I'm not a Python-person, so I'm having trouble following what you're resources look like and what you're trying to achieve.

i'll share code in a bit, since I'm bulldozing parts of it right now. But what I'm trying to do and why: I'm operating on two completely independent OpenStack clusters. For sake of simplicity let's just say that I'm creating one machine ("in the

API

category") on each, and they need to be able to reach a set of ports on each other. • ✔️ I have unique names generated for the machines, containing a number if I wanted to create more of them, and DC/region they're created in • ✅ I'm right now figuring out proper naming of security groups, to have them uniquely named inside pulumi, yet be able to tell the created machines what set of security groups they should have • ❓ Next I need to add a set of security group rules to a security group, configuring access from IPs of all created instances to port A, then port B, then port C. Each of those rules needs to have a unique name inside pulumi. So I thought I'll just use things like region, port, and machine name inside the internal identifier, and that will be unique. Except it turns out that while I can use

instance.access_ip_v4

inside the security rule for what IP it is to allow, when I try to use

instance.name

inside the name/identifier of the resource, I end up with stuff like

<pulumi.output.Output object at 0x7ca295360fa0>