This message was deleted.

btw.

pulumi up --skip-preview

works without error

Are all your inputs known for the resource where this occurs (as in the issue you linked) or are there inputs flowing from other resources?

I tracked down the problematic property and it's derived from another resource. I'm not 100% sure, because there is more code involved, but I think my problem comes from following code construct I use to get the name of a custom resource which is created from a CRD generated by crd2pulumi:

customResource.metadata.apply(m => { return pulumi.output(m!.name!)})

Is there a better way to get the generated name from a custom resource which is created from a CRD generated by crd2pulumi? (I know

resource.metadata.name

works for "normal" kubernetes resources but this doesn't work for crd2pulumi resources.)

The above looks like a bug in the way the tool works where it’s not using the correct output type definition for the outputs. But that should be an issue with type definitions and not actual execution. I would still expect you to be able to retrieve the actual value.