@Ask Inkeep Is there a way to stop the "production" and "dev" environments from being auto-created when a new project is created?

Thanks for tagging me @Aden McCusker. I'll look through relevant sources and get back to you shortly.

Hey, thanks for reaching out ! It seems our team is a little busy right now, a human will be with you within the next hour or so. In the meantime, can I help you ?

Based on the available sources, I don't have information about a way to prevent the default "development" and "production" environments from being auto-created when a new project is created. (1) (2) The documentation confirms that creating a project auto-creates the default dev and prod environments, but doesn't describe a setting or API parameter to disable this behavior. (2) Check out these potentially useful sources: • Projects & Environments • Create a new Environment • Modeling and Implementation Components If you need this capability, I'd suggest reaching out via Email to confirm whether this is supported or to request it as a feature. Would you like me to try to answer this generally based on my knowledge instead?

It seems our team is a little busy right now, a human will be with you within the next hour or so. In the meantime, Feel free to chat with our AI Bot. If it is urgent, you can escalate to the team?

For context, I'm creating projects via the API, and this still happens. IMO the auto-creation of environments should be a convenience provided by the permit frontend - it should not happen at the API level.

If you are using the api you can change the initial environments created. The create project api accepts initial_environments in the body which defines the environments that will be created, please see the api reference for more info.