resource_compute_(region)_instance_group_manager does have a documentation issue wrt. status.stateful message

[askubis]

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 a user, that user is claiming responsibility for the issue.
• Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.

Terraform Version

Terraform v1.7.1

Affected Resource(s)

compute_instance_group_manager
compute_region_instance_group_manager

Terraform Configuration

resource "google_compute_instance_group_manager" "default" {

  name               = "example-group"
  base_instance_name = "test"
  target_size        = 3
  zone               = "us-central1-f"

  version {
    instance_template = google_compute_instance_template.default.id
    name              = "primary"
  }
}

Debug Output

No response

Expected Behavior

tfstate should contain the status.stateful field

Actual Behavior

tfstate should contain the status.version.stateful field

Steps to reproduce

1. terraform apply

Important Factoids

The documentation (https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_instance_group_manager#version_target) is not consistent with the API (https://www.googleapis.com/discovery/v1/apis/compute/v1/rest) for no apparent reason (so in fact to fix it the documentation should be fixed)

References

No response

[askubis]

I would like to fix it.

[ggtisc]

@askubis it This seems more like a documentation issue than a bug. Please confirm us if you are having an error message.

About the status.version.stateful it isn't in the provided code. Could you please provide the complete code and what is the exact field that is presenting a bug?

[askubis]

@ggtisc yes, this was more of a documentation issue.

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