-
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
[Hub Generated] Public private branch 'add-ingressStartAt' #13932
[Hub Generated] Public private branch 'add-ingressStartAt' #13932
Conversation
remove .npmrc
fix prettier
The PR is created based on the updates in the private branch. The updates in the PR has already been reviewed and approved with this PR Azure/azure-rest-api-specs-pr/3012 |
Hi, @riserrad 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. vsswagger@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 |
---|---|
R4009 - RequiredReadOnlySystemData |
The response of operation:'Environments_Get' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.TimeSeriesInsights/stable/2020-05-15/timeseriesinsights.json#L140 |
R4009 - RequiredReadOnlySystemData |
The response of operation:'EventSources_Get' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.TimeSeriesInsights/stable/2020-05-15/timeseriesinsights.json#L418 |
R4009 - RequiredReadOnlySystemData |
The response of operation:'ReferenceDataSets_Get' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.TimeSeriesInsights/stable/2020-05-15/timeseriesinsights.json#L665 |
R4009 - RequiredReadOnlySystemData |
The response of operation:'AccessPolicies_Get' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.TimeSeriesInsights/stable/2020-05-15/timeseriesinsights.json#L912 |
R4009 - RequiredReadOnlySystemData |
The response of operation:'Environments_CreateOrUpdate' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.TimeSeriesInsights/stable/2020-05-15/timeseriesinsights.json#L74 |
R4009 - RequiredReadOnlySystemData |
The response of operation:'EventSources_CreateOrUpdate' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.TimeSeriesInsights/stable/2020-05-15/timeseriesinsights.json#L350 |
R4009 - RequiredReadOnlySystemData |
The response of operation:'ReferenceDataSets_CreateOrUpdate' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.TimeSeriesInsights/stable/2020-05-15/timeseriesinsights.json#L600 |
R4009 - RequiredReadOnlySystemData |
The response of operation:'AccessPolicies_CreateOrUpdate' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.TimeSeriesInsights/stable/2020-05-15/timeseriesinsights.json#L847 |
R4009 - RequiredReadOnlySystemData |
The response of operation:'Environments_Update' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.TimeSeriesInsights/stable/2020-05-15/timeseriesinsights.json#L183 |
R4009 - RequiredReadOnlySystemData |
The response of operation:'EventSources_Update' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.TimeSeriesInsights/stable/2020-05-15/timeseriesinsights.json#L461 |
️️✔️
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
|:speech_balloon: AutorestCore/Exception|"readme":"timeseriesinsights/resource-manager/readme.md",
"tag":"package-2020-05-15",
"details":"> Installing AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0)"|
|:speech_balloon: AutorestCore/Exception|"readme":"timeseriesinsights/resource-manager/readme.md",
"tag":"package-2020-05-15",
"details":"> Installed AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0->1.8.0)"|
The following errors/warnings exist before current PR submission:
|:speech_balloon: AutorestCore/Exception|"readme":"timeseriesinsights/resource-manager/readme.md",
"tag":"package-2020-05-15",
"details":"> Loading AutoRest extension '@autorest/modelerfour' (4.15.456->4.15.456)"|
️️✔️
[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
|
Hi - about this Python SDK failure: it seems to be happening at an unchanged portion of the spec, and we don't have a python SDK. Changing this would require some other validations and we don't want to do that for this GA api-version. Can we disregard this warning for this change? |
@msyyc pls help double check the python sdk failure |
@riserrad it's suggested to fix the lintdiff warning here to keep high quality #13932 (comment) |
Sure @zhenglaizhang - I just added a description to the field, according to the warning's instruction. |
Hi @msyyc , @zhenglaizhang - following up on this to have this PR checked in if possible. |
Hi @riserrad, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. |
Hi @riserrad you are adding one optional property and making this public, pls go through breaking change review process per #13932 (comment) |
Started the process. Given the current schedule, we're going to attend the Office Hours meeting in May 10th. |
Hi @zhenglaizhang - do you have an ETA of when this is going to be merged? Thanks |
Hi @msyyc the sdk python track 2 failed, could you help take a look? |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
For python, I have helped to fix the failure and the breaking change is expected |
Hi @ArcturusZhang pls help double check if go sdk breaking change is expected. |
…'add-ingressStartAt' (#1762) Create to sync Azure/azure-rest-api-specs#13932 [ReCreate this PR](https://github.com/azure-resource-manager-schemas/compare/master...AzureSDKAutomation:sdkAuto/timeseriesinsights?expand=1)
* add ingressStartAt * prettier * add a new example * Delete .npmrc remove .npmrc * fix prettier fix prettier * put readonly back for kind * Adding descriptin to ingressStartAt * fix failure for python track2 * Removing readonly from kind Co-authored-by: Go Blue <zth@umich.edu> Co-authored-by: msyyc <70930885+msyyc@users.noreply.github.com>
* add ingressStartAt * prettier * add a new example * Delete .npmrc remove .npmrc * fix prettier fix prettier * put readonly back for kind * Adding descriptin to ingressStartAt * fix failure for python track2 * Removing readonly from kind Co-authored-by: Go Blue <zth@umich.edu> Co-authored-by: msyyc <70930885+msyyc@users.noreply.github.com>
This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Changelog
Please ensure to add changelog with this PR by answering the following questions.
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
Please 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 there are following updates in the PR, ensure to request an approval from 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.