temporalio / temporalio/temporal
Support for Azure Blob Storage for 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.
Currently Archival is only supported for Gcloud and AWS S3, our org uses Azure as its cloud provider, hence we would like to use Azure Storage for Archival.
Describe the solution you'd like
We would like a plugin based solution where we can go ahead and implement our own code and pass them to something like the Server Options or any native support from Temporal side is also welcome.
Describe alternatives you've considered
We did try to go ahead and implement the Azure dependencies on our own but since it requires changes in the original source code, it would add a significant overhead on our team to maintain the codebase and keep it updated with newly released versions, we could not proceed with it.
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
The issue names no files, tests, or entry points. Start by comparing the existing Gcloud and AWS S3 archival integrations and reviewing the server options mentioned in the request. Define whether a plugin boundary or native Azure Blob support is appropriate; done means archival works with Azure Storage without maintaining a fork.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100