Network mgmt track 2 library

[archerzz]

All SDK Contribution checklist:

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

• Please open PR in Draft mode if it is:
  • Work in progress or not intended to be merged.
  • Encountering multiple pipeline failures and working on fixes.
• 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.
• I have read the contribution guidelines.
• The pull request does not introduce breaking changes.

General Guidelines and Best Practices

• 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

• 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. (Track 2 only)
• The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK. Please double check nuget.org current release version.

Additional management plane SDK specific contribution checklist:

Note: Only applies to Microsoft.Azure.Management.[RP] or Azure.ResourceManager.[RP]

• Include updated management metadata.
• Update AzureRP.props to add/remove version info to maintain up to date API versions.

Management plane SDK Troubleshooting

• If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add new service label and/or contact assigned reviewer.

• If the check fails at the Verify Code Generation step, please ensure:

  • Do not modify any code in generated folders.
  • Do not selectively include/remove generated files in the PR.
  • Do use generate.ps1/cmd to generate this PR instead of calling autorest directly.
    Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version.

  Note: We have recently updated the PSH module called by generate.ps1 to emit additional data. This would help reduce/eliminate the Code Verification check error. Please run following command:

    `dotnet msbuild eng/mgmt.proj /t:Util /p:UtilityName=InstallPsModules`
  

Old outstanding PR cleanup

Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.

[archerzz]

I comment out this assertion and a few similar ones, due to the following error in playback mode only:

Error Message:
Expected: not equal to "Sanitized"
But was: "Sanitized"

Those could be due to the fact that test framework will sanitize some content it thinks sensitive during recording. So in the playback mode, the tests will fail.

[archerzz]

This test case actually doesn't work (I tried on main branch). The following error will be thrown.

"System.InvalidOperationException : Expected scope StorageAccountsOperations.StartCreate to be marked as failed > but it succeeded
Exception: System.NotSupportedException: Parent does not have a default constructor. The default constructor must be explicitly defined."

[archerzz]

Since Storage is involved here, if we can confirm that we can put this test case aside, it will accelerate the publish of Storage mgmt track2 SDK preview as well.

[archerzz]

This is to fix the out-of-memory error in nodejs vm during autorest execution. There is a similar fix in

azure-sdk-for-net/eng/scripts/Track1CodeCheck.ps1

Line 2 in 03e7ee9

$Env:NODE_OPTIONS = "--max-old-space-size=8192"