opensearch-project / opensearch-project/data-prepper
Run S3 sink integration tests as GHA
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 374
- Forks
- 354
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
Is your feature request related to a problem? Please describe.
The s3 sink integration tests do not run automatically. Thus, PRs may be breaking behavior without our knowing.
Describe the solution you'd like
Run the s3 sink integration tests as part of the GitHub Action. To support this, create an S3 bucket in the testing CDK.
Describe alternatives you've considered (Optional)
We could consider using the same bucket as the S3 source (see #3847) and rely on the key-prefix. However, I think it would be better to have a dedicated bucket. This could also be good for testing writing without any key prefix.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the S3 sink integration tests, the testing CDK, and the GitHub Actions workflow. Add a dedicated S3 bucket through the testing CDK and include the S3 sink integration tests in the GitHub Action; done means those tests run automatically for pull requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, github-actions, java
- Domain
- ci-cd, cloud, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100