Allow caching directly to Azure or S3 blob storage
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.9k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
Cache size limits are untenable for those compiling large Rust or C++ apps that need gigabytes of caching per run.
Azure Blob Storage and S3 both offer built-in automatic blob eviction via lifecycle management.
I propose extending packages/cache/src/internal/cacheHttpClient or adding a swappable implementation to permit caching directly to Azure or S3 (either works), and enabling this behavior when the requisite environment variables are set.
This would bypass the cache service, which I believe is currently responsible for proxying uploads and handling eviction.
Required environment variables
ACTIONS_CACHE_AZURE_CONTAINER
ACTIONS_CACHE_AZURE_CONNECTION_STRING
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
Read packages/cache/src/internal/cacheHttpClient and trace the current cache-service upload and eviction flow. Review the proposed ACTIONS_CACHE_AZURE_CONTAINER and ACTIONS_CACHE_AZURE_CONNECTION_STRING settings; S3 configuration is not specified in the issue. Done means a selectable direct Azure or S3 storage path can bypass the cache service when configured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure, typescript
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100