I'm trying to import an ESC environment I was doing this fine while still in the 'default' namespace...

gifted-gigabyte-53859

03/19/2025, 8:36 AM

I'm trying to import an ESC environment I was doing this fine while still in the 'default' namespace but it's not working the first time I try in this new setup after 'default' has been deprecated. It says invalid environment name. But the environment name is valid since I copied it from the environment itself Importing environments from 'default' works, but others don't. I've tried prefixing with different values

esc env ls

correctly lists all my environments including the new ones

gifted-gigabyte-53859

03/19/2025, 8:39 AM

Derp. Ok so apparently only one combination works, which is the one I didn't try.

Copy code

environment-name         <--- doesn't work
project/environment-name <--- works
org/project/environment. <--- doesn't work

stocky-restaurant-98004

03/19/2025, 2:09 PM

You'll want to get all your environments out of the default namespace as soon as it's convenient. It's deprecated, and the OIDC perms are different for project-based environments. Basically, if you clean that up, it'll make your life easier.

gifted-gigabyte-53859

03/21/2025, 4:39 AM

@stocky-restaurant-98004 how do I move an environment into a different namespace? Can't see any way of doing it Do I have to clone them?

stocky-restaurant-98004

03/21/2025, 2:06 PM

~~Yes.~~ I think so. I believe we did it that way to make sure your workloads keep operating.

3 Views

Open in Slack

Previous Next

Pulumi Community

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.