v0.15.0

0.15.0 (2023-07-28)

Features

• Adds support for tags on SSH keys and virtual networks (#119) (69b932a)
• Adds support for specifying storage configuration when creating a device (#119) (69b932a)
• Updates include and exclude parameter support for all endpoints to match the API implementation (#119) (69b932a)

v0.14.0

0.14.0 (2023-07-27)

Features

• Updates enumerated values for Device state in device & metadata endpoints (#116) (4b6a48b)
• Documents validation rules for project names (#116) (4b6a48b)
• Adds support for Project tags (#116) (4b6a48b)

v0.13.0

0.13.0 (2023-07-21)

Features

• Adds the Search parameter method on: devices (FindOrganizationDevices), ssh_keys (FindSSHKeys), api_keys (FindAPIKeys), and memberships (FindProjectMemberships) (#115) (9242ddc)
• Improves documentation for BGP Config definitions (#115) (9242ddc)
• Replaces incorrect VirtualCircuitList for InterconnectionPort method result objects with []VirtualCircuit (#115) (9242ddc)
• Adds Name filtering parameter method on projects (FindOrganizationProjects, FindProjects) (#115) (9242ddc)

v0.12.0

0.12.0 (2023-07-11)

Features

• Add support for memory in plan specs (#114) (6515b39)

v0.11.0

0.11.0 (2023-06-30)

Bug fixes

• Organization logo was incorrectly implemented as a file. It is now implemented as a string that contains base64-encoded image data. (#111) (afbfa4e)

v0.10.0

0.10.0 (2023-06-26)

The v0.10.0 release of metal-go reduces differences between metal-go and packngo, making it easier to adopt metal-go in places where packngo is currently used. The packngo behavior of logging Sunset and Deprecation headers--which are used by the Equinix Metal API to communicate important changes such as the deprecation of facilities--is now replicated in metal-go. In addition the API spec has been updated to fix a number of issues that prevented the use of organization and capacity endpoints in metal-go.

Features

• Logs sunset & deprecation headers for backwards compatibility with packngo (#110) (f1912ae)

Bug fixes

• Fixes data type of organization logo in API responses (was file, should be string) (#108) (6f8b252)
• Removes unnecessary duplicate models for VRF route properties metal_gateway, virtual_network, and vrf (#108) (6f8b252)
• Fixes capacity reports to remove incorrect, hard-coded metro and facility names (#109) (bb06fdd)

v0.9.0

0.9.0 (2023-06-14)

The v0.9.0 release of metal-go includes a number of features and improvements to ease the transition from packngo to metal-go. This includes support for include and exclude parameters when creating various Equinix Metal resources, fixed request paths for Metal Gateway API endpoints, and support for the default project ID and default organization ID for individual users.
This release of metal-go also includes features that are not available in packngo, such as support for the Invoices API. To learn more, check out the full release notes on GitHub and visit the metal-go page on Equinix Labs.

Features

• adds support for managing VRF BGP dynamic neighbors (#101)
• adds support for Invoices API (#101)
• adds user.DefaultOrganizationId and user.DefaultProjectId (#106)
• adds plan.Categories (#106)
• adds support for include and exclude parameters when creating devices, projects, organizations, VLANs, and VRFs
• upgrade to openapi-generator v6.6.0 (#104) (eb32982)

Bug fixes

• fixes incorrect request path for Metal gateway API endpoints (#101)

NOTE: VRF features are not generally available. The interfaces related to VRF resources may change ahead of general availability.

v0.8.0

0.8.0 (2023-06-02)

The 0.8.0 release of metal-go is based on the Equinix Metal API spec as of May 9th, 2023, and includes a number of bug fixes as well as quality-of-life improvements. A number of duplicated models have been consolidated to reduce the need for type conversions when interacting with different API endpoints. In addition, we have added support for the new SOS hostname attribute on devices in order to reduce reliance on the deprecated facility attribute.

Features

• Removed duplicated Virtual Circuit models (#93)
• Added support for new SOS hostname property on devices (#94)
• Added virtual circuits and bill properties to VRF models (#94)
• Added support for toggling BFD on dynamic BGP neighbors sessions when updating a VRF (#94)

Bug Fixes

• Fixed data types for some numeric properties (#91)
• Fixed incorrect property name for spot market request model (#94)

v0.7.1

metal-go v0.7.1

This release of our experimental generated Go SDK for the Equinix Metal API removes support for passing facility as a string when creating a device. The API supports receiving facility as a string or as an array of strings, and the generated code did not handle this complexity correctly, which made it impossible to use metal-go to create a device in a facility. The updated code only supports string arrays for facility, which covers the same uses cases as the old code and successfully created devices in facilities. This release also fixes incorrect type specifications on some IP address fields. Those fields were previously defined as floats, and are now correctly defined as 32-bit integers. To learn more about our generated Go SDK, visit the equinix-labs/metal-go repo on GitHub.

BUG FIXES:

• Update incorrect property types in IP address schema #89
• Remove support for facility as a string when creating a device #90

v0.7.0

metal-go v0.7.0

This release of our experimental generated Go SDK for the Equinix Metal API adds support for additionalProperties as required in the OpenAPI v3 specification. The new support for additionalProperties allows Go SDK clients to access properties that are included in API responses but are not documented in the API spec and improves the compatibility of the generated Go SDK with future API releases. This release also introduces a default User-Agent header for improved usage metrics. To learn more about our generated Go SDK, visit the equinix-labs/metal-go repo on GitHub.

FEATURES:

• Download split spec from https://api.equinix.com/metal/v1/api-docs for more straightforward patching #69
• Enable the use of additionalProperties to access fields that are returned by the API but are not defined in the API spec #85
• Update the default User-Agent for improved usage tracking #86
• Regenerated code from latest API spec #87

BUG FIXES:

• Patch Device schema so that project and hardware_reservation properties are defined with the correct schema components #80