-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Add built in policy definition/set definition paths #1788
Conversation
} | ||
], | ||
"responses": { | ||
"200": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
404 should be valid response correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep
"description": "Gets all the built in policy definitions.", | ||
"parameters": [ | ||
{ | ||
"name": "$filter", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
policyDefinition collection requests don't support odata fliters. Only policyAssignments have filters
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
], | ||
"responses": { | ||
"200": { | ||
"description": "OK - Returns ana array of built in policy definitions.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Returns an"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
@@ -256,13 +279,6 @@ | |||
"description": "Gets all the policy definitions for a subscription.", | |||
"parameters": [ | |||
{ | |||
"name": "$filter", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So this was not supported and here by mistake?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, apparently, only policy assignment list supports filter. Not policy definitions and set definitions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, this was exposed in the CLI, I create an issue for that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -292,19 +332,9 @@ | |||
"description": "Gets all the policy definitions for a subscription at management group level.", | |||
"parameters": [ | |||
{ | |||
"name": "$filter", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same question, not supported?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, not supported
@ravbhatnagar few apis added to existing api versions, some properties removed. Can you please review from ARM side? thanks! |
@veronicagg Adding @cyl3392207, the PM for policy related ARM apis |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are the added apis new to the existing api versions or were there missing in the specs?
Please take a look at model validation results at https://travis-ci.org/Azure/azure-rest-api-specs/jobs/282957464#L577
Have you taken a look at linter results https://travis-ci.org/Azure/azure-rest-api-specs/jobs/282957459#L579 ?
@@ -137,6 +137,38 @@ | |||
} | |||
} | |||
}, | |||
"/providers/Microsoft.Authorization/policydefinitions/{policyDefinitionName}": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
was this api missing from the spec? or is it newly added to the existing api version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this was missing from the spec
} | ||
} | ||
}, | ||
"/providers/Microsoft.Authorization/policydefinitions": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
was this api missing from the spec before but existed in the service?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, we never added this to spec
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@veronicagg The model validation results are because of missing example for 404 response, which I think is redundant here, and doesn't add any value. The linter result errors are also because of missing examples. |
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: 💡 Please review potentially introduced Error(s)/Warning(s): Analysis Report 💡 File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
Approve from my side. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vivsriaus @veronicagg looks good. one minor thing.
@@ -137,6 +137,38 @@ | |||
} | |||
} | |||
}, | |||
"/providers/Microsoft.Authorization/policydefinitions/{policyDefinitionName}": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
camel case ->policyDefinitions
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: 💡 Please review potentially introduced Error(s)/Warning(s): Analysis Report 💡 File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, some missing examples that based on offline conversation will be added in a later PR.
No modification for AutorestCI/azure-sdk-for-node |
Approve |
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-version
in the path should match theapi-version
in the spec).Quality of Swagger