Ian Wahbe
Ian Wahbe
Ideally, this would disable both checks for new downloads and downloads themselves.
Adding a 👍 to the top issue is a great way to get the issue prioritized.
Hi @Navigatron. I'm sorry you're having issues here. Refresh should not hang in any circumstance. Until I figure out otherwise, I'm assuming that the hang is an error in this...
I believe the current panic is caused by a bug in pulumi-go-provider's GetSchema. I'll open a PR later to today to fix it. Looks like `p.GetSchema` was a function that...
The panic should be fixed when https://github.com/pulumi/pulumi-go-provider/pull/422 merges.
This is related to https://github.com/pulumi/pulumi-aws/issues/3149. In that case, the provider needs to read a new `config` for refresh, but since refresh uses the provider in state, this is currently impossible.
My application is robust to it, but it still feels like a bug. I'll move to pulumi/pulumi and re-open. Even weirder, this doesn't happen for all providers.
Since the failure is during a `pulumi up --refresh`, I'm guessing the failure is due to the new diff behavior.
I just checked, and it seems like upstream's behavior has improved radically here. Retrying on the latest version of hashicorp/aws, this now works (with `terraform apply -refresh=false`): ```hcl terraform {...
> [@iwahbe](https://github.com/iwahbe) maybe I missed a step but I'm struggling to repro this. But I did have a thought looking at the error. > > ``` > fetching plugin from...