mirror of https://github.com/pulumi/pulumi.git
fbf13ec4d7
In our existing code, we only use the input state for old and new properties. This is incorrect and I'm astonished we've been flying blind for so long here. Some resources require the output properties from the prior operation in order to perform updates. Interestingly, we did correclty use the full synthesized state during deletes. I ran into this with the AWS Cloudfront Distribution resource, which requires the etag from the prior operation in order to successfully apply any subsequent operations. |
||
|---|---|---|
| .. | ||
| config | ||
| deploy | ||
| idl | ||
| plugin | ||
| provider | ||
| stack | ||
| testdata | ||
| asset.go | ||
| asset_test.go | ||
| errors.go | ||
| properties.go | ||
| properties_diff.go | ||
| properties_diff_test.go | ||
| properties_test.go | ||
| resource_goal.go | ||
| resource_id.go | ||
| resource_id_test.go | ||
| resource_state.go | ||
| status.go | ||
| urn.go | ||
| urn_test.go | ||