-
Notifications
You must be signed in to change notification settings - Fork 19
/
Copy pathgroup_roles.yaml
54 lines (51 loc) · 1.49 KB
/
group_roles.yaml
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
# Roles Custom Resource Examples
# Example 1: Using groupId and roleIds to assign roles in a Development Realm
apiVersion: group.keycloak.crossplane.io/v1alpha1
kind: Roles
metadata:
name: dev-group-roles
spec:
forProvider:
realmId: "development"
groupId: "dev-group-id" # Directly specify the Group ID.
roleIds: # Directly specify the Role IDs.
- "developer-role-id"
- "tester-role-id"
providerConfigRef:
name: default
# Example 2: Using groupIdRef and roleIdsRefs to assign roles in a Production Realm
apiVersion: group.keycloak.crossplane.io/v1alpha1
kind: Roles
metadata:
name: prod-admin-roles
spec:
forProvider:
realmId: "production"
groupIdRef: # Use a reference to populate groupId.
name: "admin-group"
policy:
resolution: "Required"
roleIdsRefs: # Use references to populate roleIds.
- name: "admin-role"
policy:
resolution: "Required"
- name: "super-admin-role"
policy:
resolution: "Required"
providerConfigRef:
name: default
# Example 3: Using groupId and roleIdsRefs to assign roles in a Staging Realm
apiVersion: group.keycloak.crossplane.io/v1alpha1
kind: Roles
metadata:
name: staging-group-roles
spec:
forProvider:
realmId: "staging"
groupId: "staging-group-id" # Directly specify the Group ID.
roleIdsRefs: # Use references to populate roleIds.
- name: "staging-role"
policy:
resolution: "Required"
providerConfigRef:
name: default