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

Service Bus and EventHub : 2021-06-01-preview - Added optional Properties #15233

Merged
merged 4 commits into from
Aug 31, 2021

Conversation

v-Ajnava
Copy link
Member

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Changelog

Please ensure to add changelog with 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
    • added optional properties to 2021-06-01-preview which is not public preview
  2. When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
  3. When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
  4. If it's an update to existing version, please select SDKs of specific language and CLIs that require refresh after 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, no need to refresh 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

  • Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

    • Adding new API(s)
    • Adding a new API version
    • Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
    • Adding a new service
  • Please 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 there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

  • Removing API(s) in stable version
  • Removing properties in stable version
  • Removing API version(s) in stable version
  • Updating API in 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, @v-Ajnava 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 Jul 16, 2021

    Swagger Validation Report

    ️❌BreakingChange: 13 Errors, 0 Warnings failed [Detail]
    Rule Message
    1027 - DefaultValueChanged The new version has a different default value than the previous one.
    New: Microsoft.ServiceBus/preview/2021-06-01-preview/Rules.json#L336:9
    Old: Microsoft.ServiceBus/preview/2021-06-01-preview/Rules.json#L336:9
    1036 - ConstraintChanged The new version has a different 'maximum' value than the previous one.
    New: Microsoft.EventHub/preview/2021-06-01-preview/eventhubs.json#L248:9
    Old: Microsoft.EventHub/preview/2021-06-01-preview/eventhubs.json#L248:9
    1036 - ConstraintChanged The new version has a different 'minimum' value than the previous one.
    New: Microsoft.EventHub/preview/2021-06-01-preview/eventhubs.json#L248:9
    Old: Microsoft.EventHub/preview/2021-06-01-preview/eventhubs.json#L248:9
    1036 - ConstraintChanged The new version has a different 'maximum' value than the previous one.
    New: Microsoft.EventHub/preview/2021-06-01-preview/eventhubs.json#L253:9
    Old: Microsoft.EventHub/preview/2021-06-01-preview/eventhubs.json#L255:9
    1036 - ConstraintChanged The new version has a different 'minimum' value than the previous one.
    New: Microsoft.EventHub/preview/2021-06-01-preview/eventhubs.json#L253:9
    Old: Microsoft.EventHub/preview/2021-06-01-preview/eventhubs.json#L255:9
    1036 - ConstraintChanged The new version has a different 'maximum' value than the previous one.
    New: Microsoft.EventHub/preview/2021-06-01-preview/namespaces-preview.json#L652:13
    Old: Microsoft.EventHub/preview/2021-06-01-preview/namespaces-preview.json#L652:13
    1036 - ConstraintChanged The new version has a different 'minimum' value than the previous one.
    New: Microsoft.EventHub/preview/2021-06-01-preview/namespaces-preview.json#L652:13
    Old: Microsoft.EventHub/preview/2021-06-01-preview/namespaces-preview.json#L652:13
    1036 - ConstraintChanged The new version has a different 'maximum' value than the previous one.
    New: Microsoft.ServiceBus/preview/2021-06-01-preview/Rules.json#L336:9
    Old: Microsoft.ServiceBus/preview/2021-06-01-preview/Rules.json#L336:9
    1036 - ConstraintChanged The new version has a different 'minimum' value than the previous one.
    New: Microsoft.ServiceBus/preview/2021-06-01-preview/Rules.json#L336:9
    Old: Microsoft.ServiceBus/preview/2021-06-01-preview/Rules.json#L336:9
    1041 - AddedPropertyInResponse The new version has a new property 'maxMessageSizeInKilobytes' in response that was not found in the old version.
    New: Microsoft.ServiceBus/preview/2021-06-01-preview/Queue.json#L279:7
    Old: Microsoft.ServiceBus/preview/2021-06-01-preview/Queue.json#L279:7
    1041 - AddedPropertyInResponse The new version has a new property 'maxMessageSizeInKilobytes' in response that was not found in the old version.
    New: Microsoft.ServiceBus/preview/2021-06-01-preview/topics.json#L279:7
    Old: Microsoft.ServiceBus/preview/2021-06-01-preview/topics.json#L279:7
    1045 - AddedOptionalProperty The new version has a new optional property 'maxMessageSizeInKilobytes' that was not found in the old version.
    New: Microsoft.ServiceBus/preview/2021-06-01-preview/Queue.json#L279:7
    Old: Microsoft.ServiceBus/preview/2021-06-01-preview/Queue.json#L279:7
    1045 - AddedOptionalProperty The new version has a new optional property 'maxMessageSizeInKilobytes' that was not found in the old version.
    New: Microsoft.ServiceBus/preview/2021-06-01-preview/topics.json#L279:7
    Old: Microsoft.ServiceBus/preview/2021-06-01-preview/topics.json#L279:7
    ️⚠️LintDiff: 0 Warnings warning [Detail]
    The following errors/warnings exist before current PR submission:

    Only 30 items are listed, please refer to log for more details.

    Rule Message
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/disasterRecoveryConfigs/CheckNameAvailability'
    Location: Microsoft.ServiceBus/preview/2021-06-01-preview/DisasterRecoveryConfig.json#L37
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/AuthorizationRules'
    Location: Microsoft.ServiceBus/preview/2021-06-01-preview/AuthorizationRules.json#L37
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/AuthorizationRules/{authorizationRuleName}'
    Location: Microsoft.ServiceBus/preview/2021-06-01-preview/AuthorizationRules.json#L85
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/AuthorizationRules/{authorizationRuleName}/listKeys'
    Location: Microsoft.ServiceBus/preview/2021-06-01-preview/AuthorizationRules.json#L234
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/AuthorizationRules/{authorizationRuleName}/regenerateKeys'
    Location: Microsoft.ServiceBus/preview/2021-06-01-preview/AuthorizationRules.json#L282
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/queues/{queueName}/authorizationRules/{authorizationRuleName}/ListKeys'
    Location: Microsoft.ServiceBus/preview/2021-06-01-preview/AuthorizationRules.json#L545
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/topics/{topicName}/authorizationRules/{authorizationRuleName}/ListKeys'
    Location: Microsoft.ServiceBus/preview/2021-06-01-preview/AuthorizationRules.json#L865
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/providers/Microsoft.ServiceBus/CheckNameAvailability'
    Location: Microsoft.ServiceBus/preview/2021-06-01-preview/CheckNameAvailability.json#L37
    R4011 - DeleteOperationResponses The delete operation is defined without a 200 or 204 error response implementation,please add it.'
    Location: Microsoft.EventHub/preview/2021-06-01-preview/disasterRecoveryConfigs.json#L217
    R4011 - DeleteOperationResponses The delete operation is defined without a 200 or 204 error response implementation,please add it.'
    Location: Microsoft.ServiceBus/preview/2021-06-01-preview/DisasterRecoveryConfig.json#L217
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: resource-manager/common/v1/definitions.json#L214
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: resource-manager/common/v1/definitions.json#L204
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: resource-manager/common/v1/definitions.json#L214
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: resource-manager/common/v1/definitions.json#L204
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: resource-manager/common/v1/definitions.json#L363
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: resource-manager/common/v1/definitions.json#L353
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: resource-manager/common/v1/definitions.json#L363
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: resource-manager/common/v1/definitions.json#L353
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: resource-manager/common/v1/definitions.json#L363
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: resource-manager/common/v1/definitions.json#L353
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: resource-manager/common/v1/definitions.json#L363
    R4013 - IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: resource-manager/common/v1/definitions.json#L353
    R4018 - OperationsApiResponseSchema The response schema of operations API '/providers/Microsoft.EventHub/operations' does not match the ARM specification. Please standardize the schema.
    Location: Microsoft.EventHub/preview/2021-06-01-preview/operations.json#L37
    R4018 - OperationsApiResponseSchema The response schema of operations API '/providers/Microsoft.ServiceBus/operations' does not match the ARM specification. Please standardize the schema.
    Location: Microsoft.ServiceBus/preview/2021-06-01-preview/operations.json#L37
    R4037 - MissingTypeObject The schema 'EHNamespaceListResult' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.EventHub/preview/2021-06-01-preview/namespaces-preview.json#L578
    R4037 - MissingTypeObject The schema 'EHNamespace' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.EventHub/preview/2021-06-01-preview/namespaces-preview.json#L594
    R4037 - MissingTypeObject The schema 'properties' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.EventHub/preview/2021-06-01-preview/namespaces-preview.json#L609
    R4037 - MissingTypeObject The schema 'Identity' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.EventHub/preview/2021-06-01-preview/namespaces-preview.json#L732
    R4037 - MissingTypeObject The schema 'Encryption' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.EventHub/preview/2021-06-01-preview/namespaces-preview.json#L787
    R4037 - MissingTypeObject The schema 'KeyVaultProperties' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.EventHub/preview/2021-06-01-preview/namespaces-preview.json#L817
    ️️✔️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: 0 Warnings warning [Detail]
    The following errors/warnings are introduced by current PR:

    |:speech_balloon: AutorestCore/Exception|"readme":"eventhub/resource-manager/readme.md",
    "tag":"package-2021-06-preview",
    "details":"> Installing AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0)"|
    |:speech_balloon: AutorestCore/Exception|"readme":"eventhub/resource-manager/readme.md",
    "tag":"package-2021-06-preview",
    "details":"> Installed AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0->1.8.0)"|


    The following errors/warnings exist before current PR submission:

    Rule Message
    ⚠️ PreCheck/PropertyRedeclarationWarning "readme":"servicebus/resource-manager/readme.md",
    "tag":"package-2021-06-preview",
    "details":"Schema 'SqlRuleAction' has a property 'sqlExpression' that is already declared the parent schema 'Action' but isn't significantly different. The property has been removed from SqlRuleAction"
    ⚠️ PreCheck/PropertyRedeclarationWarning "readme":"servicebus/resource-manager/readme.md",
    "tag":"package-2021-06-preview",
    "details":"Schema 'SqlRuleAction' has a property 'compatibilityLevel' that is already declared the parent schema 'Action' but isn't significantly different. The property has been removed from SqlRuleAction"
    ⚠️ PreCheck/PropertyRedeclarationWarning "readme":"servicebus/resource-manager/readme.md",
    "tag":"package-2021-06-preview",
    "details":"Schema 'SqlRuleAction' has a property 'requiresPreprocessing' that is already declared the parent schema 'Action' but isn't significantly different. The property has been removed from SqlRuleAction"
    💬 AutorestCore/Exception "readme":"eventhub/resource-manager/readme.md",
    "tag":"package-2021-06-preview",
    "details":"> Loading AutoRest extension '@autorest/modelerfour' (4.15.456->4.15.456)"
    💬 AutorestCore/Exception "readme":"servicebus/resource-manager/readme.md",
    "tag":"package-2021-06-preview",
    "details":"> Loading AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0->1.8.0)"
    💬 AutorestCore/Exception "readme":"servicebus/resource-manager/readme.md",
    "tag":"package-2021-06-preview",
    "details":"> Loading AutoRest extension '@autorest/modelerfour' (4.15.456->4.15.456)"
    ️️✔️[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 Jul 16, 2021

    Swagger Generation Artifacts

    ️️✔️[Staging] ApiDocPreview succeeded [Detail] [Expand]

    Only 0 items are rendered, please refer to log for more details.

    ️❌[Staging] SDK Breaking Change Tracking failed [Detail]

    Only 0 items are rendered, please refer to log for more details.

    ️❌ azure-sdk-for-net failed [Detail]

    Only 0 items are rendered, please refer to log for more details.

    ️⚠️ azure-sdk-for-python warning [Detail]

    Only 0 items are rendered, please refer to log for more details.

    ️⚠️ azure-sdk-for-python-track2 warning [Detail]

    Only 0 items are rendered, please refer to log for more details.

    ️⚠️ azure-sdk-for-java warning [Detail]

    Only 0 items are rendered, please refer to log for more details.

    ️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]

    Only 0 items are rendered, please refer to log for more details.

    ️️✔️ azure-sdk-for-js succeeded [Detail] [Expand]

    Only 0 items are rendered, please refer to log for more details.

    ️⚠️ azure-resource-manager-schemas warning [Detail]

    Only 0 items are rendered, please refer to log for more details.

    ️️✔️ azure-sdk-for-go-track2 succeeded [Detail] [Expand]

    Only 0 items are rendered, please refer to log for more details.

    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-workflow-bot
    Copy link

    Hi @v-Ajnava, 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.

    @v-Ajnava v-Ajnava requested a review from dsouzaarun July 16, 2021 17:21
    @v-Ajnava v-Ajnava requested a review from apraovjr July 16, 2021 17:29
    @@ -248,15 +248,11 @@
    "intervalInSeconds": {
    "format": "int32",
    "type": "integer",
    "maximum": 900,
    "minimum": 60,
    "description": "The time window allows you to set the frequency with which the capture to Azure Blobs will happen, value should between 60 to 900 seconds"
    },
    Copy link
    Contributor

    Choose a reason for hiding this comment

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

    @v-Ajnava The description also needs to be either removed or changed

    @@ -652,8 +652,6 @@
    "maximumThroughputUnits": {
    "format": "int32",
    "type": "integer",
    "maximum": 20,
    "minimum": 0,
    "description": "Upper limit of throughput units when AutoInflate is enabled, value should be within 0 to 20 throughput units. ( '0' if AutoInflateEnabled = true)"
    },
    Copy link
    Contributor

    Choose a reason for hiding this comment

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

    @v-Ajnava The description also needs to be either removed or changed

    @@ -336,9 +336,6 @@
    "compatibilityLevel": {
    "format": "int32",
    "type": "integer",
    "default": 20,
    "minimum": 20,
    "maximum": 20,
    "description": "This property is reserved for future use. An integer value showing the compatibility level, currently hard-coded to 20."
    },
    Copy link
    Contributor

    Choose a reason for hiding this comment

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

    @v-Ajnava Also for eventhubs since this is removed, would there be new examples reflecting the new change or thats optional?

    Copy link
    Member Author

    Choose a reason for hiding this comment

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

    its optional and we don't have min/max in examples.

    Copy link
    Member Author

    Choose a reason for hiding this comment

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

    as recommended, removed min/max and description will have the range.

    Copy link

    @kasun04 kasun04 left a comment

    Choose a reason for hiding this comment

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

    Looks good. We need to update the descriptions by removing the information related to maximum limits.

    @PhoenixHe-NV PhoenixHe-NV assigned jianyexi and unassigned PhoenixHe-NV Aug 2, 2021
    @ghost
    Copy link

    ghost commented Aug 22, 2021

    Hi, @v-Ajnava. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove no-recent-activity label.

    @v-Ajnava
    Copy link
    Member Author

    @PhoenixHe-TSP please merge the PR

    @jianyexi jianyexi merged commit 09fe30c into Azure:main Aug 31, 2021
    ghost pushed a commit to Azure/azure-resource-manager-schemas that referenced this pull request Aug 31, 2021
    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 CI-BreakingChange-Go-V2
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    8 participants