FI to network #5275
Merged
FI to network #5275
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
* DataFactory Swagger Change for SapOpenHub and Rest * correct indentation * address comment of REST * fix syntax issue * Fix issue with AutoRest
* add AnomalyFinder swagger json * AnomalyFinder update swagger json * add AnomalyFinder readme * fix file path; change class name; * make camelCase style * fix typo; change operationId; remove hard code arg limitation; * fix type of "sensitivity"; change description of "timestamp";
* Swagger changes for ADF newly released features: 1. I can load data from o365 by leveraging the REST endpoint of o365 2. Support copying incremental files based on lastModifiedTime for S3/File/Blob 3. Enable ADLS Gen2 connector as both source & sink 4. Support data migration from MongoDB to CosmosDB (MongoDB API) 5. Make Kusto source/sink better and support Azure Data exploer source/sink 6. Support copy from ADLS Gen1 to ADLS Gen2 with ACL 7. serviceUrl @ S3 linked service 8. I can copy from Dynamics AX 9. AAD OAuth for OData Linked Service 10. I can copy from Oracle Service Cloud and Google Adwords * fix swagger definetion for MongoDB Srouce cursor method. * fix Amazon S3 servie url definition * fix CosmosDbMongoDbApiSink * Fix several typos * Add maxConcurrentConnections in CopySource and CopySink
* Add an Operations API for Commitment Plan RP * Add OperationEntityListResult related definitions * Fix case typo * Fix tab to spaces
…06-01/ (#5238) - Adwords -> AdWords - connectioned to -> for the
* scripts * TRAVIS_PULL_REQUEST * another try * TRAVIS_PULL_REQUEST_SLUG * TRAVIS_REPO_SLUG * Swagger to SDK * linter and ruby * not really a slug * pool * indent * strange * URI * env vars * uri * env var * TRAVIS_PULL_REQUEST_SLUG * matrix * Azure OpenAPI name * linter: autorest fix * error handling and PR_ONLY = true * syntax * pipelines. * job name * job name * Names * params, no getStatus.js * No CI, only PR validations. * displayName * revert back * no need to show vars
* node options * correct NODE_OPTIONS * lintdiff travis-ci
* 2019 Azure Stack hybrid Profile. * fixing changes for profile * remove space * formatted profile
…5219) * Renaming Search|SuggestParametersPayload to *Request and making them internal Made AutocompleteRequest internal too, and fixed some incorrect comments. * Adding Suggest API to the Azure Search data plane spec * Fixing validation error in Suggest example * Adding Index API to the Azure Search data plane spec * Make example names consistent
* updated model names in preview version to be consistent with stable version to avoid breaking changes in client side code * changed swagger files * added v2.1 swagger * added v2.1 swagger * added v2.1 swagger * added v2.1 swagger * added v2.1 swagger * resolved PR comments
* Update swagger documetation to mark Collation property as writable. Change Managed Instance collation property from read only to read and create. Add collation to properties section in ManagedInstanceCreateMax example. VSTS task: 12336257 * Remove 'cosmetics' from swagger. * Remove comma as redundant * Return to the initial, generated state. * Update swagger file and examples with time zone parameter
* empty parameters * TRAVIS_BRANCH * target branch * trying to set env var * use shell * info * more info * Pull Request Number
* added swagger for Tenant Properties added swagger for Tenant Properties * Fixed camel casing in billing.json file Fixed camel casing in billing.json file * Update billing.json * changes in DiscoverTenants contracts changes in DiscoverTenants contracts * billing.Json trim blank space billing.Json trim blank space * Update billing.json * removal of plural name removal of plural name * Updating the route Updating the route as per suggestion * Moved Swagger for Discover Tenants from billing to consumption Moved Swagger for Discover Tenants from billing to consumption * Change in Namespace followed by one additional parameter "billingAccountId" Change in Namespace followed by one additional parameter "billingAccountId" * Change of method name from discoverTenants to tanants. Change of method name from discoverTenants to tanants. * changes ion response type changes ion response type * added name after Id. Code review implementation added name after Id. Code review implementation
* Azure Security Center - break-to-composite v1 * Azure Security Center - composite api v1 - suppress email format
Remove trailing comma
…version 2018-07-10 (#5207) * Adds base for updating Microsoft.RecoveryServices from version stable/2018-01-10 to version 2018-07-10 * Updates readme * Updates API version in new specs and examples * Changes with new API version 2018-07-10 * Completed the example for SupportedOperatingSystems_Get
* Adding new properties to Databricks LS and custom activity * Fixing the version in entity files. This version isn't used, however it should the GA API version instead of preview.
* Public Preview of Mixed Reality Cloud Service This is the first check-in of Mixed Reality Azure Resource Management Open API 2.0 (Swagger) specification. All checked-in contents had been reviewed and checked-in the private Azure GitHub repo: https://github.com/Azure/azure-rest-api-specs-pr * Resolve comments * Fix typos * Amend excample by fixing the properties' case
* SDK for server restart * server restart changes2 * server restart changes 3 * server restart changes 4 * server restart changes 5
* Add 201 response to AppServicePlans_CreateOrUpdate. Fixes #3648. * Add examples of 201 response to AppServicePlans_CreateOrUpdate.
* Add tag: package-2019-01 to ruby and go readme files * Copy 2018-09-15-preview files to get a baseline * Add EventGrid swagger file along with the domain topic create/delete example files * Replace 2018-09-15-preview with 2019-02-01-preview api version in existing example files * Address CR comments and fix test * Take care of CR comment * update readme.md file and address some violations * Add 2019-01 and 2019-02-preview APIs to Java multi-api in readme.md file * update summary text per code review comments * Address CR comments
* Updating the events api response for the changed contract * updating swagger to fix errors * update * Update * 'update' * update
…arch (#5123) * add api get_services_by_subscription Add path of API "get search services by subscription" (GET/SUBSCRIPTIONS/PROVIDERS/MICROSOFT.SEARCH/SEARCHSERVICES) in the spec of API version 2015-08-19 of Azure Search (Microsoft.Search). Along with a sample. * Update search.json Rename example reference name
* Allow to run SDK generaion for 2 hours * display names * display name
Automation for azure-sdk-for-jsThis PR contains more than 3 context, SDK generation is not enabled. Contexts found:
|
Automation for azure-sdk-for-javaThis PR contains more than 3 context, SDK generation is not enabled. Contexts found:
|
Automation for azure-sdk-for-rubyThis PR contains more than 3 context, SDK generation is not enabled. Contexts found:
|
Automation for azure-sdk-for-goThis PR contains more than 3 context, SDK generation is not enabled. Contexts found:
|
Automation for azure-sdk-for-pythonThis PR contains more than 3 context, SDK generation is not enabled. Contexts found:
|
Automation for azure-sdk-for-nodeThis PR contains more than 3 context, SDK generation is not enabled. Contexts found:
|
|
Can one of the admins verify this patch? |
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.
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:
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.