production environment created by default and can't be removed or renamed

[Clasyc]

I really struggle to understand why this decision was made from a UX perspective. Why is a new environment called production created by default when setting up a new project? I'm forced to use it, and I can't rename or delete it (using UI only).

I firmly believe users should have the freedom to decide what their environments are called, and none should be enforced.

[Clasyc]

When trying to delete the production environment via the API, I receive this error:

{"message":"You cannot delete the production environment","code":"BAD_REQUEST"}

However, I found a workaround: if I use POST /environment.update to rename the production environment, I can then delete it successfully.

This suggests the validation is only checking the environment name rather than using a dedicated property flag. If the environment is meant to be protected, the system should use a specific property (like isProtected or isPermanent) instead of relying on the name field. This would prevent the workaround and ensure proper enforcement of the protection rule.

[Siumauricio]

Thank you for the report I created a issue, this will be fixed in the next version #3216