Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
package-authoring
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Title
g
gorgeous-minister-41131
03/09/2023, 11:41 PMIs there a best practices when naming resources inside of a
ComponentResourceUntitled.cpp
For example, if I do not use the base_name as part of the resource_str of the child resources, I get a conflict when instantiating FooVpcComponent. Maybe this is by design and it's my responsibility to ensure this uniqueness?
Just thinking from Terraform, where these resources would be unique to the module scope... in Pulumi's case it seems like the ComponentResource's
nameI was thinking of putting the name for the super constructor of
f"foo:aws:FooVpcComponent:{name}"l
little-cartoon-10569
03/09/2023, 11:49 PMWhy do you need to change the type? So long as the name is always different, all should be good.
The type is constant for a ComponentReosurce. The name (1st parameter to the constructor) changes. All resources created within the ComponentResource must use that name (or something derived from it) as their name.
if I do not use the base_name as part of the resource_str of the child resources, I get a conflict when instantiating FooVpcComponent. Maybe this is by design and it's my responsibility to ensure this uniqueness?Exactly.
g
gorgeous-minister-41131
03/10/2023, 12:31 AMI do not need to change the type, I was just wondering if that was expected or I was just doing something else wrong. Thank you for the info
So my conclusion is that I need to still ensure uniqueness of the resource_str for child resources across all instances of the ComponentResource of the same name.
👍
BTW just following up here: I found way at the bottom of the Resource URNs documentation, a little excerpt on what I was asking and confirms this.
https://www.pulumi.com/docs/intro/concepts/resources/names/#urns
Resources constructed as children of a component resource should ensure their names are unique across multiple instances of the component resource. In general, the name of the component resource instance itself (the name parameter passed into the component resource constructor) should be used as part of the name of the child resources.:thank-you: