Skip to content

packet-cli-v0.1.0
Compare
Choose a tag to compare
@displague displague released this 09 Oct 14:43
0.1.0
4df870e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Packet is now Equinix Metal!, keep an eye on this project for future project and command line name changes.

This release renames Packet name occurrences, URLs, and emails to Equinix Metal.

Breaking Changes

  • Updates packet-cli to use packngo-0.4.1
    • https://api.equinix.com/metal/v1 should be permitted in your network policies
    • https://api.packet.net is no longer used
  • packet device create no longer takes --storage
    This UUID parameter did not match the API spec (currently undocumented, the details can be found in packngo. The storage field expects a complex structure of disks, raids, and filesystems, not a uuid string).

What's not changing (for now)?

  • The command-line tool continues to be named packet, for now.
  • The project name (go package URL) continues to carry the packet-cli name, for now.
  • PACKET_TOKEN remains the environment variable, for now.
  • ~/.packet-cli.yaml / ~/.packet-cli.json remains the configuration file, for now.

When will this change?

In weeks and months to come. Consideration will be made regarding the legacy token and file names. We could continue checking for these names indefinitely, but we could just make a clean break with a binary rename. What about making the token and filename use the binary name? That's sounds too complicated to manage, the binary can already be packet or packet-cli depending on how you installed it.

What will happen to this repo?

Keep an eye out.

Assets 13
Loading