Skip to content

Conversation

@sandeepkv93
Copy link
Contributor

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.

/// <param name="extendedLocation">The extended location of the Virtual
/// Machine Scale Set.</param>
public VirtualMachineScaleSet(string location, string id = default(string), string name = default(string), string type = default(string), IDictionary<string, string> tags = default(IDictionary<string, string>), Sku sku = default(Sku), Plan plan = default(Plan), UpgradePolicy upgradePolicy = default(UpgradePolicy), AutomaticRepairsPolicy automaticRepairsPolicy = default(AutomaticRepairsPolicy), VirtualMachineScaleSetVMProfile virtualMachineProfile = default(VirtualMachineScaleSetVMProfile), string provisioningState = default(string), bool? overprovision = default(bool?), bool? doNotRunExtensionsOnOverprovisionedVMs = default(bool?), string uniqueId = default(string), bool? singlePlacementGroup = default(bool?), bool? zoneBalance = default(bool?), int? platformFaultDomainCount = default(int?), SubResource proximityPlacementGroup = default(SubResource), SubResource hostGroup = default(SubResource), AdditionalCapabilities additionalCapabilities = default(AdditionalCapabilities), ScaleInPolicy scaleInPolicy = default(ScaleInPolicy), string orchestrationMode = default(string), VirtualMachineScaleSetIdentity identity = default(VirtualMachineScaleSetIdentity), IList<string> zones = default(IList<string>), ExtendedLocation extendedLocation = default(ExtendedLocation))
public VirtualMachineScaleSet(string location, string id = default(string), string name = default(string), string type = default(string), IDictionary<string, string> tags = default(IDictionary<string, string>), Sku sku = default(Sku), Plan plan = default(Plan), UpgradePolicy upgradePolicy = default(UpgradePolicy), AutomaticRepairsPolicy automaticRepairsPolicy = default(AutomaticRepairsPolicy), VirtualMachineScaleSetVMProfile virtualMachineProfile = default(VirtualMachineScaleSetVMProfile), string provisioningState = default(string), bool? overprovision = default(bool?), bool? doNotRunExtensionsOnOverprovisionedVMs = default(bool?), string uniqueId = default(string), bool? singlePlacementGroup = default(bool?), bool? zoneBalance = default(bool?), int? platformFaultDomainCount = default(int?), SubResource proximityPlacementGroup = default(SubResource), SubResource hostGroup = default(SubResource), AdditionalCapabilities additionalCapabilities = default(AdditionalCapabilities), ScaleInPolicy scaleInPolicy = default(ScaleInPolicy), string orchestrationMode = default(string), SpotRestorePolicy spotRestorePolicy = default(SpotRestorePolicy), VirtualMachineScaleSetIdentity identity = default(VirtualMachineScaleSetIdentity), IList<string> zones = default(IList<string>), ExtendedLocation extendedLocation = default(ExtendedLocation))
Copy link
Contributor

Choose a reason for hiding this comment

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

This will require a customization.

@Sandido
Copy link
Contributor

Sandido commented Jun 17, 2021

The test failures in the CI checks are failing due to the API version not being updated for the Compute RP tests.

@grizzlytheodore
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list.

@grizzlytheodore
Copy link
Contributor

/azp rerun

@azure-pipelines
Copy link

Command 'rerun' is not supported by Azure Pipelines.

Supported commands
  • help:
    • Get descriptions, examples and documentation about supported commands
    • Example: help "command_name"
  • list:
    • List all pipelines for this repository using a comment.
    • Example: "list"
  • run:
    • Run all pipelines or specific pipelines for this repository using a comment. Use this command by itself to trigger all related pipelines, or specify specific pipelines to run.
    • Example: "run" or "run pipeline_name, pipeline_name, pipeline_name"
  • where:
    • Report back the Azure DevOps orgs that are related to this repository and org
    • Example: "where"

See additional documentation.

@nisha-bhatia
Copy link
Contributor

@sandeepkv93 Could you please provide the link to the Swagger PR?

@grizzlytheodore
Copy link
Contributor

@grizzlytheodore grizzlytheodore merged commit f068bff into Azure:feature/cplat-2021-04-01 Jun 22, 2021
@grizzlytheodore grizzlytheodore mentioned this pull request Jun 22, 2021
11 tasks
allenjzhang pushed a commit that referenced this pull request Jul 20, 2021
* 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 (#21928)

* Generated Files

* Tests for Spot Restore Policy

* Versioning changes

* Scenario Test record

* customization (#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 (#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 <[email protected]>

* Capacity Res. for Vmss (#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 <[email protected]>

* 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 <[email protected]>
Co-authored-by: hari-bodicherla <[email protected]>
Co-authored-by: micahjo <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants