Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TURBO_REMOTE_CACHE_SIGNATURE_KEY support #394

Open
chintan9 opened this issue Jun 18, 2024 · 0 comments
Open

TURBO_REMOTE_CACHE_SIGNATURE_KEY support #394

chintan9 opened this issue Jun 18, 2024 · 0 comments
Labels
enhancement New feature or request hacktoberfest

Comments

@chintan9
Copy link

chintan9 commented Jun 18, 2024

🚀 Feature Proposal

TURBO_REMOTE_CACHE_SIGNATURE_KEY
Turborepo can sign artifacts with a secret key before uploading them to the Remote Cache

Motivation

Please outline the motivation for the proposal.

Turborepo uses HMAC-SHA256 signatures on artifacts using a secret key you provide. Turborepo will verify the Remote Cache artifacts' integrity and authenticity when they're downloaded. Any artifacts that fail to verify will be ignored and treated as a cache miss by Turborepo.

To enable this feature, set the remoteCache options on your turbo.json config to include signature: true. Then specify your secret key by declaring the TURBO_REMOTE_CACHE_SIGNATURE_KEY environment variable.

Example

To utilize the TURBO_REMOTE_CACHE_SIGNATURE_KEY which will increase the security of the remote cache, the project config will need to be updated to include the following:

{
	"remoteCache": { "signature": true }
}

read more
https://turbo.build/repo/docs/core-concepts/remote-caching#artifact-integrity-and-authenticity-verification

@fox1t fox1t added the enhancement New feature or request label Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request hacktoberfest
Projects
None yet
Development

No branches or pull requests

3 participants