Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

destination import to read configs #350

Open
kakarukeys opened this issue Aug 28, 2024 · 0 comments
Open

destination import to read configs #350

kakarukeys opened this issue Aug 28, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@kakarukeys
Copy link

Is your feature request related to a problem? Please describe.
After creating a AWS S3 data lake destination on the UI, I wanted to import it using fivetran provider.
However the configs could not be imported. I had to leave the config block blank.
Manually adding the configs would result in a new plan to make a change.

Describe the solution you'd like

an import to a completely configured resource should not result in a plan to make a change.
it should show no configuration change

resource "fivetran_destination" "my_s3_destination" {
  group_id = fivetran_group.my_group.id

  service                      = "new_s3_datalake"
  region                       = "AWS_AP_SOUTHEAST_1"
  time_zone_offset    = "+8"
  daylight_saving_time_enabled = false

  config {
    region                   = local.region
    fivetran_role_arn = module.fivetran_role.iam_role_arn
    bucket                   = module.datalake_s3_bronze.s3_bucket_id
    prefix_path           = local.fivetran_s3_prefix
    is_private_link_required = false
}

Describe the use-cases if possible
see above.

Additional context
Girish Sathyanarayana can provide more context

@kakarukeys kakarukeys added the enhancement New feature or request label Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants