aboutsummaryrefslogtreecommitdiff
path: root/weed/command/s3.go
diff options
context:
space:
mode:
authorChris Lu <chrislusf@users.noreply.github.com>2025-07-23 11:44:36 -0700
committerGitHub <noreply@github.com>2025-07-23 11:44:36 -0700
commit5ac037f763e20ffb9559e3ea0caf3bbe82589650 (patch)
treeff733250ab085669c7cb35630579e44e1fc22a17 /weed/command/s3.go
parentdd464cd339de354937bc6af4fec6e12211cece69 (diff)
downloadseaweedfs-5ac037f763e20ffb9559e3ea0caf3bbe82589650.tar.xz
seaweedfs-5ac037f763e20ffb9559e3ea0caf3bbe82589650.zip
change priority of admin credentials from env varaibles (#7032)
* change priority of admin credentials from env varaibles * address comment
Diffstat (limited to 'weed/command/s3.go')
-rw-r--r--weed/command/s3.go8
1 files changed, 4 insertions, 4 deletions
diff --git a/weed/command/s3.go b/weed/command/s3.go
index 8dcb681b9..027bb9cd0 100644
--- a/weed/command/s3.go
+++ b/weed/command/s3.go
@@ -160,13 +160,13 @@ var cmdS3 = &Command{
]
}
- Alternatively, you can use environment variables to supplement admin credentials:
+ Alternatively, you can use environment variables as fallback admin credentials:
AWS_ACCESS_KEY_ID=your_access_key AWS_SECRET_ACCESS_KEY=your_secret_key weed s3
- This will add admin credentials from environment variables to any existing
- configuration. Environment variables are added after loading file/filer
- configurations and are skipped if the same access key already exists.
+ Environment variables are only used when no S3 configuration file is provided
+ and no configuration is available from the filer. This provides a simple way
+ to get started without requiring configuration files.
`,
}