-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add xms-ids for Privatedns #17975
Add xms-ids for Privatedns #17975
Conversation
Hi, @LinglingTong Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. vscswagger@microsoft.com |
[Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks. |
Swagger Validation Report
|
Rule | Message |
---|---|
R3021 - PathResourceTypeNameCamelCase |
Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/privateDnsZones/{privateZoneName}/ALL' Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1301 |
R4037 - MissingTypeObject |
The schema 'PrivateZoneProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1371 |
R4037 - MissingTypeObject |
The schema 'PrivateZone' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1434 |
R4037 - MissingTypeObject |
The schema 'PrivateZoneListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1453 |
R4037 - MissingTypeObject |
The schema 'VirtualNetworkLinkProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1470 |
R4037 - MissingTypeObject |
The schema 'VirtualNetworkLink' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1513 |
R4037 - MissingTypeObject |
The schema 'VirtualNetworkLinkListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1532 |
R4037 - MissingTypeObject |
The schema 'ARecord' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1549 |
R4037 - MissingTypeObject |
The schema 'AaaaRecord' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1558 |
R4037 - MissingTypeObject |
The schema 'CnameRecord' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1567 |
R4037 - MissingTypeObject |
The schema 'MxRecord' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1576 |
R4037 - MissingTypeObject |
The schema 'PtrRecord' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1590 |
R4037 - MissingTypeObject |
The schema 'SoaRecord' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1599 |
R4037 - MissingTypeObject |
The schema 'SrvRecord' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1637 |
R4037 - MissingTypeObject |
The schema 'TxtRecord' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1661 |
R4037 - MissingTypeObject |
The schema 'RecordSetProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1673 |
R4037 - MissingTypeObject |
The schema 'RecordSet' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1760 |
R4037 - MissingTypeObject |
The schema 'RecordSetListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1794 |
R4037 - MissingTypeObject |
The schema 'Resource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1811 |
R4037 - MissingTypeObject |
The schema 'TrackedResource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1832 |
R4037 - MissingTypeObject |
The schema 'SubResource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1870 |
The child tracked resource, 'virtualNetworkLinks' with immediate parent 'PrivateZone', must have a list by immediate parent operation. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L1513 |
|
The response of operation:'PrivateZones_CreateOrUpdate' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L31 |
|
The response of operation:'PrivateZones_Update' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L114 |
|
The response of operation:'PrivateZones_Get' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L243 |
|
The response of operation:'VirtualNetworkLinks_CreateOrUpdate' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L394 |
|
The response of operation:'VirtualNetworkLinks_Update' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L484 |
|
The response of operation:'VirtualNetworkLinks_Get' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L627 |
|
The response of operation:'RecordSets_CreateOrUpdate' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L745 |
|
The response of operation:'RecordSets_Update' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.Network/stable/2020-06-01/privatedns.json#L874 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
ApiReadinessCheck succeeded [Detail] [Expand]
️❌
ModelValidation: 2 Errors, 0 Warnings failed [Detail]
Rule | Message |
---|---|
OBJECT_ADDITIONAL_PROPERTIES |
Additional properties not allowed: minimumTTL Url: Microsoft.Network/stable/2020-06-01/privatedns.json#L1599:18 ExampleUrl: stable/2020-06-01/examples/RecordSetSOAPut.json#L9:19 |
OBJECT_ADDITIONAL_PROPERTIES |
Additional properties not allowed: minimumTTL Url: Microsoft.Network/stable/2020-06-01/privatedns.json#L1599:18 ExampleUrl: stable/2020-06-01/examples/RecordSetSOAPut.json#L48:27 |
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
Cross-Version Breaking Changes succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️
PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️
SDK Track2 Validation succeeded [Detail] [Expand]
Validation passes for SDKTrack2Validation
- The following tags are being changed in this PR
️️✔️
PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
Swagger Generation Artifacts
|
Hi @LinglingTong, Your PR has some issues. Please fix the CI sequentially by following the order of
|
Hi, @LinglingTong. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
@ruowan there are only a few lines of change in this PR and all the xms-ids look intuitive. Could you help with a code review and merging the PR? I also checked the model validation failures and they are not related to my changes. Thanks! |
Hi, @LinglingTong. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
@vladrai could you help to take a look at the code change? Thanks! |
Hi, @LinglingTong. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
@ruowan there are only a few places change in this PR and it should be fairly safe. I wonder maybe could you help me to take a look? Thanks! |
Hi, @LinglingTong. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
Ping @vladrai |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If changes can be done later looks good to me.
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Add a changelog entry for this PR by answering the following questions:
About this Change
APIs will need to start indicating item uniqueness in arrays. By default, uniqueness is the string property called "id" of items in an array. When that property does not exist, the x-ms-identifiers extension property must be used to specify the identifying property(s) or lack thereof. This pull request is my best guess effort to ease resource providers into the new requirement before it becomes enforced. Compliance and accuracy will need to be owned and maintained by the resource provider going forward.
See https://github.com/Azure/autorest/tree/main/docs/extensions#x-ms-identifiers.
You can also make changes after this PR is checked in. At this point, this annotation is only used by Change Analysis for change computation, so making changes afterwards shouldn’t be a breaking change.
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.
Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.