[Hub Generated] Review request for Microsoft.ApiManagement to add version preview/2019-12-01-preview#8066
Conversation
|
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
This is PR related to #8046. We couldn't the apim-2019-12-01-preview branch as it was read-only. Hence created a clone here and working on edits here. |
azure-sdk-for-net - Release
|
azure-sdk-for-go - Release
|
azure-sdk-for-js - Release
|
azure-sdk-for-java - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-python - Release
|
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@NullMDR I am trying to fix the prettier issues using https://github.com/Azure/azure-rest-api-specs/blob/master/documentation/ci-fix.md, but I am getting this error
|
|
@solankisamir You need npm install; npm run prettier -- --write "specification/apimanagement/**/*.json" |
|
@NullMDR ran the command and hit the issue below. I don't have the
|
There was a problem hiding this comment.
You shouldn't have an id field in the properties section of a resource. It conflicts with the top level id property. Please find a different name.
There was a problem hiding this comment.
It's on the top level, not inside "properties".
There was a problem hiding this comment.
@ryansbenson please see @vfedonkin comment. This is a contract associated with a proxy resource and we are just adding id to fix the ARM warnings generated as part of live traffic.
There was a problem hiding this comment.
@ryansbenson, @solankisamir , I think we will need to modify all entities to have our fields inside "properties", but it should be done in our next version, since we already behind the schedule for the version we trying to release.
There was a problem hiding this comment.
@ryansbenson we fixed this in the spec to unblock it. Can you review again?
|
@solankisamir Please merge from latest master to pick up latest scripts and try again |
…19-01-01 to version 2019-12-01-preview
* ApiManagement - renaming /properties entity to /namedValues * ApiManagement - renaming parameter name: propId to namedValueId
* ApiManagement - async operatins for NamedValues and ApiSchemas * ApiManagement - client secrets in IdentityProvider * ApiManagement - json format fixes * ApiManagement - examples fixes * ApiManagement - fixed identtyProviderContract * ApiManagement - secrets in subscriptions * ApiManagement - secrets in OpenIdConnectProviders and AuthServers * ApiManagement - secrets in TenantAccess * ApiManagement - fix example * ApiManagement - fixes
* ApiManagement - tagDescription id * ApiManagement - policyDescriptions * ApiManagement - policyDescriptions small fix * ApiManagement - policyDescriptions sample * ApiManagement - revisions id and api schema doc * ApiManagement - tag descriptions list example * ApiManagement - ciphers info
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run automation - sdk |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@ryansbenson sorry! I made a mistake to merge it. Could you please review this PR, if still need some change we can open another or revert this one. @solankisamir Sorry. Please hold on the following process since ARM didn't sign off yet. Thanks. |
|
@myronfanqiu You can create a PR to revert this one |
For all async operations, add x-ms-long-running-operation:true and , add "x-ms-long-running-operation-options" extension with "final-state-via" property. "x-ms-long-running-operation-options": {
"final-state-via": "location"
}or "x-ms-long-running-operation-options": {
"final-state-via": "azure-async-operation"
}Refers to: specification/apimanagement/resource-manager/Microsoft.ApiManagement/preview/2019-12-01-preview/apimapis.json:2361 in 13fb704. [](commit_id = 13fb704, deletion_comment = False) |
| "responses": { | ||
| "202": { | ||
| "description": "Request to update NamedValue was accepted.", | ||
| "headers": { |
There was a problem hiding this comment.
For all async operations, add x-ms-long-running-operation:true and
, add "x-ms-long-running-operation-options" extension with "final-state-via" property.
"x-ms-long-running-operation-options": {
"final-state-via": "location"
}or
"x-ms-long-running-operation-options": {
"final-state-via": "azure-async-operation"
}| "paths": { | ||
| "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/namedValues": { | ||
| "get": { | ||
| "tags": [ |
There was a problem hiding this comment.
missing ListBySubscrition and ListByResourceGroup calls
There was a problem hiding this comment.
We don't have such methods, "ListByService" only
| } | ||
| ], | ||
| "responses": { | ||
| "202": { |
There was a problem hiding this comment.
add sync response 200 as well.. as service could respond synchronously if no changes.
There was a problem hiding this comment.
We use 204 for "update was successful" since no any data returned
| "Location": { | ||
| "description": "The URL where the status of the long running operation can be checked.", | ||
| "type": "string" | ||
| } |
There was a problem hiding this comment.
check other comments on LRO tracking extension annotation
There was a problem hiding this comment.
@sanjaiganesh , should we remove this header description and use this instead?:
"x-ms-long-running-operation-options": {
"final-state-via": "location"
}
|
looks fine.. added few comments. please address them in separate PR. added armsignoff. |
@sanjaiganesh Thanks for the review. @vfedonkin can you create another PR with the changes requested. |
If you are a MSFT employee you can view your work branch via this link.
Contribution checklist: