feat(ci): automate integration tests#2322
Open
wpessers wants to merge 30 commits into
Open
Conversation
…ine language config type, add type guard for checking language support
…th for supported languages
…e with node:timers/promises setTimeout
…rval default to 2s
…tion for specific lang
…egration test cdk toolkit actions and tighten permissions
… and drop redundant permissions
…uild layer logic for both release and integration test
wpessers
force-pushed
the
feat/ci/automate-integration-tests
branch
from
02c41e3 to
673e796
Compare
wpessers
added
enhancement
…gration tests in gh actions
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Automated integration testing
resolves #2079
Description
Currently the PR includes a new GitHub workflow to run integration tests. It can be triggered manually, and also is already triggered automatically on tag pushes for the python layer. For an example of such a run: https://github.com/wpessers/opentelemetry-lambda/actions/runs/26541989902 Here the publish step fails, but that's simply because I don't have the necessary infra in my personal aws account that is being used to test this.
TODO
Some stuff left to do before merging this PR:
nodejs.test.tsandpython.test.tsare nearly identical)