Sync from master to dev-storagesync-Microsoft.StorageSync-2020-09-01 #13987
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
* Add the march public preview API version of extended location * Tweak: remove references to iot * Address comments from Phoenix by removing 500 references and adding back the default version tag * Revert privatepreview changes * Tweak: remove "500" from the swagger itself * Tweak: remove dash from readme * fix python pipeline * Tweak: run prettier against the repo folder * Tweak: remove 404 from customlocations.json and CustomLocationsGet.json * Tweak: csharp README sdk output folder path to fix downstream generation issue Co-authored-by: 00Kai0 <sunkaihuisos@gmail.com>
* Update readme.go.md * Update deviceupdate.json * Update deviceupdate.json * Update deviceupdate.json
* [DataFactory] Add privateEndpointConnection apis * resolve some style errors * resolve * resolve 1 * commit * resolve 1 comment
* PIM API Specs * update readme * Update * Update readme * operation id fix * name fix * Name changes * fix * Fix * Changes based on docs generated * Scope fix in example * Updates for documentation * Change operation name * Update examples * Add expanded properties * Fix formatting * Fixes * Fix * fixes * Update the policy specs * Fix the policy objects and pell checks * fix the checks * fix the property * fix syntax * Prettier Co-authored-by: Aman Swaika <amansw@microsoft.com> Co-authored-by: Gaurav Mishra (IDENTITY) <gamish@microsoft.com>
…review/2020-07-01-preview (#13258) * New Readme Config File * New Go Language Readme Config File * New Azure AZ Readme Config File * New Azure CLI Readme Config File * New Typescript Language Readme Config File * New Python Language Readme Config File * New C# Language Readme Config File * New AzureResourceSchema Readme Config File * New Swagger Spec File * New Swagger Example Spec File * Addings examples and swagger from prod * removing autogenerated files * added kibana custom word * moving swagger files one directory up * moving custom words to swagger folder * moving custom words to readme directory * removed custom words * changed double preview to preview * added systemdata as part of the spec * fixing prettyness * added systemData for tagrules * moving system data to a level down * added a new type of response definition * changed theget type of montor * reverting swagger to without systemdata * added systemdata in properties * added system data elasticmonitor resource and tags * Added 2 new properties to operation result * fixing go sdk generation * added no name space for track python * Using confluent python.md
* Adding chat API preview5 * Fix style issue + adding `Idempotency` to custom-words.txt dictionary
* MFA MUA V1 swagger changes * Copying json from 2021-02-01 to 2021-02-01-preview * Moving these details under Preview folder * Fixing Avocado errors * updated version in example json files * ResourceGuardProxy related changes * Resolved spell check errors Co-authored-by: Madhumanti Dey <madhude@microsoft.com>
…n preview/2021-04-01-preview (#13357) * Adds base for updating Microsoft.DocumentDB from version preview/2021-03-01-preview to version 2021-04-01-preview * Updates readme * Updates API version in new specs and examples * Adding new API for fetching backup information(such as latest restorable timestmap) for a resource. Also, adding startTime,endTime to restorable.json * Adding new API for fetching backup information(such as latest restorable timestmap) for a resource. Also, adding startTime,endTime to restorable.json * Adding new API for fetching backup information(such as latest restorable timestmap) for a resource. Also, adding startTime,endTime to restorable.json
* Update readme.python.md * Update readme.python.md
…rsion stable/2019-11-01 (#13194) * Adding tagValue and tagKey to ReportConfigFilter * remove the addition of tagValue * Adding TagValue in the config filter * make filter name property nullable
Co-authored-by: Meet Shah <meeshah@microsoft.com>
* Create Base CV 3.2 config * Add language and start updating examples * Add model version, corrct other smaller elements * Tweak language code formatting and description * Correct Read available resource version * Attempt to fix failing build * Ensure parity with ComputerVisionErrors * Add model version for vision * Correct ModelVersion to model-version * Fix JSON formatting error * Update query param name for model version to "model-version" * Remove unused error codes from OCR's supported list * Fix failing tests on OCR operation * Split vision and ocr Model-Version into to separate elements * Fix case sensitivity issue * Add parent "error" object, remove requestId from ComputerVisionError object * Fix the number of returned captions (maxCandidate is set to 1 so API should return only one caption) Co-authored-by: bob <bob@bob.com> Co-authored-by: Ryogo Kanatani <ryogok@microsoft.com>
* stable version release * updated to stable * fixed readme * updated output folder * updated output folder * corrected output dir path * fixed path * added java readme
privateEndpointNetworkPolicies
* [Monitor] Fix invalid tags * Update readme.md * Update readme.python.md * Update readme.go.md
…13355) * [Management Plane][Azure Search] Adding new API version for exposing Encryption with CMK. * Fixing prittier and model validation errors * Fixing errors raised by lintdiff and ModelValidations
* Add automation rules api * Move incident enums to common * fix schema * more fixes * update examples * update examples * remove automation rules OData support * fix typo in LA provider name * Update swagger * Update examples * prepare for PR * fix typos and prettier * fix typos and prettier * fix lint errors * fix lint errors * fix lint errors * fix lint errors * fix lint errors * fix linting error * Remove multiple allOf statements * Remove multiple allOf statements
* fixing examples in ARM spec * fixing resource ids in the examples
This was referenced Apr 16, 2021
* add multivarite * add v1.1-preview * reformat changepoint example * change typo in readme * fix prettier-check error * add export model example * fix prettier error
* introduce knowledge store swagger * add knowledge store to 2020 apis Co-authored-by: Austin Drefke <jdrefke@microsoft.com>
Co-authored-by: Austin Drefke <jdrefke@microsoft.com>
* Initial commit (copying over stable API version) * Making changes to support message metadata
Co-authored-by: Akash Keshari <akkeshar@microsoft.com>
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.
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.
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.
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.
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.