swagger: '2.0' info: version: 2020-08-01-preview title: Microsoft Azure AccessControlClient AccessConnector File Locks API schemes: - https tags: - name: File Locks paths: ? /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NetApp/netAppAccounts/{accountName}/capacityPools/{poolName}/volumes/{volumeName}/breakFileLocks : post: tags: - File Locks summary: Microsoft Azure Break File Locks description: Break all the file locks on a volume operationId: microsoftAzureVolumesBreakfilelocks parameters: - $ref: ../../../../../common-types/resource-management/v5/types.json#/parameters/SubscriptionIdParameter - $ref: ../../../../../common-types/resource-management/v5/types.json#/parameters/ResourceGroupNameParameter - $ref: '#/parameters/AccountName' - $ref: '#/parameters/PoolName' - $ref: '#/parameters/VolumeName' - $ref: ../../../../../common-types/resource-management/v5/types.json#/parameters/ApiVersionParameter - name: body description: Optional body to provide the ability to clear file locks with selected options in: body required: false schema: $ref: '#/definitions/breakFileLocksRequest' responses: '200': description: OK - terminal state '202': description: Accepted headers: Location: type: string default: description: Error response describing why the operation failed. schema: $ref: ../../../../../common-types/resource-management/v5/types.json#/definitions/ErrorResponse x-ms-long-running-operation: true x-ms-long-running-operation-options: final-state-via: location x-ms-examples: Volumes_BreakFileLocks: $ref: examples/Volumes_BreakFileLocks.json definitions: breakFileLocksRequest: description: Break file locks request type: object properties: clientIp: type: string description: To clear file locks on a volume for a particular client pattern: ^(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)$ example: 101.102.103.104 confirmRunningDisruptiveOperation: type: boolean description: Break File locks could be a disruptive operation for application as locks on the volume will be broken, if want to process, set to true. default: false parameters: AccountName: name: accountName type: string pattern: ^[a-zA-Z0-9][a-zA-Z0-9\-_]{0,127}$ in: path required: true description: The name of the NetApp account x-ms-parameter-location: method PoolName: name: poolName type: string in: path required: true pattern: ^[a-zA-Z0-9][a-zA-Z0-9\-_]{0,63}$ minLength: 1 maxLength: 64 description: The name of the capacity pool x-ms-parameter-location: method VolumeName: name: volumeName type: string in: path required: true pattern: ^[a-zA-Z][a-zA-Z0-9\-_]{0,63}$ minLength: 1 maxLength: 64 description: The name of the volume x-ms-parameter-location: method x-ms-parameterized-host: hostTemplate: '{endpoint}' useSchemePrefix: false parameters: - $ref: '#/parameters/Endpoint'