embulk / embulk/embulk-output-s3
Test on GitHub Actions with the real Amazon S3 if needed
- Dominant language
- Java
- Stars
- 16
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
For the time being, `embulk-output-s3` is not tested with the real Amazon S3.
The Embulk project may want to have an AWS account maintained by the community.
Or, we may want to test with a "S3-compatible" local storage (ex. MinIO), but note that they may not be 100% S3-compatible. (For example in MinIO: https://min.io/docs/minio/linux/operations/concepts/thresholds.html#conflicting-objects)
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. First clarify whether the project wants community-managed AWS credentials for real S3 or a MinIO-based alternative, then inspect the existing GitHub Actions configuration and test setup. Done means the chosen storage path runs reliably in CI and exercises embulk-output-s3 against it.
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
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100