forked from Azure/azure-rest-api-specs
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update to latest Azure master #3
Merged
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
…titions and Several Relational sets (#6617) * [DataFactory]Add AzurePostgreSql Sink and Oracle/SapTable/Netezza Partitoins and dedicated datasets for relational * Fix typo. * update SapBwCube * fix issue brought by merging from azure branch * remove SapBwCube and Sybase for investigation * will postpone SapBwSource in another coming PR. * refine case of Oracle in description
* copy spec content from previous version * Update Volume and Drive API for Azure Stack Fabric Admin to 2019-05-01 * add the missing word
* fix: addsServices_update example - service is an object not an array - casing on "notificationEmailEnabledForGlobalAdmins" * fix: addsServicesUserPreference_add example - setting is an object rather than an array * fix: configuration_update example - tenant is an object rather than array * fix: services_addAlertFeedback example - alertFeedback is object instead of array - feeback -> feedback * fix: serviceMembers_getConnectorMetadata example - Missing required parameter "metricName" - flatten value in response * fix: alerts_listAddsAlerts example - additionalInformation is an array value * fix: addsServices_listServerAlerts example - additionalInformation is an array type
Alpha isn't required, but avoids merge conflicts what putting them at the end causes.
* Introduce ADX Command * Use full ADX name
* Adding missing Swagger spec. * Updated README.md with reference to added directory.
…eview/2019-01-01-preview (#6643) * Adds base for updating Microsoft.Portal from version preview/2015-08-01-preview to version 2019-01-01-preview * Updates readme * Updates API version in new specs and examples * Fix readmes for new api version
- Add "body" to response - createGroupRequest -> createManagementGroupRequest
* Updated QnAMaker Runtime API headers descriptions * Update swagger title * removed content-type header * Common tag and title for Runtime Undo Authorization header change * Update title * update readme * update readme
* update package '@azure/rest-api-specs-scripts' 0.4.0 * remove '@azure/rest-api-specs-scripts' related job in preproduction pipeline. * fix
* Added Keyvault and MSI parameters to create SAP Monitor * Camel case for new fields * Fixed casing
Remove header/null body for RESPONSE_SCHEMA_NOT_IN_SPEC errors
Remove leading slash for DOUBLE_FORWARD_SLASHES_IN_URL errors
* Mark ownerEmail as required properties for workspace RP * fix examples
Remove hard tabs
* Fixing errors in swagger examples of Azure Backup * Updating reference path for moved file * Removing trailing commas in examples
…tings and AzureBlobFSWriteSettings (#6954) * add property blockSizeInMB for blobsink and blobFSsink * fix property type * Move property from BlobSink (datasetV1) to AzureBlobStorageWriteSettings (datasetV2) * Enable override for StoreWriteSettings * remove redundant property
* Add validation transfer API for Microsoft.Billing. * Fix syntax. * Fix spelling Co-Authored-By: Nick Schonning <[email protected]> * Fix Semantic. * Remove unused definition. * Fix example. * Convert the validate api response to a list. * Restructure the example. * Address review comments.
* Fixing errors in swagger examples of Azure Backup * Updating reference path for moved file * Removing trailing commas in examples * Fixing semantic errors in Azure backup example
* adding_version_2019_05_15 * fix_error_in_examples_case_issue * fix_version_in_examples * enother_try_to_fix_examples * another_try * handle_error_201_in_examples * fix_readmego * another_try_fix_readme_files * try_fix_readme * fix_readme_and_resolve_comment * add_ofers_change * add_suppression * add_dor_and_ofer_changes * try_understand_one_error * try_the_other_string * try_add_suppressions * try_another_suppressions_syntax * try_suppressions * try_zim_suggestion * trying_to_fix_example_kusto_data_connection_validation * trying_to_fix_example_kusto_databases_check_name_availability * try2 * try3 * delete_suppressions * try4
* commit with 2018-09-30 files * incremental snapshots going in disk.json * adding incremental examples * upload size bytes and incremental snapshots * adding diskSizeBytes to disk.json * adding descriptions to the disk create option enums * adding diskSizeBytes as a read only field * adding encryptionSettingsVersion * updating readme * add example * removing extra descriptions * Revert "removing extra descriptions" This reverts commit 3a0f6498ff6d12663a4929cc78d05911112124c7. * adding enum descriptions back in * adding descriptions for some enums * fixing incorrect use of name and replacing it with the correct property value * adding unique id * fixing the snapshots examples so that model validation passes - don't send a read only field in the request * fixing typo * removing diskSizeBytes from snapshot\disk update properties and adding a unique id for disk properties * pr comments
…#7013) * New Readme Config File * New Go Language Readme Config File * New Typescript Language Readme Config File * New Python Language Readme Config File * New C# Language Readme Config File * New Ruby Language Readme Config File * New Swagger Spec File * New Swagger Example Spec File * Initialize the swagger spec review for azure data. * fix validation issues. * fixed Linter check. * fix by comments. * fix by comments * fix by comments. * fix CI error. * fix by comments. * fix build issue. * update the resource definition * update examples. * fix swagger * fix examples issue. * Swagger review comments * Moving azure-sdk on line up
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.