model_interconnection_port_role.go

/*
Metal API

# Introduction Equinix Metal provides a RESTful HTTP API which can be reached at <https://api.equinix.com/metal/v1>. This document describes the API and how to use it.  The API allows you to programmatically interact with all of your Equinix Metal resources, including devices, networks, addresses, organizations, projects, and your user account. Every feature of the Equinix Metal web interface is accessible through the API.  The API docs are generated from the Equinix Metal OpenAPI specification and are officially hosted at <https://metal.equinix.com/developers/api>.  # Common Parameters  The Equinix Metal API uses a few methods to minimize network traffic and improve throughput. These parameters are not used in all API calls, but are used often enough to warrant their own section. Look for these parameters in the documentation for the API calls that support them.  ## Pagination  Pagination is used to limit the number of results returned in a single request. The API will return a maximum of 100 results per page. To retrieve additional results, you can use the `page` and `per_page` query parameters.  The `page` parameter is used to specify the page number. The first page is `1`. The `per_page` parameter is used to specify the number of results per page. The maximum number of results differs by resource type.  ## Sorting  Where offered, the API allows you to sort results by a specific field. To sort results use the `sort_by` query parameter with the root level field name as the value. The `sort_direction` parameter is used to specify the sort direction, either either `asc` (ascending) or `desc` (descending).  ## Filtering  Filtering is used to limit the results returned in a single request. The API supports filtering by certain fields in the response. To filter results, you can use the field as a query parameter.  For example, to filter the IP list to only return public IPv4 addresses, you can filter by the `type` field, as in the following request:  ```sh curl -H 'X-Auth-Token: my_authentication_token' \\   https://api.equinix.com/metal/v1/projects/id/ips?type=public_ipv4 ```  Only IP addresses with the `type` field set to `public_ipv4` will be returned.  ## Searching  Searching is used to find matching resources using multiple field comparissons. The API supports searching in resources that define this behavior. Currently the search parameter is only available on devices, ssh_keys, api_keys and memberships endpoints.  To search resources you can use the `search` query parameter.  ## Include and Exclude  For resources that contain references to other resources, sucha as a Device that refers to the Project it resides in, the Equinix Metal API will returns `href` values (API links) to the associated resource.  ```json {   ...   \"project\": {     \"href\": \"/metal/v1/projects/f3f131c8-f302-49ef-8c44-9405022dc6dd\"   } } ```  If you're going need the project details, you can avoid a second API request.  Specify the contained `href` resources and collections that you'd like to have included in the response using the `include` query parameter.  For example:  ```sh curl -H 'X-Auth-Token: my_authentication_token' \\   https://api.equinix.com/metal/v1/user?include=projects ```  The `include` parameter is generally accepted in `GET`, `POST`, `PUT`, and `PATCH` requests where `href` resources are presented.  To have multiple resources include, use a comma-separated list (e.g. `?include=emails,projects,memberships`).  ```sh curl -H 'X-Auth-Token: my_authentication_token' \\   https://api.equinix.com/metal/v1/user?include=emails,projects,memberships ```  You may also include nested associations up to three levels deep using dot notation (`?include=memberships.projects`):  ```sh curl -H 'X-Auth-Token: my_authentication_token' \\   https://api.equinix.com/metal/v1/user?include=memberships.projects ```  To exclude resources, and optimize response delivery, use the `exclude` query parameter. The `exclude` parameter is generally accepted in `GET`, `POST`, `PUT`, and `PATCH` requests for fields with nested object responses. When excluded, these fields will be replaced with an object that contains only an `href` field.

API version: 1.0.0
Contact: support@equinixmetal.com
*/

// Code generated by OpenAPI Generator (https://openapi-generator.tech); DO NOT EDIT.

package v1

import (
	"encoding/json"
	"fmt"
)

// InterconnectionPortRole Either 'primary' or 'secondary'.
type InterconnectionPortRole string

// List of InterconnectionPort_role
const (
	INTERCONNECTIONPORTROLE_PRIMARY   InterconnectionPortRole = "primary"
	INTERCONNECTIONPORTROLE_SECONDARY InterconnectionPortRole = "secondary"
)

// All allowed values of InterconnectionPortRole enum
var AllowedInterconnectionPortRoleEnumValues = []InterconnectionPortRole{
	"primary",
	"secondary",
}

func (v *InterconnectionPortRole) UnmarshalJSON(src []byte) error {
	var value string
	err := json.Unmarshal(src, &value)
	if err != nil {
		return err
	}
	enumTypeValue := InterconnectionPortRole(value)
	for _, existing := range AllowedInterconnectionPortRoleEnumValues {
		if existing == enumTypeValue {
			*v = enumTypeValue
			return nil
		}
	}

	return fmt.Errorf("%+v is not a valid InterconnectionPortRole", value)
}

// NewInterconnectionPortRoleFromValue returns a pointer to a valid InterconnectionPortRole
// for the value passed as argument, or an error if the value passed is not allowed by the enum
func NewInterconnectionPortRoleFromValue(v string) (*InterconnectionPortRole, error) {
	ev := InterconnectionPortRole(v)
	if ev.IsValid() {
		return &ev, nil
	} else {
		return nil, fmt.Errorf("invalid value '%v' for InterconnectionPortRole: valid values are %v", v, AllowedInterconnectionPortRoleEnumValues)
	}
}

// IsValid return true if the value is valid for the enum, false otherwise
func (v InterconnectionPortRole) IsValid() bool {
	for _, existing := range AllowedInterconnectionPortRoleEnumValues {
		if existing == v {
			return true
		}
	}
	return false
}

// Ptr returns reference to InterconnectionPort_role value
func (v InterconnectionPortRole) Ptr() *InterconnectionPortRole {
	return &v
}

type NullableInterconnectionPortRole struct {
	value *InterconnectionPortRole
	isSet bool
}

func (v NullableInterconnectionPortRole) Get() *InterconnectionPortRole {
	return v.value
}

func (v *NullableInterconnectionPortRole) Set(val *InterconnectionPortRole) {
	v.value = val
	v.isSet = true
}

func (v NullableInterconnectionPortRole) IsSet() bool {
	return v.isSet
}

func (v *NullableInterconnectionPortRole) Unset() {
	v.value = nil
	v.isSet = false
}

func NewNullableInterconnectionPortRole(val *InterconnectionPortRole) *NullableInterconnectionPortRole {
	return &NullableInterconnectionPortRole{value: val, isSet: true}
}

func (v NullableInterconnectionPortRole) MarshalJSON() ([]byte, error) {
	return json.Marshal(v.value)
}

func (v *NullableInterconnectionPortRole) UnmarshalJSON(src []byte) error {
	v.isSet = true
	return json.Unmarshal(src, &v.value)
}