Justin Van Patten

> A customer did it like above, but has a stack with 2 default providers: What language are they using? What's the version of the SDK? What version of Pulumi...

Sorry for the trouble @snebjorn. Thanks for opening the issue. This looks like an issue with AWSX (or potentially the docker provider). Transferring this to the AWSX repo and someone...

I can repro the same error with a TypeScript program (without involving MLCs or AWSx): ```typescript import * as pulumi from "@pulumi/pulumi"; import * as aws from "@pulumi/aws"; const config:...

The reason the invoke returns an empty object is because of [this](https://github.com/pulumi/pulumi/blob/184e579e54554a4cb3f41f82cbeebd64f033315a/sdk/go/common/resource/plugin/provider_plugin.go#L1316-L1319): ```go // If the provider is not fully configured, return an empty property map. if !p.cfgknown { return...

Looks like #16897 didn't fully address the flakiness.

From inside a generated SDK: if a function returns a sensitive value, would we make the non-Output variant error, pointing to the Output variant? Or emit a warning, but still...

> We should likely have at least one internal retry to address intermittent connection issues in CI, as users can experience these just as we do. A retry in the...

@Defman, thanks for opening the issue and sorry for the trouble. Did you originally get an error during the second `pulumi up` or was it only after running the `pulumi...

So the idea is that we'd have some standard global way of saying "suppress provider deprecation warnings" and a provider would interpret that how it wants? In the case of...

Just a quick update: We're working towards a fix that doesn't involve doing the "empty" import update, so that the stack's update history remains clean.