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.

Pulumi Community

I’m not sure there’s actually an issue here. The type `"aws:lb:ApplicationLoadBalancer"` is a bit confusing, but that should be the component resource you’re creating (which you are creating)

The component resources themselves are resources, so they need to be represented in the stack

That’s what all the `awsx:x` resources are and I’m not sure why the naming convention for <https://github.com/pulumi/pulumi-awsx/blob/ac937595322bf1560b67598a612b4374253cd6aa/nodejs/awsx/lb/application.ts#L54> chose to use the `aws:lb` namespace

If it were to actually create the cloud resource, you’d see:
```+   ├─ aws:lb:ApplicationLoadBalancer  test                   create     
 +   │  └─ aws:lb:LoadBalancer          test                   create```
Where the first item is the component resource and the second item is the actual load balancer

Oh. I thought that the stuff it was creating was AWS infrastructure. But instead it's some kind of Pulumi state?

So you're saying there's no actual bug here and I should just let that stuff get created?  Do I need to worry that I have already created Pulumi objects for this stuff in my general infra project and am now creating a second instance of Pulumi objects in this app server project?

I sent a PR to fix the namespace issue because that was indeed confusing me: <https://github.com/pulumi/pulumi-awsx/pull/557>

You can think of those Pulumi objects as simply stack state for tracking things, so I wouldn’t worry about the creation of those projects.

Ok. How can I tell if it's going to create AWS infra that I should pay closer attention to?

The resource types are unique — in the example I had above, the actual AWS load balancer is called `aws:lb:LoadBalancer` — in general, `awsx` _shouldn’t_ have `aws:` with the exception unfortunately being `aws:lb:ApplicationLoadBalancer`

(at least from what I can see in a quick code search on that package)