Skip to content

Conversation

@orargaman
Copy link
Contributor

@orargaman orargaman commented Mar 11, 2020

Latest improvements:

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

Contribution checklist:

  • I have reviewed the documentation for the workflow.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.
  • The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

  • Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
  • adding/removing APIs.
  • adding/removing properties.
  • adding/removing API-version.
  • adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

  • If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
    Please follow the link to find more details on API review process.

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Mar 11, 2020

azure-sdk-for-go - Release

⚠️ warning [Logs] [Expand Details]

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Mar 11, 2020

azure-sdk-for-java - Release

No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Mar 11, 2020

azure-sdk-for-net - Release

️✔️ succeeded [Logs] [Expand Details]

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Mar 11, 2020

azure-sdk-for-js - Release

️✔️ succeeded [Logs] [Expand Details]

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Mar 11, 2020

azure-sdk-for-python - Release

- Breaking Change detected in SDK

⚠️ warning [Logs] [Expand Details]
  • ⚠️ Generate from 8210d51 with merge commit 64541c6. SDK Automation 13.0.17.20200326.3
  • ⚠️azure-mgmt-loganalytics [Logs]  [Release SDK Changes] Breaking Change Detected
    [build_package] /usr/lib/python3.6/distutils/dist.py:261: UserWarning: Unknown distribution option: 'long_description_content_type'
    [build_package]   warnings.warn(msg)
    [build_package] /usr/lib/python3.6/distutils/dist.py:261: UserWarning: Unknown distribution option: 'long_description_content_type'
    [build_package]   warnings.warn(msg)
    [breaking_change_setup] Ignoring mock: markers 'python_version <= "2.7"' don't match your environment
    [breaking_change_setup] Cannot uninstall requirement azure-nspkg, not installed
    [breaking_change_setup] Command '['/usr/local/bin/python', '-m', 'pip', 'uninstall', '-y', 'azure-nspkg']' returned non-zero exit status 1.
    [ChangeLog] Size of delta 19.139% size of original (original: 16631 chars, delta: 3183 chars)
    [ChangeLog] **Features**
    [ChangeLog] 
    [ChangeLog]   - Added operation group OperationalInsightsManagementClientOperationsMixin
    [ChangeLog] 
    [ChangeLog] **Breaking changes**
    [ChangeLog] 
    [ChangeLog]   - Removed operation WorkspacesOperations.purge
    [ChangeLog]   - Removed operation WorkspacesOperations.get_search_results
    [ChangeLog]   - Removed operation WorkspacesOperations.get_schema
    [ChangeLog]   - Removed operation WorkspacesOperations.update_search_results
    [ChangeLog]   - Removed operation WorkspacesOperations.list_link_targets
    [ChangeLog]   - Removed operation group StorageInsightsOperations
    [ChangeLog]   - Removed operation group SavedSearchesOperations

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

1 similar comment
@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@akning-ms akning-ms added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Mar 16, 2020
@orargaman
Copy link
Contributor Author

Currently the BreakingChange Test is failing on the cluster API’s. Those APIS are in private preview and are only used by two customers. Both those customers are aware of the changes in the API and are currently using it as shown in my updates.

@PhoenixHe-NV
Copy link

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Mar 16, 2020

azure-cli-extensions - Release

No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured

Copy link
Contributor

@pilor pilor left a comment

Choose a reason for hiding this comment

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

Question about sku capacity

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@PhoenixHe-NV
Copy link

@jianyexi Why we report error in breakingchange in preview API? Could you please help to have a look?

@jianyexi
Copy link
Contributor

@jianyexi Why we report error in breakingchange in preview API? Could you please help to have a look?

currently , breaking-change does not distinguish between preview API and stable API

@PhoenixHe-NV
Copy link

@jianyexi But breaking change in preview api is allowed and should not block PR from merging. @akning-ms We need to make change and unblock this right?

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@pilor pilor added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed ARMChangesRequested WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Mar 25, 2020
@PhoenixHe-NV PhoenixHe-NV added the Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 label Mar 26, 2020
@PhoenixHe-NV
Copy link

@akning-ms Please help to merge this PR. All the breaking change happens in preview API.

@yoramsinger
Copy link
Contributor

@akning-ms please merge this PR. Thanks.

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@orargaman orargaman requested a review from mmyyrroonn March 27, 2020 08:41
@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@PhoenixHe-NV
Copy link

@akning-ms Please help to merge this PR

@akning-ms akning-ms merged commit 64541c6 into Azure:master Mar 30, 2020
00Kai0 pushed a commit to 00Kai0/azure-rest-api-specs that referenced this pull request Oct 12, 2020
* Update cluster and linked services API

* Update LinkedServicesGet.json

Fix

* fix json

* Prettier

* fix modelValidation

* fix modelValidation 2

* Fixes for PR

* separate linkedServices to new file

* Update readme.md

* Fix PR

* Change capacityReservationLevel to capacity

* Fix version

* writeAccessResourceId fix camel case

Co-authored-by: Or Argaman <[email protected]>
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 ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants