provision

S3-Credentials.md

@@ -288,6 +288,9 @@ Bucket-specific permissions work with all configuration methods:
 # One-step: create user with a readwrite policy for a specific bucket
 s3.user.provision -name bucket1_user -bucket mybucket -role readwrite
 
+# Grant the same user access to another bucket (skips user creation, attaches policy)
+s3.user.provision -name bucket1_user -bucket otherbucket -role readonly
+
 # Or step-by-step:
 s3.user.create -name bucket1_user
 s3.policy -put -name mybucket-policy -file mybucket-policy.json

weed-shell.md

@@ -257,7 +257,7 @@ Or use the one-step convenience command:
 ```
 
 Roles: `readonly`, `readwrite`, `admin`. The bucket must be a literal name (no wildcards).
-If the user already exists, the command fails without creating an orphaned policy.
+If the user already exists, the command skips user creation and attaches the new policy to the existing user (no new credentials are printed).
 
 ### Manage credentials
 ```