Metal-Go v0.7.0 Release
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. Finally, this helps transition us from the old Packet packngo SDK! To learn more about our generated Go SDK, visit the equinix-labs/metal-go repo on GitHub.metal-go v0.15.0
A number of features and improvements have landed in metal-go since the v0.9.0 release last month. As of the latest release, v0.15.0, metal-go has gained support for: tags on projects, SSH keys, and virtual networks specifying storage configuration when creating a new device logging Sunset & Deprecation headers for backwards compatibility with packngo (especially important in light of the upcoming deprecation of facilities) filtering projects by name when loading all projects for a user or organization using the name query parameter searching devices by hostname, description, short_id, reservation short_id, tags, plan name, plan slug, facility code, facility name, operating system name, operating system slug, or IP addresses using the search query parameter For a full list of the changes that have landed in metal-go since v0.9.0, check out the the metal-go releases page on GitHub.metal-cli v0.15.0
The v0.15.0 release of metal-cli begins our migration from the packngo SDK to metal-go. The following subcommands have been updated to use metal-go in this release: init metros operating-systems plan project In addition, all subcommands have gained the --http-header flag, which can be used to add custom HTTP headers to any request that is sent to the Equinix Metal API as part of a metal-cli command execution.
