64696b42b8
Do not return the inputs as the state for update previews that use an unconfigured provider. Returning the inputs as the state allows the language SDKs to incorrectly treat unknown properties as known (because we can't call `Update` on an unconfigured provider, we can't know which properties are unknown). Users can re-enable the existing behavior by setting the `PULUMI_LEGACY_PROVIDER_PREVIEW` environment variable to a truthy value (e.g. `1`, `true`, etc.). Most users will be unaffected by these changes. The most common programs that may be affected are those that combine the creation of a managed Kubernetes cluster with the deployment of applications to that cluster. These programs generally need to configure a k8s provider instance by constructing a kubeconfig from the output of the managed k8s cluster. Any changes to the cluster that cause the kubeconfig to be unknown then cause the provider to go unconfigured at runtime. Prior to these changes, resources managed by the k8s provider would have some known outputs in this scenario, as the engine would treat the resource's input values as its output values. After these changes, the resource's outputs will be treated as unknown. The most frequent affect that this has is that applies/stack outputs that depend on the outputs of a k8s resource managed by a provider with an unknown kubeconfig will not run/be displayed as `output`s during previews, respectively. We might be able to improve on this by taking advantage of schema information and filling in unknown values for properties that do not exist in the inputs. Fixes #7521. Co-authored-by: Justin Van Patten <jvp@justinvp.com> Co-authored-by: Luke Hoban <luke@pulumi.com> |
||
|---|---|---|
| .. | ||
| dotnet | ||
| go | ||
| nodejs | ||
| proto | ||
| python | ||
| go.mod | ||
| go.sum | ||
| README.md | ||