- Sort Score
- Result 10 results
- Languages All
Results 101 - 110 of 3,167 for user4 (0.14 sec)
-
cmd/iam-object-store.go
} return nil } var ( usersListKey = "users/" svcAccListKey = "service-accounts/" groupsListKey = "groups/" policiesListKey = "policies/" stsListKey = "sts/" policyDBPrefix = "policydb/" policyDBUsersListKey = "policydb/users/" policyDBSTSUsersListKey = "policydb/sts-users/" policyDBGroupsListKey = "policydb/groups/" )
Registered: Sun Jun 16 00:44:34 UTC 2024 - Last Modified: Thu Jun 13 22:26:38 UTC 2024 - 19.5K bytes - Viewed (0) -
helm-releases/minio-5.1.0.tgz
ts[].actions[]` - list of actions granted ### Create user after install Install the chart, specifying the users you want to create after install: ```bash helm install --set users[0].accessKey=accessKey,users[0].secretKey=secretKey,users[0].policy=none,users[1].accessKey=accessKey2,users[1].secretRef=existingSecret,users[1].secretKey=password,users[1].policy=none minio/minio ``` Description of the configuration parameters used above - - `users[].accessKey` - accessKey of user - `users[].secretKey`...
Registered: Sun Jun 16 00:44:34 UTC 2024 - Last Modified: Sun Mar 03 18:49:37 UTC 2024 - 21.3K bytes - Viewed (0) -
helm-releases/minio-5.2.0.tgz
ts[].actions[]` - list of actions granted ### Create user after install Install the chart, specifying the users you want to create after install: ```bash helm install --set users[0].accessKey=accessKey,users[0].secretKey=secretKey,users[0].policy=none,users[1].accessKey=accessKey2,users[1].secretRef=existingSecret,users[1].secretKey=password,users[1].policy=none minio/minio ``` Description of the configuration parameters used above - - `users[].accessKey` - accessKey of user - `users[].secretKey`...
Registered: Sun Jun 16 00:44:34 UTC 2024 - Last Modified: Sun Apr 28 10:14:37 UTC 2024 - 21.7K bytes - Viewed (0) -
staging/src/k8s.io/api/authentication/v1/types.go
} // UserInfo holds the information about the user needed to implement the // user.Info interface. type UserInfo struct { // The name that uniquely identifies this user among all active users. // +optional Username string `json:"username,omitempty" protobuf:"bytes,1,opt,name=username"` // A unique value that identifies this user across time. If this user is // deleted and another user by the same name is added, they will have
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Thu May 23 17:42:49 UTC 2024 - 10K bytes - Viewed (0) -
docs_src/openapi_webhooks/tutorial001.py
@app.webhooks.post("new-subscription") def new_subscription(body: Subscription): """ When a new user subscribes to your service we'll send you a POST request with this data to the URL that you register for the event `new-subscription` in the dashboard. """ @app.get("/users/") def read_users():
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Fri Oct 20 09:00:44 UTC 2023 - 550 bytes - Viewed (0) -
manifests/charts/gateways/istio-ingress/templates/zzz_profile.yaml
1. The builtin values.yaml defaults 2. The profile the user selects 3. Users input (-f or --set) Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2). However, we can workaround this by placing all of (1) under a specific key (.Values.defaults). We can then merge the profile onto the defaults, then the user settings onto that.
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Tue Apr 02 22:30:06 UTC 2024 - 1.5K bytes - Viewed (0) -
manifests/charts/istio-control/istio-discovery/templates/zzz_profile.yaml
1. The builtin values.yaml defaults 2. The profile the user selects 3. Users input (-f or --set) Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2). However, we can workaround this by placing all of (1) under a specific key (.Values.defaults). We can then merge the profile onto the defaults, then the user settings onto that.
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Tue Apr 02 22:30:06 UTC 2024 - 1.5K bytes - Viewed (0) -
manifests/zzz_profile.yaml
1. The builtin values.yaml defaults 2. The profile the user selects 3. Users input (-f or --set) Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2). However, we can workaround this by placing all of (1) under a specific key (.Values.defaults). We can then merge the profile onto the defaults, then the user settings onto that.
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Tue Apr 02 22:30:06 UTC 2024 - 1.5K bytes - Viewed (0) -
manifests/charts/base/templates/zzz_profile.yaml
1. The builtin values.yaml defaults 2. The profile the user selects 3. Users input (-f or --set) Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2). However, we can workaround this by placing all of (1) under a specific key (.Values.defaults). We can then merge the profile onto the defaults, then the user settings onto that.
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Tue Apr 02 22:30:06 UTC 2024 - 1.5K bytes - Viewed (0) -
manifests/charts/default/templates/zzz_profile.yaml
1. The builtin values.yaml defaults 2. The profile the user selects 3. Users input (-f or --set) Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2). However, we can workaround this by placing all of (1) under a specific key (.Values.defaults). We can then merge the profile onto the defaults, then the user settings onto that.
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Tue Apr 02 22:30:06 UTC 2024 - 1.5K bytes - Viewed (0)