Connector Schedule: fivetran_connector_schedule

The fivetran_connector_schedule resource lets you manage the schedule of a connector: pause or resume the connector and set its sync_frequency and daily_sync_time. For more information about each attribute, see the fivetran_connector_schedule reference in the Terraform registry.

Example configuration

resource "fivetran_connector_schedule" "example" {
  # Optional:
  # connector_id      = "<CONNECTOR_ID>"
  # connector_name    = "<CONNECTOR_NAME>"
  # daily_sync_time   = "<DAILY_SYNC_TIME>"
  # group_id          = "<GROUP_ID>"
  # pause_after_trial = "<PAUSE_AFTER_TRIAL>"
  # paused            = "<PAUSED>"
  # schedule_type     = "<SCHEDULE_TYPE>"
  # sync_frequency    = "<SYNC_FREQUENCY>"
  # schedule {
  #   # Optional:
  #   # cron          = "<CRON>"
  #   # days_of_week  = ["<DAYS_OF_WEEK>"]
  #   # interval      = 0
  #   # schedule_type = "<SCHEDULE_TYPE>"
  #   # time_of_day   = "<TIME_OF_DAY>"
  # }
}

For new configurations, we recommend the fivetran_connection_v2 resource. It replaces fivetran_connection and fivetran_connector_schedule with a single resource that uses native HCL for connector configuration. To move existing configurations, follow our Migrate to fivetran_connection_v2 guide.

Notes

• Required fields are uncommented. Optional fields are commented out so that you can enable only the settings that apply to your configuration.
• Values in <UPPERCASE> are placeholders. Replace them with your own values before you run terraform apply.
• Fields marked # sensitive are sensitive in the provider schema, so Terraform hides their values in plan and apply output. Terraform still stores these values in the state file. Pass them in through variables instead of hardcoding them, and keep your state in a secure backend. For more information, see the Terraform documentation on sensitive data in state.
• Fields marked # immutable cannot be changed after the resource is created.
• The example lists only the fields that you can set. Read-only and deprecated attributes are omitted.
• For more information about every attribute, see the Fivetran provider documentation in the Terraform registry.