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

Machine Learning Compute: Add optional deleteAll parameter #3959

Merged
merged 2 commits into from
Jan 4, 2018

Conversation

shutchings
Copy link
Contributor

@shutchings shutchings commented Dec 18, 2017

Description

When deleting an operationalization cluster we leave behind the ACR, Application Insights, and Storage Accounts so the user has them for history. However some users do not want to delete these manually if they are not needed. The optional 'deleteAll' parameter adds the ability to delete all resources associated with the cluster as well.

REST spec PR


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.

@shutchings shutchings changed the title Add optional deleteAll parameter Machine Learning Compute: Add optional deleteAll parameter Dec 18, 2017
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.

  1. Please get latest from upstream
  2. Execute from root msbuild build.proj (this will update the build tools)
  3. Then build your project from IDE or command line
    msbuild build.proj /t:Build /p:Scope=SDKs\MachineLEarningCompute
  4. Update PR

@shutchings
Copy link
Contributor Author

Done. It looks like this created a new AzSdk.RP.props file. Are there any other expected changes?

@shutchings
Copy link
Contributor Author

@shahabhijeet Could I get another look at this? My powershell cmdlet release deadline is coming up. Thanks!

<PackageTags>Microsoft Azure Machine Learning Compute management;</PackageTags>
<PackageReleaseNotes>Orchestrator properties and orchestrator service principal are optional since the resource provider will create one if not provided.</PackageReleaseNotes>
<Version>0.3.0</Version>
<PackageTags>Microsoft Azure Machine Learning Compute management;REST HTTP client;azureofficial;windowsazureofficial;netcore451511</PackageTags>
Copy link
Member

Choose a reason for hiding this comment

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

@shutchings please remove all the extra tags that were removed earlier. Those tags does not make any sense.
All these tags are not required for searching your nuget package. Please remove them. We are cleaning these tags across all SDKs.

@shutchings
Copy link
Contributor Author

@shahabhijeet I removed the tags. Anything else?

@shahabhijeet shahabhijeet merged commit b75102a into Azure:psSdkJson6 Jan 4, 2018
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