feat: Add feature flag to gate the Azure Blob storage connector#2036
Merged
edwinjosechittilappilly merged 1 commit intoJul 7, 2026
Conversation
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
3 tasks
feat: Add feature flag to gate the Azure Blob storage connector Issue - #2027 Summary - Added `OPENRAG_AZURE_BLOB_ENABLED`, a standalone kill switch (default `true`) that force-hides the Azure Blob connector independently of `IBM_AUTH_ENABLED`, and wired it through every deployment surface. Backend - Added `is_azure_blob_enabled()` in `src/config/settings.py`, reading `OPENRAG_AZURE_BLOB_ENABLED` (default `true`). - Updated `AzureBlobConnector.is_available()` to AND the new flag with the existing `IBM_AUTH_ENABLED` / `OPENRAG_DEV_AZURE_BLOB` gate. Deployment - Documented and defaulted the new env var in `.env.example` and `docker-compose.yml`. - Threaded `OPENRAG_AZURE_BLOB_ENABLED` through the Helm chart (`values.yaml` `global.azureBlob.enabled`, `backend-dotenv.yaml`) and the Go operator's `env.go` default env vars. Connector Access - `governable_connector_types()` now drops `azure_blob` when `OPENRAG_AZURE_BLOB_ENABLED` is off, even if IBM auth is on. Tests - Added a unit test verifying `azure_blob` is excluded under the kill switch while `aws_s3` and `ibm_cos` remain governable.
mpawlow
force-pushed
the
mp/feat/saas/0.6.2/gh-2027-azure-blob-connector-feature-flag
branch
from
July 6, 2026 22:14
c3ac440 to
0d7197b
Compare
3 tasks
edwinjosechittilappilly
merged commit Jul 7, 2026
cf8999d
into
release-saas-ga-0.6.2
27 of 29 checks passed
github-actions
Bot
deleted the
mp/feat/saas/0.6.2/gh-2027-azure-blob-connector-feature-flag
branch
July 7, 2026 06:32
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
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.
Issue
Reference Pull Request
Summary
OPENRAG_AZURE_BLOB_ENABLED, a standalone kill switch (defaulttrue) that force-hides the Azure Blob connector independently ofIBM_AUTH_ENABLED, and wired it through every deployment surface.Backend
is_azure_blob_enabled()insrc/config/settings.py, readingOPENRAG_AZURE_BLOB_ENABLED(defaulttrue).AzureBlobConnector.is_available()to AND the new flag with the existingIBM_AUTH_ENABLED/OPENRAG_DEV_AZURE_BLOBgate.Deployment
.env.exampleanddocker-compose.yml.OPENRAG_AZURE_BLOB_ENABLEDthrough the Helm chart (values.yamlglobal.azureBlob.enabled,backend-dotenv.yaml) and the Go operator'senv.godefault env vars.Connector Access
governable_connector_types()now dropsazure_blobwhenOPENRAG_AZURE_BLOB_ENABLEDis off, even if IBM auth is on.Tests
azure_blobis excluded under the kill switch whileaws_s3andibm_cosremain governable.