Skip to content

Customer Contact

Riley Karson edited this page Dec 12, 2022 · 4 revisions

Raising GCP-internal issues with the provider development team

GitHub issues raised against this repository are subject to community support from the provider's development team. If you've raised an issue that's high priority (eg: breaking in production, blocking a scheduled integration, etc) and have a TAM (Technical Account Manager) or other internal contact at Google, you can instruct them to reach out to the Googler portion of the provider team internally. For feature requests and bugs, go/request-terraform and go/terraform-faq are good starting points for them, and for less well defined issues g/terraform-team is a good contact. The majority of the Google provider development team works for Google but we're often unaware of the efforts of your TAMs or other internal contacts if they haven't reached out to us directly.

Particularly, this applies if you've raised an issue with a TAM, product PM, or other internal contact and the associated GitHub issue does not have a priority label or issuetracker link to reflect that the provider team is aware of the request.

If your contacts are unfamiliar with Terraform / the provider, you can also refer them to go/terraform-faq for an internal page with more context.