Remove immutablity from ForwardingRule resource

[felipegc]

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 the 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 the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

According to the API the ForwardingRule does accept patch operations but the resource forces to be recreated while changing the fields values. There are few field which supposed to be updatable such as "allowPscGlobalAccess" and "allowGlobalAccess"

New or Affected Resource(s)

• google_compute_forwarding_rule

Potential Terraform Configuration

# Propose what you think the configuration to take advantage of this feature should look like.
# We may not use it verbatim, but it's helpful in understanding your intent.

References

• #API

[felipegc]

@trodge Could you help understanding why this resource is immutable? Do you know if there is a specifc reason for that? What are the impacts if I remove it to make some fields updatable? Thanks in advance

[felipegc]

There is just one field which is missing (allowPscGlobalAccess) from being updatable. I managed to figure out how we generate the endpoint specific for that which overrides the immutability behavior from the resource and at the same time deals with the fingerprint(necessary to make update against this field)

[github-actions]

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.