Skip to content

feat: Add feature flag to gate the Azure Blob storage connector#2036

Merged
edwinjosechittilappilly merged 1 commit into
release-saas-ga-0.6.2from
mp/feat/saas/0.6.2/gh-2027-azure-blob-connector-feature-flag
Jul 7, 2026
Merged

feat: Add feature flag to gate the Azure Blob storage connector#2036
edwinjosechittilappilly merged 1 commit into
release-saas-ga-0.6.2from
mp/feat/saas/0.6.2/gh-2027-azure-blob-connector-feature-flag

Conversation

@mpawlow

@mpawlow mpawlow commented Jul 6, 2026

Copy link
Copy Markdown
Collaborator

Issue

Reference Pull Request

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 mpawlow self-assigned this Jul 6, 2026
@coderabbitai

coderabbitai Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 0761d1f6-f13d-45bf-af47-61129e964e5d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch mp/feat/saas/0.6.2/gh-2027-azure-blob-connector-feature-flag

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot added backend 🔷 Issues related to backend services (OpenSearch, Langflow, APIs) docker tests enhancement 🔵 New feature or request labels Jul 6, 2026
@github-actions github-actions Bot added enhancement 🔵 New feature or request and removed enhancement 🔵 New feature or request labels Jul 6, 2026
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
mpawlow force-pushed the mp/feat/saas/0.6.2/gh-2027-azure-blob-connector-feature-flag branch from c3ac440 to 0d7197b Compare July 6, 2026 22:14
@github-actions github-actions Bot added enhancement 🔵 New feature or request and removed enhancement 🔵 New feature or request labels Jul 6, 2026

@edwinjosechittilappilly edwinjosechittilappilly left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@github-actions github-actions Bot added the lgtm label Jul 7, 2026
@edwinjosechittilappilly
edwinjosechittilappilly merged commit cf8999d into release-saas-ga-0.6.2 Jul 7, 2026
27 of 29 checks passed
@github-actions
github-actions Bot deleted the mp/feat/saas/0.6.2/gh-2027-azure-blob-connector-feature-flag branch July 7, 2026 06:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backend 🔷 Issues related to backend services (OpenSearch, Langflow, APIs) docker enhancement 🔵 New feature or request lgtm tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature]: Introduce a new feature flag to govern the enablement of the Azure Blob Storage connector

2 participants