Redeploying Connectors

Use the same destination and connection name to update an existing connection:

fivetran deploy --api-key <YOUR_BASE64_API_KEY> --destination <YOUR_DESTINATION_NAME> --connection <YOUR_CONNECTION_NAME> --configuration <PATH_TO_CONFIGURATION_JSON>

During an interactive deployment, the CLI asks you to confirm that you want to overwrite the existing connector code. Use --yes for an intentional automated redeployment.

Redeployment has the following behavior:

• The new code is used when the next sync starts.
• If a sync is already running, that sync finishes using the previous code.
• Code, dependency, or Python-version changes will affect the next sync, so test them before deployment.
• Do not pass configuration for a code-only update unless you intend to change stored configuration values.
• Redeploying code does not backfill columns added to previously delivered rows. Trigger a historical re-sync when a schema change requires existing data to be reloaded.
• If you change a table's primary key, drop the destination table and perform a historical re-sync to preserve data integrity.

For a safer release process, deploy the same code to a separate test connection and configuration first. After validation, deploy it to the production connection.

To roll back, redeploy a previously tested revision from version control. You can also download the deployed connector code from the connection's Settings tab. The download does not contain configuration or state.

Configuration behavior during redeployment

Treat configuration and code as separate deployment inputs:

• Supplying a non-empty configuration file during redeployment replaces the connection's stored configuration with the supplied keys and values.
• Supplying an empty configuration object keeps the existing stored values.
• Omitting configuration when redeploying an existing connection keeps the current configuration.
• After deployment, you can edit configuration values from the connection's setup form.

If configuration is managed in the Fivetran dashboard, omit --configuration from routine code-only redeployments. This prevents a local or CI/CD file from unintentionally replacing production values.