Skip to content

Update guide for ch acl commands to better reflect difference between gsutil and gcloud storage format #1911

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sushantkhanna wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update guide for ch acl commands to better reflect difference between gsutil and gcloud storage format #1911

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions GCLOUD-MIGRATION.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,6 +83,11 @@ Replaced by `gcloud storage {buckets|objects} describe` and `gcloud storage {buc

**`gsutil acl ch` -> `gcloud storage <RESOURCE> update`**

Please note, for Gsutil, we followed a format of ENTITY:ROLE. For Gcloud, this format changes to a key-value pair, similar to `entity=user-tim@gmail.com,role=OWNER` for the `-u` flag as an example.
We need to append a prefix for emails/ids entities depending on the flag. For `-u` it is `user-`, for `-g`, it is `group-` and for `-p` it is `project-`.

Also, in Gsutil, we used to utilise abbreviations for roles themselves, like R for READ, W for Write, etc. For Gcloud, we want to use the full terms similar to JSON for GCS as can be found in [documentation](https://docs.cloud.google.com/storage/docs/access-control/lists#permissions).

| gsutil Flag | gcloud storage Flag | Applies To | Notes |
| --- | --- | --- | --- |
| -u | --add-acl-grant=GRANT | Buckets/Objects | Adds grant for a user. Format: ENTITY:ROLE |
Expand Down Expand Up @@ -115,6 +120,11 @@ Replaced by `gcloud storage buckets describe` and `gcloud storage buckets update

**`gsutil defacl ch` -> `gcloud storage buckets update`**

Please note, for Gsutil, we followed a format of ENTITY:ROLE. For Gcloud, this format changes to a key-value pair, similar to `entity=user-tim@gmail.com,role=OWNER` for the `-u` flag as an example.
We need to append a prefix for emails/ids entities depending on the flag. For `-u` it is `user-`, for `-g`, it is `group-` and for `-p` it is `project-`.

Also, in Gsutil, we used to utilise abbreviations for roles themselves, like R for READ, W for Write, etc. For Gcloud, we want to use the full terms similar to JSON for GCS as can be found in [documentation](https://docs.cloud.google.com/storage/docs/access-control/lists#permissions).

| gsutil Flag | gcloud storage Flag | Notes |
| --- | --- | --- |
| -u | --add-default-object-acl-grant=GRANT | Adds grant for a user. Format: ENTITY:ROLE. |
Expand Down
Loading