You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Investigate what and how multiple staging environments could look like.
Why
Currently we have a live and staging environment. With a single staging environment this makes it difficult to display multiple pieces of work which may be in progress. Whilst prototyping can be done on a local machine, sharing work proves difficult with a single staging environment.
Who needs to be involved
Developer
Done
When the team's developer has an understanding of what and how multiple staging environments could look and work like for the MoJ DS site. This work is not to undertake the actioning of multiple staging environments, but to investigate and scope what it could look like and how it could be done.
The text was updated successfully, but these errors were encountered:
We would also need an automated action to teardown the test container once the branch is merged.
Questions
Does everything have to go through staging?
This might create additional friction and slow things down. if the work is standalone and has been approved on test, forcing a merge to staging (and deploy) and then a merge to main might be annoying. Equally having merges from "test" branches, might make staging a bit redundant. It would only really be of benefit when we have two different things in test that we want to preview together, before deploying.
How does the domain work?
Deploying out a container with a dynamic ingress based on the branch name is relatively straightforward. How does the subdomain get connected to the ingress? Do we have to dynamically create DNS records? or do cloudflare setup a wildcard somehow?
What
Investigate what and how multiple staging environments could look like.
Why
Currently we have a live and staging environment. With a single staging environment this makes it difficult to display multiple pieces of work which may be in progress. Whilst prototyping can be done on a local machine, sharing work proves difficult with a single staging environment.
Who needs to be involved
Done
When the team's developer has an understanding of what and how multiple staging environments could look and work like for the MoJ DS site. This work is not to undertake the actioning of multiple staging environments, but to investigate and scope what it could look like and how it could be done.
The text was updated successfully, but these errors were encountered: