v4.86.0

Added

• The following endpoints for the new Service Transfer feature, which enables transfers of Linodes between customer accounts, have been added:
  • Service Transfers List (GET /account/service-transfers). Returns a collection of all created and accepted Service Transfers.
  • Service Transfer Create (POST /account/service-transfers). Creates a transfer request for the specified services. At this time, only Linodes can be transferred.
  • Service Transfer Cancel (DELETE /account/service-transfers/{token}). Cancels the Service Transfer for the provided token.
  • Service Transfer View (GET /account/service-transfers/{token}). Returns the details of the Service Transfer for the provided token.
  • Service Transfer Accept (POST /account/service-transfers/{token}/accept). Accept an Service Transfer for the provided token to receive the services included in the transfer to your account.

Changed

• The following endpoints have been deprecated:

  • Entity Transfers List (GET /account/entity-transfers).
  • Entity Transfer Create (POST /account/entity-transfers).
  • Entity Transfer Cancel (DELETE /account/entity-transfers/{token}).
  • Entity Transfer View (GET /account/entity-transfers/{token}).
  • Entity Transfer Accept (POST /account/entity-transfers/{token}/accept).

• The Firewall Create (POST /networking/firewalls) beta endpoint has been updated with the following:

  • The required rules.inbound_policy and rules.outbound_policy properties were added to allow controlling default behavior for inbound and outbound traffic, respectively.
  • The rules.inbound.action and rules.outbound.action properties were added to control traffic for individual rules. These properties are required for inbound and outbound rules and override the rules.inbound_policy and rules.outbound_policy properties, respectively.
  • Previously, rules.inbound was required. It is now optional.
  • The rules.inbound.label, rules.inbound.description, rules.outbound.label, and rules.outbound.description properties were added for organization and display purposes.
  • Previously, up to five active Firewalls could be assigned to a single Linode service. Now, only one active Firewall can be assigned to a single Linode service.

Fixed

• A bug has been fixed that prevented correct filtering for the Service Transfers List (GET /account/service-transfers) endpoint is_sender property.

• The Volume Attach (POST /volumes/{volumeId}/attach) endpoint erroneously marked the linode_id property as nullable and required. This has been corrected to state that the property is optional and only accepts an integer .

v4.85.0

Fixed

• The Maintenance List (GET /account/maintenance) beta endpoint previously returned information for inactive Linodes. This has been fixed to exclude information for inactive Linodes.

• The Domain Update (PUT /domains/{domainId}) endpoint request body schema erroneously stated that the domain and type properties were required. The spec has been updated to mark these properties as optional.

• The Domain Create (POST /domains) endpoint and Domain Update (PUT /domains/{domainId}) endpoint SHELL request samples incorrectly stated a display_group property and excluded the tags property. The samples have been updated to state the group and tags properties.

• The following Domain schema properties have been updated to include the following missing value traits:

  • domain: minimum 1 and maximum 255 characters
  • status: a default value of active
  • refresh_sec: a valid, default value of 0, which is equivalent to 14400
  • retry_sec: a valid, default value of 0, which is equivalent to 14400
  • expire_sec: a valid, default value of 0, which is equivalent to 1209600

• The Account View (GET /account) endpoint response body balance_uninvoiced description inaccurately stated that "Bandwidth charges are not included in the estimate." This has been corrected to state that "Transfer charges are not included in the estimate."

v4.84.1

Changed

• The Entity Transfer Create (POST /account/entity-transfers) endpoint description has been updated to include warnings regarding Linode Backups and associated DNS records.

Fixed

• The Linode CLI command examples and schema were faulty and have been fixed for the following endpoints:

  • Entity Transfers List (GET /account/entity-transfers).
  • Entity Transfer Create (POST /account/entity-transfers).
  • Entity Transfer Cancel (DELETE /account/entity-transfers/{token}).
  • Entity Transfer View (GET /account/entity-transfers/{token}).
  • Entity Transfer Accept (POST /account/entity-transfers/{token}/accept).

v4.84.0

Added

