-
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
trafficmanager: adding the missing enum values for traffic manager endpoint #16472
trafficmanager: adding the missing enum values for traffic manager endpoint #16472
Conversation
…dpoint These are required in the API but undocumented - so pulling these out explicitly
Hi, @tombuildsstuff 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. [email protected] |
Swagger pipeline started successfully, please wait for status update in this comment. |
[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 pipeline started successfully, please wait for status update in this comment. |
Thank you for your contribution tombuildsstuff! We will review the pull request and get back to you soon. |
ping @msyyc |
/azp run |
Swagger Validation Report
|
Rule | Message |
---|---|
R4011 - DeleteOperationResponses |
The delete operation is defined without a 200 or 204 error response implementation,please add it.' Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L930 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1051 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1113 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1117 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1194 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1325 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1329 |
R4015 - NestedResourcesMustHaveListOperation |
The nested resource 'HeatMapModel' does not have list operation, please add it. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1081 |
R4037 - MissingTypeObject |
The schema 'DeleteOperationResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L953 |
R4037 - MissingTypeObject |
The schema 'EndpointProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L964 |
R4037 - MissingTypeObject |
The schema 'HeatMapModel' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1081 |
R4037 - MissingTypeObject |
The schema 'UserMetricsModel' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1096 |
R4037 - MissingTypeObject |
The schema 'QueryExperience' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1111 |
R4037 - MissingTypeObject |
The schema 'TrafficFlow' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1133 |
R4037 - MissingTypeObject |
The schema 'HeatMapProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1159 |
R4037 - MissingTypeObject |
The schema 'HeatMapEndpoint' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1188 |
R4037 - MissingTypeObject |
The schema 'Endpoint' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1201 |
R4037 - MissingTypeObject |
The schema 'CheckTrafficManagerRelativeDnsNameAvailabilityParameters' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1216 |
R4037 - MissingTypeObject |
The schema 'DnsConfig' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1229 |
R4037 - MissingTypeObject |
The schema 'MonitorConfig' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1248 |
R4037 - MissingTypeObject |
The schema 'ProfileProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1341 |
R4037 - MissingTypeObject |
The schema 'Profile' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1427 |
R4037 - MissingTypeObject |
The schema 'ProfileListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1442 |
R4037 - MissingTypeObject |
The schema 'TrafficManagerNameAvailability' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1454 |
R4037 - MissingTypeObject |
The schema 'Region' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1479 |
R4037 - MissingTypeObject |
The schema 'GeographicHierarchyProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1499 |
R4037 - MissingTypeObject |
The schema 'TrafficManagerGeographicHierarchy' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1508 |
R4037 - MissingTypeObject |
The schema 'UserMetricsProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1523 |
R4037 - MissingTypeObject |
The schema 'Resource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1532 |
R4037 - MissingTypeObject |
The schema 'TrackedResource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2018-08-01/trafficmanager.json#L1550 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
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.
️️✔️
[Staging] SDK Track2 Validation succeeded [Detail] [Expand]
Validation passes for SDKTrack2Validation
- The following tags are being changed in this PR
️️✔️
[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
[Staging] Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
Swagger Generation Artifacts
|
Azure Pipelines successfully started running 1 pipeline(s). |
Hi @tombuildsstuff, Your PR has some issues. Please fix the CI sequentially by following the order of
|
Hi @tombuildsstuff Please follow advice of bot to fix CI. All |
Hi @ArcturusZhang Please help confirm breaking change of Go. |
ping @ArcturusZhang - any update here? |
Hi, @tombuildsstuff. 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 @ArcturusZhang - any update here? |
Hi, @tombuildsstuff. 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 |
... it's waiting for the relevant service team to review it? |
Hi, @ArcturusZhang Please review Go breaking change. |
…dpoint (Azure#16472) * trafficmanager: adding the missing enum values for traffic manager endpoint These are required in the API but undocumented - so pulling these out explicitly * trafficmanager: casing to TitleCase
…dpoint (Azure#16472) * trafficmanager: adding the missing enum values for traffic manager endpoint These are required in the API but undocumented - so pulling these out explicitly * trafficmanager: casing to TitleCase
These are required in the API but undocumented - so pulling these out explicitly
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:
in s360Contribution 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 copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.
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.