Skip to content
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

Nithin/action group webhooks with azure active directory integration #6218

Conversation

nithinpnp
Copy link
Contributor

@nithinpnp nithinpnp commented Jun 4, 2019

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:

  • I have reviewed the documentation for the workflow.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.
  • The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

  • Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
  • adding/removing APIs.
  • adding/removing properties.
  • adding/removing API-version.
  • adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

  • If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
    Please follow the link to find more details on API review process.

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Jun 4, 2019

SDK Automation [Logs] (Generated from 1dca2b0)

Succeeded Python: Azure/azure-sdk-for-python [Logs] [Diff]
Succeeded Java: Azure/azure-sdk-for-java [Logs] [Diff]
  • No packages generated.
Failed Go: Azure/azure-sdk-for-go [Logs]
  • No packages generated.
Succeeded JavaScript: Azure/azure-sdk-for-js [Logs] [Diff]
Failed Ruby: Azure/azure-sdk-for-ruby [Logs] [Diff]

@AutorestCI
Copy link

AutorestCI commented Jun 4, 2019

Automation for azure-sdk-for-python

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-python#5914

@AutorestCI
Copy link

AutorestCI commented Jun 4, 2019

Automation for azure-sdk-for-java

A 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:
Azure/azure-sdk-for-java#2993

@AutorestCI
Copy link

AutorestCI commented Jun 4, 2019

Automation for azure-sdk-for-ruby

A 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:
Azure/azure-sdk-for-ruby#2640

@AutorestCI
Copy link

AutorestCI commented Jun 4, 2019

Automation for azure-sdk-for-js

A 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:
Azure/azure-sdk-for-js#3892

@AutorestCI
Copy link

AutorestCI commented Jun 4, 2019

Automation for azure-sdk-for-go

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-go#5039

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@nithinpnp
Copy link
Contributor Author

spell check error is because of specification\mediaservices\resource-manager\Microsoft.Media\stable\2018-07-01\Encoding.json file row 1200 column 95 "specified" is there. This spelling is wrong. This the reason for the failure. We don't own this resource. pls advice

@nschonni
Copy link
Contributor

nschonni commented Jun 5, 2019

The spelling issue will be fixed in #6145, sorry for the noise

@nithinpnp
Copy link
Contributor Author

@NelsonDaniel . Could you please review this pull request ?

@NelsonDaniel NelsonDaniel added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Jun 7, 2019
Copy link

@NelsonDaniel NelsonDaniel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. But, requesting ARM feedback since 4 properties were added in Model "WebhookReceiver"

@nithinpnp
Copy link
Contributor Author

nithinpnp commented Jun 7, 2019

I noticed that person who reviewed #WaitForArmFeedback in an earlier pull request had requested previous API version for easy diff. I am new to the team hence did not add that in the earlier commit message. The prior API version is 2019-03-01. This set of changes is for 2019-06-01.

@nithinpnp
Copy link
Contributor Author

@ravbhatnagar , @KrisBash .. could you please review this ?

Copy link

@NelsonDaniel NelsonDaniel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM but still waiting for ARM feedback. I will be OOF. I am adding the Reasign label in case this needs to be merged before I am back

@nithinpnp
Copy link
Contributor Author

@shahabhijeet Could you please review ?

Copy link
Member

@shahabhijeet shahabhijeet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if ActionGroup_API.json is the new API of your REST spec, would be great if you can add a commit that shows the delta of what got changed in the new API version.
If the only thing that changed is the API version, please provide a detailed description of your PR.
Also we need ARM signOff as this is a new API version.
Having a commit that shows the diff also helps ARM to quickly review your new REST spec.

}
},
"patch": {
"description": "Updates an existing action group's tags. To update other fields use the CreateOrUpdate method.",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CreateOrUpdate [](start = 104, length = 14)

Does the PUT of actionGroup allow partial resource body? In other words, does it act like PATCH?

}
},
"x-ms-pageable": {
"nextLinkName": null
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

null [](start = 36, length = 4)

You should set this to "nextLink" even if your service only returns 1 page. Doing so will make adding paging easier for you in the future.

}
},
"x-ms-pageable": {
"nextLinkName": null
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

null [](start = 36, length = 4)

I'd set this to "nextLink" here too even if the service only returns 1 page.

Copy link
Member

@majastrz majastrz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The incremental changes on top of 2019-03-01 look good. I added some comments that you should consider taking, but they are not blocking.

@majastrz majastrz added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Jun 17, 2019
@nithinpnp
Copy link
Contributor Author

@shahabhijeet Could you please review. Please note ARM team has signed off

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants