Update Azure Governance Policy api-version to 2018-03-01#3032
Update Azure Governance Policy api-version to 2018-03-01#3032marstr merged 9 commits intoAzure:masterfrom
Conversation
- add many missing examples - improve/complete descriptions and summaries
Add/correct some response codes
AutoRest linter results for SDK Related Validation Errors/WarningsThese errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns. File: specification/resources/resource-manager/readme.md
|
AutoRest linter results for ARM Related Validation Errors/WarningsThese errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns. File: specification/resources/resource-manager/readme.md
|
Automation for azure-sdk-for-nodeEncountered a Subprocess error: (azure-sdk-for-node)
Command: ['/usr/local/bin/autorest', '/tmp/tmp6rn5la_d/rest/specification/resources/resource-manager/readme.md', '--license-header=MICROSOFT_MIT_NO_VERSION', '--node-sdks-folder=/tmp/tmp6rn5la_d/sdk', '--nodejs', '--use=@microsoft.azure/autorest.nodejs@^2.1.43'] AutoRest code generation utility [version: 2.0.4262; node: v7.10.1]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
Loading AutoRest core '/root/.autorest/@microsoft.azure_autorest-core@2.0.4275/node_modules/@microsoft.azure/autorest-core/dist' (2.0.4275)
Loading AutoRest extension '@microsoft.azure/autorest.nodejs' (^2.1.43->2.1.59)
Loading AutoRest extension '@microsoft.azure/autorest.modeler' (2.3.44->2.3.44)
[Exception] No input files provided.
Use --help to get help information. |
marstr
left a comment
There was a problem hiding this comment.
Our CI system is pretty unhappy with this PR. Before I review this in earnest, could you fix the invalid JSON that is likely messing with our tooling?
https://travis-ci.org/Azure/azure-rest-api-specs/jobs/376107691#L699
Automation for azure-libraries-for-javaThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
|
I'd love to. Thing is, that file exists and is completely valid JSON: https://github.com/mentat9/azure-rest-api-specs/blob/master/specification/resources/resource-manager/Microsoft.Authorization/stable/2018-03-01/examples/listBuiltInPolicyDefinitions.json I haven't learned all the quirks of Travis, but it looks like it's detecting something different than what the message says. I don't see anything wrong with that file, or anything wrong in the nearby JSON. All of the local validation tools find that file and validate it just fine. Have you come across this kind of error before? |
|
Adding @pilor |
Change policyAssignment result for nonexistent delete by ID to match all other delete methods Attempt to fix Travis FNF error
AutoRest linter results for SDK Related Validation Errors/WarningsThese errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns. File: specification/resources/resource-manager/readme.md
|
AutoRest linter results for ARM Related Validation Errors/WarningsThese errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns. File: specification/resources/resource-manager/readme.md
|
AutoRest linter results for ARM Related Validation Errors/WarningsThese errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns. File: specification/resources/resource-manager/readme.md
|
AutoRest linter results for SDK Related Validation Errors/WarningsThese errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns. File: specification/resources/resource-manager/readme.md
|
…ile as much as possible.
AutoRest linter results for ARM Related Validation Errors/WarningsThese errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns. File: specification/resources/resource-manager/readme.md
|
AutoRest linter results for SDK Related Validation Errors/WarningsThese errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns. File: specification/resources/resource-manager/readme.md
|
AutoRest linter results for ARM Related Validation Errors/WarningsThese errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns. File: specification/resources/resource-manager/readme.md
|
AutoRest linter results for SDK Related Validation Errors/WarningsThese errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns. File: specification/resources/resource-manager/readme.md
|
AutoRest linter results for SDK Related Validation Errors/WarningsThese errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns. File: specification/resources/resource-manager/readme.md
|
AutoRest linter results for ARM Related Validation Errors/WarningsThese errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns. File: specification/resources/resource-manager/readme.md
|
|
OK, I've fixed the Travis issue. Turns out sometimes JSON references to external files interpret the file path as case sensitive. Autorest running against a local repo on my dev box resolves $ref as case INsensitive, but when it runs against a GitHub repo, it resolves that same $ref as case sensitive. This is a bad tool bug, IMO. |
| }, | ||
| "policyDefinitions": [ | ||
| { | ||
| "policyDefinitionId": "/subscriptions/ae640e6b-ba3e-4256-9d62-2993eecfa6f2/providers/Microsoft.Authorization/policyDefinitions/7433c107-6db4-4ad1-b57a-a76dce0154a1", |
There was a problem hiding this comment.
an MG policySet wouldn't be able to reference a policyDefinition in a subscription (can only reference at the same level or above). Should change this to an MG level reference for completeness
| @@ -0,0 +1,51 @@ | |||
| { | |||
| "parameters": { | |||
| "policyAssignmentId": "providers/Microsoft.Management/managementGroups/MyManagementGroup/providers/Microsoft.Authorization/policyAssignments/LowCostStorage", | |||
There was a problem hiding this comment.
Nah, the slash is in the path template: /{policyAssignmentId}. Including it in the parameter would create a double slash. Similar thing happens in examples of the /{scope}/. . . path.
| @@ -0,0 +1,36 @@ | |||
| { | |||
| "parameters": { | |||
| "policyAssignmentId": "providers/Microsoft.Management/managementGroups/MyManagementGroup/providers/Microsoft.Authorization/policyAssignments/LowCostStorage", | |||
| "resourceName": "MyTestComputer.cloudapp.net", | ||
| "subscriptionId": "ae640e6b-ba3e-4256-9d62-2993eecfa6f2", | ||
| "api-version": "2018-03-01", | ||
| "$filter": "atScope()" |
There was a problem hiding this comment.
if atScope() was provided only policies that were assigned directly on the resource would be returned, the response below has subscription level resources
There was a problem hiding this comment.
Quite right. I'll get it fixed up.
AutoRest linter results for ARM Related Validation Errors/WarningsThese errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns. File: specification/resources/resource-manager/readme.md
|
AutoRest linter results for SDK Related Validation Errors/WarningsThese errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns. File: specification/resources/resource-manager/readme.md
|
|
Ok, so I compared the policyAssignment.json, policyDefinition.json with the previos version using a diff tool. There were no major changes. I also took a look at policySetDefinition.json which is a new file. APIs for this are already live on service side. So signing off from ARM side. |
|
@marstr, all checks are passing: can you close your change request/comment? |
|
@mentat9, are these changes deployed from your side, and ready for me to merge? |
|
Actually, I just discovered some wording changes I want to make in description fields. I'll ping back after those are done. |
AutoRest linter results for SDK Related Validation Errors/WarningsThese errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns. File: specification/resources/resource-manager/readme.md
|
AutoRest linter results for ARM Related Validation Errors/WarningsThese errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns. File: specification/resources/resource-manager/readme.md
|
|
@marstr, We are good to go from a service perspective, and my description updates are in. Please merge at your earliest convenience after checks succeed. |
|
@marstr do you happen to know whom I should follow this failure up with? I need to generate the Node.js SDK, but the docs give an email alias that no longer exists for the Node.js SDK team.
|
|
@AutorestCI rebuild azure-sdk-for-node |
Encountered a Subprocess error
Command: ['/usr/local/bin/autorest', '/tmp/tmpda054lkj/rest/specification/resources/resource-manager/readme.md', '--license-header=MICROSOFT_MIT_NO_VERSION', '--node-sdks-folder=/tmp/tmpda054lkj/sdk', '--nodejs', '--use=@microsoft.azure/autorest.nodejs@^2.1.43'] AutoRest code generation utility [version: 2.0.4262; node: v7.10.1]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
Loading AutoRest core '/root/.autorest/@microsoft.azure_autorest-core@2.0.4278/node_modules/@microsoft.azure/autorest-core/dist' (2.0.4278)
Loading AutoRest extension '@microsoft.azure/autorest.nodejs' (^2.1.43->2.1.59)
Loading AutoRest extension '@microsoft.azure/autorest.modeler' (2.3.44->2.3.44)
[Exception] No input files provided.
Use --help to get help information. |
|
@AutorestCI rebuild azure-sdk-for-node |
Encountered a Subprocess error
Command: ['/usr/local/bin/autorest', '/tmp/tmpnpmjnkn8/rest/specification/resources/resource-manager/readme.md', '--license-header=MICROSOFT_MIT_NO_VERSION', '--node-sdks-folder=/tmp/tmpnpmjnkn8/sdk', '--nodejs', '--use=@microsoft.azure/autorest.nodejs@^2.1.43'] AutoRest code generation utility [version: 2.0.4280; node: v8.11.3]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
Loading AutoRest core '/root/.autorest/@microsoft.azure_autorest-core@2.0.4280/node_modules/@microsoft.azure/autorest-core/dist' (2.0.4280)
Loading AutoRest extension '@microsoft.azure/autorest.nodejs' (^2.1.43->2.1.59)
Loading AutoRest extension '@microsoft.azure/autorest.modeler' (2.3.44->2.3.44)
[Exception] No input files provided.
Use --help to get help information. |
|
Really not sure what the problem is-- when I copy those args, modify to my local versions of the SDK and rest-api-specs and run locally, it's fine. I'm opening a PR for you @mentat9. |
This api spec combines api-version 2017-06-01-preview and 2016-12-01 into one, cleans up all validation issues, adds full examples, and clarifies/improves all descriptions. It should be fully back-compatible.
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information
api-versionin the path should match theapi-versionin the spec).Quality of Swagger