temporalio / temporalio/temporal
Defining a storage class on S3 archival
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
We have a policy of using only STANDARD_IA storage class. Currently, there is no ability to specify the storage class to use in S3 Archival configurations. This is blocking us from using S3 archival.
Describe the solution you'd like
Support additional S3 connection "kwargs" which will all just be passed to the connection or add storage_class as an option.
Describe alternatives you've considered
We are considering using filestore archival instead. Either that or implementing our own archiver.
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 archival configuration and the connection setup it uses; the issue provides no file or test names. Verify that the configuration can request STANDARD_IA and that archival succeeds with that storage class.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100