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

[Hub Generated] Review request for Microsoft.PowerBIdedicated to add version stable/2017-10-01 #15915

Conversation

cfurmanczyk
Copy link
Contributor

@cfurmanczyk cfurmanczyk commented Sep 3, 2021

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.

Changelog

Add a changelog entry for this PR by answering the following questions:

  1. What's the purpose of the update?
    • new service onboarding
    • new API version
    • update existing version for new feature
    • update existing version to fix swagger quality issue in s360
    • Other, please clarify
  2. When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
  3. When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
  4. If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.
    • SDK of .NET (need service team to ensure code readiness)
    • SDK of Python
    • SDK of Java
    • SDK of Js
    • SDK of Go
    • PowerShell
    • CLI
    • Terraform
    • No refresh required for updates in this PR

Contribution checklist:

If any further question about AME onboarding or validation tools, please view the FAQ.

ARM API Review Checklist

Applicability: ⚠️

If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

  • Change to data plane APIs
  • Adding new properties
  • All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

  • Check this box if any of the following apply to the PR so that label “WaitForARMFeedback” will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

    • Adding a new service
    • Adding new API(s)
    • Adding a new API version
      -[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.
  • Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

  • If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist

If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

  • Removing API(s) in a stable version
  • Removing properties in a stable version
  • Removing API version(s) in a stable version
  • Updating API in a stable or public preview version with Breaking Change Validation errors
  • Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.

Please follow the link to find more details on PR review process.

@openapi-workflow-bot
Copy link

Hi, @cfurmanczyk Thanks for your PR. I am workflow bot for review process. Here are some small tips.

  • Please ensure to do self-check against checklists in first PR comment.
  • PR assignee is the person auto-assigned and responsible for your current PR reviewing and merging.
  • For specs comparison cross API versions, Use API Specs Comparison Report Generator
  • If there is CI failure(s), to fix CI error(s) is mandatory for PR merging; or you need to provide justification in PR comment for explanation. How to fix?

  • Any feedback about review process or workflow bot, pls contact swagger and tools team. [email protected]

    @openapi-workflow-bot
    Copy link

    [Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks.

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Sep 3, 2021

    Swagger Validation Report

    ️❌BreakingChange: 12 Errors, 0 Warnings failed [Detail]
    Rule Message
    1040 - AddedReadOnlyPropertyInResponse The new version has a new read-only property 'tenantId' in response that was not found in the old version.
    New: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L780:7
    Old: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L761:7
    1040 - AddedReadOnlyPropertyInResponse The new version has a new read-only property 'friendlyName' in response that was not found in the old version.
    New: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L780:7
    Old: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L761:7
    1040 - AddedReadOnlyPropertyInResponse The new version has a new read-only property 'origin' in response that was not found in the old version.
    New: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L635:7
    Old: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L635:7
    1041 - AddedPropertyInResponse The new version has a new property 'capacity' in response that was not found in the old version.
    New: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L837:7
    Old: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L818:7
    1041 - AddedPropertyInResponse The new version has a new property 'resourceType' in response that was not found in the old version.
    New: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L931:7
    Old: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L897:7
    1041 - AddedPropertyInResponse The new version has a new property 'description' in response that was not found in the old version.
    New: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L643:11
    Old: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L643:11
    1041 - AddedPropertyInResponse The new version has a new property 'properties' in response that was not found in the old version.
    New: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L635:7
    Old: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L635:7
    1045 - AddedOptionalProperty The new version has a new optional property 'capacity' that was not found in the old version.
    New: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L837:7
    Old: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L818:7
    1045 - AddedOptionalProperty The new version has a new optional property 'tenantId' that was not found in the old version.
    New: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L780:7
    Old: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L761:7
    1045 - AddedOptionalProperty The new version has a new optional property 'friendlyName' that was not found in the old version.
    New: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L780:7
    Old: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L761:7
    1045 - AddedOptionalProperty The new version has a new optional property 'tenantId' that was not found in the old version.
    New: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L866:7
    Old: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L842:7
    1045 - AddedOptionalProperty The new version has a new optional property 'friendlyName' that was not found in the old version.
    New: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L866:7
    Old: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L842:7
    ️⚠️LintDiff: 1 Warnings warning [Detail]
    The following errors/warnings are introduced by current PR:
    Rule Message
    ⚠️ R2001 - AvoidNestedProperties Consider using x-ms-client-flatten to provide a better end user experience
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L670


    The following errors/warnings exist before current PR submission:

    Rule Message
    R3030 - PathResourceProviderMatchNamespace The last resource provider 'Microsoft.PowerBIDedicated' doesn't match the namespace.
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L40
    R3030 - PathResourceProviderMatchNamespace The last resource provider 'Microsoft.PowerBIDedicated' doesn't match the namespace.
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L266
    R3030 - PathResourceProviderMatchNamespace The last resource provider 'Microsoft.PowerBIDedicated' doesn't match the namespace.
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L316
    R3030 - PathResourceProviderMatchNamespace The last resource provider 'Microsoft.PowerBIDedicated' doesn't match the namespace.
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L366
    R3030 - PathResourceProviderMatchNamespace The last resource provider 'Microsoft.PowerBIDedicated' doesn't match the namespace.
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L408
    R3030 - PathResourceProviderMatchNamespace The last resource provider 'Microsoft.PowerBIDedicated' doesn't match the namespace.
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L447
    R3030 - PathResourceProviderMatchNamespace The last resource provider 'Microsoft.PowerBIDedicated' doesn't match the namespace.
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L480
    R3030 - PathResourceProviderMatchNamespace The last resource provider 'Microsoft.PowerBIDedicated' doesn't match the namespace.
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L529
    R3030 - PathResourceProviderMatchNamespace The last resource provider 'Microsoft.PowerBIDedicated' doesn't match the namespace.
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L560
    R4018 - OperationsApiResponseSchema The response schema of operations API '/providers/Microsoft.PowerBIDedicated/operations' does not match the ARM specification. Please standardize the schema.
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L529
    R4037 - MissingTypeObject The schema 'OperationListResult' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L614
    R4037 - MissingTypeObject The schema 'display' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L641
    R4037 - MissingTypeObject The schema 'error' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L946
    ⚠️ R2029 - PageableOperation Based on the response model schema, operation 'Capacities_ListSkus' might be pageable. Consider adding the x-ms-pageable extension.
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L448
    ⚠️ R2029 - PageableOperation Based on the response model schema, operation 'Capacities_ListSkusForCapacity' might be pageable. Consider adding the x-ms-pageable extension.
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L481
    ⚠️ R3018 - EnumInsteadOfBoolean Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: nameAvailable
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L983
    ⚠️ R4002 - LocationMustHaveXmsMutability Property 'location' must have ''x-ms-mutability':['read', 'create']' extension defined. Resource Model: 'Resource'
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L613
    ⚠️ R4006 - DeprecatedXmsCodeGenerationSetting The x-ms-code-generation-setting extension is being deprecated. Please remove it and move settings to readme file for code generation.
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L7
    ⚠️ R4030 - UniqueXmsExample Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: Get details of a capacity
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L153
    ⚠️ R4030 - UniqueXmsExample Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: Get details of a capacity
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L319
    ⚠️ R4030 - UniqueXmsExample Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: Get details of a capacity
    Location: Microsoft.PowerBIdedicated/stable/2017-10-01/powerbidedicated.json#L411
    ️️✔️Avocado succeeded [Detail] [Expand]
    Validation passes for Avocado.
    ️️✔️ModelValidation succeeded [Detail] [Expand]
    Validation passes for ModelValidation.
    ️️✔️SemanticValidation succeeded [Detail] [Expand]
    Validation passes for SemanticValidation.
    ️️✔️Cross-Version Breaking Changes succeeded [Detail] [Expand]
    There are no breaking changes.
    ️️✔️CredScan succeeded [Detail] [Expand]
    There is no credential detected.
    ️️✔️[Staging] SDK Track2 Validation succeeded [Detail] [Expand]
    Validation passes for SDKTrack2Validation

    ️️✔️[Staging] PrettierCheck succeeded [Detail] [Expand]
    Validation passes for PrettierCheck.
    ️️✔️[Staging] SpellCheck succeeded [Detail] [Expand]
    Validation passes for SpellCheck.
    ️️✔️[Staging] Lint(RPaaS) succeeded [Detail] [Expand]
    Validation passes for Lint(RPaaS).
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Sep 3, 2021

    Swagger Generation Artifacts

    ️️✔️[Staging] ApiDocPreview succeeded [Detail] [Expand]
     Please click here to preview with your @microsoft account. 
    ️❌[Staging] SDK Breaking Change Tracking failed [Detail]

    Breaking Changes Tracking

    ️✔️azure-sdk-for-go - powerbidedicated/mgmt/2021-01-01/powerbidedicated - Approved - v58.3.0
    azure-sdk-for-go - powerbidedicated/mgmt/2017-10-01/powerbidedicated - Approved - v58.3.0
    +	Field `Code` of struct `ErrorResponse` has been removed
    +	Field `Message` of struct `ErrorResponse` has been removed
    ️✔️azure-sdk-for-python-track2 - track2_azure-mgmt-powerbidedicated - 1.0.0
    ️❌ azure-sdk-for-net failed [Detail]
    • Failed [Logs]Release - Generate from 99c77e2. SDK Automation 14.0.0
      warn	Skip initScript due to not configured
      command	sudo apt-get install -y dotnet-sdk-5.0
      command	autorest --version=V2 --csharp --reflect-api-versions --license-header=MICROSOFT_MIT_NO_VERSION [email protected]/[email protected] --csharp-sdks-folder=/home/vsts/work/1/s/azure-sdk-for-net/sdk ../azure-rest-api-specs/specification/powerbidedicated/resource-manager/readme.md
      cmderr	[Autorest] realpath(): Permission denied
      cmderr	[Autorest] realpath(): Permission denied
      cmderr	[Autorest] realpath(): Permission denied
      cmderr	[Autorest] realpath(): Permission denied
      cmderr	[Autorest] realpath(): Permission denied
      cmderr	[Autorest] realpath(): Permission denied
    • Microsoft.Azure.Management.PowerBIDedicated [View full logs]  [Release SDK Changes]
      cmdout	[msbuild]      2>/home/vsts/work/1/s/azure-sdk-for-net/sdk/powerbidedicated/Microsoft.Azure.Management.PowerBIDedicated/src/Customizations/CustomCapacitiesOperations.cs(13,47): error CS0535: 'CustomCapacitiesOperations' does not implement interface member 'ICapacitiesOperations.CheckNameAvailabilityWithHttpMessagesAsync(string, CheckCapacityNameAvailabilityParameters, Dictionary<string, List<string>>, CancellationToken)' [/home/vsts/work/1/s/azure-sdk-for-net/sdk/powerbidedicated/Microsoft.Azure.Management.PowerBIDedicated/src/Microsoft.Azure.Management.PowerBIDedicated.csproj]
      cmdout	[msbuild]      2>/home/vsts/work/1/s/azure-sdk-for-net/sdk/powerbidedicated/Microsoft.Azure.Management.PowerBIDedicated/src/Customizations/CustomCapacitiesOperations.cs(13,47): error CS0535: 'CustomCapacitiesOperations' does not implement interface member 'ICapacitiesOperations.CheckNameAvailabilityWithHttpMessagesAsync(string, CheckCapacityNameAvailabilityParameters, Dictionary<string, List<string>>, CancellationToken)' [/home/vsts/work/1/s/azure-sdk-for-net/sdk/powerbidedicated/Microsoft.Azure.Management.PowerBIDedicated/src/Microsoft.Azure.Management.PowerBIDedicated.csproj]
      cmdout	[msbuild] /home/vsts/work/1/s/azure-sdk-for-net/sdk/powerbidedicated/Microsoft.Azure.Management.PowerBIDedicated/src/Customizations/CustomCapacitiesOperations.cs(13,47): error CS0535: 'CustomCapacitiesOperations' does not implement interface member 'ICapacitiesOperations.CheckNameAvailabilityWithHttpMessagesAsync(string, CheckCapacityNameAvailabilityParameters, Dictionary<string, List<string>>, CancellationToken)' [/home/vsts/work/1/s/azure-sdk-for-net/sdk/powerbidedicated/Microsoft.Azure.Management.PowerBIDedicated/src/Microsoft.Azure.Management.PowerBIDedicated.csproj]
      cmdout	[msbuild]      2>/home/vsts/work/1/s/azure-sdk-for-net/sdk/powerbidedicated/Microsoft.Azure.Management.PowerBIDedicated/src/Customizations/CustomCapacitiesOperations.cs(13,47): error CS0535: 'CustomCapacitiesOperations' does not implement interface member 'ICapacitiesOperations.CheckNameAvailabilityWithHttpMessagesAsync(string, CheckCapacityNameAvailabilityParameters, Dictionary<string, List<string>>, CancellationToken)' [/home/vsts/work/1/s/azure-sdk-for-net/sdk/powerbidedicated/Microsoft.Azure.Management.PowerBIDedicated/src/Microsoft.Azure.Management.PowerBIDedicated.csproj]
      cmdout	[msbuild]          /home/vsts/work/1/s/azure-sdk-for-net/sdk/powerbidedicated/Microsoft.Azure.Management.PowerBIDedicated/src/Customizations/CustomCapacitiesOperations.cs(13,47): error CS0535: 'CustomCapacitiesOperations' does not implement interface member 'ICapacitiesOperations.CheckNameAvailabilityWithHttpMessagesAsync(string, CheckCapacityNameAvailabilityParameters, Dictionary<string, List<string>>, CancellationToken)' [/home/vsts/work/1/s/azure-sdk-for-net/sdk/powerbidedicated/Microsoft.Azure.Management.PowerBIDedicated/src/Microsoft.Azure.Management.PowerBIDedicated.csproj]
      cmdout	[msbuild]          /home/vsts/work/1/s/azure-sdk-for-net/sdk/powerbidedicated/Microsoft.Azure.Management.PowerBIDedicated/src/Customizations/CustomCapacitiesOperations.cs(13,47): error CS0535: 'CustomCapacitiesOperations' does not implement interface member 'ICapacitiesOperations.CheckNameAvailabilityWithHttpMessagesAsync(string, CheckCapacityNameAvailabilityParameters, Dictionary<string, List<string>>, CancellationToken)' [/home/vsts/work/1/s/azure-sdk-for-net/sdk/powerbidedicated/Microsoft.Azure.Management.PowerBIDedicated/src/Microsoft.Azure.Management.PowerBIDedicated.csproj]
      cmdout	[msbuild]          /home/vsts/work/1/s/azure-sdk-for-net/sdk/powerbidedicated/Microsoft.Azure.Management.PowerBIDedicated/src/Customizations/CustomCapacitiesOperations.cs(13,47): error CS0535: 'CustomCapacitiesOperations' does not implement interface member 'ICapacitiesOperations.CheckNameAvailabilityWithHttpMessagesAsync(string, CheckCapacityNameAvailabilityParameters, Dictionary<string, List<string>>, CancellationToken)' [/home/vsts/work/1/s/azure-sdk-for-net/sdk/powerbidedicated/Microsoft.Azure.Management.PowerBIDedicated/src/Microsoft.Azure.Management.PowerBIDedicated.csproj]
      cmdout	[msbuild]          /home/vsts/work/1/s/azure-sdk-for-net/sdk/powerbidedicated/Microsoft.Azure.Management.PowerBIDedicated/src/Customizations/CustomCapacitiesOperations.cs(13,47): error CS0535: 'CustomCapacitiesOperations' does not implement interface member 'ICapacitiesOperations.CheckNameAvailabilityWithHttpMessagesAsync(string, CheckCapacityNameAvailabilityParameters, Dictionary<string, List<string>>, CancellationToken)' [/home/vsts/work/1/s/azure-sdk-for-net/sdk/powerbidedicated/Microsoft.Azure.Management.PowerBIDedicated/src/Microsoft.Azure.Management.PowerBIDedicated.csproj]
      error	Script return with result [failed] code [1] signal [null] cwd [azure-sdk-for-net]: dotnet
    ️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs]Release - Generate from 99c77e2. SDK Automation 14.0.0
      command	sh ./eng/initScript.sh ../../../../../azure-sdk-for-go_tmp/initInput.json ../../../../../azure-sdk-for-go_tmp/initOutput.json
      command	generator automation ../../../../../azure-sdk-for-go_tmp/generateInput.json ../../../../../azure-sdk-for-go_tmp/generateOutput.json
    • ️✔️powerbidedicated/mgmt/2021-01-01/powerbidedicated [View full logs]  [Release SDK Changes]
      info	[Changelog] No exported changes
    • ️✔️powerbidedicated/mgmt/2017-10-01/powerbidedicated [View full logsBreaking Change Detected
      info	[Changelog] ### Breaking Changes
      info	[Changelog]
      info	[Changelog] - Field `Code` of struct `ErrorResponse` has been removed
      info	[Changelog] - Field `Message` of struct `ErrorResponse` has been removed
      info	[Changelog]
      info	[Changelog] ### New Content
      info	[Changelog]
      info	[Changelog] - New function `DedicatedCapacityMutableProperties.MarshalJSON() ([]byte, error)`
      info	[Changelog] - New function `LogSpecification.MarshalJSON() ([]byte, error)`
      info	[Changelog] - New function `MetricSpecification.MarshalJSON() ([]byte, error)`
      info	[Changelog] - New function `MetricSpecificationDimensionsItem.MarshalJSON() ([]byte, error)`
      info	[Changelog] - New struct `ErrorResponseError`
      info	[Changelog] - New struct `LogSpecification`
      info	[Changelog] - New struct `MetricSpecification`
      info	[Changelog] - New struct `MetricSpecificationDimensionsItem`
      info	[Changelog] - New struct `OperationProperties`
      info	[Changelog] - New struct `ServiceSpecification`
      info	[Changelog] - New field `Error` in struct `ErrorResponse`
      info	[Changelog] - New field `Origin` in struct `Operation`
      info	[Changelog] - New field `Properties` in struct `Operation`
      info	[Changelog] - New field `Mode` in struct `DedicatedCapacityProperties`
      info	[Changelog] - New field `TenantID` in struct `DedicatedCapacityProperties`
      info	[Changelog] - New field `FriendlyName` in struct `DedicatedCapacityProperties`
      info	[Changelog] - New field `Mode` in struct `DedicatedCapacityMutableProperties`
      info	[Changelog] - New field `TenantID` in struct `DedicatedCapacityMutableProperties`
      info	[Changelog] - New field `FriendlyName` in struct `DedicatedCapacityMutableProperties`
      info	[Changelog] - New field `Description` in struct `OperationDisplay`
      info	[Changelog] - New field `ResourceType` in struct `SkuDetailsForExistingResource`
      info	[Changelog] - New field `Capacity` in struct `ResourceSku`
      info	[Changelog]
      info	[Changelog] Total 1 breaking change(s), 23 additive change(s).
      info	[Changelog]
    ️️✔️ azure-sdk-for-js succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs]Release - Generate from 99c77e2. SDK Automation 14.0.0
      warn	Skip initScript due to not configured
      command	autorest --version=V2 --typescript --license-header=MICROSOFT_MIT_NO_VERSION [email protected]/[email protected] --typescript-sdks-folder=/home/vsts/work/1/s/azure-sdk-for-js/azure-sdk-for-js ../../azure-rest-api-specs/specification/powerbidedicated/resource-manager/readme.md
    • ️✔️@azure/arm-powerbidedicated [View full logs]  [Release SDK Changes]
      cmderr	[npmPack] loaded rollup.config.js with warnings
      cmderr	[npmPack] (!) Unused external imports
      cmderr	[npmPack] default imported from external module 'rollup' but never used
      cmderr	[npmPack] ./esm/powerBIDedicatedManagementClient.js → ./dist/arm-powerbidedicated.js...
      cmderr	[npmPack] created ./dist/arm-powerbidedicated.js in 289ms
    ️⚠️ azure-sdk-for-python-track2 warning [Detail]
    ️⚠️ azure-resource-manager-schemas warning [Detail]
    • ⚠️Warning [Logs]Release - Generate from 99c77e2. Schema Automation 14.0.0
      command	.sdkauto/initScript.sh ../azure-resource-manager-schemas_tmp/initInput.json ../azure-resource-manager-schemas_tmp/initOutput.json
      cmderr	[initScript.sh] WARN old lockfile
      cmderr	[initScript.sh] npm WARN old lockfile The package-lock.json file was created with an old version of npm,
      cmderr	[initScript.sh] npm WARN old lockfile so supplemental metadata must be fetched from the registry.
      cmderr	[initScript.sh] npm WARN old lockfile
      cmderr	[initScript.sh] npm WARN old lockfile This is a one-time fix-up, please be patient...
      cmderr	[initScript.sh] npm WARN old lockfile
      warn	File azure-resource-manager-schemas_tmp/initOutput.json not found to read
      command	.sdkauto/generateScript.sh ../azure-resource-manager-schemas_tmp/generateInput.json ../azure-resource-manager-schemas_tmp/generateOutput.json
      cmderr	[generateScript.sh] (node:2428) UnhandledPromiseRejectionWarning: SyntaxError: Unexpected end of JSON input
      cmderr	[generateScript.sh]     at JSON.parse (<anonymous>)
      cmderr	[generateScript.sh]     at Object.readJsonFile (/home/vsts/work/1/s/azure-resource-manager-schemas/generator/utils.ts:176:17)
      cmderr	[generateScript.sh]     at getCurrentTemplateRefs (/home/vsts/work/1/s/azure-resource-manager-schemas/generator/generate.ts:293:21)
      cmderr	[generateScript.sh]     at /home/vsts/work/1/s/azure-resource-manager-schemas/generator/generate.ts:300:29
      cmderr	[generateScript.sh] (Use `node --trace-warnings ...` to show where the warning was created)
      cmderr	[generateScript.sh] (node:2428) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
      cmderr	[generateScript.sh] (node:2428) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
    • ️✔️powerbidedicated [View full logs]  [Release Schema Changes]
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-workflow-bot
    Copy link

    Hi @cfurmanczyk, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review.
    Action: To initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
    If you want to know the production traffic statistic, please see ARM Traffic statistic.
    If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ms/swaggerfeedback.

    @openapi-workflow-bot
    Copy link

    NewApiVersionRequired reason:

    A service’s API is a contract with customers and is represented by using the api-version query parameter. Changes such as adding an optional property to a request/response or introducing a new operation is a change to the service’s contract and therefore requires a new api-version value. This is critically important for documentation, client libraries, and customer support.

    EXAMPLE: if a customer calls a service in the public cloud using api-version=2020-07-27, the new property or operation may exist but if they call the service in a government cloud, air-gapped cloud, or Azure Stack Hub cloud using the same api-version, the property or operation may not exist. Because there is no clear relationship between the service api-version and the new property/operation, customers can’t trust the documentation and Azure customer have difficulty helping customers diagnose issues. In addition, each client library version documents the service version it supports. When an optional property or new operation is added to a service and its Swagger, new client libraries must be produced to expose this functionality to customers. Without updating the api-version, it is unclear to customers which version of a client library supports these new features.

    @cfurmanczyk cfurmanczyk force-pushed the dev-powerbidedicated-Microsoft.PowerBIdedicated-2017-10-01 branch from 76fbd05 to f882f4a Compare September 3, 2021 22:00
    @msyyc msyyc requested a review from david-msft September 6, 2021 02:40
    @msyyc
    Copy link
    Member

    msyyc commented Sep 6, 2021

    Hi @ArcturusZhang Please help confirm breaking change for Go

    Copy link
    Contributor

    @david-msft david-msft left a comment

    Choose a reason for hiding this comment

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

    rest looks good to me

    @msyyc
    Copy link
    Member

    msyyc commented Sep 17, 2021

    @cfurmanczyk please follow the bot advice to ask for approve for swagger breaking change.
    image

    @ArcturusZhang ArcturusZhang added the Approved-SdkBreakingChange-Go Approve the breaking change tracking for azure-sdk-for-go label Sep 17, 2021
    @cfurmanczyk
    Copy link
    Contributor Author

    @ArcturusZhang Added fields are to satisfy s360 issues where the swagger specification is missing fields our service provides.

    @msyyc
    Copy link
    Member

    msyyc commented Oct 21, 2021

    /azp run

    @azure-pipelines
    Copy link

    Azure Pipelines successfully started running 1 pipeline(s).

    @JeffreyRichter JeffreyRichter added the Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 label Nov 3, 2021
    @msyyc msyyc merged commit 99c77e2 into Azure:main Nov 9, 2021
    ghost pushed a commit to Azure/azure-resource-manager-schemas that referenced this pull request Nov 9, 2021
    LeiWang3 pushed a commit to LeiWang3/azure-rest-api-specs that referenced this pull request Mar 31, 2022
    …version stable/2017-10-01 (Azure#15915)
    
    * Update missing properties in PowerBIDedicated objects 2017-10-01
    
    * Move PowerBIDedicated properties to new definitions
    
    * Realign error response to recommended schema. 202 response not necessary in older api-version.
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 Approved-SdkBreakingChange-Go Approve the breaking change tracking for azure-sdk-for-go CI-BreakingChange-Go FixS360
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    5 participants