Data sources¶

guance_permissions¶

A role permission is defined to grant a user permission to perform a specific action on a specific resource.

Guance Cloud supports a number of different role permissions, and you can create new roles for users and assign permission scopes to roles to meet the permission needs of your organization.

Example Usage¶

data "guance_permissions" "demo" {
}

output "permissions" {
  value = data.guance_permissions.demo
}

Schema¶

Optional

• is_support_custom_role (Boolean) Filter the permission list that supports custom role.

Read-Only

• permissions (Attributes List) The list of the permissions. (see below for nested schema)

Nested Schema for permissions¶

Read-Only:

• desc (String) The description of the permission.
• disabled (Number) The disabled status of the permission.
• is_support_custom_role (Number) Whether support custom role.
• is_support_general (Number) Whether support general.
• is_support_owner (Number) Whether support owner.
• is_support_read_only (Number) Whether support readonly.
• is_support_ws_admin (Number) Whether support WsAdmin.
• key (String) The key of the permission.
• name (String) The name of the permission.
• subs (Attributes List) The list of the sub permissions. (see below for nested schema)

Nested Schema for permissions.subs¶

Read-Only:

• desc (String) The description of the permission.
• disabled (Number) The disabled status of the permission.
• is_support_custom_role (Number) Whether support custom role.
• is_support_general (Number) Whether support general.
• is_support_owner (Number) Whether support owner.
• is_support_read_only (Number) Whether support readonly.
• is_support_ws_admin (Number) Whether support WsAdmin.
• key (String) The key of the permission.
• name (String) The name of the permission.

guance_members¶

A workspace member is a user who has access to a workspace.

Guance Cloud supports managing all members of the current workspace through member management, including setting role permissions, inviting members and setting permissions for members, configuring member groups, and setting SSO single sign-on.

Relationships:

graph LR
    A[Workspace] --> B[Member]

Example Usage¶

variable "email" {
  type = string
}

data "guance_members" "demo" {
  search = var.email
}

output "member" {
  value = data.guance_members.demo.members
}

Schema¶

Optional

• search (String) Search the member by email or name.

Read-Only

• members (Attributes List) The list of the members. (see below for nested schema)

Nested Schema for members¶

Optional:

• email (String) Email
• name (String) User name
• roles (Attributes List) Role, value must be one of: owner, wsAdmin, general, readOnly, other value will be ignored. (see below for nested schema)

Read-Only:

• create_at (String) The unix timestamp in seconds of the member creation.
• uuid (String) The uuid of the member.

Nested Schema for members.roles¶

Optional:

• name (String) The name of the role.
• uuid (String) The UUID of the role.