forked from Azure/azure-rest-api-specs
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Export API with Json Output and Add missing Api /apis/operations/poli…
…cies (Azure#1656) * Document Export API with Json output * Add API Operation Policies Collection * Removed X-Ms-Example from x-ms-paths * Fix the issue with Contract reference and add the example back. * Associate correct Example with Swagger * Adding Accept header at same level apiId
- Loading branch information
1 parent
c57f7d2
commit f153008
Showing
3 changed files
with
181 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
17 changes: 17 additions & 0 deletions
17
.../Microsoft.ApiManagement/2017-03-01/examples/ApiManagementGetApiExportInOpenApi2dot0.json
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,17 @@ | ||
| { | ||
| "parameters": { | ||
| "serviceName": "apimService1", | ||
| "resourceGroupName": "rg1", | ||
| "api-version": "2017-03-01", | ||
| "subscriptionId": "subid", | ||
| "apiId": "echo-api", | ||
| "Accept": "application/vnd.swagger.link+json" | ||
| }, | ||
| "responses": { | ||
| "200": { | ||
| "body": { | ||
| "link": "https://apimgmtstaobxxxxxxx.blob.core.windows.net/api-export/Echo API.json?sv=2015-07-08&sr=b&sig=xxxxxxxxxx%3D&se=2017-09-08T21:54:08Z&sp=r" | ||
| } | ||
| } | ||
| } | ||
| } |
27 changes: 27 additions & 0 deletions
27
...er/Microsoft.ApiManagement/2017-03-01/examples/ApiManagementListApiOperationPolicies.json
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| { | ||
| "parameters": { | ||
| "serviceName": "apimService1", | ||
| "resourceGroupName": "rg1", | ||
| "api-version": "2017-03-01", | ||
| "subscriptionId": "subid", | ||
| "apiId": "599e2953193c3c0bd0b3e2fa", | ||
| "operationId": "599e29ab193c3c0bd0b3e2fb" | ||
| }, | ||
| "responses": { | ||
| "200": { | ||
| "body": { | ||
| "value": [ | ||
| { | ||
| "id": "/subscriptions/subid/resourceGroups/rg1/providers/Microsoft.ApiManagement/service/apimService1/apis/599e2953193c3c0bd0b3e2fa/operations/599e29ab193c3c0bd0b3e2fb/policies/policy", | ||
| "type": "Microsoft.ApiManagement/service/apis/operations/policies", | ||
| "name": "policy", | ||
| "properties": { | ||
| "policyContent": "<!--\r\n IMPORTANT:\r\n - Policy elements can appear only within the <inbound>, <outbound>, <backend> section elements.\r\n - Only the <forward-request> policy element can appear within the <backend> section element.\r\n - To apply a policy to the incoming request (before it is forwarded to the backend service), place a corresponding policy element within the <inbound> section element.\r\n - To apply a policy to the outgoing response (before it is sent back to the caller), place a corresponding policy element within the <outbound> section element.\r\n - To add a policy position the cursor at the desired insertion point and click on the round button associated with the policy.\r\n - To remove a policy, delete the corresponding policy statement from the policy document.\r\n - Position the <base> element within a section element to inherit all policies from the corresponding section element in the enclosing scope.\r\n - Remove the <base> element to prevent inheriting policies from the corresponding section element in the enclosing scope.\r\n - Policies are applied in the order of their appearance, from the top down.\r\n-->\r\n<policies>\r\n <inbound>\r\n <validate-jwt header-name=\"dd\">\r\n <required-claims>\r\n <claim name=\"bla\" separator=\"\">\r\n <value>xxx</value>\r\n </claim>\r\n </required-claims>\r\n </validate-jwt>\r\n <base />\r\n </inbound>\r\n <backend>\r\n <base />\r\n </backend>\r\n <outbound>\r\n <base />\r\n </outbound>\r\n</policies>" | ||
| } | ||
| } | ||
| ], | ||
| "nextLink": "" | ||
| } | ||
| } | ||
| } | ||
| } |