Package version
Additional parameters for the operation
Optional. User-defined properties to be stored with the file or directory, in the format of a comma-separated list of name and value pairs "n1=v1, n2=v2, ...", where each value is base64 encoded.
Additional parameters for the operation
Additional parameters for the operation
Determines the behavior of the rename operation. Possible values include: 'legacy', 'posix'
Optional and only valid if Hierarchical Namespace is enabled for the account. Sets POSIX access permissions for the file owner, the file owning group, and others. Each class may be granted read, write, or execute permission. The sticky bit is also supported. Both symbolic (rwxrw-rw-) and 4-digit octal notation (e.g. 0766) are supported.
Only valid if Hierarchical Namespace is enabled for the account. This umask restricts permission settings for file and directory, and will only be applied when default Acl does not exist in parent directory. If the umask bit has set, it means that the corresponding permission will be disabled. Otherwise the corresponding permission will be determined by the permission. A 4-digit octal notation (e.g. 0022) is supported here. If no umask was specified, a default umask - 0027 will be used.
Provides a client-generated, opaque value with a 1 KB character limit that is recorded in the analytics logs when storage analytics logging is enabled.
A lease ID for the source path. If specified, the source path must have an active lease and the leaase ID must match.
Additional parameters for the operation
The timeout parameter is expressed in seconds. For more information, see Setting Timeouts for Blob Service Operations.
Generated using TypeDoc
Optional Parameters.