First of all, this is currently not supported as is so I’ll push this as a feature request to our product board.
For your remote/staging environment, I think you could be able to achieve this in an automated context using our CLI by creating/dropping environment with forest environments commands (You can get more infos on the github repository)
For your production environment … The only workaround I can think of would be to promote a new production each time you want to rotate your forest env secret (You should see a switch production button in your environment settings, documentation is available here).
I’m switching the topic to product suggestion and pushing it to our product board, as I understand that this will be a manual solution.
Having process parity between production and staging is a requirement for being able to do relevant rehearsals. Is there a way to promote environments to pre-prod ones? I’m not sure if it makes sense as I don’t know what an environment being tagged as “production” on Forest entails.
In the meantime, what is process to make sure the new production environment is the exact same for our users once promoted?
Create new-production environment targeting the same URL as the previous one
Copy layout from production to new-production
Promote
Would these steps guarantee the parity of this new environment?
Hi @leo_elevo, when you create a new environment (new-production), it’ll inherit automatically from the UI of your previous production. No need to do a copy layout with our new development workflow
I’m trying to achieve the same as leo_elevo, rotate the env secret for a given environment.
I understand that I can create new environments, but it seems the new environment is a blank canvas with no role permissions set and I would like to keep exactly the same permissions that I currently have on the existing environment without having to re-configure them one by one manually. Do you have any suggestions how to achieve this with the least amount of manual work?
