1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
//
// SPDX-License-Identifier: Apache-2.0
//! Identity Project commands
use ;
use AsyncOpenStack;
use crate::;
/// Projects
///
/// A project is the base unit of resource ownership. Resources are owned by a specific project. A
/// project is owned by a specific domain.
///
/// (Since Identity API v3.4) You can create a hierarchy of projects by setting a parent_id when
/// you create a project. All projects in a hierarchy must be owned by the same domain.
///
/// (Since Identity API v3.6) Projects may, in addition to acting as containers for OpenStack
/// resources, act as a domain (by setting the attribute is_domain to true), in which case it
/// provides a namespace in which users, groups and other projects can be created. In fact, a
/// domain created using the POST /domains API will actually be represented as a project with
/// is_domain set to true with no parent (parent_id is null).
///
/// Given this, all projects are considered part of a project hierarchy. Projects created in a
/// domain prior to v3.6 are represented as a two-level hierarchy, with a project that has
/// is_domain set to true as the root and all other projects referencing the root as their parent.
///
/// A project acting as a domain can potentially also act as a container for OpenStack resources,
/// although this depends on whether the policy rule for the relevant resource creation allows
/// this.
///
/// **Note**
///
/// A project’s name must be unique within a domain and no more than 64 characters. A project’s
/// name must be able to be sent within valid JSON, which could be any UTF-8 character. However,
/// this is constrained to the given backend where project names are stored. For instance,
/// MySQL’s restrictions states that UTF-8 support is constrained to the characters in the Basic
/// Multilingual Plane (BMP). Supplementary characters are not permitted. Note that this last
/// restriction is generally true for all names within resources of the Identity API. Creating a
/// project without using a domain scoped token, i.e. using a project scoped token or a system
/// scoped token, and also without specifying a domain or domain_id, the project will
/// automatically be created on the default domain.
/// Supported subcommands