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: code/examples/create_and_populate_groups/README.md
+52Lines changed: 52 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,3 +6,55 @@ There is logic to prevent the creation of duplicate groups.
6
6
The Globus credentials for the service user must be provided via the environment variables GCS_CLI_CLIENT_ID and GCS_CLI_CLIENT_SECRET.
7
7
8
8
Provide a subscription UUID in subscription_id in the group config to verify the group within the subscription. The service must have Administrator access to permit this
9
+
10
+
## Group configuration file format
11
+
12
+
The path to a valid YAML or JSON group configuration file needs to be supplied as a command line argument.
13
+
14
+
### YAML
15
+
16
+
```yaml
17
+
---
18
+
<group name>:
19
+
description: "<optional group description>"
20
+
members:
21
+
- id: "<globus user uuid>"
22
+
role: "<admin | member>"
23
+
user: "<informational field only - user email?>"
24
+
...
25
+
policies:
26
+
authentication_assurance_timeout: 1800
27
+
group_members_visibility: members
28
+
group_visibility: authenticated
29
+
is_high_assurance: false
30
+
join_requests: false
31
+
signup_fields: []
32
+
subscription_id: "<optional subscription UUID>"
33
+
```
34
+
35
+
### JSON
36
+
37
+
```json
38
+
{
39
+
"<group name>": {
40
+
"description": "<optional group description>",
41
+
"members": [
42
+
{
43
+
"user": "<informational field only - user email?>",
0 commit comments