ci: expose STRANDS_TEST_API_KEYS_SECRET_NAME to integration tests #513
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.
Description
Small PR as a prerequisite for #510. This will allow us to run the tests and verify before merging that the tests succeed.
Q: Why is this needed?
A: The integration test is running as a pull_request_target. This means the workflow that gets executed is the current one that is in main. The workflow in main does not set the STRANDS_TEST_API_KEYS_SECRET_NAME. However, STRANDS_TEST_API_KEYS_SECRET_NAME is needed by the code that is being tested, which is the cloned code from the fork. So, we need to either merge STRANDS_TEST_API_KEYS_SECRET_NAME first, or we need to optimistically merge based on testing outside of the PRs checks.
Related Issues
#510
Type of Change
Other (please describe): 2 phased change for #510
Testing
How have you tested the change? Verify that the changes do not break functionality or introduce warnings in consuming repositories: agents-docs, agents-tools, agents-cli
hatch run prepare
Checklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.