v1alpha3

type PacketCluster struct {
	metav1.TypeMeta   `json:",inline"`
	metav1.ObjectMeta `json:"metadata,omitempty"`

	Spec   PacketClusterSpec   `json:"spec,omitempty"`
	Status PacketClusterStatus `json:"status,omitempty"`
}

type PacketClusterList struct {
	metav1.TypeMeta `json:",inline"`
	metav1.ListMeta `json:"metadata,omitempty"`
	Items           []PacketCluster `json:"items"`
}

type PacketClusterSpec struct {
	// ProjectID represents the Packet Project where this cluster will be placed into
	ProjectID string `json:"projectID"`

	// Facility represents the Packet facility for this cluster
	// +optional
	Facility string `json:"facility,omitempty"`

	// Metro represents the Packet metro for this cluster
	// +optional
	Metro string `json:"metro,omitempty"`

	// ControlPlaneEndpoint represents the endpoint used to communicate with the control plane.
	// +optional
	ControlPlaneEndpoint clusterv1.APIEndpoint `json:"controlPlaneEndpoint"`

	// VIPManager represents whether this cluster uses CPEM or kube-vip to
	// manage its vip for the api server IP
	// +kubebuilder:validation:Enum=CPEM;KUBE_VIP
	// +kubebuilder:default:=CPEM
	VIPManager VIPManagerType `json:"vipManager"`
}

type PacketClusterStatus struct {
	// Ready denotes that the cluster (infrastructure) is ready.
	// +optional
	Ready bool `json:"ready"`
}

type PacketMachine struct {
	metav1.TypeMeta   `json:",inline"`
	metav1.ObjectMeta `json:"metadata,omitempty"`

	Spec   PacketMachineSpec   `json:"spec,omitempty"`
	Status PacketMachineStatus `json:"status,omitempty"`
}

type PacketMachineList struct {
	metav1.TypeMeta `json:",inline"`
	metav1.ListMeta `json:"metadata,omitempty"`
	Items           []PacketMachine `json:"items"`
}

type PacketMachineSpec struct {
	OS           string   `json:"OS"` //nolint: tagliatelle
	BillingCycle string   `json:"billingCycle"`
	MachineType  string   `json:"machineType"`
	SshKeys      []string `json:"sshKeys,omitempty"` //nolint: stylecheck

	// Facility represents the Packet facility for this cluster.
	// Override from the PacketCluster spec.
	// +optional
	Facility string `json:"facility,omitempty"`

	// Metro represents the Packet metro for this cluster
	// Override from the PacketCluster spec.
	// +optional
	Metro string `json:"metro,omitempty"`

	// IPXEUrl can be used to set the pxe boot url when using custom OSes with this provider.
	// Note that OS should also be set to "custom_ipxe" if using this value.
	// +optional
	IPXEUrl string `json:"ipxeURL,omitempty"`

	// HardwareReservationID is the unique device hardware reservation ID, a comma separated list of
	// hardware reservation IDs, or `next-available` to automatically let the Packet api determine one.
	// +optional
	HardwareReservationID string `json:"hardwareReservationID,omitempty"`

	// ProviderID is the unique identifier as specified by the cloud provider.
	// +optional
	ProviderID *string `json:"providerID,omitempty"`

	// Tags is an optional set of tags to add to Packet resources managed by the Packet provider.
	// +optional
	Tags Tags `json:"tags,omitempty"`
}

type PacketMachineStatus struct {
	// Ready is true when the provider resource is ready.
	// +optional
	Ready bool `json:"ready"`

	// Addresses contains the Packet device associated addresses.
	Addresses []corev1.NodeAddress `json:"addresses,omitempty"`

	// InstanceStatus is the status of the Packet device instance for this machine.
	// +optional
	InstanceStatus *PacketResourceStatus `json:"instanceStatus,omitempty"`

	// Any transient errors that occur during the reconciliation of Machines
	// can be added as events to the Machine object and/or logged in the
	// controller's output.
	// +optional
	ErrorReason *capierrors.MachineStatusError `json:"errorReason,omitempty"`

	// ErrorMessage will be set in the event that there is a terminal problem
	// reconciling the Machine and will contain a more verbose string suitable
	// for logging and human consumption.
	//
	// This field should not be set for transitive errors that a controller
	// faces that are expected to be fixed automatically over
	// time (like service outages), but instead indicate that something is
	// fundamentally wrong with the Machine's spec or the configuration of
	// the controller, and that manual intervention is required. Examples
	// of terminal errors would be invalid combinations of settings in the
	// spec, values that are unsupported by the controller, or the
	// responsible controller itself being critically misconfigured.
	//
	// Any transient errors that occur during the reconciliation of Machines
	// can be added as events to the Machine object and/or logged in the
	// controller's output.
	// +optional
	ErrorMessage *string `json:"errorMessage,omitempty"`
}

type PacketMachineTemplate struct {
	metav1.TypeMeta   `json:",inline"`
	metav1.ObjectMeta `json:"metadata,omitempty"`

	Spec PacketMachineTemplateSpec `json:"spec,omitempty"`
}

type PacketMachineTemplateList struct {
	metav1.TypeMeta `json:",inline"`
	metav1.ListMeta `json:"metadata,omitempty"`
	Items           []PacketMachineTemplate `json:"items"`
}

type PacketMachineTemplateResource struct {
	// Spec is the specification of the desired behavior of the machine.
	Spec PacketMachineSpec `json:"spec"`
}

type PacketMachineTemplateSpec struct {
	Template PacketMachineTemplateResource `json:"template"`
}

type PacketResourceStatus string

type Tags []string

type VIPManagerType string