Unhelpful google_cloudfunctions_function error message

[ericnorris]

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

Terraform v1.0.0
on linux_amd64

Affected Resource(s)

• google_cloudfunctions_function

Terraform Configuration Files

N/A

Debug Output

N/A

Panic Output

N/A

Expected Behavior

The provider should have returned a helpful error when trying to deploy an invalid Cloud Function.

Actual Behavior

Error: Error while updating cloudfunction configuration: %!s(<nil>)
with google_cloudfunctions_function.function
on main.tf line 49, in resource "google_cloudfunctions_function" "function":

Steps to Reproduce

This is kind of hard to reproduce, but you'd need to make a Cloud Function, update it to something invalid, and then hope that you get this nil error message.

Important Factoids

I believe the issue is this here:

terraform-provider-google/google/resource_cloudfunctions_function.go

Lines 657 to 658 in 7afef3b

	if rerr != nil {
	return fmt.Errorf("Error while updating cloudfunction configuration: %s", err)

rerr is non-nil, but the message prints out err, which is nil, obscuring what rerr actually is.

References

None that I could find.

[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.