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

SDK Client Library for AzureRM.Billing and tests #2838

Merged
merged 3 commits into from Feb 24, 2017
Merged

SDK Client Library for AzureRM.Billing and tests #2838

merged 3 commits into from Feb 24, 2017

Conversation

Panda-Wang
Copy link

Add the newly generated SDK Client for Azure Resource Management Billing
Service and tests.

Description

We are going to ship Billing Resource Provider via ARM as our first preview release. Here's the swagger spec: https://raw.githubusercontent.com/Azure/azure-rest-api-specs/master/arm-billing/2017-02-27-preview/swagger/billing.json
The SDK library was generated based on the swagger and tests have been added as requested.
Here's the link to internal code review: http://codeflow/Client/CodeFlow2010.application?server=http://codeflow/Services/DiscoveryService.svc&review=caixiaw-ad44ccf2cfab428090be3046975f2e7f

This checklist is used to make sure that common guidelines for a pull request are followed.

General Guidelines

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

SDK Generation Guidelines

  • If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
  • The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as a link to the swagger spec, used to generate the code.
  • The project.json and AssemblyInfo.cs files have been updated with the new version of the SDK.

Add the newly generated SDK Client for Azure Resource Management Billing
Service and tests.
@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@azurecla
Copy link

Hi @Panda-Wang, 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;

@Panda-Wang
Copy link
Author

Can you help to remove the CLA required label as I'm MSFT FTE and should not require CLA? thanks a lot.

@shahabhijeet
Copy link
Member

@azuresdkci add to whitelist

1 similar comment
@shahabhijeet
Copy link
Member

@azuresdkci add to whitelist

@shahabhijeet
Copy link
Member

@azuresdkci test this please

@Panda-Wang
Copy link
Author

@jlian fyi

@hovsepm
Copy link
Contributor

hovsepm commented Feb 22, 2017

@azuresdkci add to whitelist

[assembly: AssemblyDescription("Provides management functionality for Microsoft Azure Billing.")]

[assembly: AssemblyVersion("2.0.0.0")]
[assembly: AssemblyFileVersion("3.0.0.0")]
Copy link
Contributor

Choose a reason for hiding this comment

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

please align these versions with the project.json file for this project

Copy link
Author

Choose a reason for hiding this comment

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

updated to 1.0.0.0

[assembly: AssemblyConfiguration("")]
[assembly: AssemblyCompany("Microsoft")]
[assembly: AssemblyProduct("Billing.Tests")]
[assembly: AssemblyCopyright("Copyright � Microsoft Corporation")]
Copy link
Contributor

Choose a reason for hiding this comment

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

� [](start = 40, length = 1)

please change this sign to '(C)'

Copy link
Author

Choose a reason for hiding this comment

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

fixed

Project("{8BB2217D-0F2D-49D1-97BC-3654ED321F3B}") = "Microsoft.Rest.ClientRuntime.Azure.Authentication", "..\..\ClientRuntime\Microsoft.Rest.ClientRuntime.Azure.Authentication\Microsoft.Rest.ClientRuntime.Azure.Authentication.xproj", "{6319205D-BBFC-4150-BEAE-31B1C9B911DD}"
EndProject
Project("{8BB2217D-0F2D-49D1-97BC-3654ED321F3B}") = "TestFramework", "..\..\TestFramework\Microsoft.Rest.ClientRuntime.Azure.TestFramework\TestFramework.xproj", "{C4C4E1C8-B99D-4D90-8C27-6D0C0A268BA5}"
EndProject
Copy link
Contributor

Choose a reason for hiding this comment

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

you do not need to reference all these projects. just Microsoft.Azure.Management.Billing and Billing.Tests should be enough.

Copy link
Author

Choose a reason for hiding this comment

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

removed

</PropertyGroup>
<Import Project="$(VSToolsPath)\DotNet\Microsoft.DotNet.Props" Condition="'$(VSToolsPath)' != ''" />
<PropertyGroup Label="Globals">
<ProjectGuid>4ee713c9-0164-4a9d-b573-5552c76f3dda</ProjectGuid>
Copy link
Member

Choose a reason for hiding this comment

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

@Panda-Wang please make sure these guids are unique. In case if you are using another test project to model your test project

Copy link
Author

Choose a reason for hiding this comment

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

good catch! i did copy from CDN and forgot to update GUID.

public class InvoicesTests : TestBase
{
const string DownloadUrlExpand = "downloadUrl";
const string RangeFilter = "invoicePeriodEndDate ge 2017-01-31 and invoicePeriodEndDate le 2017-02-28";
Copy link
Member

Choose a reason for hiding this comment

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

@Panda-Wang is this still valid in sdk? If yes then the SDK and PS developer experience is different.
You are fine with this difference in functionality?

Copy link
Author

Choose a reason for hiding this comment

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

yes, the filter is valid in SDK. For PS, we decided to have different behavior for the 1st release. If customer gives feedback on requesting date range filter, we will add it in later release. The reason we dont want to add it in 1st release is because we think it's a bit confusing and since we only have very few data (3 month data) for now, the data range filter might not be very useful.

@shahabhijeet shahabhijeet merged commit 4d37cc1 into Azure:AutoRest Feb 24, 2017
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.

None yet

6 participants