Vivek Lakshmanan

Thanks for the suggestion. I have added this to our backlog to discuss.

@ghostsquad it might be more interesting to understand how you would like some of these features to fit together for your use case. It appears you are trying to leverage...

Thanks for opening the issue. I have added this to our backlog to consider.

@joffreychambrin Thanks for opening the issue. This is interesting. I am not entirely sure how the replication config is being recorded in the state for a bucket when it is...

@omninonsense thanks for the great repro! Would you please consider upgrading your provider to 3.19.4 and double checking it is actually being used? 1. Remove the `pulumi:disable-default-providers` setting 2. Run...

@omninonsense ah so this is failing with an empty/brand new stack?

Confirmed this is happening without disabling default kubernetes provider - you just need to use `ConfigFile` on the non-default provider. The problem seems to be that the invoke to `kubernetes:yaml:decode`...

Investigating further - it is indeed the case that the invoke never actually makes it to the underlying provider. The issue in my repro was that if the underlying kubernetes...

A hacky workaround for now would be to either: 1. Run the pulumi up with `--skip-preview` 2. Move the ConfigFile resource into an apply block wrapping the unknown configuration options...

> Short term we could error out the invoke if the provider was unknown? That's probably a better error than returning undef. @Frassle apologies I dropped the ball on following...