Releases: crossplane-contrib/provider-equinix-metal
Releases · crossplane-contrib/provider-equinix-metal
v0.0.11
v0.0.10
Fixes
- Updates CRDs to v1 for conformance testing
- Correctly treats VirtualNetwork Metro as immutable
Features
- Adds optional VXLAN field to VirtualNetwork
Improvements
- Includes metro field in print columns
- Moves device facility and VirtualNetwork facilityCode to priority=1 print columns (-o wide)
- Updates crossplane-runtime to 0.13.1 (pre-release)
- fix documentation and examples for hardwareReservationID
- use metro in README.md device examples
v0.0.9
v0.0.8
v0.0.7
v0.0.6
Crossplane 0.11 compatibility
The provider is renamed to crossplane-provder-packet and updated for Crossplane v0.11.
See https://github.com/packethost/crossplane-provider-packet#install-the-packet-provider for installation notes.
Changes include:
- a new README.md and more repository metadata addition and updates (makefile, listing, issue guidance)
- Device spec has moved to spec.forProvider
- Device status has moved to status.atProvider
- Initializers are used to fill in omitted spec.forProvider parameters after creation
- Device credentials are created in a secret with ssh user/pass/address information
- ProjectID has been moved out of Device and can now be configured in the Provider spec, optionally. ProjectID must be specified in the provider secret if it is omitted in the Provider (permitting blind reuse of CCM and CSI secrets).
- Provider secret format has changed from a single string (APIKey) to a json struct including APIKey, ProjectID, and others to be used later
- Print columns and categories have been added, enabling kubectl get packet -o wide and adding more details
- More fields have been added to forProvider and atProvider Device. (atProvider fields will not mirror forProvider fields unless they can differ - this reduces noise while expressing intent)
- forProvider fields that are not Packet API updateable are now marked as immutable (delete the resource and recreate it to change these fields)