Initiates the process to change the container's access mode
v1/{account}/{container}?accessmode
x-emc-file-access-mode | required | access mode to switch to. Transition to ReadOnly from ReadWrite and to ReadWrite from ReadOnly are not supported. Valid values: Disabled, ReadOnly, ReadWrite |
x-emc-file-access-duration | optional | in seconds for which the access mode should be enforced. |
x-emc-file-access-host-list | required | list of hosts or subnets which are allowed to mount the file system |
x-emc-file-access-uid | required | ID specified by the client while accessing the objects belonging to the resource (bucket) whose access mode is being changed |
x-emc-file-access-token | optional | to identify the objects that are to be granted file access. The ViPR system provides this token to the client in response to the Access Mode PUT operation. When the user included this token in the future PUT requests the ViPR system can identify the objects that were and were not present when this token was generated. Default: NULL (applies the access mode change to all the objects in the bucket) |
The following conditions must be met in order to call this operation.
container and account corresponding to this container should exist
No Request Payload
x-emc-file-access-mode | always | the access mode the ViPR system is currently enforcing on the objects in the bucket |
x-emc-file-access-duration | always | the time after which the file access mode will fall back to being default unless it is renewed with another PUT request. |
x-emc-file-access-host-list | always | list of hosts or subnets which will be allowed to mount the file system |
x-emc-file-access-uid | always | ID that will have access to the objects |
x-emc-file-access-token | always | be saved and used by the client in future requests to identify the objects that will be affected by the current operation. |
The response does not have a body on success.