-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Adding note about API being in preview #8088
Closed
Closed
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
…22 to version 2019-11-04
* Update swagger spec to add existing log analytics workspace * remove read only * changes * pretty * ID changed to Id * run prettier
* add patch to gallery spec * change descriptions to updated * updateresource * Added example and id/type to UpdateResource * add name * remove location in examples * make gallery json pretty
…n operation (#7724) * Swagger spec update :- Add the missing PATCH for VmssExtension operation * remove name * another try by adding back name with "readonly". I guess, a 3rd commit may be required (with readonly for type) * Added "readOnly": true for type * add type explicitly in VMSSExtension & Vmss Extension Update. * Make the publisher & type "readonly" in the VirtualMachineScaleSetExtensionUpdateProperties * just use VirtualMachineScaleSetExtensionProperties * Add 201 as well.
* Adding invoices under billing subscriptions * adding invoiceType * fixing operationId * removing next link from get * removing next link from get
* Add access condition headers * Add MySQL data source type to preview swagger
…ponse (#7793) * Billing RP spec changes for listInvoiceSectionsWithCreateSubscriptionPermission API * Updated the operation id * Added x-ms-pageable * Added next link * Deleted unused file ProductCancelByBillingAccount * Incorporated review comments Incorporated review comments * Added new properties in Invoicing APIs Added new properties in Invoicing APIs * Incorporated review comments Incorporated review comments * Added invoiceEmailOptIn in the UpdateBillingProfile request Added invoiceEmailOptIn in the UpdateBillingProfile request * Update billing.json * Updating the verbs from Create BillingProfile and InvoiceSection entities Updating the verbs from Create BillingProfile and InvoiceSection entities * Corrected the enum valure to match it with actual implementation Corrected the enum valure to match it with actual implementation * Updated * Updating BillingRoleDefinition Permission property to match with actual API response Updating BillingRoleDefinition Permission property to match with actual API response * Updated * Correcting the querystring parameter name as per actual implementation Correcting the querystring parameter name as per actual implementation * Updated examples to match it with actual API implementation Updated examples to match it with actual API implementation
* Fix Microsoft.policyInsights/policyMetadata query parameter * Fix slim metadata properties
…ersion preview/2018-02-28-preview (#7784)
* add ta v3.0-preview.1 * resolve comments * fix spaces * update examples * resolve comments * update /healthcare and score * update Bioentity and entityrecord * temp * update api changes based on meeting discussions * update healthcare * update entity linking * update naming/description * update pii * update required * udpate required --> still need kv pair for details inside innererror * update summary and description * resolve comments -- update opreationid, model-version, errors, etc * update error * update error * remove optional in response, update uppercase of Optional in requests * update space * resolve comments * revole comments * remove /healthcare * update score range in description * update description * update aka.ms links * update pii description to use personal information * resolve comments -- updte detectedLnauges & operationId * update error enum * update /readme.md * update aka.ms links * update aka.ms links * update preview read me name & descrition * update all examples to /examples * update unkown word to custom-word.txt * git update folder case name * update input name to match with example json files * update 500 to default --> same as previous version .json files * update MultiLanguageBatchInput * update examples formatting * update formatting of .json * update x-ms-examples descriptions * test required false for model-version&showStats * update model-version and showStats * update formatting * add x-nullabletrue * update formmating * update pii example forammating * update formaating * update formatting * update textanalytics.json format * testing * update model-vesrion * detele required false * prettier --write * remove exmpales from TextAnalytics.json * test keyphrase * keyphrase * keyphrase retry * update keyphrase back * update ta.json split []
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-go
|
azure-sdk-for-java
|
azure-sdk-for-js
|
azure-sdk-for-python
|
This was referenced Jan 8, 2020
zikalino
approved these changes
Jan 9, 2020
zikalino
suggested changes
Jan 9, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could you change this PR to network-december-release branch?
This is standard practice in case of network spec.
Pull request contains merge conflicts. |
Sent new PR here: #8104 |
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.