CryptoKeyIAMMember

Import

IAM member imports use space-delimited identifiers; the resource in question, the role, and the account. This member resource can be imported using the crypto_key_id, role, and member identity e.g.

$ pulumi import gcp:kms/cryptoKeyIAMMember:CryptoKeyIAMMember crypto_key "your-project-id/location-name/key-ring-name/key-name roles/viewer user:foo@example.com"

IAM binding imports use space-delimited identifiers; first the resource in question and then the role. These bindings can be imported using the crypto_key_id and role, e.g.

$ pulumi import gcp:kms/cryptoKeyIAMMember:CryptoKeyIAMMember crypto_key "your-project-id/location-name/key-ring-name/key-name roles/editor"

IAM policy imports use the identifier of the resource in question. This policy resource can be imported using the crypto_key_id, e.g.

$ pulumi import gcp:kms/cryptoKeyIAMMember:CryptoKeyIAMMember crypto_key your-project-id/location-name/key-ring-name/key-name

Properties

Link copied to clipboard

) An IAM Condition for a given binding. Structure is documented below.

Link copied to clipboard
val cryptoKeyId: Output<String>

The crypto key ID, in the form {project_id}/{location_name}/{key_ring_name}/{crypto_key_name} or {location_name}/{key_ring_name}/{crypto_key_name}. In the second form, the provider's project setting will be used as a fallback.

Link copied to clipboard
val etag: Output<String>

(Computed) The etag of the project's IAM policy.

Link copied to clipboard
val id: Output<String>
Link copied to clipboard
val member: Output<String>
Link copied to clipboard
Link copied to clipboard
Link copied to clipboard
val role: Output<String>

The role that should be applied. Note that custom roles must be of the format [projects|organizations]/{parent-name}/roles/{role-name}.

Link copied to clipboard
val urn: Output<String>