You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
image_version html tag doesn't work well that we're always led a tag for Composer 1 in google_composer_environment document page because there are two image_version tags in the page for Composer 1 and Composer 2. Does someone have any idea to make the html tag works well?
Note: I believe this issue is talking about the anchor tag used for the image_version field, which always references the first instance. Because these anchors are generated by the HashiCorp provider site (based on our markdown), I don't think this can be fixed on our end. We can't change the field name, and I don't believe there is a mechanism that allows us to override the HashiCorp markdown rendering.
Community Note
Description
image_version
html tag doesn't work well that we're always led a tag for Composer 1 in google_composer_environment document page because there are twoimage_version
tags in the page for Composer 1 and Composer 2. Does someone have any idea to make the html tag works well?https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/composer_environment#image_version
New or Affected Resource(s)
Potential Terraform Configuration
Terraform isn't involved due to the behavior of the documentation
References
b/302797053
The text was updated successfully, but these errors were encountered: