This PR provides a couple of features related to mount storages process.
CP_CAP_LIMIT_MOUNTS , CP_CAP_SKIP_MOUNTS and CP_CAP_FORCE_MOUNTS parameters shall respect storage paths.
Background
Datastorages may be unregistered and registered again with a new ID.
Usage example:
CP_CAP_LIMIT_MOUNTS=1,2,bucket,3,bucket2/path2
Note: This PR provides changes for mount during the launch run case. pipe-fuse process may fail in running launches due to inability to refresh temporary credentials.
Implement an ability to rewrite mount options for separate launch for specific storages.
add CP_CAP_MOUNT_OPTIONS_ prefix to run parameters
This PR provides a couple of features related to mount storages process.
CP_CAP_LIMIT_MOUNTS
,CP_CAP_SKIP_MOUNTS
andCP_CAP_FORCE_MOUNTS
parameters shall respect storage paths.Background
Datastorages may be unregistered and registered again with a new ID.
Usage example:
Note: This PR provides changes for mount during the launch run case.
pipe-fuse
process may fail in running launches due to inability to refresh temporary credentials.CP_CAP_MOUNT_OPTIONS_
prefix to run parametersUsage example:
CP_CAP_AUTOSCALE_INHERITABLE_PARAMETER_PREFIXES
var