We just discovered a more serious issue with the “fork - apply migrations - promote” approach to applying migrations to the primary environment.
The name of the new environment will be different than the previous/original primary environment. And that means the environment name we pass in the X-Environment header to the API has to be updated every time we need to get migrations into the primary environment.
This isn’t a scalable process. It really needs an alternative approach.
Thanks.