- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 64 for users5 (0.27 sec)
-
src/main/java/org/codelibs/fess/es/user/cbean/ca/bs/BsUserCA.java
*/ package org.codelibs.fess.es.user.cbean.ca.bs; import org.codelibs.fess.es.user.allcommon.EsAbstractConditionAggregation; import org.codelibs.fess.es.user.allcommon.EsAbstractConditionQuery; import org.codelibs.fess.es.user.cbean.ca.UserCA; import org.codelibs.fess.es.user.cbean.cq.UserCQ; import org.codelibs.fess.es.user.cbean.cq.bs.BsUserCQ;
Registered: Wed Jun 12 13:08:18 UTC 2024 - Last Modified: Thu Feb 22 01:37:57 UTC 2024 - 212.4K bytes - Viewed (1) -
cluster/gce/gci/configure-helper.sh
create-kubelet-kubeconfig "${KUBELET_APISERVER}" fi } function create-kubeproxy-user-kubeconfig { echo "Creating kube-proxy user kubeconfig file" cat <<EOF >/var/lib/kube-proxy/kubeconfig apiVersion: v1 kind: Config users: - name: kube-proxy user: token: ${KUBE_PROXY_TOKEN} clusters: - name: local cluster:
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Mon Jun 10 22:07:47 UTC 2024 - 141.1K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.5.md
1. Export existing PodSecurityPolicy objects: * `kubectl get podsecuritypolicies -o yaml > psp.yaml` 2. Review and delete any PodSecurityPolicy objects you do not want all pod-creating users to be able to use (NOTE: Privileged users that were making use of those policies will also lose access to those policies). For example: * `kubectl delete podsecuritypolicies/my-privileged-policy` 3. After upgrading to 1.5.5, re-create the exported PodSecurityPolicy objects:
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Thu Dec 24 02:28:26 UTC 2020 - 136.4K bytes - Viewed (0) -
cmd/site-replication.go
} } return nil } // heal all users and their service accounts that are present on this site, // provided current cluster has the most recent update. func (c *SiteReplicationSys) healUsers(ctx context.Context, objAPI ObjectLayer, user string, info srStatusInfo) error { // create user if missing; fix user policy mapping if missing us := info.UserStats[user] c.RLock() defer c.RUnlock() if !c.enabled {
Registered: Sun Jun 16 00:44:34 UTC 2024 - Last Modified: Fri May 24 23:05:23 UTC 2024 - 184.3K bytes - Viewed (0) -
pkg/printers/internalversion/printers.go
{Name: "Role", Type: "string", Description: rbacv1beta1.RoleBinding{}.SwaggerDoc()["roleRef"]}, {Name: "Age", Type: "string", Description: metav1.ObjectMeta{}.SwaggerDoc()["creationTimestamp"]}, {Name: "Users", Type: "string", Priority: 1, Description: "Users in the roleBinding"}, {Name: "Groups", Type: "string", Priority: 1, Description: "Groups in the roleBinding"},
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Tue Jun 11 14:04:15 UTC 2024 - 128.3K bytes - Viewed (0) -
api/openapi-spec/v3/apis__certificates.k8s.io__v1alpha1_openapi.json
"description": "ManagedFields maps workflow-id and version to the set of fields that are managed by that workflow. This is mostly for internal housekeeping, and users typically shouldn't need to set or understand this field. A workflow can be the user's name, a controller's name, or the name of a specific apply path like \"ci-cd\". The set of fields is always in the version that the workflow used when modifying the object.", "items": {
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Fri Mar 08 04:18:56 UTC 2024 - 119K bytes - Viewed (0) -
fastapi/applications.py
You can **read items**. ## Users You will be able to: * **Create users** (_not implemented_). * **Read users** (_not implemented_). """ ) ``` '''
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Sat May 18 00:48:03 UTC 2024 - 172.2K bytes - Viewed (0) -
src/database/sql/sql.go
closed bool // closemuScanHold is whether the previous call to Scan kept closemu RLock'ed // without unlocking it. It does that when the user passes a *RawBytes scan // target. In that case, we need to prevent awaitDone from closing the Rows // while the user's still using the memory. See go.dev/issue/60304. // // It is only used by Scan, Next, and NextResultSet which are expected // not to be called concurrently.
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Thu May 23 01:16:53 UTC 2024 - 103.6K bytes - Viewed (0) -
api/maven-api-model/src/main/mdo/maven.mdo
</field> <field> <name>notifiers</name> <version>4.0.0+</version> <description>Configuration for notifying developers/users when a build is unsuccessful, including user information and notification mode.</description> <association> <multiplicity>*</multiplicity> <type>Notifier</type> </association>
Registered: Wed Jun 12 09:55:16 UTC 2024 - Last Modified: Tue Apr 23 13:29:46 UTC 2024 - 115.1K bytes - Viewed (0) -
api/openapi-spec/v3/apis__storagemigration.k8s.io__v1alpha1_openapi.json
"description": "ManagedFields maps workflow-id and version to the set of fields that are managed by that workflow. This is mostly for internal housekeeping, and users typically shouldn't need to set or understand this field. A workflow can be the user's name, a controller's name, or the name of a specific apply path like \"ci-cd\". The set of fields is always in the version that the workflow used when modifying the object.", "items": {
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Fri Mar 08 04:18:56 UTC 2024 - 133.3K bytes - Viewed (0)