osc identity project create
Creates a project, where the project may act as a domain.
Relationship: https://docs.openstack.org/api/openstack-identity/3/rel/projects
Usage: osc identity project create [OPTIONS] --name <NAME>
Options:
-
--description <DESCRIPTION>
— The description of the project -
--domain-id <DOMAIN_ID>
— The ID of the domain for the project.For projects acting as a domain, the
domain_id
must not be specified, it will be generated by the Identity service implementation.For regular projects (i.e. those not acing as a domain), if
domain_id
is not specified, butparent_id
is specified, then the domain ID of the parent will be used. If neitherdomain_id
orparent_id
is specified, the Identity service implementation will default to the domain to which the client’s token is scoped. If bothdomain_id
andparent_id
are specified, and they do not indicate the same domain, anBad Request (400)
will be returned. -
--enabled <ENABLED>
— If set totrue
, project is enabled. If set tofalse
, project is disabled. The default istrue
Possible values:
true
,false
-
--is-domain <IS_DOMAIN>
— If set totrue
, project is enabled. If set tofalse
, project is disabled. The default istrue
Possible values:
true
,false
-
--name <NAME>
— The name of the project, which must be unique within the owning domain. A project can have the same name as its domain -
--immutable <IMMUTABLE>
Possible values:
true
,false
-
--parent-id <PARENT_ID>
— The ID of the parent of the project.If specified on project creation, this places the project within a hierarchy and implicitly defines the owning domain, which will be the same domain as the parent specified. If
parent_id
is not specified andis_domain
isfalse
, then the project will use its owning domain as its parent. Ifis_domain
istrue
(i.e. the project is acting as a domain), thenparent_id
must not specified (or if it is, it must benull
) since domains have no parents.parent_id
is immutable, and can’t be updated after the project is created - hence a project cannot be moved within the hierarchy.New in version 3.4
-
--tags <TAGS>
— A list of simple strings assigned to a project. Tags can be used to classify projects into groups