You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered: