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

added issue api and tests #4250

Merged
merged 2 commits into from
May 1, 2018
Merged

added issue api and tests #4250

merged 2 commits into from
May 1, 2018

Conversation

solankisamir
Copy link
Member

@solankisamir solankisamir commented Apr 19, 2018

Description

Added support for issue api and policy in non encoded xml format
Relevant rest spec pr
Azure/azure-rest-api-specs#2806
Azure/azure-rest-api-specs#2893
Azure/azure-rest-api-specs#2881
Azure/azure-rest-api-specs#2882


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 the commitid of your swagger spec or link to the swagger spec, used to generate the code.
  • The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

@solankisamir
Copy link
Member Author

@dsgouda @shahabhijeet @promoisha can you take a look?

Copy link
Contributor

@dsgouda dsgouda 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 for the most part

@@ -15,6 +15,9 @@ internal static partial class SdkInfo
new Tuple<string, string, string>("ApiManagement", "ApiDiagnostic", "2018-01-01"),
new Tuple<string, string, string>("ApiManagement", "ApiDiagnosticLogger", "2018-01-01"),
new Tuple<string, string, string>("ApiManagement", "ApiExport", "2018-01-01"),
new Tuple<string, string, string>("ApiManagement", "ApiIssue", "2018-01-01"),
Copy link
Contributor

Choose a reason for hiding this comment

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

Please run msbuild build.proj /t:build /p:Scope=SDKs\ApiManagement
and commit changes to the .props file

Copy link
Member Author

Choose a reason for hiding this comment

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

built again. there is no change in api version and no change in .props file

@@ -9,8 +9,8 @@
[assembly: AssemblyTitle("Microsoft Azure API Management Resource Management Library")]
[assembly: AssemblyDescription("Provides Api management capabilities for Microsoft Azure.")]

[assembly: AssemblyVersion("4.0.0.0")]
[assembly: AssemblyFileVersion("4.0.0.0")]
[assembly: AssemblyVersion("4.0.1.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 do not update the AssemblyVersion here

Copy link
Member Author

Choose a reason for hiding this comment

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

reverted

Copy link
Contributor

@dsgouda dsgouda left a comment

Choose a reason for hiding this comment

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

LGTM

@dsgouda dsgouda merged commit 3660a2e into Azure:psSdkJson6 May 1, 2018
@solankisamir solankisamir deleted the policyissueupdate branch May 3, 2018 16:21
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.

2 participants