fix(domain-record): Add dns_zone to tfstate when using terraform import #1024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
remyleone
pushed a commit
to remyleone/terraform-provider-scaleway
that referenced
this pull request
Mar 28, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to #1023
When importing a domain record, it goes into the first
if: https://github.com/scaleway/terraform-provider-scaleway/blob/master/scaleway/resource_domain_record.go#L267By the end, the
dnsZonethat is parsed is never set : https://github.com/scaleway/terraform-provider-scaleway/blob/master/scaleway/resource_domain_record.go#L340I suggest here setting the
dns_zoneat the end, feedback welcome if you see other ways to fix this issue.Tested locally on Terraform 1.0.7.