- Sort Score
- Result 10 results
- Languages All
Results 1 - 7 of 7 for wasm (0.5 sec)
-
docs/multi-user/README.md
"s3:GetObject", "s3:PutObject" ], "Effect": "Allow", "Resource": ["arn:aws:s3:::mybucket/${aws:username}/*"] } ] } ``` If the user is authenticating using an STS credential which was authorized from OpenID connect we allow all `jwt:*` variables specified in the JWT specification, custom `jwt:*` or extensions are not supported. List of policy variables for OpenID based STS. - `jwt:sub` - `jwt:iss`
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Mar 21 06:38:06 GMT 2023 - 8K bytes - Viewed (0) -
internal/grid/README.md
conn := manager.Connection(host) payload := []byte("request") response, err := conn.SingleRequest(ctx, grid.HandlerDiskInfo, payload) ``` If the error type is `*RemoteErr`, then the error was returned by the remote server. Otherwise it is a local error. Context timeouts are propagated, and a default timeout of 1 minute is added if none is specified. There is no cancellation propagation for single payload requests.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 9.4K bytes - Viewed (0) -
docs/integrations/veeam/README.md
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 5.4K bytes - Viewed (0) -
docs/bucket/notifications/README.md
} ] } } ``` This output shows that a document has been created for the event in Elasticsearch. Here we see that the document ID is the bucket and object name. In case `access` format was used, the document ID would be automatically generated by Elasticsearch. ## Publish MinIO events via Redis
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 84K bytes - Viewed (2) -
docs/bigdata/README.md
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 14.7K bytes - Viewed (0) -
docs/bucket/replication/README.md
the `X-Amz-Replication-Status` changes from `PENDING` to `COMPLETED` or `FAILED` after replication attempt either succeeded or failed respectively. On the destination side, a `X-Amz-Replication-Status` status of `REPLICA` indicates that the object was replicated successfully. Any replication failures are automatically re-attempted during a periodic disk scanner cycle. To perform bi-directional replication, repeat the above process on the target site - this time setting the source bucket...
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Jan 24 23:46:33 GMT 2023 - 18.2K bytes - Viewed (0) -
docs/logging/README.md
- Additionally in the case of the erasure coded setup `tags.objectErasureMap` provides per object details about - Pool number the object operation was performed on. - Set number the object operation was performed on. - The list of drives participating in this operation belong to the set. ```json { "version": "1", "deploymentid": "51bcc7b9-a447-4251-a940-d9d0aab9af69",
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Aug 15 23:04:20 GMT 2023 - 9.9K bytes - Viewed (2)