807b09d6a6
- Differentiate between resource references that have no ID (i.e. because the referenced resource is not a CustomResource) and resource references that have IDs that are not known. This is necessary for proper backwards-compatible serialization of resource references. - Fix the key that stores a resource reference's package version in the .NET, NodeJS, and Python SDKs. - Ensure that the resource monitor's marshalling/unmarshalling of inputs and outputs to/from calls to `Construct` retain resource references as appropriate. - Fix serialization behavior for resources -> resource references in the Go SDK: if a resource's ID is unknown, it should still be serialized as a resource reference, albeit a reference with an unknown ID. |
||
|---|---|---|
| .. | ||
| pulumi | ||
| test | ||
| test_with_mocks | ||
| setup.py | ||