Update node canary to test different node version and cpu architecture #294
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue description:
Description of changes:
Rollback procedure:
Revert the change.
Ensure you've run the following tests on your changes and include the link below:
Tested the changes with a test workflow yaml file which run the test cases for different node version and cpu architectures. In addition, the existing ec2 default canary is also triggered without specifying the additional inputs. This is used to verify the current changes won't affect existing node ec2 canary. See details in this test run: https://github.com/aws-observability/aws-application-signals-test-framework/actions/runs/11484786155
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.