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.

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

Switch to manual riff-raff.yaml file #547

Closed
wants to merge 1 commit into from

Conversation

akash1810
Copy link
Member

@akash1810 akash1810 commented Oct 11, 2024

What does this change?

This is to allow testing of guardian/riff-raff#1383 whilst the riff-raff.yaml generator from GuCDK hasn't been updated.

This riff-raff.yaml is a stripped down version of the generated one, only uploading the application artifact to S3, and deploying the application CloudFormation stack.

How to test?

With guardian/riff-raff#1383 on Riff-Raff CODE, and starting with main being deployed, this branch should deploy successfully, as normal.

This service uses the GuEc2AppExperimental pattern from GuCDK (#526). A "normal" deployment means CFN doubles the capacity of the ASG, waits for new instances to send a SUCCESS signal, then terminates old instances by halving ASG capacity. Indeed, this is what was observed.

This is to allow testing of guardian/riff-raff#1383
whilst the `riff-raff.yaml` generator from GuCDK hasn't been updated.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant