Allow using google_project.id as an input across the provider

[slevenick]

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

We have seen several issues where users use the standard id field from google_project as an input into other resources. The issue is that id for this resource is in the normal ID format, which is projects/{{project}} while most resources expect the project as only {{project}}.

We should make resources accept the project as both {{project}} and projects/{{project}} to allow for use of both google_project.id and google_project.project_id. This will be a change across many resources

New or Affected Resource(s)

• google_*

Most resources that use projects

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

• Incorrect documentation - monitoring_monitored_project [BETA] #10691

[rileykarson]

Note: We can likely restrict to "known" projects, i.e. fields named exactly "project" or cases that call getProject