damp-airline-3844201/03/2024, 11:46 PM
). The fixes are related to component option propagation, i.e. how options such as
are used by
The gist is that the logic is being standardized across each of the language SDKs, with respect to how the options are set on the child resources based on the provided options. For example. in some SDKs, the
option was ignored. Another example is how
would be erroneously propagated to the children.
Most programs will be unaffected by these fixes, however there's one case where a replacement might occur. In the dotnet SDK, the
resource was erroneously setting the child's parent to that of the
itself (see issue). Same is true for
resource. This is now fixed, and Pulumi will automatically fix the parenting relationship, without causing replacement.
There is one edge case where replacement would still occur, that's if the provider is different between the
and its parent.
If you're using the dotnet SDK: to prepare for this change, please review any usage of
, and, if
option is used directly, be aware that the child resources may be replaced to have the correct parent.
See the PRs for more details:
• #2709 Component option propagation (Go SDK)
• #2713 Component option propagation (NodeJS SDK)
• #2717 Component option propagation (Python SDK)
• #2720 Component option propagation (.NET SDK)
Thanks and feel free to reach out if you have questions!