-
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
Dataplane policy states and events API swagger #8562
Conversation
Data plane sample fixes and resolving autorest tool compile errors
Added more examples for dp and minor fixes
Update api version in exisiting events API examples to be 2019-10-01
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-net
|
azure-sdk-for-js
|
azure-sdk-for-python
|
azure-sdk-for-java
|
azure-sdk-for-go
|
Can one of the admins verify this patch? |
Fix model validator errors
Azure Pipelines successfully started running 1 pipeline(s). |
Remove aggrigate data plane events and states examples from swagger
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
Azure Pipelines successfully started running 1 pipeline(s). |
@NarineM - can you please set something up with armapireview to go over this? It will be much quicker in person since this is a new type. |
@pilor Just pushed a new iteration that addresses your comments. I can see this warning from cli-extension, do you know what it complains about?: |
No, I don't know the specifics on that but I have seen it on my own PRs which went through just fine. The SDK reviewer is a better contact. |
SDK automation is throwing an error if the parameter descriptions for $expand do not match across PolicyStates and PolicyEvents API.
Azure Pipelines successfully started running 1 pipeline(s). |
@raych1 Can you help with this new error from SDK automation log?, it says branch changes need to be squished. Looks like something with the tool. Now this issue impacts all language SDK. |
@NullMDR , can you help with the SDK automation failures? |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
@raych1 thanks. So far all PR merge validation issues have been resolved except prettier check. This PR can be merged unless you tell me the prettier check issue is blocking. As of now I can not figure out why the tool is not running or what it complains about. The log says something with formatting, but can not figure out. can you run prettier on your local box for any of the files it complains about and let me know what is the issue? Here is the log that has file names that failed in prettier checks: https://dev.azure.com/azure-sdk/public/_build/results?buildId=326037&view=logs&j=b56e9678-4dad-5642-289c-5530cc4dad11&t=9e18c5d1-dc43-58a1-0344-6ef37d05bd7f&l=65 |
Please go ahead with merging this PR when you get a chance if you do not find anything with prettier check. |
@NarineM, prettierCheck is required to pass. @NullMDR , can you help Narine, he failed to run prettier? |
Pull request contains merge conflicts. |
@NarineM I've fixed your prettier failure by running |
Pull request contains merge conflicts. |
1 similar comment
Pull request contains merge conflicts. |
No commit pushedDate could be found for PR 8562 in repo Azure/azure-rest-api-specs |
Pull request contains merge conflicts. |
Azure Pipelines successfully started running 1 pipeline(s). |
@NullMDR, thank you. I have resolved merge conflicts. The only failure now remaining is related to api version (under breaking change category). As we discussed earlier this change needs to be published for the same api version 2019-10-01. Please go ahead with merging this PR. |
@jianyexi Why adding property in response will be considered as breaking change? |
@NullMDR It is not breaking change because this property is only appended when the client specifies it in request URL with $expand clause. This functionality is available in the current version of API on the RP side, so it should be published under the same API version 2019-10-01 and not a new version. |
@NullMDR , can you go ahead with merging this PR? Let me know what is blocking if anything. thanks. |
I think this is reasonable. Hi @akning-ms would you please have us merge this PR? This breaking change should be acceptable based on the author's comments |
* swagger documentation for data plane PolicyStates API * enable events api in 2019-10-01 api version * data plane events API and data plane states API fixes * Data plane sample fixes and resolving autorest tool compile errors Data plane sample fixes and resolving autorest tool compile errors * Added more examples for dp and minor fixes Added more examples for dp and minor fixes * Update api version in exisiting events API examples Update api version in exisiting events API examples to be 2019-10-01 * Fix model validator errors Fix model validator errors * Remove aggrigate data plane events and states examples from swagger Remove aggrigate data plane events and states examples from swagger * Revert - Add back references to aggrigated component counts Revert - Add back references to aggrigated component counts * Added additional properties bag to data plane json object Added additional properties bag to data plane json object * Added policyEvents for 2019-10-01 in readme * fixed sample ref file path * Addressed PR review feedback Addressed PR review feedback * Fix SDK automation error SDK automation is throwing an error if the parameter descriptions for $expand do not match across PolicyStates and PolicyEvents API. * Fix prettier Co-authored-by: Phoenix He <tih@microsoft.com>
Latest improvements:
Added data plane events and states API under version 2019-10-01. Added samples.
@pilor