[NOT AZURE] Updated Azure Stack Infrastructure Insights Admin SDK

[deathly809]

Description

Recreated the FRP specifications and regenerated the SDK.

Azure/azure-rest-api-specs#2812

---

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.

[dsgouda]

Looks good, just needs a version bump

[dsgouda]

Looks like this package is already published and there are some additive changes being introduced. Please update the package version number

[deathly809]

@dsgouda Done! Also, do we publish the Nugets? We might have to update the package release notes.

[dsgouda]

@deathly809 I believe so, please check here

[deathly809]

@dsgouda I already updated the version. So I have to kick off the build process correct? Just to be 100% clear.

[dsgouda]

By build if you mean publish the package, then yes. The "build" itself was done successfully here by the CI machines.
What you may have to consider is updating the PackageReleaseNotes, let me know if you plan to do so

[deathly809]

@dsgouda I have been trying to get feedback on that. We might just have a single PR to update all the admin PackageReleaseNotes and then kick of a publish job.

[dsgouda]

That would be a good idea. Will merge this for now, feel free to open a new PR for the release notes.

[dsgouda]

LGTM