CreateGroup
POST {{baseUrl}}/groups/
Creates a new group in your tenancy.
You must specify your tenancy's OCID as the compartment ID in the request object (remember that the tenancy is simply the root compartment). Notice that IAM resources (users, groups, compartments, and some policies) reside within the tenancy itself, unlike cloud resources such as compute instances, which typically reside within compartments inside the tenancy. For information about OCIDs, see Resource Identifiers.
You must also specify a name for the group, which must be unique across all groups in your tenancy and cannot be changed. You can use this name or the OCID when writing policies that apply to the group. For more information about policies, see How Policies Work.
You must also specify a description for the group (although it can be an empty string). It does not have to be unique, and you can change it anytime with UpdateGroup.
After you send your request, the new object's lifecycleState
will temporarily be CREATING. Before using the
object, first make sure its lifecycleState
has changed to ACTIVE.
After creating the group, you need to put users in it and write policies for it. See AddUserToGroup and CreatePolicy.
Request Body
{"name"=>"exercitation", "compartmentId"=>"{{tenancy_ocid}}", "description"=>"tempor culpa cupidatat"}
HEADERS
Key | Datatype | Required | Description |
---|---|---|---|
opc-retry-token | string | A token that uniquely identifies a request so it can be retried in case of a timeout or | |
server error without risk of executing that same action again. Retry tokens expire after 24 | |||
hours, but can be invalidated before then due to conflicting operations (e.g., if a resource | |||
has been deleted and purged from the system, then a retry of the original creation request | |||
may be rejected). | |||
Content-Type | string | ||
Date | string | (Required) Current Date | |
Authorization | string | (Required) Signature Authentication on Authorization header | |
x-content-sha256 | string | (Required) Content sha256 for POST, PUT and PATCH operations |
RESPONSES
status: OK
{"id":"in sint in","compartmentId":"adipisicing","name":"commodo dolor","description":"incididunt eiusmod ea occaecat fugiat","timeCreated":"1983-06-21T18:16:23.202Z","lifecycleState":"INACTIVE","definedTags":{},"freeformTags":{},"inactiveStatus":23440942}