• The following endpoints for the new Entity Transfer feature, which enables transfers of Linodes between customer accounts, have been added:

  • Entity Transfers List (GET /account/entity-transfers). Returns a collection of all created and accepted Entity Transfers.
  • Entity Transfer Create (POST /account/entity-transfers). Creates a transfer request for the specified entities. At this time, only Linodes can be transferred.
  • Entity Transfer Cancel (DELETE /account/entity-transfers/{token}). Cancels the Entity Transfer for the provided token.
  • Entity Transfer View (GET /account/entity-transfers/{token}). Returns the details of the Entity Transfer for the provided token.
  • Entity Transfer Accept (POST /account/entity-transfers/{token}/accept). Accept an Entity Transfer for the provided token to receive the entities included in the transfer to your account.

• The Linode Firewalls List (GET /linode/instances/{linodeId}/firewalls) endpoint has been added. This endpoint provides Firewall information for Firewalls associated with a particular Linode.

Changed

• The request body schema for the Domain Record Create (POST /domains/{domainId}/records) endpoint has been updated to include details regarding the different functions of the name and target properties for all record types. Previously, only minor details for the A and AAAA record types were provided.

• The request body schema for the Firewalls Create (POST /networking/firewalls) beta endpoint has been updated to specify that the label property is now required and must be unique.

Fixed

• The shell request sample for the Volume Attach (POST /volumes/{volumeId}/attach) endpoint erroneously stated a PUT request. It has been corrected to state a POST request.

v4.83.2

Changed

• The limit of Firewalls per Linode service has been increased from 3 to 5. Descriptions for Firewall (/networking) beta endpoints were updated to reflect this increase.

• The description for the User Create (POST /account/users) endpoint has been updated to include details for the email confirmation that is sent to newly-created Users.

• The description for the Kubernetes Cluster Recycle (POST /lke/clusters/{clusterId}/recycle) endpoint has been updated to include more descriptive language regarding recycling all Nodes within an LKE Cluster.

Fixed

• Descriptions for Object Storage (/object-storage) endpoints contained broken links to S3 API documentation. These links have been fixed.

v4.83.1

Fixed

• Corrected typos found in the API Specification.

v4.83.0

Added

• The LKE Kubernetes Cluster Recycle (POST /lke/clusters/{clusterId}/recycle) endpoint can now be used to recycle all of the Nodes in a Kubernetes cluster. Replacement Nodes are installed with the latest available patch for the Cluster's Kubernetes Version.

• The LKE Node View (GET /lke/clusters/{clusterID}/nodes/{nodeId}) endpoint can now be used to view the details of an individual Node within a Kubernetes cluster.

• The LKE Node Recycle (POST /lke/clusters/{clusterId}/nodes/{nodeId}/recycle) endpoint can now be used to recycle a Node within a Kubernetes cluster. Replacement Nodes are installed with the latest available patch for the Cluster's Kubernetes Version.

Updated

• The LKE Kubernetes Cluster Update (PUT /lke/clusters/{clusterId}) endpoint now includes the k8s_version property in its request body schema. This property can be used to upgrade a Kubernetes cluster to the next minor version. New and recycled Nodes in this cluster will be deployed using the latest supported patch of this version.

v4.82.0

Fixed

• A bug was fixed to reject leading zeroes on ports set in Firewalls inbound and outbound rules. The following endpoints have been updated to reflect this new exclusion:

  • Firewall Create (POST /networking/firewalls)
  • Firewall Update (PUT /networking/firewalls/{firewallId})
  • Firewall Rules Update (PUT /networking/firewalls/{firewallId}/rules)

• The Object Storage Object ACL Config Update (PUT /object-storage/buckets/{clusterId}/{bucket}/object-acl) endpoint previously specified the object name as a query parameter. This was corrected to specify the object name in the request body.

• The following endpoints were corrected to include page, pages, and results in their response objects:

  • User Logins List All (GET /account/logins)
  • Logins List (GET /profile/logins)

v4.81.0

Fixed

• A bug was fixed to allow preservation of URL parameters for service monitor addresses set at the following endpoints:

  • Managed Service Create (POST /managed/services)
  • Managed Service Update (PUT /managed/services/{serviceId})

• OAuth Reference has been updated to include Firewall, Maintenance, and Object Storage security scopes.

• The x-linode-grant for the Event Mark as Seen (POST /account/events/{eventId}/seen) endpoint has been corrected to read_only. Previously, it was stated as read_write.

• The OAuth scope for the Firewalls List (GET /networking/firewalls) endpoint has been correct to firewall:read_only. Previously, it was stated as firewalls:read_only.

4.81.0: [Update] Managed Service Create/Update address examples (#364)

* Add URL examples to POST /managed/services

* Add spacing