- Sort Score
- Result 10 results
- Languages All
Results 391 - 400 of 729 for Command (3.43 sec)
-
docs/sts/assume-role.md
``` [foobar] region = us-east-1 aws_access_key_id = foobar aws_secret_access_key = foo12345 ``` > NOTE: In the following commands `--role-arn` and `--role-session-name` are not meaningful for MinIO and can be set to any value satisfying the command line requirements. ```
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 7.2K bytes - Viewed (0) -
Jenkinsfile
* * mavenBuild("<jdk>", "<profiles> <goals> <plugins> <properties>" * * @param jdk the jdk tool name (in jenkins) to use for this build * @param extraArgs extra command line args */ def mavenBuild(jdk, extraArgs) { script { try { withEnv(["JAVA_HOME=${tool "$jdk"}", "PATH+MAVEN=${tool "$jdk"}/bin:${tool "maven_3_latest"}/bin",
Registered: Sun Dec 28 03:35:09 UTC 2025 - Last Modified: Thu Jul 10 12:31:48 UTC 2025 - 2K bytes - Viewed (0) -
helm-releases/minio-3.3.2.tgz
rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sat Dec 11 17:26:01 UTC 2021 - 14.6K bytes - Viewed (0) -
helm-releases/minio-3.3.4.tgz
rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sat Dec 11 17:59:34 UTC 2021 - 14.6K bytes - Viewed (0) -
helm-releases/minio-3.4.2.tgz
rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Dec 21 02:58:25 UTC 2021 - 15.2K bytes - Viewed (0) -
helm-releases/minio-3.4.4.tgz
rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Fri Dec 31 04:21:24 UTC 2021 - 15.2K bytes - Viewed (0) -
helm-releases/minio-3.4.5.tgz
rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Wed Jan 05 19:32:55 UTC 2022 - 15.2K bytes - Viewed (0) -
helm-releases/minio-3.5.3.tgz
rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. ### Upgrading the Chart You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sun Feb 13 23:43:44 UTC 2022 - 15.4K bytes - Viewed (0) -
compat/maven-model-builder/src/main/java/org/apache/maven/model/profile/ProfileActivationContext.java
/** * Gets the user properties to use for interpolation and profile activation. The user properties have been * configured directly by the user on his discretion, e.g. via the {@code -Dkey=value} parameter on the command * line. * * @return The user properties, never {@code null}. */ Map<String, String> getUserProperties(); /** * Gets the base directory of the current project (if any). *Registered: Sun Dec 28 03:35:09 UTC 2025 - Last Modified: Tue Feb 25 08:27:34 UTC 2025 - 2.9K bytes - Viewed (0) -
docs/site-replication/run-multi-site-minio-idp.sh
./mc admin policy info minio1 rw if [ $? -eq 0 ]; then echo "expecting the command to fail, exiting.." exit_1 fi ./mc admin policy info minio2 rw if [ $? -eq 0 ]; then echo "expecting the command to fail, exiting.." exit_1 fi ./mc admin policy info minio3 rw if [ $? -eq 0 ]; then echo "expecting the command to fail, exiting.." exit_1 fi ./mc admin user info minio1 foobar
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Sep 24 08:03:58 UTC 2024 - 12.1K bytes - Viewed (0)