Creates a new custom Role.
Scopes
You will need authorization for the https://www.googleapis.com/auth/cloud-platform scope to make a valid call.
If unset, the scope for this method defaults to https://www.googleapis.com/auth/cloud-platform.
You can set the scope for this method like this: iam1 --scope <scope> organizations roles-create ...
Required Scalar Argument
- <parent> (string)
- The
parent
parameter's value depends on the target resource for the request, namelyprojects
ororganizations
. Each resource type'sparent
value format is described below: *projects.roles.create()
:projects/{PROJECT_ID}
. This method creates project-level custom roles. Example request URL:https://iam.googleapis.com/v1/projects/{PROJECT_ID}/roles
*organizations.roles.create()
:organizations/{ORGANIZATION_ID}
. This method creates organization-level custom roles. Example request URL:https://iam.googleapis.com/v1/organizations/{ORGANIZATION_ID}/roles
Note: Wildcard (*) values are invalid; you must specify a complete project ID or organization ID.
- The
Required Request Value
The request value is a data-structure with various fields. Each field may be a simple scalar or another data-structure. In the latter case it is advised to set the field-cursor to the data-structure's field to specify values more concisely.
For example, a structure like this:
CreateRoleRequest:
role:
deleted: boolean
description: string
etag: string
included-permissions: [string]
name: string
stage: string
title: string
role-id: string
can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.
-r .role deleted=true
- The current deleted state of the role. This field is read only. It will be ignored in calls to CreateRole and UpdateRole.
description=consetetur
- Optional. A human-readable description for the role.
etag=voluptua.
- Used to perform a consistent read-modify-write.
included-permissions=et
- The names of the permissions this role grants when bound in an IAM policy.
- Each invocation of this argument appends the given value to the array.
name=erat
- The name of the role. When
Role
is used inCreateRole
, the role name must not be set. WhenRole
is used in output and other input such asUpdateRole
, the role name is the complete path. For example,roles/logging.viewer
for predefined roles,organizations/{ORGANIZATION_ID}/roles/my-role
for organization-level custom roles, andprojects/{PROJECT_ID}/roles/my-role
for project-level custom roles.
- The name of the role. When
stage=consetetur
- The current launch stage of the role. If the
ALPHA
launch stage has been selected for a role, thestage
field will not be included in the returned definition for the role.
- The current launch stage of the role. If the
-
title=amet.
- Optional. A human-readable title for the role. Typically this is limited to 100 UTF-8 bytes.
-
.. role-id=sed
- The role ID to use for this role. A role ID may contain alphanumeric characters, underscores (
_
), and periods (.
). It must contain a minimum of 3 characters and a maximum of 64 characters.
- The role ID to use for this role. A role ID may contain alphanumeric characters, underscores (
About Cursors
The cursor position is key to comfortably set complex nested structures. The following rules apply:
- The cursor position is always set relative to the current one, unless the field name starts with the
.
character. Fields can be nested such as in-r f.s.o
. - The cursor position is set relative to the top-level structure if it starts with
.
, e.g.-r .s.s
- You can also set nested fields without setting the cursor explicitly. For example, to set a value relative to the current cursor position, you would specify
-r struct.sub_struct=bar
. - You can move the cursor one level up by using
..
. Each additional.
moves it up one additional level. E.g....
would go three levels up.
Optional Output Flags
The method's return value a JSON encoded structure, which will be written to standard output by default.
- -o out
- out specifies the destination to which to write the server's result to.
It will be a JSON-encoded structure.
The destination may be
-
to indicate standard output, or a filepath that is to contain the received bytes. If unset, it defaults to standard output.
- out specifies the destination to which to write the server's result to.
It will be a JSON-encoded structure.
The destination may be
Optional General Properties
The following properties can configure any call, and are not specific to this method.
-
-p $-xgafv=string
- V1 error format.
-
-p access-token=string
- OAuth access token.
-
-p alt=string
- Data format for response.
-
-p callback=string
- JSONP
-
-p fields=string
- Selector specifying which fields to include in a partial response.
-
-p key=string
- API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.
-
-p oauth-token=string
- OAuth 2.0 token for the current user.
-
-p pretty-print=boolean
- Returns response with indentations and line breaks.
-
-p quota-user=string
- Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.
-
-p upload-type=string
- Legacy upload protocol for media (e.g. "media", "multipart").
-
-p upload-protocol=string
- Upload protocol for media (e.g. "raw", "multipart").