Xynoclafe/2020 06 version #9888
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Swagger pipeline started successfully, please wait for status update in this comment. |
|
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-net - Release
|
azure-sdk-for-python - Release
- Breaking Change detected in SDK
|
Azure CLI Extension Generation - 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
|
Trenton Generation - 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
|
azure-sdk-for-python-track2 - Release
|
azure-sdk-for-go - Release
|
azure-sdk-for-js - Release
|
azure-sdk-for-java - Release
|
This was referenced Jun 18, 2020
Closed
Closed
|
Can one of the admins verify this patch? |
|
There are 3 changes in this PR:
|
|
@filizt , can you share the reason of removing Java SDK support? |
@raych1 Supporting Java SDK requires some changes to be done in the swagger but given that we don't have a hard requirement to release a Java SDK at the moment, we'd like to remove the support for it along with the changes. We can evaluate and release it, if there is a need in the future. |
raych1
approved these changes
Jun 23, 2020
raych1
added
the
Approved-BreakingChange
|
@akning-ms , the breaking change is about reverting previous changes: one is to removing JAVA SDK support in readme and the other is to revert the parameter name change which was approved in another api version. These changes doesn't have impacts on service side and only impact SDK side. Please help force merge this PR, thanks. |
iscai-msft
added a commit
to iscai-msft/azure-rest-api-specs
that referenced
this pull request
Oct 5, 2020
…into fix_kv_python_readme * 'master' of https://github.com/Azure/azure-rest-api-specs: (22 commits) Update DeletionRecovery Level (Azure#9895) Updating operations API to enable metrics via public metrics REST API. (Azure#9918) Xynoclafe/2020 06 version (Azure#9888) update java md (Azure#9923) Compute 2020-06-01 API version (Azure#9167) Merge Dev containerservice microsoft.container service 2020 06 01 (Azure#9914) new Batch Document Translation API Preview 1.0 (Azure#9218) 1. Add a property as required (Azure#9899) Operational insights delete wrong lines data export (Azure#9849) [SRP]Adding allowBlobPublicAccess and minimumTlsVersion property for June19 and April19 (Azure#9831) [Hub Generated] Review request for Microsoft.ContainerInstance to add version stable/2019-12-01 (Azure#9838) add Java to AVS (Azure#9855) LaMigrationDate (Azure#9882) change vmware client name to AVSClient (Azure#9863) Fix typo in common private links definition for actionsRequired (Azure#9727) Microsoft.Support RP documentation updates (Azure#9880) BUG FIX: Fixed HopLink properties: context should be a dictionary, uint32 from… (Azure#9868) Update ci-fix.md (Azure#9881) Update Attestation control plane swagger to include 2 new defaultprovider API (Azure#9819) update java readme digitaltwins (Azure#9878) ...
00Kai0
pushed a commit
to 00Kai0/azure-rest-api-specs
that referenced
this pull request
Oct 12, 2020
* Update Resources 2020-06 to include changes from 2019-10 (From PR - Azure#9441) * Update Resources 2020-06 to include changes from 2019-10 (From PR - Azure#9580) * Rollback java support for Resources API version 2020-06-01
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds changes from 2019-10-01 missed in the new version
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.