Skip to content

Conversation

@wendyNEU
Copy link
Contributor

Description


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.

@dsgouda
Copy link
Contributor

dsgouda commented Jan 22, 2019

@wendyNEU

  • Please fix the PR description/title
  • Looks like no new code was generated. Please create a generate.ps1 file similar to this and regenerate the code.

@wendyNEU wendyNEU changed the title Ps sdk json6 Generate new SDK for ManagedServiceIdentity with new swagger api version Jan 23, 2019
@wendyNEU
Copy link
Contributor Author

Hi dsgouda, generate.cmd already exist, do we still need generate.ps1?

@dsgouda
Copy link
Contributor

dsgouda commented Jan 23, 2019

@wendyNEU yes, we are moving all RPs to using generate.ps1 to generate SDKs

Operations = new Operations(this);
UserAssignedIdentities = new UserAssignedIdentitiesOperations(this);
BaseUri = new System.Uri("https://management.azure.com");
ApiVersion = "2015-08-31-preview";
Copy link
Contributor

Choose a reason for hiding this comment

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

@wendyNEU are you planning to release a stable version for your api version 2015-08-31-preview ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I plan to release a stable version for api version 2018-11-30

<Version>0.11.0</Version>
<AssemblyName>Microsoft.Azure.Management.ManagedServiceIdentity</AssemblyName>
<PackageTags>Microsoft Azure resource management;msi;managedserviceidentity;</PackageTags>
<PackageReleaseNotes>Taking dependency on 10.0.3 version of Newtonsoft nuget package.</PackageReleaseNotes>
Copy link
Contributor

Choose a reason for hiding this comment

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

Please update the PackageReleaseNotes here

<PackageId>Microsoft.Azure.Management.ManagedServiceIdentity</PackageId>
<Description>Provides developers with libraries for ManagedSericeIdentity under Azure Resource manager to perform CRUD operations on identities.</Description>
<Version>0.10.0-preview</Version>
<Description>Provides developers with libraries for ManagedServiceIdentity under Azure Resource manager to perform CRUD operations on identities.</Description>
Copy link
Contributor

Choose a reason for hiding this comment

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

Please remove description, use PackageReleaseNotes instead



# Microsoft Azure SDK for .NET
## All PRs should be opened against master branch. This branch is being retired and will be deleted.
Copy link
Contributor

Choose a reason for hiding this comment

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

We have already defaulted our repo to master branch, don't think we need this change. Appreciate the help

@wendyNEU
Copy link
Contributor Author

It seems the test is broken, will take a look and send another commit to fix it.

@wendyNEU wendyNEU closed this Jan 23, 2019
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.

3 participants