chore(destination-mongodb): remove strict-encrypt variant, use env-aware TLS enforcement #72812

aaronsteers · 2026-02-04T00:19:01Z

What

Removes the separate destination-mongodb-strict-encrypt connector by migrating its TLS enforcement logic into the base destination-mongodb connector, making it responsive to the DEPLOYMENT_MODE=CLOUD environment variable.

This is part of a broader effort to eliminate strict-encrypt connector variants, which create cross-connector dependencies in the publish workflow and complicate progressive rollouts (see workflow comments).

How

Added spec() override in MongodbDestination that removes the TLS configuration option for standalone instances when running in cloud deployment mode
Added TLS enforcement check in check() method that throws ConfigErrorException if a standalone instance doesn't have TLS enabled in cloud mode
Removed the dockerRepository override in metadata.yaml that pointed cloud to the strict-encrypt variant
Deleted the entire destination-mongodb-strict-encrypt connector directory

Review guide

MongodbDestination.java - Verify:
- getIsCloudDeployment() is accessible (inherited from BaseConnector)
- The spec JSON path navigation correctly targets the TLS property
- The check logic matches the original strict-encrypt behavior
metadata.yaml - Confirm the registry override change is correct

User Impact

Cloud users: No functional change - TLS will still be enforced for standalone MongoDB instances, just via the base connector image with environment-aware behavior
OSS users: No change - TLS remains optional as before
Simplifies connector maintenance: One fewer connector to maintain and publish

Can this PR be safely reverted and rolled back?

YES 💚

Link to Devin run: https://app.devin.ai/sessions/bebef009e9144b0a8b6ad3f164acd8d6
Requested by: AJ Steers (@aaronsteers)

…are TLS enforcement - Add spec() override to MongodbDestination that removes TLS option for standalone instances when DEPLOYMENT_MODE=CLOUD - Add TLS enforcement check in check() method for cloud deployment mode - Remove registryOverrides.cloud.dockerRepository pointing to strict-encrypt - Delete destination-mongodb-strict-encrypt connector directory This migration allows the base connector to handle both OSS and Cloud deployments, enforcing TLS in Cloud mode without needing a separate strict-encrypt connector. Co-Authored-By: AJ Steers <aj@airbyte.io>

devin-ai-integration · 2026-02-04T00:19:06Z

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

Disable automatic comment and CI monitoring

octavia-bot · 2026-02-04T00:19:12Z

Note

📝 PR Converted to Draft

More info...

Thank you for creating this PR. As a policy to protect our engineers' time, Airbyte requires all PRs to be created first in draft status. Your PR has been automatically converted to draft status in respect for this policy.

As soon as your PR is ready for formal review, you can proceed to convert the PR to "ready for review" status by clicking the "Ready for review" button at the bottom of the PR page.

To skip draft status in future PRs, please include [ready] in your PR title or add the skip-draft-status label when creating your PR.

github-actions · 2026-02-04T00:19:27Z

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

💡 Show Tips and Tricks

PR Slash Commands

Airbyte Maintainers (that's you!) can execute the following slash commands on your PR:

🛠️ Quick Fixes
- /format-fix - Fixes most formatting issues.
- /bump-version - Bumps connector versions, scraping changelog description from the PR title.
❇️ AI Testing and Review:
- /ai-docs-review - Provides AI-powered documentation recommendations for PRs with connector changes.
- /ai-prove-fix - Runs prerelease readiness checks, including testing against customer connections.
- /ai-canary-prerelease - Rolls out prerelease to 5-10 connections for canary testing.
- /ai-review - AI-powered PR review for connector safety and quality gates.
🚀 Connector Releases:
- /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-preview.{git-sha}) for all modified connectors in the PR.
- /bump-progressive-rollout-version - Bumps connector version with an RC suffix (2.16.10-rc.1) for progressive rollouts (enableProgressiveRollout: true).
  - Example: /bump-progressive-rollout-version changelog="Add new feature for progressive rollout"
☕️ JVM connectors:
- /update-connector-cdk-version connector=<CONNECTOR_NAME> - Updates the specified connector to the latest CDK version.
  Example: /update-connector-cdk-version connector=destination-bigquery
- /bump-bulk-cdk-version bump=patch changelog='foo' - Bump the Bulk CDK's version. bump can be major/minor/patch.
🐍 Python connectors:
- /poe connector source-example lock - Run the Poe lock task on the source-example connector, committing the results back to the branch.
- /poe source example lock - Alias for /poe connector source-example lock.
- /poe source example use-cdk-branch my/branch - Pin the source-example CDK reference to the branch name specified.
- /poe source example use-cdk-latest - Update the source-example CDK dependency to the latest available version.
⚙️ Admin commands:
- /force-merge reason="<REASON>" - Force merges the PR using admin privileges, bypassing CI checks. Requires a reason.
  Example: /force-merge reason="CI is flaky, tests pass locally"

📚 Show Repo Guidance

Helpful Resources

