DataBox Edge - Rename from edgegateway to databoxedge, added a new version of API#7115
DataBox Edge - Rename from edgegateway to databoxedge, added a new version of API#7115lirenhe merged 16 commits intoAzure:masterfrom anponnet:master
Conversation
Rename edgegateway to databoxedge, create new version of API Co-Authored-By: Arun Ramachandran <arramach@microsoft.com>
Correcting readme scripts
|
Can one of the admins verify this patch? |
Automation for azure-sdk-for-goA PR has been created for you: |
Automation for azure-sdk-for-pythonA PR has been created for you: |
nschonni
left a comment
There was a problem hiding this comment.
You'll need to update the ignore for the misspelled "Fulfilment" for the old version if you're renaming the file
azure-rest-api-specs/cSpell.json
Lines 572 to 576 in 1cf4036
| "$ref": "./examples/UploadCertificatePost.json" | ||
| } | ||
| } | ||
|
|
There was a problem hiding this comment.
Fulfilment -> Fulfillment
| "enum": [ "Untracked", "AwaitingFulfillment", "AwaitingPreparation", "AwaitingShipment", "Shipped", "Arriving", "Delivered", "ReplacementRequested", "LostDevice", "Declined", "ReturnInitiated", "AwaitingReturnShipment", "ShippedBack", "CollectedAtMicrosoft" ], |
|
@anponnet , there are a couple of tool check errors in this PR, could you help to fix the Avocado error which is required for the merge (public.rest-api-specs (Avocado) Failing after 6m — Avocado failed )? |
KrisBash
left a comment
There was a problem hiding this comment.
Reviewed changes in the new version vs 2019-03-01. LGTM
@lirenhe I have fixed the validation errors and tests are passed. Can you please review |
|
@lirenhe the spellcheck was flagging a typo in the Enum value. It was suppressed on the old version (but not fixed with the rename). Not sure the new version should be merged/released without fixing that |
|
@anponnet Would you please fix the spellcheck error https://github.com/Azure/azure-rest-api-specs/pull/7115/checks?check_run_id=223623035 |
@phoenix We have to release a new version of API to fix it. We will fix it and send a new CR with updated version |
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.