-
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
[Re-open of #6422] Introducing subAssessments type (Microsoft.Security provider) #7101
Conversation
In Testing, Please Ignore[Logs] (Generated from edb4eee, Iteration 19).NET: test-repo-billy/azure-sdk-for-net [Logs] [Diff]
Go: test-repo-billy/azure-sdk-for-go [Logs] [Diff]Python: test-repo-billy/azure-sdk-for-python [Logs] [Diff]
JavaScript: test-repo-billy/azure-sdk-for-js [Logs] [Diff]
|
Automation for azure-sdk-for-pythonA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
Automation for azure-sdk-for-goA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
Can one of the admins verify this patch? |
Reopen of signed off PR (with paths change) |
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.
When will this pr be ready?
.../security/resource-manager/Microsoft.Security/preview/2019-01-01-preview/subAssessments.json
Show resolved
Hide resolved
Hi, this pr is ready on our end |
Hi,
ARG has specifically asked this, as otherwise, upon sync, they will be needed to query per each subscription + assessment id combo, which makes the query scale pretty huge for both our side and their.
Regarding the type, it remains Microsoft.security/assessments/subassessments for both APIs.
This has been tried.
Regarding the manifest pr – if im not wrong, it doesn’t has the type represented in it, but only the name and route. Have I missed something?
Thanks,
Hila
From: Chris Eggert <[email protected]>
Sent: Wednesday, September 11, 2019 7:52 PM
To: Azure/azure-rest-api-specs <[email protected]>
Cc: Hila Markovitch <[email protected]>; Author <[email protected]>
Subject: Re: [Azure/azure-rest-api-specs] [Re-open of #6422] Introducing subAssessments type (Microsoft.Security provider) (#7101)
@pilor commented on this pull request.
________________________________
In specification/security/resource-manager/Microsoft.Security/preview/2019-01-01-preview/subAssessments.json<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fpull%2F7101%23discussion_r323349961&data=02%7C01%7CHila.Markovitch%40microsoft.com%7C3520a14fcbba401d35f208d736d85aec%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637038175222880986&sdata=I3E2eqrTAtfBZtz5J4kH6ZWh0vNSWbtaiHEr0VVIqlw%3D&reserved=0>:
+ "security": [{
+ "azure_auth": ["user_impersonation"]
+ }],
+ "securityDefinitions": {
+ "azure_auth": {
+ "type": "oauth2",
+ "authorizationUrl": "https://login.microsoftonline.com/common/oauth2/authorize",
+ "flow": "implicit",
+ "description": "Azure Active Directory OAuth2 Flow",
+ "scopes": {
+ "user_impersonation": "impersonate your user account"
+ }
+ }
+ },
+ "paths": {
+ "/{scope}/providers/Microsoft.Security/subAssessments": {
Have you tried this in dogfood? How will you represent this type in your manifest? as assessments/subAssessments and just "subAssessments"? Currently your manifest PR has it just listed as a "subAssessments" resourceType which seems a bit misleading. RBAC also becomes an issue when its reprsented as two different actions.
Did ARG specifically ask for this? Subscription level GETs are typically only used for top-level resources.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fpull%2F7101%3Femail_source%3Dnotifications%26email_token%3DALJQAEC42XC6GOH523DLKWLQJEO2XA5CNFSM4IS6KP6KYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCENDUBY%23discussion_r323349961&data=02%7C01%7CHila.Markovitch%40microsoft.com%7C3520a14fcbba401d35f208d736d85aec%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637038175222885975&sdata=sjEKv2SFiiQJsTcToxSD06O9m%2BIs8wNUVhnuh0tpGnY%3D&reserved=0>, or mute the thread<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALJQAEEMOUX2GDYDLIJWDXLQJEO2XANCNFSM4IS6KP6A&data=02%7C01%7CHila.Markovitch%40microsoft.com%7C3520a14fcbba401d35f208d736d85aec%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637038175222890965&sdata=vFN9jTeeghpYF8dtwienU3%2B87zY7ULDO5r4i76IkV04%3D&reserved=0>.
|
Hi @himarkov I approved these changes for now. When this is ready to merge, please let me know. If this is not going to get ready for short, I suggest to close this pr, and open a new one when this is ready to merge |
Hi, this is ready to be merged. |
Merged |
Sorted and removed duplicates as well
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.