Resource Tagging and New MVE Endpoints
Resource Tagging – Customers now have the ability to create, modify, and delete resource tags to manage their active services via the Megaport API. Resource tags are key and value pairs that act as metadata for organizing Megaport resources. These tags will appear in the Service Inventory report by default for the company who has implemented the tags providing they own the service the tag is put against.
New Endpoints for MVE – The new endpoints GET v3/locations and GET v4/product/mve/images have been added. v3/locations and v4/product/mve/images are intended to replace v2/locations and v3/product/mve/images. The MVE details have moved to v4/product/mve/images. If the v3/locations diversityZones has a value in the mveMaxCpuCoreCount then you can order any MVE from the v4/product/mve/images endpoint as long as the size is less than the maxMaxCpuCoreCount.
Add Max Length Validation to Service Level Reference Field – Validations have been changed for the Service Level Reference field (costCentre) so that this field now has a maximum value of 255 characters.
Fixed – API was responding with a 400 error instead of a 404 when querying a product that doesn’t exist.