You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/spec/v1beta2/buckets.md
+14-2
Original file line number
Diff line number
Diff line change
@@ -537,8 +537,20 @@ The leading question mark is optional.
537
537
The query values from the `sasKey` data field in the Secrets gets merged with the ones in the `spec.endpoint` of the `Bucket`.
538
538
If the same key is present in the both of them, the value in the `sasKey` takes precedence.
539
539
540
-
Note that the Azure SAS Token has an expiry date and it should be updated before it expires so that Flux can
541
-
continue to access Azure Storage.
540
+
**Note:** The SAS token has an expiry date and it must be updated before it expires to allow Flux to
541
+
continue to access Azure Storage. It is allowed to use an account-level or container-level SAS token.
542
+
543
+
The minimum permissions for an account-level SAS token are:
544
+
545
+
- Allowed services: `Blob`
546
+
- Allowed resource types: `Container`, `Object`
547
+
- Allowed permissions: `Read`, `List`
548
+
549
+
The minimum permissions for a container-level SAS token are:
550
+
551
+
- Allowed permissions: `Read`, `List`
552
+
553
+
Refer to the [Azure documentation](https://learn.microsoft.com/en-us/rest/api/storageservices/create-account-sas#blob-service) for a full overview on permissions.
0 commit comments