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
'Know what you are running' - a principle from the Build, Release and Deploy guild, relating to having assurance on exactly which versions, artefacts and infrastructure are deployed to environments
What would be the benefit to the Home Office of adopting this principle?
This mitigates risks of inconsistency between prod and non-prod environments, makes issue tracing easier and allows for quicker recovery and redeployment
How might people follow it
There is existing guidance (patterns) being created for this site on Immutable Artefacts and Infrastructure as code
Additional information
N/A
Please confirm the below
I have looked at the writing-a-principle standard and think this would meet the standard
I have looked through our existing principles and think this is not covered elsewhere
I have checked through the open issues on the repository and this principle has not already been suggested
The text was updated successfully, but these errors were encountered:
What is the principle you are suggesting?
'Know what you are running' - a principle from the Build, Release and Deploy guild, relating to having assurance on exactly which versions, artefacts and infrastructure are deployed to environments
What would be the benefit to the Home Office of adopting this principle?
This mitigates risks of inconsistency between prod and non-prod environments, makes issue tracing easier and allows for quicker recovery and redeployment
How might people follow it
There is existing guidance (patterns) being created for this site on Immutable Artefacts and Infrastructure as code
Additional information
N/A
Please confirm the below
The text was updated successfully, but these errors were encountered: