From 8ad6227767a3a3ffd03bd3301d5044d65d08e687 Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Mon, 13 Apr 2026 13:12:06 -0700 Subject: [PATCH] provision --- S3-Credentials.md | 3 +++ weed-shell.md | 2 +- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/S3-Credentials.md b/S3-Credentials.md index b2a88ec..fdb80e6 100644 --- a/S3-Credentials.md +++ b/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 diff --git a/weed-shell.md b/weed-shell.md index 2d9bc9d..6a04e60 100644 --- a/weed-shell.md +++ b/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 ```