This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@guardian/cdk@59.5.0
Minor Changes
f4e2a7c: feat(experimental-ec2-pattern): Pattern to deploy ASG updates w/CFN
Included in this update is a new experimental pattern GuEc2AppExperimental, which can be used in place of a GuEc2App:
import { GuEc2AppExperimental } from "@guardian/cdk/lib/experimental/patterns/ec2-app";
This pattern will add an AutoScalingRollingUpdate policy
to the autoscaling group.
This allows application updates to be performed like a standard CloudFormation update,
and using the custom logic provided by Riff-Raff's autoscaling deployment type is unnecessary.
This experimental pattern has few requirements.
Add the build number to the application artifact
This change requires versioned artifacts.
The easiest way to achieve this is by adding the build number to the filename of the artifact:
The riff-raff.yaml file should remove the deploy action of the autoscaling deployment type.
Though including it shouldn't break anything, it would result in a longer deployment time as instance will be rotated by both CloudFormation and Riff-Raff's custom logic.
The uploadArtifacts step of the autoscaling deployment type should still be included, with the cloud-formation deployment type depending on it.
This step uploads the versioned artifact to S3.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@guardian/cdk@59.5.0
Minor Changes
f4e2a7c: feat(experimental-ec2-pattern): Pattern to deploy ASG updates w/CFN
Included in this update is a new experimental pattern
GuEc2AppExperimental
, which can be used in place of aGuEc2App
:This pattern will add an
AutoScalingRollingUpdate
policy to the autoscaling group. This allows application updates to be performed like a standard CloudFormation update, and using the custom logic provided by Riff-Raff'sautoscaling
deployment type is unnecessary.This experimental pattern has few requirements.
Add the build number to the application artifact
This change requires versioned artifacts.
The easiest way to achieve this is by adding the build number to the filename of the artifact:
riff-raff.yaml
The
riff-raff.yaml
file should remove thedeploy
action of theautoscaling
deployment type. Though including it shouldn't break anything, it would result in a longer deployment time as instance will be rotated by both CloudFormation and Riff-Raff's custom logic.The
uploadArtifacts
step of theautoscaling
deployment type should still be included, with thecloud-formation
deployment type depending on it. This step uploads the versioned artifact to S3.