No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

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

not sure whether stack imports would be too feasible on an automated process like this

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