Merged
Conversation
…te (#6683) * Add terminate notification profile and scheduled events profile to the Microosft.Compute autorest config. * Correct definition format * Update specification/compute/resource-manager/Microsoft.Compute/stable/2019-03-01/compute.json Co-Authored-By: Nick Schonning <nschonni@gmail.com> * Update specification/compute/resource-manager/Microsoft.Compute/stable/2019-03-01/compute.json Co-Authored-By: Nick Schonning <nschonni@gmail.com> * Add ScheduledEventsProfile to the UpdateVMScaleSetVM model, and add instance view expansion to get VM Scale Set VM. * Add an example for terminate scheduled events, and add type:object to scheudled events and termiante profile schemas. * Add example reference into compute.json * Fix example file naming. * Fix terminate scheduled event reference.
Remove empty body for RESPONSE_SCHEMA_NOT_IN_SPEC errors
- Add "body" for RESPONSE_BODY_NOT_IN_EXAMPLE errors - "path" -> "folderPath"
- Remove empty body for RESPONSE_SCHEMA_NOT_IN_SPEC errors - Unstrigify response body values
* RosettaNet Process configuration apis Integration account - RosettaNet CRUD APIs Integration account- agreement changes for RosettaNet agreement type. * updated examples path * fixes CI errors Fixed casing as required by CI * ModelValidation fixes * merge conflicts resoultion * CI fixes * Additional model validation fixes * test fixes * operation test fix * removed breaking changes * pr feedback * added custom words for spell check
Remove empty body for RESPONSE_SCHEMA_NOT_IN_SPEC errors
Change "parameters" to "body" for RESPONSE_BODY_NOT_IN_EXAMPLE errors
* Add way to override the service url * fix file reference * removed readonly property
* added entities + exand * added cases missing properties * renamed inner entities * fixed error in 'get all entitiy queries' example * fixed error in 'get all entitiy queries' example * fixed model validation errors * fixed typos * changed entities location * changed entities location * changed entities location * fixed indentation issues * fixed confidence reasons + reuse alert severity * GetAll entities returned * added custom words * fixed filehash entity defenition * removed cases changes (will be in another PR) * removed cases changes (will be in another PR) * removed cases changes (will be in another PR) * removed bookmarkEntity from entities api (currently not supported) * rerun tests
…ew/v1.0 - Changing format of points from string to object as requested by Azure board and fleshing out properties. (#6776) * update to switch ink point format from a string to an object with properties * Adding xms for unit in request section * fix for new inkpoint object format * fix for new inkpoint object format * fix for new inkpoint object format * Adding the root inkrecognition unit * Ink Point description update * Ink Point description update * description updates * Ink Point description update * re-naming inputDevice to inputDeviceKind * Update specification/cognitiveservices/data-plane/InkRecognizer/preview/v1.0/InkRecognizer.json Co-Authored-By: Nick Schonning <nschonni@gmail.com> * Update specification/cognitiveservices/data-plane/InkRecognizer/preview/v1.0/InkRecognizer.json Co-Authored-By: Nick Schonning <nschonni@gmail.com> * Update specification/cognitiveservices/data-plane/InkRecognizer/preview/v1.0/InkRecognizer.json Co-Authored-By: Nick Schonning <nschonni@gmail.com>
* trigger ci * trigger * undo readmechange * fix readme * just triggereing rebuild * fix
* add HyperVGeneation in SharedVMImageVersion * reuse HyperVGenerationType
* fix: servicefabric character encoding * fix: Remove empty body for model validation
* add only tag for ruby sdk * fix the format * add 2019-08
* Improving Security Center pricing API documentation * More pricing documentation changes
…eview/2018-10-01-preview (#6825) * Adds base for updating Microsoft.Portal from version preview/2015-08-01-preview to version 2018-10-01-preview * Updates readme * Updates API version in new specs and examples * fix the 2018-10-01-preview json spec
Previously wasn't flagged by oav. It also uncovered other issues
Remove empty "body" for RESPONSE_SCHEMA_NOT_IN_SPEC errors
nitegupt
pushed a commit
that referenced
this pull request
Apr 2, 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 <aulliani@yahoo.com> Co-authored-by: Eugene Tolmachev <e.tolmachev@gmail.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
19 participants
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.