Changed the Region Move specification to official name of the service… (

#11131)

* Changed the Region Move specification to official name of the service ResourceMover

* Added Lint corrections

Co-authored-by: Ajay Gupta <ajgupt@microsoft.com>

specification/regionmove/resource-manager/Microsoft.Migrate/preview/2019-10-01-preview/examples/MoveCollections_BulkRemove.json → specification/resourcemover/resource-manager/Microsoft.Migrate/preview/2019-10-01-preview/examples/MoveCollections_Prepare.json

@@ -4,10 +4,12 @@
     "subscriptionId": "subid",
     "resourceGroupName": "rg1",
     "api-version": "2019-10-01-preview",
-    "validateOnly": false,
-    "moveResources": [
-      "/subscriptions/subid/resourceGroups/rg1/providers/Microsoft.Migrate/MoveCollections/movecollection1/MoveResources/moveresource1"
-    ]
+    "body": {
+      "validateOnly": false,
+      "moveResources": [
+        "/subscriptions/subid/resourceGroups/rg1/providers/Microsoft.Migrate/MoveCollections/movecollection1/MoveResources/moveresource1"
+      ]
+    }
   },
   "responses": {
     "200": {

specification/regionmove/resource-manager/Microsoft.Migrate/preview/2019-10-01-preview/regionmovecollection.json → specification/resourcemover/resource-manager/Microsoft.Migrate/preview/2019-10-01-preview/resourcemovercollection.json

@@ -1610,6 +1610,10 @@
           "description": "Gets or sets Name of the API.\r\nThe name of the operation being performed on this particular object. It should\r\nmatch the action name that appears in RBAC / the event service.\r\nExamples of operations include:\r\n* Microsoft.Compute/virtualMachine/capture/action\r\n* Microsoft.Compute/virtualMachine/restart/action\r\n* Microsoft.Compute/virtualMachine/write\r\n* Microsoft.Compute/virtualMachine/read\r\n* Microsoft.Compute/virtualMachine/delete\r\nEach action should include, in order:\r\n(1) Resource Provider Namespace\r\n(2) Type hierarchy for which the action applies (e.g. server/databases for a SQL\r\nAzure database)\r\n(3) Read, Write, Action or Delete indicating which type applies. If it is a PUT/PATCH\r\non a collection or named value, Write should be used.\r\nIf it is a GET, Read should be used. If it is a DELETE, Delete should be used. If it\r\nis a POST, Action should be used.\r\nAs a note: all resource providers would need to include the \"{Resource Provider\r\nNamespace}/register/action\" operation in their response.\r\nThis API is used to register for their service, and should include details about the\r\noperation (e.g. a localized name for the resource provider + any special\r\nconsiderations like PII release).",
           "type": "string"
         },
+        "isDataAction": {
+          "description": "Indicates whether the operation is a data action",
+          "type": "boolean"
+        },
         "display": {
           "$ref": "#/definitions/Display"
         },

specification/regionmove/resource-manager/readme.azureresourceschema.md → specification/resourcemover/resource-manager/readme.azureresourceschema.md

@@ -19,6 +19,6 @@ output-folder: $(azureresourceschema-folder)/schemas
 
 # all the input files in this apiVersion
 input-file:
-  - Microsoft.Migrate/preview/2019-10-01-preview/regionmovecollection.json
+  - Microsoft.Migrate/preview/2019-10-01-preview/resourcemovercollection.json
 
 ```

specification/regionmove/resource-manager/readme.md → specification/resourcemover/resource-manager/readme.md

@@ -35,7 +35,7 @@ These settings apply only when `--tag=package-2019-10-01-preview` is specified o
 
 ```yaml $(tag) == 'package-2019-10-01-preview'
 input-file:
-  - Microsoft.Migrate/preview/2019-10-01-preview/regionmovecollection.json
+  - Microsoft.Migrate/preview/2019-10-01-preview/resourcemovercollection.json
 ```
 
 ---