5c0b62e1aa
As it stands, we serialize more than is correct when registering resources: in addition to serializing the RegisterResource RPC, we also wait for input properties to resolve in the same context. Unfortunately, this means that we can create cycles in the promise graph when a resource A is constructed in an earlier turn than some resource B and one of B's output properties is an input to resource A. These changes fix this issue by allowing input properties to resolve *before* serializing the RegisterResource RPC. Some integration tests had taken a dependency on the ordering of resources in either the output of the `pulumi` command or the checkpoint file. The only test that took a dependency on command output was updated s.t. its resources have exactly one legal topographical sort (and therefore their ordering is deterministic). The other tests were updated s.t. their validation did not depend on resource ordering. |
||
|---|---|---|
| .. | ||
| nodejs | ||
| proto | ||
| README.md | ||