Skip to content

Sync DataContract with latest WAP settings #1834

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

Merged
merged 2 commits into from
Feb 24, 2016
Merged

Sync DataContract with latest WAP settings #1834

merged 2 commits into from
Feb 24, 2016

Conversation

sanjkum
Copy link
Contributor

@sanjkum sanjkum commented Feb 19, 2016

Fix for the bug #4639382 (http://vstfrd:8080/Azure/RD/_workitems#_a=edit&id=4639382). As part of this the Data Contract is updated to be in syn with Tenant API of WAP

@azurecla
Copy link

Hi @sanjkum, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.azure.com.

TTYL, AZPRBOT;

@azuresdkci
Copy link

Can one of the admins verify this patch?

@azurecla
Copy link

@sanjkum, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.

Thanks, AZPRBOT;

@hovsepm
Copy link
Contributor

hovsepm commented Feb 23, 2016

@azuresdkci retest this please

@hovsepm
Copy link
Contributor

hovsepm commented Feb 23, 2016

@azuresdkci retest this please number 2

@markcowl
Copy link
Member

@markcowl markcowl changed the title Dev Sync DataContract with latest WAP settings Feb 23, 2016
hovsepm pushed a commit that referenced this pull request Feb 24, 2016
Sync DataContract with latest WAP settings
@hovsepm hovsepm merged commit d6a620c into Azure:dev Feb 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants