Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update deployment.md #335

Merged
merged 1 commit into from
Oct 7, 2024
Merged

Update deployment.md #335

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions patterns/deployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ When developing services and applications development teams must consider their

This is a fundamental step in the design of the solution, development teams must consider the technical impact of different strategies alongside the impact to service during deployments. This starts at the point of building the CI pipelines and permeates through to final live deployment pipelines. Different approaches may be applicable depending on the chosen approach, for example serverless deployments as opposed to VM based deployments.

Deployments must be repeatable and [idempotent](../practices/continuous-integration.md#deploy-what-you-tested), so that deploying the same version twice will result in the dame deployed environment.
Deployments must be repeatable and [idempotent](../practices/continuous-integration.md#deploy-what-you-tested) so that deploying the same version twice will result in the same deployed environment.

## CI/CD pipeline-based deployment

Expand Down Expand Up @@ -120,9 +120,9 @@ The following table includes steps that development teams should consider when p

### Failure mode

If initial smoke tests fail OR monitoring identifies increased failures / other indicator OR Further smoke tests fail:
If initial smoke tests fail OR monitoring identifies increased failures / other indicators OR Further smoke tests fail:

1. Traffic is migrated back to previously healthy leg.
1. Traffic is migrated back to the previously healthy leg.
1. Release is marked as failed.

### Game days and chaos testing
Expand Down
Loading