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
+5-2Lines changed: 5 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -538,12 +538,15 @@ The query values from the `sasKey` data field in the Secrets gets merged with th
538
538
If the same key is present in the both of them, the value in the `sasKey` takes precedence.
539
539
540
540
**Note:** SAS Token has an expiry date and it should be updated before it expires so that Flux can
541
-
continue to access Azure Storage. Also, The source-controller requires a bucket-level SAS token since it checks if the bucket exists and this fails with a container-level SAS token.
542
-
The minimum permissions for the SAS Token is:
541
+
continue to access Azure Storage. Also, The source-controller can use a account-level SAS token or a container-level SAS token.
542
+
The minimum permissions for an account-level SAS Token is:
543
543
- Allowed services: Blob
544
544
- Allowed resource types: Container, Object
545
545
- Allowed permission: Read, List
546
546
547
+
The minimum permissions for a container-level SAS Token is:
548
+
- Permission: Read, List
549
+
547
550
#### GCP
548
551
549
552
When a Bucket's `.spec.provider` is set to `gcp`, the source-controller will
0 commit comments