Skip to content

Comments

Align Microsoft.ServiceNetworking with repo conventions#24060

Closed
mikeharder wants to merge 5 commits intoAzure:mainfrom
mikeharder:typespec-ci-traffic-controller
Closed

Align Microsoft.ServiceNetworking with repo conventions#24060
mikeharder wants to merge 5 commits intoAzure:mainfrom
mikeharder:typespec-ci-traffic-controller

Conversation

@mikeharder
Copy link
Member

No description provided.

@openapi-workflow-bot
Copy link

Hi, @mikeharder 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. vscswagger@microsoft.com

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented May 19, 2023

    Swagger Validation Report

    ️❌BreakingChange: 25 Errors, 0 Warnings failed [Detail]
    compared swaggers (via Oad v0.10.4)] new version base version
    TrafficController.json 2023-05-01-preview(de72737) 2023-05-01-preview(main)
    Rule Message
    1025 - RequiredStatusChange The 'required' status changed from the old version('False') to the new version('True').
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L1113:7
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L1219:7
    1034 - AddedRequiredProperty The new version has new required property 'fqdn' that was not found in the old version.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L1071:9
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L1177:9
    1034 - AddedRequiredProperty The new version has new required property 'fqdn' that was not found in the old version.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L1111:5
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L1217:5
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L175:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L195:11
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L214:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L240:11
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L279:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L311:11
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L327:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L365:11
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L386:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L430:11
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L430:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L480:11
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L437:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L488:11
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L476:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L533:11
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L483:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L541:11
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L548:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L612:11
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L555:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L620:11
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L603:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L674:11
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L610:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L682:11
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L669:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L747:11
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L713:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L797:11
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L720:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L805:11
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L759:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L850:11
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L766:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L858:11
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L831:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L929:11
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L838:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L937:11
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L886:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L991:11
    1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
    New: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L893:11
    Old: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L999:11
    ️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
    There are no breaking changes.
    ️⌛CredScan pending [Detail]
    ️❌LintDiff: 8 Errors, 17 Warnings failed [Detail]
    compared tags (via openapi-validator v2.1.2) new version base version
    package-2023-05-01-preview package-2023-05-01-preview(de72737) package-2023-05-01-preview(main)

    [must fix]The following errors/warnings are introduced by current PR:

    Rule Message Related RPC [For API reviewers]
    ResourceNameRestriction The resource name parameter 'trafficControllerName' should be defined with a 'pattern' restriction.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L158
    RPC-Uri-V1-05
    ResourceNameRestriction The resource name parameter 'trafficControllerName' should be defined with a 'pattern' restriction.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L369
    RPC-Uri-V1-05
    ResourceNameRestriction The resource name parameter 'trafficControllerName' should be defined with a 'pattern' restriction.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L413
    RPC-Uri-V1-05
    ResourceNameRestriction The resource name parameter 'associationName' should be defined with a 'pattern' restriction.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L413
    RPC-Uri-V1-05
    ResourceNameRestriction The resource name parameter 'trafficControllerName' should be defined with a 'pattern' restriction.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L652
    RPC-Uri-V1-05
    ResourceNameRestriction The resource name parameter 'trafficControllerName' should be defined with a 'pattern' restriction.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L696
    RPC-Uri-V1-05
    ResourceNameRestriction The resource name parameter 'frontendName' should be defined with a 'pattern' restriction.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L696
    RPC-Uri-V1-05
    RequiredReadOnlyProperties Property 'fqdn' is a required property. It should not be marked as 'readonly'
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L1111
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L57
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L88
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L122
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L159
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L198
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L263
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L311
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L370
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L414
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L460
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L532
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L587
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L653
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L697
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L743
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L815
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L870


    The following errors/warnings exist before current PR submission:

    Rule Message
    PutResponseSchemaDescription Description of 200 response code of a PUT operation MUST include term 'update'.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L231
    PutResponseSchemaDescription Description of 200 response code of a PUT operation MUST include term 'update'.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L500
    PutResponseSchemaDescription Description of 200 response code of a PUT operation MUST include term 'update'.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L783
    ⚠️ ProvisioningStateSpecifiedForLRODelete 200 response schema in long running DELETE operation is missing ProvisioningState property. A LRO DELETE operations 200 response schema must have ProvisioningState specified.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L336
    ⚠️ ProvisioningStateSpecifiedForLRODelete 200 response schema in long running DELETE operation is missing ProvisioningState property. A LRO DELETE operations 200 response schema must have ProvisioningState specified.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L619
    ⚠️ ProvisioningStateSpecifiedForLRODelete 200 response schema in long running DELETE operation is missing ProvisioningState property. A LRO DELETE operations 200 response schema must have ProvisioningState specified.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L902
    ⚠️ SchemaDescriptionOrTitle Schema should have a description or title.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L1025
    ⚠️ SchemaDescriptionOrTitle Schema should have a description or title.
    Location: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L1145
    ️️✔️Avocado succeeded [Detail] [Expand]
    Validation passes for Avocado.
    ️️✔️ApiReadinessCheck succeeded [Detail] [Expand]
    ️⚠️~[Staging] ServiceAPIReadinessTest: 0 Warnings warning [Detail]

    API Test is not triggered due to precheck failure. Check pipeline log for details.

    ️️✔️SwaggerAPIView succeeded [Detail] [Expand]
    ️️✔️CadlAPIView succeeded [Detail] [Expand]
    ️️✔️TypeSpecAPIView succeeded [Detail] [Expand]
    ️❌ModelValidation: 17 Errors, 0 Warnings failed [Detail]
    Rule Message
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in Operations_List.
    Url: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L57:14
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in TrafficControllerInterface_ListBySubscription.
    Url: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L88:14
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in TrafficControllerInterface_ListByResourceGroup.
    Url: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L122:14
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in TrafficControllerInterface_Get.
    Url: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L159:14
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in TrafficControllerInterface_CreateOrUpdate.
    Url: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L198:14
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in TrafficControllerInterface_Update.
    Url: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L263:16
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in TrafficControllerInterface_Delete.
    Url: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L311:17
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in AssociationsInterface_ListByTrafficController.
    Url: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L370:14
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in AssociationsInterface_Get.
    Url: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L414:14
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in AssociationsInterface_CreateOrUpdate.
    Url: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L460:14
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in AssociationsInterface_Update.
    Url: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L532:16
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in AssociationsInterface_Delete.
    Url: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L587:17
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in FrontendsInterface_ListByTrafficController.
    Url: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L653:14
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in FrontendsInterface_Get.
    Url: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L697:14
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in FrontendsInterface_CreateOrUpdate.
    Url: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L743:14
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in FrontendsInterface_Update.
    Url: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L815:16
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in FrontendsInterface_Delete.
    Url: Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json#L870:17
    ️️✔️SemanticValidation succeeded [Detail] [Expand]
    Validation passes for SemanticValidation.
    ️⌛PoliCheck pending [Detail]
    ️️✔️PrettierCheck succeeded [Detail] [Expand]
    Validation passes for PrettierCheck.
    ️️✔️SpellCheck succeeded [Detail] [Expand]
    Validation passes for SpellCheck.
    ️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
    Validation passes for Lint(RPaaS).
    ️️✔️CadlValidation succeeded [Detail] [Expand]
    Validation passes for CadlValidation.
    ️️✔️TypeSpec Validation succeeded [Detail]
    Rule Message
    InConsistentSwagger "details":"The generated swagger file 2023-05-01-preview/TrafficController.json from typespec specification/servicenetworking/Microsoft.ServiceNetworking is not the same as the '/mnt/vss/_work/1/azure-rest-api-specs/specification/servicenetworking/resource-manager/Microsoft.ServiceNetworking/preview/2023-05-01-preview/TrafficController.json' in PR,
    please make sure the swagger is consistent with the generated swagger. You can find the difference in the pipeline log."
    ️️✔️PR Summary succeeded [Detail] [Expand]
    Validation passes for Summary.
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented May 19, 2023

    Swagger Generation Artifacts

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

    Breaking Changes Tracking

    azure-sdk-for-go - sdk/resourcemanager/servicenetworking/armservicenetworking - 0.3.0
    +	Enum `FrontendIPAddressVersion` has been removed
    +	Field `IPAddressVersion`, `Mode`, `PublicIPAddress` of struct `FrontendProperties` has been removed
    +	Field `Properties` of struct `FrontendUpdate` has been removed
    +	Field `Properties` of struct `TrafficControllerUpdate` has been removed
    +	Struct `FrontendPropertiesIPAddress` has been removed
    +	Struct `FrontendUpdateProperties` has been removed
    +	Type of `AssociationProperties.AssociationType` has been changed from `*string` to `*AssociationType`
    +	Type of `AssociationUpdateProperties.AssociationType` has been changed from `*string` to `*AssociationType`
    +	Type of `AssociationUpdateProperties.Subnet` has been changed from `*AssociationSubnet` to `*AssociationSubnetUpdate`
    azure-sdk-for-python-track2 - track2_azure-mgmt-servicenetworking - 1.0.0b1
    +	Model AssociationUpdate no longer has parameter properties
    +	Model Frontend no longer has parameter ip_address_version
    +	Model Frontend no longer has parameter mode
    +	Model Frontend no longer has parameter public_ip_address
    +	Model FrontendUpdate no longer has parameter properties
    +	Model TrafficControllerUpdate no longer has parameter properties
    ️⚠️ azure-sdk-for-python-track2 warning [Detail]
    • ⚠️Warning [Logs] Generate from 50cf3a2a4f5bd54b2edf663fa6ba92e67ad5e447. SDK Automation 14.0.0
      command	sh scripts/automation_init.sh ../azure-sdk-for-python_tmp/initInput.json ../azure-sdk-for-python_tmp/initOutput.json
      cmderr	[automation_init.sh] WARNING: Skipping azure-nspkg as it is not installed.
      warn		specification/servicenetworking/Microsoft.ServiceNetworking/tspconfig.yaml skipped due to azure-sdk-for-python-track2 not found in tspconfig.yaml
      command	sh scripts/automation_generate.sh ../azure-sdk-for-python_tmp/generateInput.json ../azure-sdk-for-python_tmp/generateOutput.json
      cmderr	[automation_generate.sh] npm notice
      cmderr	[automation_generate.sh] npm notice New minor version of npm available! 9.5.1 -> 9.6.7
      cmderr	[automation_generate.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.6.7>
      cmderr	[automation_generate.sh] npm notice Run `npm install -g npm@9.6.7` to update!
      cmderr	[automation_generate.sh] npm notice
    • ️✔️track2_azure-mgmt-servicenetworking [View full logs]  [Preview SDK Changes] Breaking Change Detected
      info	[Changelog] ### Features Added
      info	[Changelog]
      info	[Changelog]   - Model AssociationUpdate has a new parameter association_type
      info	[Changelog]   - Model AssociationUpdate has a new parameter subnet
      info	[Changelog]   - Model Frontend has a new parameter fqdn
      info	[Changelog]
      info	[Changelog] ### Breaking Changes
      info	[Changelog]
      info	[Changelog]   - Model AssociationUpdate no longer has parameter properties
      info	[Changelog]   - Model Frontend no longer has parameter ip_address_version
      info	[Changelog]   - Model Frontend no longer has parameter mode
      info	[Changelog]   - Model Frontend no longer has parameter public_ip_address
      info	[Changelog]   - Model FrontendUpdate no longer has parameter properties
      info	[Changelog]   - Model TrafficControllerUpdate no longer has parameter properties
    ️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs] Generate from 50cf3a2a4f5bd54b2edf663fa6ba92e67ad5e447. SDK Automation 14.0.0
      command	sh ./eng/scripts/automation_init.sh ../../../../../azure-sdk-for-go_tmp/initInput.json ../../../../../azure-sdk-for-go_tmp/initOutput.json
      warn		specification/servicenetworking/Microsoft.ServiceNetworking/tspconfig.yaml skipped due to azure-sdk-for-go not found in tspconfig.yaml
      command	generator automation-v2 ../../../../../azure-sdk-for-go_tmp/generateInput.json ../../../../../azure-sdk-for-go_tmp/generateOutput.json
    • ️✔️sdk/resourcemanager/servicenetworking/armservicenetworking [View full logs]  [Preview SDK Changes] Breaking Change Detected
      info	[Changelog] ### Breaking Changes
      info	[Changelog]
      info	[Changelog] - Type of `AssociationProperties.AssociationType` has been changed from `*string` to `*AssociationType`
      info	[Changelog] - Type of `AssociationUpdateProperties.AssociationType` has been changed from `*string` to `*AssociationType`
      info	[Changelog] - Type of `AssociationUpdateProperties.Subnet` has been changed from `*AssociationSubnet` to `*AssociationSubnetUpdate`
      info	[Changelog] - Enum `FrontendIPAddressVersion` has been removed
      info	[Changelog] - Struct `FrontendPropertiesIPAddress` has been removed
      info	[Changelog] - Struct `FrontendUpdateProperties` has been removed
      info	[Changelog] - Field `IPAddressVersion`, `Mode`, `PublicIPAddress` of struct `FrontendProperties` has been removed
      info	[Changelog] - Field `Properties` of struct `FrontendUpdate` has been removed
      info	[Changelog] - Field `Properties` of struct `TrafficControllerUpdate` has been removed
      info	[Changelog]
      info	[Changelog] ### Features Added
      info	[Changelog]
      info	[Changelog] - New enum type `AssociationType` with values `AssociationTypeSubnets`
      info	[Changelog] - New struct `AssociationSubnetUpdate`
      info	[Changelog] - New field `Fqdn` in struct `FrontendProperties`
      info	[Changelog]
      info	[Changelog] Total 10 breaking change(s), 5 additive change(s).
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented May 19, 2023

    Generated ApiView

    Language Package Name ApiView Link
    Swagger Microsoft.ServiceNetworking https://apiview.dev/Assemblies/Review/6fe6b6157b3b45038e9790707f354d0b
    TypeSpec Microsoft.ServiceNetworking https://apiview.dev/Assemblies/Review/3c7ad7b2a9654f3a8b8f4d83c879c69a
    Go sdk/resourcemanager/servicenetworking/armservicenetworking https://apiview.dev/Assemblies/Review/e7eca335d7b04146b9ad21d4a99ee396

    @mikeharder mikeharder changed the title [TypeSpec CI] Add Microsoft.ServiceNetworking Align Microsoft.ServiceNetworking with repo conventions May 19, 2023
    @mikeharder mikeharder marked this pull request as draft May 19, 2023 01:35

    - template: templates/steps/typespec-ci.yml
    parameters:
    Folder: specification/servicenetworking/resource-manager/Microsoft.ServiceNetworking/cadl
    Copy link
    Member

    Choose a reason for hiding this comment

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

    We need to get the "cadl" name out of the folder structure when as we fix this project.

    @mikeharder
    Copy link
    Member Author

    mikeharder commented May 19, 2023

    @markcowl: I gave this my best shot, but I'm stuck at this point. I think the next issue to fix is the examples:

    warning @azure-tools/typespec-autorest/example-loading:
    Skipping example file AssociationDelete.json because it does not contain an operationId and/or title.
    

    https://dev.azure.com/azure-sdk/public/_build/results?buildId=2789095&view=logs&j=9cd39ef8-47c1-5b58-08db-8c3708712f1b&t=462145f3-d740-50de-51e9-126e7c0a29e2&l=18

    There may be more issues, for example the readme*.md files under resource-manager might be outdated and/or incorrect.

    Feel free to push changes to this PR, or create a new PR if you prefer.

    @AzureRestAPISpecReview AzureRestAPISpecReview added BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required resource-manager labels May 19, 2023
    @openapi-workflow-bot
    Copy link

    Hi @mikeharder, 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.
    Note: To avoid breaking change, you can refer to Shift Left Solution for detecting breaking change in early phase at your service code repository.

    @mikeharder
    Copy link
    Member Author

    Closing in favor of #24082

    @mikeharder mikeharder closed this May 23, 2023
    @mikeharder mikeharder deleted the typespec-ci-traffic-controller branch May 23, 2023 04:29
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

    Labels

    BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required CI-BreakingChange-Go resource-manager

    Projects

    None yet

    Development

    Successfully merging this pull request may close these issues.

    4 participants