Thank you so much for the comment. and I agree with you regarding modern folders. I have the same experience when it comes to these, as many do not either use, or do not really know the impact it can bring in to organizing and managing automations.
Regarding the question:
Going back to the same post, I would still stick with the answer I gave previously, which is to have separate Orchestrator instances for Dev, Test, and Prod.
I know, the features the modern folders have now, we could do the same thing in the same instance. But, when it comes to environment management, there are few things that we need to think…
- How we are to manage updates
- Disaster recovery
- Separation from development
– there could be many more…
When it comes to development environments, usually things are messy. We change many things time to time, configure stuff, upload and test processes, delete… (basically we do everything possible)
In production, we need to have proper control, and less involvement from different people unless its really needed.
We could do this in the same instance using modern folders… Agree… but, when it comes to system updates, if we are to upgrade the Orchestrator version, we are affecting all three environments at the same time. And this may end up with consequences that we wouldn’t even know and take time to resolve.
So its always safe to have separate instances for different environments like dev, test and prod.
However, this is also depending on the budget…
To add more, I do really recommend using modern folders and its features to properly organize and separate the automation solutions we have between different organizational units…
Also with the latest feature that enables to publish packages to different folders, really help people to organize the solutions and make them more secure and specific.