Human Role

Schema Properties

Property	Type	Description
access_level Default	string	Whether this person may request write access. read_only, the default, means read access at all times and no more. read_write means the same read access, plus the ability to obtain write access for a limited period through the elevate action. Examples:`read_only`
cluster_id Required	string	The identifier of the cluster this role belongs to. Cannot be changed after creation. Examples:`emea/sandbox/welcome/welcome_cluster01`
effective_grants Computed	list(object)	Every permission this role currently holds. Read-only.
enabled Computed	boolean	Whether the person can currently connect. Set to false by the disable action when the password has not been changed for three months, and back to true by rotate_password. Rotating the password is the only way to re-enable an account.
name Computed	string	The name of the role, derived from the person's platform nickname and unique within the cluster. Use it as the username when connecting. Examples:`h_flastname`
password_last_rotated_at Computed	string	When the password of this role was last set through this service. A password older than three months is disabled.
password_location Computed	string	The Vault UI URL where the password of this role is stored.
user_id RequiredForceNew	string	The identifier of the person this role belongs to, which is their email address. The person must be a real user of the platform; the role is named after them and cannot be created for an account that is not a person. Cannot be changed after creation. Examples:`firstname.lastname@worldline.com`

resource "gi_cassandra_human_role" "example" {  attributes = {    cluster_id = "emea/sandbox/welcome/welcome_cluster01"    user_id    = "firstname.lastname@worldline.com"  }}

Schema Properties

Usage Notes