Forum Discussion
Minimizing Production Pipeline Migration
Generally when you start using Deployment Pipelines, your existing space becomes Production so no URLs and bookmarks are lost. Then you have a one time opportunity to deploy backwards to Test, and again to Dev. Then you start working in DEV going forward.
If you created a new Production environment, then no, you cannot migrate the URLs. They are tied to the workspace. If you are new to this, you could remove the deployment pipeline and start over using the method above (make it Prod, deploy backwards to create Test and Dev). If that isn't feasable anymore, then your users will need to do a one time migration to new URLs.
Security is another reason. You cannot migrate that, so you would need to add them to the prod workspace (or better yet, don't, but add them to the App in that workspace - best practice) and manually remove them from Dev/Test.
Generally when you start using Deployment Pipelines, your existing space becomes Production so no URLs and bookmarks are lost. Then you have a one time opportunity to deploy backwards to Test, and again to Dev. Then you start working in DEV going forward.
If you created a new Production environment, then no, you cannot migrate the URLs. They are tied to the workspace. If you are new to this, you could remove the deployment pipeline and start over using the method above (make it Prod, deploy backwards to create Test and Dev). If that isn't feasable anymore, then your users will need to do a one time migration to new URLs.
Security is another reason. You cannot migrate that, so you would need to add them to the prod workspace (or better yet, don't, but add them to the App in that workspace - best practice) and manually remove them from Dev/Test.
Thanks! This answers my question and will adjust how I request workspaces in the future.