google_bigquery_reservation_assignment reservation argument inconsistency

[zhalas]

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

When importing google_bigquery_reservation_assignment e.g. using import block reservation is set to a bare reservation name, e.g. reservation-name on the other hand when setting this argument referencing id of google_bigquery_reservation as seen in the documentation (e.g. reservation = google_bigquery_reservation.basic.id) it is set to the fully qualified name, e.g projects/PROJECT-NAME/locations/REGION/reservations/RESERVATION-NAME While both forms seem to work, it causes some annoyances, so it would be ideal if we can harmonize this.

Provider version affected: 5.10.0 (the latest at the moment of creating the issue).

New or Affected Resource(s)

• google_bigquery_reservation_assignment

b/319231296

[rileykarson]

@shuyama1 can you update the forwarded bug? Thanks!

[shuyama1]

@shuyama1 can you update the forwarded bug? Thanks!

I don't think this ticket has been forwarded yet.