You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/index.md
+38Lines changed: 38 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,6 +71,44 @@ Britive tenant. The below list is the order of operations for determining the to
71
71
3. Value retrieved from environment variable `BRITIVE_API_TOKEN`
72
72
4. If none of the above are available an interactive login will be performed and temporary credentials will be stored locally for future use with the CLI
73
73
74
+
## `PROFILE` Parameter Construction (`checkout` and `checkin`)
75
+
76
+
The general construction of a `PROFILE` parameter for `checkout` and `checkin` (in addition to profile aliases)
77
+
is in the format `Application Name/Environment Name/Profile Name`.
78
+
79
+
Behind the scenes `pybritive` will always use this format. However, there are specific application types where
80
+
`Application Name == Environment Name`. For these application types, it is acceptable to provide a 2 part `PROFILE`
81
+
parameter in the format `Application Name/Profile Name`. `pybritive` will convert this to the required 3 part
82
+
format before interacting with backend services.
83
+
84
+
Additionally, `ls profiles -f list` and `cache profiles` will return the 2 part format where applicable. It is still acceptable
85
+
to provide the 3 part format in all cases so any existing profile aliases or other configurations will not be impacted.
86
+
87
+
Below is the list of application types in which a 2 part format is acceptable.
88
+
89
+
* GCP
90
+
* Azure
91
+
* Oracle
92
+
* Google Workspace
93
+
94
+
The list can be generated (assuming the caller has the required permissions) on demand with the following command.
95
+
96
+
~~~bash
97
+
pybritive api applications.catalog \
98
+
--query '[*].{"application type": name,"2 part format allowed":requiresHierarchicalModel}' \
99
+
--format table
100
+
~~~
101
+
102
+
Additionally, the `Environment Name` can be any one of three values. AWS example values are provided.
103
+
104
+
*`environmentId` - 123456789012
105
+
*`environmentName` - 123456789012 (Sigma Labs)
106
+
*`alternateEnvironmentName` - Sigma Labs
107
+
108
+
Any of the above values in the `Environment Name` position will be accepted.
109
+
110
+
When running `ls profiles -f list` and `cache profiles`, the `environmentName` field will be shown.
0 commit comments