@kapa.ai I’m working on enabling an external secrets manager for connectors. The documentation states: “Modifying the configuration of connector secret storage will cause all existing connectors to fail. You will need to recreate these connectors to ensure they are reading from the appropriate secret store.” I’d like to avoid losing any existing connection state because we’re managing connections via Terraform state. Creating entirely new connections would break assumptions around incremental syncs and similar behaviors, and it would also create a poor user experience. How can I keep the existing connections intact while migrating them to read/write secrets from an external secrets manager?

The documentation is explicit that changing the connector secret storage backend (e.g., enabling an external secrets manager) will cause all existing connectors to fail, and that you must recreate those connectors so they read from the new secret store.[Secret values] This same warning appears consistently across platform versions and in the enterprise implementation guides.[Enterprise guide] There is no documented, supported procedure in these sources for: • Migrating existing connections in-place to a new secrets backend, or • Preserving connection objects (and their IDs) while seamlessly switching them to use the external secrets manager. The docs instead treat this as a breaking change that requires connector recreation. Given that limitation: • From the available documentation, the only supported path is: a. Change the secrets manager configuration. b. Recreate the connectors so they use the new secret store.[Secret values] • The knowledge sources do not describe any official migration tooling or workflow to keep existing connection IDs/states intact while switching the secrets backend. Because of that, I can’t confidently describe a safe, supported way (from Airbyte’s docs) to do what you’re asking—i.e., preserve existing connections and their Terraform-managed state while changing the secrets backend—without going through connector recreation. If this constraint is a blocker, the best next step would be to raise it with Airbyte support or in the community/forum to see if there is any undocumented or upcoming migration mechanism; it is not covered in the documentation provided here. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.