Secrets

Fixtures store [env] values in plaintext inside fixture.toml, and bocal push uploads them to the registry as-is. Because fixtures are meant to be shared, any secret placed in [env] (API keys, tokens) is exposed to everyone with bucket read access and may be cached or indexed downstream.

The rule

Treat [env] as carrying test-tier values, not production secrets:

  • Store a literal only when it's non-sensitive — a test API key (sk_test_…), a feature-flag boolean, non-sensitive config.
  • For real secrets, keep them in your normal secret store and let [env] carry only a pointer or a test-tier value.
  • Restrict registry bucket access and enable bucket-level encryption at rest (SSE).
  • Treat bocal push as publishing — once pushed, assume the values are out of your control even after deletion.

Why plaintext is a deliberate choice

This is a v0 decision, not a known gap. bocal's intended use is sharing test data — the "keep real secrets elsewhere, put only a pointer or test value in [env]" rule is the contract for what belongs in a fixture. Encryption at rest is delegated to S3 bucket SSE + ACLs.

Note that credentials for the registry itself are never in any bocal file — they come from the AWS chain (see Configuration). Only [env] values you author are plaintext.

Per-fixture application-layer encryption (age/SOPS) is tracked as future work but is not planned for v0; the plaintext model is considered sufficient for the test-data sharing bocal is built for.