Document BACKUP_SKIP_ACCESS_CHECK and EXPORT_SKIP_ACCESS_CHECK env vars#449
Merged
Conversation
Adds docs for the two env vars introduced in weaviate#11645 (released in v1.37.8). Both default to false and skip the write-and-delete access probe that runs when a backup/export backend initializes — useful for immutable (write-once / WORM) buckets or least-privilege credentials that cannot delete objects. - env-vars/index.md: add EXPORT_SKIP_ACCESS_CHECK to the General reference table - export.md: add EXPORT_SKIP_ACCESS_CHECK row; clarify runtime-config note (the new var is applied at startup, not runtime-configurable) - backups.md: add a "Skip the storage access check" section for BACKUP_SKIP_ACCESS_CHECK (applies to all cloud backup backends) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
![orca-security-eu[bot]](https://avatars.githubusercontent.com/in/276244?s=60&v=4){kind=small}
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority | |
|---|---|---|---|
 Passed |
Infrastructure as Code |  0  0  0  0 |
View in Orca |
| Passed |
SAST | 0 0 0 0 |
View in Orca |
| Passed |
Secrets | 0 0 0 0 |
View in Orca |
| Passed |
Vulnerabilities | 0 0 0 0 |
View in Orca |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the two new environment variables introduced in weaviate#11645 ("Add env vars to disable bucket access check"), first released in v1.37.8:
BACKUP_SKIP_ACCESS_CHECKEXPORT_SKIP_ACCESS_CHECKWhen a backup or collection-export backend initializes, Weaviate verifies that the configured credentials can write to and delete from the target bucket by writing a temporary
access-checkobject and then removing it. That probe fails on immutable (write-once / WORM) buckets, or with least-privilege credentials that cannot delete objects. Setting the relevant variable totrueskips the probe.Both variables default to
false, apply to the S3, GCS, and Azure backends, and are read at startup (not runtime-configurable).Changes
docs/deploy/configuration/env-vars/index.md— addEXPORT_SKIP_ACCESS_CHECKto the General reference table.docs/deploy/configuration/export.md— addEXPORT_SKIP_ACCESS_CHECKto the export env-var table, and fix the runtime-config note (previously "All four variables are runtime-configurable" — clarified that the new var is applied at startup).docs/deploy/configuration/backups.md— add a "Skip the storage access check" section documentingBACKUP_SKIP_ACCESS_CHECK(placed under Configuration since it applies to all cloud backup backends).🤖 Generated with Claude Code