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

[AutoPR Microsoft.Azure.Management.Compute] For VmSizecustomization #4398

Draft
wants to merge 304 commits into
base: master
Choose a base branch
from

Conversation

openapi-sdkautomation[bot]
Copy link

Create to sync Azure/azure-rest-api-specs#14785

Installation Instructions

In order to use the generated nuget package in your app, you will have to use it from a private feed.
To create a private feed, see the following link:
https://docs.microsoft.com/en-us/nuget/hosting-packages/local-feeds
This will allow you to create a new local feed and add the location of the new feed as one of the sources.

Direct Download

The generated package can be directly downloaded from here:

@openapi-sdkautomation openapi-sdkautomation bot force-pushed the sdkAuto/14785/Microsoft.Azure.Management.Compute branch 2 times, most recently from 0957574 to 1dfeb8e Compare June 19, 2021 01:30
@openapi-sdkautomation openapi-sdkautomation bot force-pushed the sdkAuto/14785/Microsoft.Azure.Management.Compute branch from 1dfeb8e to 2bf5ad7 Compare June 24, 2021 08:00
pakrym and others added 14 commits June 24, 2021 08:07
# 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](https://github.com/Azure/azure-sdk-for-net/blob/main/CONTRIBUTING.md).**
- [ ] **The pull request does not introduce [breaking changes](https://github.com/dotnet/corefx/blob/master/Documentation/coding-guidelines/breaking-change-rules.md).**

### [General Guidelines and Best Practices](https://github.com/Azure/azure-sdk-for-net/blob/main/CONTRIBUTING.md#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](https://github.com/Azure/azure-powershell/blob/master/documentation/development-docs/cleaning-up-commits.md).

### [Testing Guidelines](https://github.com/Azure/azure-sdk-for-net/blob/main/CONTRIBUTING.md#testing-guidelines)
- [ ] Pull request includes test coverage for the included changes.

### [SDK Generation Guidelines](https://github.com/Azure/azure-sdk-for-net/blob/main/CONTRIBUTING.md#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](https://github.com/Azure/azure-sdk-for-net/tree/main/eng/mgmt/mgmtmetadata).
- [ ] 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.
…#22112)

* Added JWT writer

* fixed bugs

* Removed dependency on System.IdentityModel.Tokens.Jwt

* cleaned up tests

* Exposed registered claims as properties

* cleaned up code

* fixed build break

* Update sdk/webpubsub/Azure.Messaging.WebPubSub/tests/WebPubSubParseConnectionStringTests.cs

Co-authored-by: Matt Ellis <matt.ellis@microsoft.com>

* PR review feedback

* fixed build break

* we are ok with ASCII

* merged with main and updated to build

* Added error checks

* fixed misspelling

Co-authored-by: Matt Ellis <matt.ellis@microsoft.com>
* Check for API review status only if release date is set in changelog

* Change property name to ReleaseStatus

Co-authored-by: Praveen Kuttappan <praveen.kuttappan@gmail.com>
Co-authored-by: Christopher Scott <chriscott@hotmail.com>
Co-authored-by: Praveen Kuttappan <praveen.kuttappan@gmail.com>
…2059)

The focus of these changes is to introduce the `AmqpAnnotatedMessage`
abstraction as the basis for `EventData`, allowing access to the full set
of AMQP message data.  This enables scenarios such as interaction with
other message brokers that make use of the protocol in ways that are not otherwise
exposed within the Event Hubs client.

This set of changes will be followed by refactoring of the `AmqpMessageConverter`
to work with the full AMQP message rather than the known `EventData` subset.
* Regenerate .NET SDK for Event Grid 2021-06-01-preview

* remove fun code

* Record tests

* regenerate tests

* update version

* update assymblyinfo file

Co-authored-by: Ashraf Hamad <ahamad@ntdev.microsoft.com>
jsquire and others added 29 commits July 19, 2021 15:54
The focus of these changes is to remove the explicit references to the
`Azure.Core` package; these can cause the run to fail when rewritten for
daily runs due to existing project references to `Azure.Core`.
* Add AAD sample to README.

* Increase sleep time to allow permissions to propagate
Increment package version after release of Azure.Messaging.EventGrid
Co-authored-by: Heath Stewart <heaths@outlook.com>
* code generation

* avail

* updates

* RECORDINGS

* new recordings

* new recording

* new recording

* recordings

* updated test because it seems like the market place offer/sku does not exist anymore then re-recorded test

* Add new Property SpotRestorePolicy to VMScaleSets (Azure#21928)

* Generated Files

* Tests for Spot Restore Policy

* Versioning changes

* Scenario Test record

* customization (Azure#22054)

* update

* add capacity Reservation update

* customizations

* fix duplicates, Capaciy Reservation for vmss

* Generated SDK modules and recorded tests for Capacity Reservation and Capacity reservation in VM - API version 2021-04-01 (Azure#22383)

* updated sdk tests

* updated sdk

* updated sdk

* udpated cpe

* regenerated the sdk and re recorded the tests

* updated sdk

Co-authored-by: Theodore Chang <thchan@microsoft.com>

* Capacity Res. for Vmss (Azure#22429)

* starting changes for vmss sdk test for CR

* updating vmss test base with cr items

* adding vmss changes to vmss scenario test correctly

* adding vmss passing test

* adding tests and version updates

* moving cr location in param

Co-authored-by: Theodore Chang <thchan@microsoft.com>

* assembly version update

* remove duplicate definition in tests/helpers.cs

* update with CapacityReservations_Update 202 status return

* sdk gen from latest swagger change

* new recording for new test just added

* RestorePoint test recording

* code gen again to check diff

* Update compute_resource-manager.txt

update commit info to use latest compute swagger

* added morescription to package release note. updated compute_resource-manager.txt right commit.  re-generated sdk with CapacityReservationGroupInstanceViewTypes, CapacityReservationInstanceViewTypes, and ExpandTypesForGetCapacityReservationGroups changed to modelAsString true

* Update AzSdk.RP.props

Co-authored-by: Sandeep Vishnu <sandeepkv93@gmail.com>
Co-authored-by: hari-bodicherla <43284966+hari-bodicherla@users.noreply.github.com>
Co-authored-by: micahjo <69926788+micahjo@users.noreply.github.com>
… to Azure Storage Emulator with shortcut (Azure#22710)

* Set account name for dev store account
* Use TokenCredential in search clients

* Update public API file
* fix(auth): HMAC is recreated and re-issued on redirect.
…t` function (Azure#22735)

* add the ForwardsClientCalls attribute to UseClientContext function

* add forwardsClientCalls to ResourceGroupOperations

* update the tenantOperations
Co-authored-by: Chidozie Ononiwu <chononiw@microsoft.com>
Co-authored-by: Binjie Qian <biqian@microsoft.com>
* feedback from arch board review

* update api

* move to lowercase folder

* remove unused recordings
Azure#22781)

* SDK update for adding managed identity support for IaaS VM restore in recoveryservicesbackup

* updating sdk version
* [DataFactory]Added new features into 4.21.0

* update

* update
Merge c05934f68838f550b5328b766c5024e5d8169be9 into a38f415f168c5ad2410df089b80d1a39882f10ad
@openapi-sdkautomation openapi-sdkautomation bot force-pushed the sdkAuto/14785/Microsoft.Azure.Management.Compute branch from b1d5771 to 23dc164 Compare July 22, 2021 15:42
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.