Terraform provider: group_id stored as external_id in Terraform state
CompletedHi, I'm applying a Terraform plan for an AWS lambda connector. One of the required properties is group_id, I see this is reported through the Fivetran API as external_id, and is also stored in the TF state as external_id.
The main problem around this issue is that every time I check the TF plan and I see a difference:
~ config {
- external_id = "xxxxx" -> null
(meaning that I'm not declaring an external_id value, so it will be removed from the state, I have group_id instead)
I found a workaround, if I declare the external_id the problem is gone, but now I have both group_id and external_id with the same value and for the same purpose.
Please let me know if this is a valid bug and if it can be fixed in future TF provider versions for a cleaner TF config.
Thanks,
Rodrigo Collavo
-
Official comment
Rodrigo Juan Collavo our most recent release includes updated functionality to solve this issue.
We now only accept the group_id value and we've created logic to handle external_id automatically so now external_id is read only. Before this change if you hadn't specified the external_id value in config section you would receive a notification from Terraform each time you updating config/applying changes. Now it will just be stored by us automatically and you don't need to think about it again!
-
Rodrigo Juan Collavo - thanks so much for the note, I'm working with engineering to determine the next steps here and will get back to you. Next time that you have a bug, please submit a support ticket because that will get you the best responsiveness, our feature request backlog is long and we're slowly chipping away at it with our product team whereas we have tons of support folks who can help to get you an outcome for bugs much faster.
Please sign in to leave a comment.
Comments
2 comments