mirror of https://github.com/pulumi/pulumi.git
7b57041780
We currently try calculating auto-naming strategy even for component resources, which doesn't make much sense. It turns out components can have type tokens of arbitrary shape (i.e. not necessarily `package:module:name` but can be anything), which trips our autonaming calculation expectations. The PR dodges that problem by (correctly) not calculating any autonaming strategy for component resources, only for custom resources. An integration test creates a component resource with an unusual type token and makes sure the deployment goes well and component URN is what we expect (there is no `name` property). Resolve https://github.com/pulumi/pulumi/issues/18499 |
||
|---|---|---|
| .. | ||
| Pulumi.yaml | ||
| index.ts | ||
| package.json | ||