This message was deleted.

sparse-intern-71089

01/12/2021, 1:14 AM

This message was deleted.

little-cartoon-10569

01/12/2021, 1:20 AM

If you're ok with deleting the subnet this once, I'd consider removing the name from the subnet. You'll get this sort of problem if you name your resources.

little-cartoon-10569

01/12/2021, 1:20 AM

You could use namePrefix, or nothing (let Pulumi generate the name). If Pulumi can generate the name or name suffix, then this problem doesn't occur.

gentle-account-13294

01/12/2021, 6:46 PM

hmm.. we are specifying the

resource-name

quite a few places. In general would u consider that to be a bad practice then ? Also tagging a colleague @gifted-vase-28337

little-cartoon-10569

01/12/2021, 8:01 PM

Yes, I think so. Give Pulumi the broadest scope to "do its thing", including naming. https://www.pulumi.com/docs/intro/concepts/programming-model/#autonaming

gentle-account-13294

01/12/2021, 10:11 PM

Thank you !! that helps !!

gentle-account-13294

01/12/2021, 11:27 PM

As a follow up to above suggestion, is there a way to provide a custom prefix for

resource-name

little-cartoon-10569

01/12/2021, 11:34 PM

Depends on the resource. Many resources have a

namePrefix

input.

little-cartoon-10569

01/12/2021, 11:34 PM

Which resource are you looking at?

little-cartoon-10569

01/12/2021, 11:36 PM

Looks like

subnet

doesn't have a name or namePrefix, just tags... 😞

little-cartoon-10569

01/12/2021, 11:38 PM

But resources including IAM Roles, RDS SubnetGroups and ALB TargetGroups all support namePrefix.

✅ 1

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.