Let canary be driven by a new CloudFormation stack to a new account. Historically, the same canary stack has been shared between aws-sdk-rust and smithy-rs. Now that we are planning to also run the canary as part of smithy-rs CI, we should a separate canary stack deployed to a separate account to not affect one another.
This PR will update the canary workflow to point to the newly deployed canary stack. While doing so, it obviates the need for the environment variables for S3 canary. Instead, it downloads cdk-outputs.json (a result of running npx cdk --app "node build/bin/aws-sdk-rust/canary-only.js" deploy --outputs-file cdk-outputs.json) and passes it to canary-runner.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Motivation and Context
Let canary be driven by a new CloudFormation stack to a new account. Historically, the same canary stack has been shared between
aws-sdk-rustandsmithy-rs. Now that we are planning to also run the canary as part ofsmithy-rsCI, we should a separate canary stack deployed to a separate account to not affect one another.This PR will update the canary workflow to point to the newly deployed canary stack. While doing so, it obviates the need for the environment variables for S3 canary. Instead, it downloads
cdk-outputs.json(a result of runningnpx cdk --app "node build/bin/aws-sdk-rust/canary-only.js" deploy --outputs-file cdk-outputs.json) and passes it tocanary-runner.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.