ShortTermRetentionManagadInstance

[v-djnisi]

Description

Azure-Rest-API-Specs pull request: Azure/azure-rest-api-specs#3979

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

• Please add REST spec PR link to the SDK PR
• I have read the contribution guidelines.
• The pull request does not introduce breaking changes.

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.

[v-djnisi]

Squashed commits from #4934

[dsgouda]

There should be a .txt file generated/modified when code is generated, please commit this file too

[dsgouda]

Needs some changes

[v-djnisi]

I regenerated files and pushed them. I used synced azure-rest-api branch before regenerating, and it generated some files that are not connected to my changes. Is that a problem?

[dsgouda]

These files are expected

[dsgouda]

@v-djnisi I have approved the PR but this cannot be merged until the PR for REST spec is merged.

[jaredmoo]

Change looks good overall, just need to update csproj & AssemblyInfo

[jaredmoo]

@dsgouda please take a look at Travis build failure, it's not in our area

[v-djnisi]

@jaredmoo @dsgouda I don't see any failures.

One more thing, is there a reason why we are not merging this API? It seems to me that this PR is waiting on rest-api-for-specs, and rest-api-for-specs is waiting on this PR. Is there anything I can do besides pinging? We need to finish powershell by the end of the month.

[dsgouda]

@v-djnisi @jaredmoo it looks like the REST spec API PR is still not merged. We won't be able to merge this PR until the REST spec gets merged

[v-djnisi]

@dsgouda azure-rest-api-specs just got approved and merged.

[dsgouda]

LGTM