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

Removing compute router nat log_config results in perma-diff #9943

Closed
c2thorn opened this issue Aug 30, 2021 · 1 comment · Fixed by GoogleCloudPlatform/magic-modules#5154, hashicorp/terraform-provider-google-beta#3581 or #9950
Assignees

Comments

@c2thorn
Copy link
Collaborator

c2thorn commented Aug 30, 2021

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
  • Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.
  • If an issue is assigned to the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.

Terraform Version

Affected Resource(s)

  • google_compute_router_nat

Expected Behavior

Field is removed

Actual Behavior

API request does not send the empty field, resulting in a perma-diff

Steps to Reproduce

Create a google_compute_router_nat resource with log_config.
Attempt to remove the log_config in a separate apply.

References

  • b/197129964
@github-actions
Copy link

github-actions bot commented Oct 1, 2021

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.