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
merge master #3
Merged
Merged
merge master #3
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
For releasing ScopeMap and Token features, we need to retrieve models from the scopemap spec file. The existing SDK version doesn't incorporate changes from the scopemap spec file. Requesting a new SDK build. Please suggest changes if deemed necessary.
* added NetworkRuleSets list API * added x-ms-pageable and formating * removed readonly for compatibilityLevel
* Swagger changes for dynamics alternate key. * Add a clearer description.
* Update ManagedNetwork Tags * Revert space change * remove extra comma
No schema change, just removal of extra line.
* Following changes are related to updating the arm api version number to GA version. Current version number is 2018-08-20-preview. GA version number is 2019-09-16 * Add new example, change example names, and update kind. * Remove common from examples.
* Adds base for updating Microsoft.Network from version stable/2019-06-01 to version 2019-07-01 * Updates readme * Updates API version in new specs and examples * Update API version in VMSS' specs (#7008) * Add reference to existing base definition & fix errors in descriptions of Network's provisioningState property (#7026) * Improve Network's descriptions (#6974) * New Skus and Generations for VirtualNetworkVpnGateways (#7089) * New Skus and generations for VirtualNetwork VpnGateways * Minor Typo fix * update [email protected] (#7054) * Lock typescript version to fix compile error (#7068) * Fix description for vpnGatewayGeneration. * Add VirtualRouter top level resource Identity under Microsoft.Network/ExpressRoutePort and MacSecConfig under Microsoft.Network/ExpressRouteLink (#7005) * Fixed required properties in TrafficAnalyticsProperties: networkWatcehr.json (#7080) * Added traffic selector policy definition to virtualNetworkGateway.json (#7066) * Support for changes in ConnectionMonitor API (#7075) * Updating Network Config Diagnostics API desc (#7117) * Added priority field in the request routing rule (#7131) * Added priority field in the request routing rule * Added min and max * Minor * Added new owner to Azure Networking (#7145) added number213 to Az NW * Add Mssql value to Application Rule Type enum (#7169) * Add privateLinkConnectionProperties to network interface. (#7189) * Add privateLinkConnectionProperties to network interface on 2019-07-01. * Small changes for descriptions in the property. * make the new property to be read-only. * Brooklyn Gateway Packet Capture feature (#7151) * PacketCaptureOperationforVPNGateways * Update virtualNetworkGateway.json * Update VirtualNetworkGatewayConnectionStopPacketCapture.json * Update VirtualNetworkGatewayStopPacketCapture.json * Update VirtualNetworkGatewayStopPacketCapture.json * Update VirtualNetworkGatewayConnectionStopPacketCapture.json * Update VirtualNetworkGatewayConnectionStartPacketCapture.json * Update VirtualNetworkGatewayStartPacketCapture.json * Update virtualNetworkGateway.json * fixing examples * fixing virtualNetworkGateway.json * fixing params * fixing path params * response body * example errors * example errors * example errors * filterdata * Update virtualNetworkGateway.json * fixing Comments * Fixing ARM Comments * Remove duplicate definition
* Generate storage admin spec for 2019-08-08 * Change settings update operation id. * Add filter for list storage accounts. * Change order of FilterParameter and SummaryParameter * Change summary type in examples * Fix async operation * Add admin list acquisition scenario * Change acquisition body * Fix typo. * fix circular reference. * Fix comment * Change rest api. * Fix typo * Add back 2015-12-01 and fix comment * Fix comment * fix merge validation fail * fix model validation for farm * change nextlink name * fix nextpagelink issue.
* Azure Backup Version 2019-05-13 addition New api version 2019-05-13 for ProtectedItems_Get,ProtectedItems_CreateOrUpdate,RecoveryPoints_List,RecoveryPoints_Get,Restores_Trigger, BackupJobs_List, BackupProtectedItems_List and version 2017-07-01 for ProtectionPolicies_CreateOrUpdate * Update bms.json Fixing inconsistent description for recoverytype across workloads * Fixing description for recoveryType enum * Fixing Lintdiff and spell check failures * Lintdiff fix * Lintdiff another fix * another of lintdiff fix * Another one of never ending lintdiff failures Can we have tool to run this privately over the changes or can we have all the breaking changes in single go rather than one by one? * Another of lintdiff failure fix Getting them one by one and fixing them one by one * Lintdiff failure one by one * Litdiff another one of failure * Lintdiff Failure fix * Removing redundant models across api versions * Fixing redundant models * Semantics failure fix * Lintdiff Failure fix * Semantic failure fix * Semantics Failure fix * Camel casing failure * Update bms.json Adding azure vm workload policy back and copying IaaSVMRestoreRequest to 2017-07-01 * Updating examples * Pasting auto generated json specs * Fixing spelling mistakes and an unintended change * Moving examples to right folders * Fixing recovery point inconsistency * Removing ASE contracts * Fixing alongwith spelling mistake * Incorporating PR comments * Moving Get and Patch on vaultconfig to version 2019-05-13 Moving Patch and Get of vault config to 2019-05-13 * Taken care of Ryan's pending comments * Fixing validation errors * Updating vault config feature flag name * Taken care of Ryan's comment Policy comment is still pending * Moved all policy actions to 2019-05-13 version * Moving Settings and sorting models in alphabatical order * Mark additionalDetail as readonly
* Add v3.0 swagger * Update read me files * Add missing examples files * remove extra examples files * Up0date swagger file * Modify swagger file * swagger syntax fix * Fix swagger examples * Update LUIS-Authoring.json fix semantic bugs
* adding first readme file * properly named operation ids * fixed cli readme * disabled debugging by default
* Added Namespace properties for BYOK * semantic fixed * fixed spellcheck
* Adds base for updating Microsoft.StorageSync from version stable/2019-03-01 to version 2019-06-01 * Updates readme * Updates API version in new specs and examples * Update StorageSync 2019-06-01 protocol with cloud tiering and recall status (#7161) * introduce cloud tiering and recall status * fix validation errors * Additional validation fixes * [Microsoft.StorageSync] Fix tags for 2019-06-01 version in readme (#7413) * Fix tag for 2019-06-01 version in readme.md * Remove uneeded spaces and add new version to Multi-API
* adding package-2019-08 to python multiapi * changes for python * try different version of autorest * added trim-aio * additional fixes to multiapi generation
* Rest API for the RP Microsoft.AppPlatform * Fix spellcheck. * Resolve comment of changing operation "CheckNameAvailability" to "Services_CheckNameAvailability".
mudit794
pushed a commit
that referenced
this pull request
Feb 26, 2020
* Add encryption scope API to 2019-06-01. Add encryption scope API to 2019-06-01. * Address CI failures. * Fix CI failures #2. * Address CI failures #3. Co-authored-by: Anthony Kunnel Jose <[email protected]>
mudit794
pushed a commit
that referenced
this pull request
Feb 26, 2020
* 2019-08-09-preview * spell out networks * username and credential needed to add an IdentitySource * post listAdminCredentials * standardize on username, password, nsxt and vcenter * add nsxt to custom-words.txt * default cluster does not have provisioningState * it extends DefaultClusterProperties * add Circuit expressRoutePrivatePeeringID * back out some minor changes for sdk generation * identitySources and Circuit authorizations are updateable * add PrivateClouds_ListInSubscription * Long running operation for Clusters_Delete (#1) * npm run prettier * location for all resources (#2) * Revert "location for all resources (#2)" (#3) This reverts commit 432e37b. * add description TODOs * example is PrivateClouds_Update * require body in PrivateClouds_Update * replaced TODOs with descriptions * spellcheck * "x-ms-secret": true * Revert ""x-ms-secret": true" This reverts commit 3358dff. Co-authored-by: Andrew Ulliani <[email protected]> Co-authored-by: Eugene Tolmachev <[email protected]>
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.