Breaking Changes Guide - Breaking changes, migration guides, and upgrade deadlines
Developing Connectors Locally
Managing Connector Secrets
On-Demand Regression Tests
#connector-ci-issues
#connector-publish-updates
#connector-build-statuses

📝 Edit this welcome message.

github-actions · 2026-02-04T00:21:46Z

`destination-mongodb` Connector Test Results

5 files 5 suites 12m 46s ⏱️
111 tests 108 ✅ 3 💤 0 ❌
123 runs 120 ✅ 3 💤 0 ❌

Results for commit 35139b0.

♻️ This comment has been updated with latest results.

Co-Authored-By: AJ Steers <aj@airbyte.io>

devin-ai-integration

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 4 additional flags.

devin-ai-integration

Devin Review found 1 new potential issue.

View issue and 6 additional flags in Devin Review.

devin-ai-integration · 2026-02-04T00:28:08Z

...on-mongodb/src/main/java/io/airbyte/integrations/destination/mongodb/MongodbDestination.java

+        final JsonNode instanceConfig = config.get(MongoUtils.INSTANCE_TYPE);
+        final var instance = MongoUtils.MongoInstanceType.fromValue(instanceConfig.get(MongoUtils.INSTANCE).asText());
+        if (instance.equals(MongoUtils.MongoInstanceType.STANDALONE) && !MongoUtils.tlsEnabledForStandaloneInstance(config, instanceConfig)) {
+          throw new ConfigErrorException("TLS connection must be used to read from MongoDB.");


🟡 Incorrect error message says 'read from' for a destination connector

The error message in the TLS enforcement check incorrectly says "TLS connection must be used to read from MongoDB" but this is a destination connector that writes to MongoDB, not reads from it.

Click to expand

Issue

At line 94, when TLS is not enabled for a standalone instance in cloud mode, the error message states:

throw new ConfigErrorException("TLS connection must be used to read from MongoDB.");

This message was copied from the original MongodbDestinationStrictEncrypt which had the same incorrect wording. For a destination connector, the message should say "write to" instead of "read from".

Impact

This is a cosmetic issue that may confuse users when they see the error message, as it incorrectly describes the operation being performed. The functionality works correctly - TLS enforcement still happens properly.

Recommendation: Change the error message to: "TLS connection must be used to write to MongoDB."

Was this helpful? React with 👍 or 👎 to provide feedback.

…loudDeployment() Co-Authored-By: AJ Steers <aj@airbyte.io>

Co-Authored-By: AJ Steers <aj@airbyte.io>

github-actions · 2026-02-04T02:32:01Z

docs/integrations/destinations/mongodb.md

-| 0.1.1   | 2021-09-29 | [6536](https://github.com/airbytehq/airbyte/pull/6536)   | Destination MongoDb: added support via TLS/SSL             |
-
-</details>
+| 0.3.0 | 2026-02-04 | [*PR_NUMBER_PLACEHOLDER*](https://github.com/airbytehq/airbyte/pull/*PR_NUMBER_PLACEHOLDER*) | Remove strict-encrypt variant; use environment-aware TLS enforcement |


[markdownlint] _{reported by reviewdog 🐶}
MD049/emphasis-style Emphasis style [Expected: underscore; Actual: asterisk]

github-actions · 2026-02-04T02:32:01Z

docs/integrations/destinations/mongodb.md

-| 0.1.1   | 2021-09-29 | [6536](https://github.com/airbytehq/airbyte/pull/6536)   | Destination MongoDb: added support via TLS/SSL             |
-
-</details>
+| 0.3.0 | 2026-02-04 | [*PR_NUMBER_PLACEHOLDER*](https://github.com/airbytehq/airbyte/pull/*PR_NUMBER_PLACEHOLDER*) | Remove strict-encrypt variant; use environment-aware TLS enforcement |


[markdownlint] _{reported by reviewdog 🐶}
MD049/emphasis-style Emphasis style [Expected: underscore; Actual: asterisk]

github-actions · 2026-02-04T02:32:49Z

docs/integrations/destinations/mongodb.md

-| 0.1.1   | 2021-09-29 | [6536](https://github.com/airbytehq/airbyte/pull/6536)   | Destination MongoDb: added support via TLS/SSL             |
-
-</details>
+| 0.3.0 | 2026-02-04 | [*PR_NUMBER_PLACEHOLDER*](https://github.com/airbytehq/airbyte/pull/*PR_NUMBER_PLACEHOLDER*) | Remove strict-encrypt variant; use environment-aware TLS enforcement |


[markdownlint-fix] _{reported by reviewdog 🐶}

Suggested change

| 0.3.0 | 2026-02-04 | [*PR_NUMBER_PLACEHOLDER*](https://github.com/airbytehq/airbyte/pull/*PR_NUMBER_PLACEHOLDER*) | Remove strict-encrypt variant; use environment-aware TLS enforcement |

| 0.3.0 | 2026-02-04 | [_PR_NUMBER_PLACEHOLDER_](https://github.com/airbytehq/airbyte/pull/*PR_NUMBER_PLACEHOLDER*) | Remove strict-encrypt variant; use environment-aware TLS enforcement |

github-actions · 2026-02-04T02:36:40Z

Deploy preview for airbyte-docs ready!

✅ Preview
https://airbyte-docs-9taczydhh-airbyte-growth.vercel.app

Built with commit 35139b0.
This pull request is being automatically deployed with vercel-action

aaronsteers requested a review from a team as a code owner February 4, 2026 00:19

devin-ai-integration bot assigned aaronsteers Feb 4, 2026

octavia-bot bot marked this pull request as draft February 4, 2026 00:19

octavia-squidington-iii added connectors/destination/mongodb connectors/destination/mongodb-strict-encrypt labels Feb 4, 2026

fix: format imports and comments in MongodbDestination.java

dc30905

Co-Authored-By: AJ Steers <aj@airbyte.io>

devin-ai-integration bot reviewed Feb 4, 2026

View reviewed changes

github-actions bot added the dependencies-change label Feb 4, 2026

aaronsteers marked this pull request as ready for review February 4, 2026 00:24

github-actions bot removed the dependencies-change label Feb 4, 2026

devin-ai-integration bot reviewed Feb 4, 2026

View reviewed changes

devin-ai-integration bot and others added 3 commits February 4, 2026 01:30

fix(destination-mongodb): use cloudDeploymentMode() instead of getIsC…

d98ae75

…loudDeployment() Co-Authored-By: AJ Steers <aj@airbyte.io>

fix(destination-mongodb): fix import ordering for Spotless

c7f01bf

Co-Authored-By: AJ Steers <aj@airbyte.io>

chore(destination-mongodb): bump version to 0.3.0

35139b0

Co-Authored-By: AJ Steers <aj@airbyte.io>

github-actions bot reviewed Feb 4, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(destination-mongodb): remove strict-encrypt variant, use env-aware TLS enforcement #72812

chore(destination-mongodb): remove strict-encrypt variant, use env-aware TLS enforcement #72812

Uh oh!

aaronsteers commented Feb 4, 2026 •

edited by devin-ai-integration bot

Loading

Uh oh!

devin-ai-integration bot commented Feb 4, 2026

Uh oh!

octavia-bot bot commented Feb 4, 2026

Uh oh!

github-actions bot commented Feb 4, 2026

PR Slash Commands

Helpful Resources

Uh oh!

github-actions bot commented Feb 4, 2026 •

edited

Loading

Uh oh!

devin-ai-integration bot left a comment

Uh oh!

devin-ai-integration bot left a comment

Uh oh!

devin-ai-integration bot Feb 4, 2026

Uh oh!

github-actions bot Feb 4, 2026

Uh oh!

github-actions bot Feb 4, 2026

Uh oh!

github-actions bot Feb 4, 2026

Uh oh!

github-actions bot commented Feb 4, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	\| 0.3.0 \| 2026-02-04 \| [PR_NUMBER_PLACEHOLDER](https://github.com/airbytehq/airbyte/pull/PR_NUMBER_PLACEHOLDER) \| Remove strict-encrypt variant; use environment-aware TLS enforcement \|
	\| 0.3.0 \| 2026-02-04 \| [_PR_NUMBER_PLACEHOLDER_](https://github.com/airbytehq/airbyte/pull/PR_NUMBER_PLACEHOLDER) \| Remove strict-encrypt variant; use environment-aware TLS enforcement \|

chore(destination-mongodb): remove strict-encrypt variant, use env-aware TLS enforcement #72812

Are you sure you want to change the base?

chore(destination-mongodb): remove strict-encrypt variant, use env-aware TLS enforcement #72812

Uh oh!

Conversation

aaronsteers commented Feb 4, 2026 • edited by devin-ai-integration bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What

How

Review guide

User Impact

Can this PR be safely reverted and rolled back?

Uh oh!

devin-ai-integration bot commented Feb 4, 2026

🤖 Devin AI Engineer

Uh oh!

octavia-bot bot commented Feb 4, 2026

Uh oh!

github-actions bot commented Feb 4, 2026

👋 Greetings, Airbyte Team Member!

PR Slash Commands

Helpful Resources

Uh oh!

github-actions bot commented Feb 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

destination-mongodb Connector Test Results

Uh oh!

devin-ai-integration bot left a comment

Choose a reason for hiding this comment

✅ Devin Review: No Issues Found

Uh oh!

devin-ai-integration bot left a comment

Choose a reason for hiding this comment

Uh oh!

devin-ai-integration bot Feb 4, 2026

Choose a reason for hiding this comment

Issue

Impact

Uh oh!

github-actions bot Feb 4, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Feb 4, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Feb 4, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Feb 4, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

aaronsteers commented Feb 4, 2026 •

edited by devin-ai-integration bot

Loading

github-actions bot commented Feb 4, 2026 •

edited

Loading

`destination-mongodb` Connector Test Results