This message was deleted.

The only thing I got to work when I did this was to add the 2nd provider,

pulumi stack export

, search/replace all uess of 1st with 2nd,

pulumi stack import

, then remove 1st provider.

I was hoping to use a different provider for eks while running some deployments under ci/cd

Maybe you need two projects? Separate the EKS stuff out completely.

Fortunately it is in its own project, its deployments to a staging environment that I've automated in CI (within the cluster). The kubeconfig will be different between local deployments and deployments from CI. I'd like to be able to update the staging environment manually from time to time. As it stands with the kubeconfig differing, the deployment can only be managed by either CI or locally. I've just defaulted to entirely managed by CI for now, but would be nice to have a workaround for local updates at some point