Support importing `googleplay_app_iam` #517

New issue

Open

opened 2026-10-14 08:49:22 +00:00 by anish · 0 comments

anish commented

2026-10-14 08:49:22 +00:00

Owner

googleplay_user supports terraform import by email, but googleplay_app_iam doesn't implement ImportState.

When an app grant already exists outside state, for example after moving a resource address, creating it fails with 409 alreadyExists, and the only way out is to delete the grant in Play Console and recreate it.

Read already finds the grant from user_id and app_id, so import could accept <email>/<package> (or the full developers/<id>/users/<email>/grants/<package> name), set those two attributes, and let Read fill in the rest. Read would also need to populate permissions from the grant's appLevelPermissions so an imported resource doesn't plan a change.

`googleplay_user` supports `terraform import` by email, but `googleplay_app_iam` doesn't implement `ImportState`. When an app grant already exists outside state, for example after moving a resource address, creating it fails with `409 alreadyExists`, and the only way out is to delete the grant in Play Console and recreate it. `Read` already finds the grant from `user_id` and `app_id`, so import could accept `<email>/<package>` (or the full `developers/<id>/users/<email>/grants/<package>` name), set those two attributes, and let `Read` fill in the rest. `Read` would also need to populate `permissions` from the grant's `appLevelPermissions` so an imported resource doesn't plan a change.

anish added the

labels

2026-10-14 08:49:22 +00:00

anish added this to the DevOps TODO project

2026-10-14 08:49:23 +00:00