Closed lym953 closed 1 month ago
Right now, two identical snapshots are created for each stack used by integration tests. For example, lambda_python_stack.py has:
lambda_python_stack.py
correct-lambda_python_stack-snapshot.json
test-lambda_python_stack-snapshot.json
The "test" one is supposed to be used locally and not supposed to be committed to git.
Remove the "test" snapshots from Git.
aws-vault exec sso-serverless-sandbox-account-admin -- scripts/run_integration_tests.sh still works.
aws-vault exec sso-serverless-sandbox-account-admin -- scripts/run_integration_tests.sh
test-lambda-function-stack-legacy-datadog-api-snapshot.json is empty, which is unexpected. I will take a look and fix it in another PR.
test-lambda-function-stack-legacy-datadog-api-snapshot.json
Motivation
Right now, two identical snapshots are created for each stack used by integration tests. For example,
lambda_python_stack.py
has:correct-lambda_python_stack-snapshot.json
test-lambda_python_stack-snapshot.json
The "test" one is supposed to be used locally and not supposed to be committed to git.
What does this PR do?
Remove the "test" snapshots from Git.
Testing Guidelines
aws-vault exec sso-serverless-sandbox-account-admin -- scripts/run_integration_tests.sh
still works.Additional Notes
test-lambda-function-stack-legacy-datadog-api-snapshot.json
is empty, which is unexpected. I will take a look and fix it in another PR.Types of Changes
Check all that apply