Merge branch 'main' into feature/cplat-2021-10-01

Author: grizzlytheodore

.github/PULL_REQUEST_TEMPLATE.md

@@ -43,7 +43,7 @@ Otherwise your PR may be subject to ARM review requirements. Complete the follow
   - Adding a new service
   - Adding new API(s)
   - Adding a new API version
-    -[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.
+    -[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the [wiki](https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/208/OpenAPI-Hub-Adding-new-API-version).
 
 - [ ] Ensure you've reviewed following [guidelines](https://aka.ms/rpguidelines) including [ARM resource provider contract](https://github.com/Azure/azure-resource-manager-rpc) and [REST guidelines](https://github.com/microsoft/api-guidelines/blob/vNext/azure/Guidelines.md). Estimated time (4 hours). This is required before you can request review from ARM API Review board.
 

.github/issue_assignment.yml

@@ -2,5 +2,5 @@
 - rule: 
     booleanFilterExpression: "APIStewardshipBoard-ReviewRequested"
     assignees:
-      - mikekistler
+      
 

.github/pull_request_assignment.yml

@@ -152,6 +152,14 @@
     reviewers:
       - zhenglaizhang
 
+- rule:
+    paths:
+      - "specification/videoanalyzer/resource-manager/**"
+      - "specification/cognitiveservices/resource-manager/**"
+      - "specification/dataprotection/**"
+    reviewers:
+      - xiaoxuqi-ms
+      
 - rule:
     paths:
       - "documentation/**"
@@ -190,4 +198,4 @@
       - changlong-liu
       - msyyc
       - qiaozha
-      - weidong
+      - dw511214992

CODEOWNERS

@@ -11,7 +11,7 @@
 /specification/batch/ @paterasMSFT @dpwatrous
 /specification/batchai/ @alexanderyukhanov
 /specification/billing/ @wilcobmsft @asarkar84
-/specification/cdn/ @csmengwan @injyzarif @prakharsharma10
+/specification/cdn/ @jorinmejia @yunhemsft @jessicl-ms @sinadell @rrahulms @t-bzhan
 /specification/cognitiveservices/ @felixwa @yangyuan
 /specification/compute/ @bilaakpan-ms @sandido @dkulkarni-ms @haagha @madewithsmiles @MS-syh2qs @grizzlytheodore @hyonholee @mabhard @danielli90 @smotwani @ppatwa @vikramd-ms @savyasachisamal @yunusm @ZhidongPeng @nkuchta @maheshnemichand @najams @changov
 /specification/consumption/ @kjeur @panda-wang
@@ -20,7 +20,7 @@
 /specification/containerservice/ @yangl900
 /specification/cosmos-db/ @dmakwana @MehaKaushik @wmengmsft @shurd
 /specification/customer-insights/ @tjlvtao
-/specification/datafactory/ @shawnxzq @zhangyd2015
+/specification/datafactory/ @Frey-Wang @zhangyd2015 @davidzhaoyue
 /specification/datalake-analytics/ @ro-joowan
 /specification/datalake-store/ @ro-joowan
 /specification/datamigration/ @hitenjava
@@ -85,4 +85,4 @@
 /specification/**/resource-manager/**/readme.az.md @jsntcy @qiaozha
 /specification/**/resource-manager/**/readme.cli.md @jsntcy @qiaozha
 /specification/**/resource-manager/**/readme.go.md @ArcturusZhang
-/specification/**/resource-manager/**/readme.python.md @msyyc @RAY-316 @BigCat20196
+/specification/**/resource-manager/**/readme.python.md @msyyc @BigCat20196

arm-compute/quickstart-templates/aliases.json

@@ -29,8 +29,8 @@
           },
           "openSUSE-Leap": {
             "publisher": "SUSE",
-            "offer": "openSUSE-Leap",
-            "sku": "42.3",
+            "offer": "opensuse-leap-15-3",
+            "sku": "gen2",
             "version": "latest"
           },
           "RHEL": {
@@ -41,8 +41,8 @@
           },
           "SLES": {
             "publisher": "SUSE",
-            "offer": "SLES",
-            "sku": "15",
+            "offer": "sles-15-sp3",
+            "sku": "gen2",
             "version": "latest"
           },
           "UbuntuLTS": {
@@ -53,6 +53,12 @@
           }
         },
         "Windows": {
+          "Win2022Datacenter": {
+            "publisher": "MicrosoftWindowsServer",
+            "offer": "WindowsServer",
+            "sku": "2022-Datacenter",
+            "version": "latest"
+          },
           "Win2019Datacenter": {
             "publisher": "MicrosoftWindowsServer",
             "offer": "WindowsServer",

custom-words.txt

@@ -1,4 +1,4 @@
-A128CBCPAD
+A128CBCPAD
 A192CBCPAD
 A256CBCPAD
 AADDS
@@ -301,6 +301,10 @@ browsable
 bruceper
 Bsaling
 bsls
+Buildpack
+Buildpacks
+buildpack
+buildpacks
 Burstable
 byoa
 BYOC
@@ -456,6 +460,7 @@ csrs
 currentbillingfeatures
 currentuser
 customerinsights
+customhostname
 customhostnames
 customimages
 customimagesearch
@@ -478,6 +483,7 @@ Cyrl
 dacl
 dailyforecast
 dailyhistorical
+dapr
 darkgrey
 Darussalam
 databox
@@ -531,6 +537,7 @@ decisionrule
 decodable
 Decompounder
 dedicatedhsm
+dedup
 deduping
 deduplication
 defanged
@@ -627,6 +634,7 @@ Dtus
 duration'PT
 dwgzippackage
 dynamicpersongroups
+Dynatrace
 EAPMSCHA
 EAPMSCHAP
 EAPTLS
@@ -1390,11 +1398,13 @@ offboard
 offboards
 officedocument
 OLTP
+OIDC
 onboarded
 Onboarding
 Onboards
 ondemand
 ondemandgc
+onedeploy
 onmachine
 omex
 onmicrosoft
@@ -1535,6 +1545,7 @@ Preprovisioned
 Prerelease
 prerestore
 pretrained
+prevalidated
 previewrows
 prevsharesnapshot
 prevsnapshot
@@ -1770,6 +1781,7 @@ runtimes
 rwdlacup
 rwxrw
 Saas
+Safenet
 salesforcetables
 saling
 salinuxvm
@@ -1919,6 +1931,7 @@ sqldatabase
 SQLDB
 SQLDW
 SQLMI
+sqlmigration
 sqlpool
 Sqlpools
 SQLRDS
@@ -2404,6 +2417,7 @@ DOCM
 PPSX
 PPTM
 XLSM
+xcool
 DOCM
 multislot
 noAddressPrefixes
@@ -2427,6 +2441,8 @@ Ctlr
 vcenters
 Mwarev
 pmem
+actuals
+Actuals
 rawphysical
 rawvirtual
 sesparse
@@ -2439,4 +2455,22 @@ stackset
 CSPM
 autoprovisioning
 schemagroups
-videoanalyzer
+videoanalyzer
+Unsecure
+Noreuse
+loadtestservice
+testmanager
+additionalmetrics
+loadtests
+appcomponents
+clientmetrics
+vusers
+clientmetric
+testruns
+odatatestxx
+testrun
+loadtest
+xvalue
+yvalue
+servermetrics
+IAASVM

documentation/Semantic-and-Model-Violations-Reference.md

@@ -9,6 +9,9 @@ This document lists the set of automated rules that can be validated against swa
 | [CIRCULAR_INHERITANCE](#CIRCULAR_INHERITANCE) | |
 | [DUPLICATE_PARAMETER](#DUPLICATE_PARAMETER) | |
 | [EMPTY_PATH_PARAMETER_DECLARATION](#EMPTY_PATH_PARAMETER_DECLARATION) | |
+| [EQUIVALENT_PATH](#EQUIVALENT_PATH) | |
+| [OBJECT_MISSING_REQUIRED_PROPERTY_DEFINITION](#OBJECT_MISSING_REQUIRED_PROPERTY_DEFINITION) | |
+| [OBJECT_MISSING_REQUIRED_PROPERTY_SCHEMA](#OBJECT_MISSING_REQUIRED_PROPERTY_SCHEMA) | |
 | [DUPLICATE_OPERATIONID](#DUPLICATE_OPERATIONID) | |
 | [MULTIPLE_BODY_PARAMETERS](#MULTIPLE_BODY_PARAMETERS) | |
 | [INVALID_PARAMETER_COMBINATION](#INVALID_PARAMETER_COMBINATION) | |
@@ -63,6 +66,7 @@ This document lists the set of automated rules that can be validated against swa
 | [READONLY_PROPERTY_NOT_ALLOWED_IN_REQUEST](#READONLY_PROPERTY_NOT_ALLOWED_IN_REQUEST) | |
 | [SCHEMA_VALIDATION_FAILED](#SCHEMA_VALIDATION_FAILED) | |
 | [SECRET_PROPERTY](#SECRET_PROPERTY) |  |
+| [WRITEONLY_PROPERTY_NOT_ALLOWED_IN_RESPONSE](#WRITEONLY_PROPERTY_NOT_ALLOWED_IN_RESPONSE) |  |
 | [DISCRIMINATOR_VALUE_NOT_FOUND](#DISCRIMINATOR_VALUE_NOT_FOUND) |  |
 | [INVALID_XMS_DISCRIMINATOR_VALUE](#INVALID_XMS_DISCRIMINATOR_VALUE) | [OAV133](#INVALID_XMS_DISCRIMINATOR_VALUE) |
 | [DISCRIMINATOR_PROPERTY_NOT_FOUND](#DISCRIMINATOR_PROPERTY_NOT_FOUND) | [OAV134](#DISCRIMINATOR_PROPERTY_NOT_FOUND) |
@@ -83,7 +87,7 @@ This document lists the set of automated rules that can be validated against swa
 | [RESPONSE_SCHEMA_NOT_IN_SPEC](#RESPONSE_SCHEMA_NOT_IN_SPEC) | [OAV113](#RESPONSE_SCHEMA_NOT_IN_SPEC) |
 | [RESPONSE_STATUS_CODE_NOT_IN_SPEC](#RESPONSE_STATUS_CODE_NOT_IN_SPEC) | [OAV112](#RESPONSE_STATUS_CODE_NOT_IN_SPEC) |
 | [RESPONSE_VALIDATION_ERROR](#RESPONSE_VALIDATION_ERROR) | [OAV108](#RESPONSE_VALIDATION_ERROR) |
-| [X-MS-EXAMPLE_NOTFOUND_ERROR](#X-MS-EXAMPLE_NOTFOUND_ERROR) | [OAV107](#X-MS-EXAMPLE_NOTFOUND_ERROR) |
+| [XMS_EXAMPLE_NOTFOUND_ERROR](#XMS_EXAMPLE_NOTFOUND_ERROR) | [OAV107](#XMS_EXAMPLE_NOTFOUND_ERROR) |
 | [ERROR_IN_PREPARING_REQUEST](#ERROR_IN_PREPARING_REQUEST) | [OAV106](#ERROR_IN_PREPARING_REQUEST) |
 | [REQUIRED_PARAMETER_EXAMPLE_NOT_FOUND](#REQUIRED_PARAMETER_EXAMPLE_NOT_FOUND) | [OAV105](#REQUIRED_PARAMETER_EXAMPLE_NOT_FOUND) |
 | [JSON_PARSING_ERROR](#JSON_PARSING_ERROR) | [OAV104](#JSON_PARSING_ERROR) |
@@ -97,6 +101,7 @@ This document lists the set of automated rules that can be validated against swa
 | [LRO_RESPONSE_CODE](#LRO_RESPONSE_CODE) | |
 | [LRO_RESPONSE_HEADER](#LRO_RESPONSE_HEADER) | |
 | [MISSING_RESOURCE_ID](#MISSING_RESOURCE_ID) | |
+| [INVALID_RESPONSE_HEADER](#INVALID_RESPONSE_HEADER) | |
 
 
 ### Validation Warnings
@@ -172,6 +177,22 @@ This document lists the set of automated rules that can be validated against swa
 
 **How to fix the violation**: Remove one of the equivalent paths or rename it.
 
+### <a name="OBJECT_MISSING_REQUIRED_PROPERTY_DEFINITION" />OBJECT_MISSING_REQUIRED_PROPERTY_DEFINITION
+
+**Output Message**: Missing required property definition: {0}.
+
+**Description**: Property indicated as required in "required" array for the model is missing its definition.
+
+**How to fix the violation**: Verify that the properties included in the "required" array have all been defined in swagger.
+
+### <a name="OBJECT_MISSING_REQUIRED_PROPERTY_SCHEMA" />OBJECT_MISSING_REQUIRED_PROPERTY_SCHEMA
+
+**Output Message**: Missing required property: {0}.
+
+**Description**: Property indicated as required according to [OpenAPI 2.0 specification](https://github.com/OAI/OpenAPI-Specification/blob/main/versions/2.0.md) for this schema.
+
+**How to fix the violation**: Adding this property to schema in swagger.
+
 ### <a name="EMPTY_PATH_PARAMETER_DECLARATION" />EMPTY_PATH_PARAMETER_DECLARATION
 
 **Output Message**: Path parameter declaration cannot be empty: {0}.
@@ -769,14 +790,6 @@ This document lists the set of automated rules that can be validated against swa
 
 **How to fix the violation**: See inner details for the violations and fix.
 
-### <a name="X-MS-EXAMPLE_NOTFOUND_ERROR" />X-MS-EXAMPLE_NOTFOUND_ERROR
-
-**Output Message**: x-ms-example not found in {0}.
-
-**Description**: Each operation should have example defined.
-
-**How to fix the violation**: Add `x-ms-example` declaration for this operation.
-
 ### <a name="ERROR_IN_PREPARING_REQUEST" />ERROR_IN_PREPARING_REQUEST
 
 **Description**: Error when preparing the request for validation.
@@ -818,7 +831,15 @@ This document lists the set of automated rules that can be validated against swa
 
 **Description**: The secret is not allowed to return in response when it's annotated with x-ms-secret:true.
 
-**How to fix the violation**: Remove this secret value from the response.
+**How to fix the violation**: Remove this secret value from the response in example or in traffic payload.
+
+### <a name="WRITEONLY_PROPERTY_NOT_ALLOWED_IN_RESPONSE" />WRITEONLY_PROPERTY_NOT_ALLOWED_IN_RESPONSE
+
+**Output Message**: Write-only property {0} is not allowed in the response.
+
+**Description**: Write only property is not allowed to return in response when it's annotated with "x-ms-mutability": ["create", "update"].
+
+**How to fix the violation**: Remove this property from the response in example or in traffic payload.
 
 
 ### <a name="ROUNDTRIP_INCONSISTENT_PROPERTY" />ROUNDTRIP_INCONSISTENT_PROPERTY
@@ -861,22 +882,38 @@ This document lists the set of automated rules that can be validated against swa
 
 **Output Message**: Respond to the initial request of a long running operation, Patch/Post call must return 201 or 202, Delete call must return 202 or 204, Put call must return 202 or 201 or 200, but {statusCode} being returned.
 
-**Description**: Long running operation must return specific response code as per http method type when this operation is annotated with x-ms-long-running-operation:true. See [RPC - Asynchronous Operations](https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/Addendum.md#asynchronous-operations) for more details.
+**Description**: Long running operation must return specific response code as per http method type in example or in traffic payload when this operation is annotated with x-ms-long-running-operation:true. See [RPC - Asynchronous Operations](https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/Addendum.md#asynchronous-operations) for more details.
 
-**How to fix the violation**: Correct the response code per the guidance or remove annotation of x-ms-long-running-operation.
+**How to fix the violation**: Correct the response code per the guidance or remove annotation of x-ms-long-running-operation in example or in traffic payload.
 
 ### <a name="LRO_RESPONSE_HEADER" />LRO_RESPONSE_HEADER
 
 **Output Message**: Long running operation should return {header} in header but not being provided.
 
 **Description**: Long running operation must return location header or azure-AsyncOperation header in response when this operation is annotated with x-ms-long-running-operation:true.
 
-**How to fix the violation**: Adding one of these headers to the response.
+**How to fix the violation**: Adding one of these headers to the response in example or in traffic payload.
 
 ### <a name="MISSING_RESOURCE_ID" />MISSING_RESOURCE_ID
 
 **Output Message**: id is required to return in response of GET/PUT resource calls but not being provided.
 
 **Description**: `id` is a required field of azure resource to return in response body of each GET or PUT call when this resource is annotated as x-ms-azure-resource: true. This field is important to the platform because it is used as the identifier for references on other objects. e.g. "id": "/subscriptions/{id}/resourceGroups/{group}/providers/{rpns}/{type}/{name}".
 
-**How to fix the violation**: Adding id to the response body.
+**How to fix the violation**: Adding id to the response body in example or in traffic payload.
+
+### <a name="XMS_EXAMPLE_NOTFOUND_ERROR" />XMS_EXAMPLE_NOTFOUND_ERROR
+
+**Output Message**: "x-ms-example" not found in {"operationId"} operation.
+
+**Description**: Example is required to provide for each operation and it's annotated by "x-ms-example". Example is important because it is displayed in rest API document. See [x-ms-examples](https://github.com/Azure/azure-rest-api-specs/blob/main/documentation/x-ms-examples.md) for details.
+
+**How to fix the violation**: Adding separated example JSON file and reference it with "x-ms-examples" annotation in swagger.
+
+### <a name="INVALID_RESPONSE_HEADER" />INVALID_RESPONSE_HEADER
+
+**Output Message**: Header {header} is required in response but not provided.
+
+**Description**: {header} is declared in response schema in swagger but it's not provided in response in example or in traffic payload.
+
+**How to fix the violation**: Adding this {header} to the response in example or in traffic payload.