Vivek Lakshmanan

https://github.com/pulumi/pulumi-aws/issues/2128 is another instance of this.

Note that if we support https://github.com/pulumi/pulumi-kubernetes-operator/issues/122 we will have to ensure the secret injection mechanism can mount secrets into the job/pod encapsulating the stack.

Breaking out the suggestion to use flux etc. from #50 here instead. Some possibilities here include integrating with https://fluxcd.io/docs/components/source/gitrepositories/. This could allow users to choose to install the [Flux Source...

An added benefit here is to leverage support for a variety of source control providers which have been known to cause problems with go-git - the library that the underlying...

Hi @UnP1u9 - thanks for opening the issue. Could you share a small repro code snippet? Could you also share any additional details from the error?

@tusharshahrs Could we break this issue up? For the first issue you mentioned, correct me if I am wrong, but is this in the context of aws-native? Our api docs...

@igordrnobrega sorry for not responding sooner. Are you sure your provider is fully updated to 3.22.1? Existing resources have an embedded link to their provider version. If this is on...

FWIW I just saw the same behavior in https://github.com/pulumi/pulumi-gcp/pull/900

Thanks for opening the issue. @stack72 thoughts on fixing the token here and adding an alias to avoid breaks?

We don't really call into kubectl in any way in the provider. But there might be authentication plugins configured in the kubeconfig that can assume interactive access. Curious if your...