API v4.173.0

4.173.0,

Changed

Fixed

  • Fixed a bug that allowed unsupported IPv6 address zone_id notation in requests when creating or updating Cloud Firewall rules.

API v4.170.2

4.170.2,

Added

  • Linode Resize ( POST /linode/instances/{linodeId}/resize)

  • Added type property with two values:

    • warm: the Linode remains powered on until the migration is complete.
    • cold: the Linode is powered down and migrated. When the migration is complete, the Linode is powered on.
  • Linode Migrate ( POST /linode/instances/{linodeId}/migrate)

  • Added migration_type property with two values:

    • warm: the Linode remains powered on until the migration is complete.
    • cold: the Linode is powered down and migrated. When the migration is complete, the Linode is powered on.

API v4.170.0

4.170.0,

Added

  • Customers can now view, create, update, and delete VPCs, VPC subnets, and Configuration Profile Interfaces with the API.
    • VPCs List (GET /vpcs)
    • VPC Create (POST /vpcs)
    • VPC View (GET /vpcs/{vpcId})
    • VPC Update (PUT /vpcs/{vpcId})
    • VPC Delete (DELETE /vpcs/{vpcId})
    • VPC Subnets List (GET /vpcs/{vpcId}/subnets)
    • VPC Subnet Create (POST /vpcs/{vpcId}/subnets)
    • VPC Subnet View (GET /vpcs/{vpcId}/subnets/{vpcSubnetId})
    • VPC Subnet Update (PUT /vpcs/{vpcId}/subnets/{vpcSubnetId})
    • VPC Subnet Delete (DELETE /vpcs/{vpcId}/subnets/{vpcSubnetId})
    • Configuration Profile Interfaces List (GET /linode/instances/{linodeId}/configs/{configId}/interfaces)
    • Configuration Profile Interface Add (POST /linode/instances/{linodeId}/configs/{configId}/interfaces)
    • Configuration Profile Interface View (GET /linode/instances/{linodeId}/configs/{configId}/interfaces/{interfaceId})
    • Configuration Profile Interface Update (PUT /linode/instances/{linodeId}/configs/{configId}/interfaces/{interfaceId})
    • Configuration Profile Interface Delete (DELETE /linode/instances/{linodeId}/configs/{configId}/interfaces/{interfaceId})
    • Configuration Profile Interfaces Order (POST /linode/instances/{linodeId}/configs/{configId}/interfaces/order)

Changed

  • As part of the VPC launch, the following endpoints have been modified:
    • Linode Create (POST /linode/instances)
    • Linode Clone (POST /linode/instances/{linodeId}/clone)
    • Firewall Create (POST /networking/firewalls)
    • IPv4 Address Delete (DELETE /linode/instances/{linodeId}/ips/{address})
    • IP Addresses Assign (POST /networking/ips/assign)
    • IP Addresses Share (POST /networking/ips/share)
    • Support Ticket Request (POST /support/tickets)
    • User’s Grants View (GET /account/users/{username}/grants)
    • User’s Grants Update (PUT /account/users/{username}/grants)
    • All commands with request and response bodies that include Interfaces.

API v4.169.1

4.169.1,

Fixed

  • Account Availability ( GET /account/availability)
    • Update CLI actions from Camel case (e.g. getAvailability) to Hyphen-cased (e.g. get-availability )
    • Fix server URL so the CLI will be able to target the endpoints in v4beta path.

API v4.169.0

4.169.0,

Added

Changed

  • Database Engine ( GET /databases/engines):

    • Added database size and used space data for Managed Database object response
  • Images ( POST /images, POST /images/upload)

    • Adds documentation for the cloud_init field in the POST /images and POST /images/upload request bodies

Fixed

API v4.168.0

4.168.0,

Added

Cloud Firewall is now available on NodeBalancer.

  • You can list Firewalls assigned to NodeBalancers Firewalls List.
  • You can add a firewall to a NodeBalancer NodeBalancer Create.
  • Firewall rule information for NodeBalancers; firewalls only apply to inbound TCP traffic to NodeBalancers.

API v4.167.3

4.167.3,

Changed

  • You can now assign a Firewall to a Linode compute instance by utilizing the firewall_id when running the Linode Create operation.

  • The following rate limit changes have been made:

    • General API request rate limit reduced from 1,600 requests every 2 minutes to 800 requests every 2 minutes.
    • Default operation rate limit reduced from 800 requests per minute to 400 requests per minute.
    • GET collection operation default rate limit reduced from 400 requests per minute to 200 requests per minute.
    • Statistics operations rate limit reduced from 100 requests per minute to 50 requests per minute.

API v4.167.0

4.167.0,

Changed

  • Previously, running the Linode View operation on a suspended Linode returned a 400 response with a “This Linode has been suspended” error message. Now, running this operation on suspended Linodes returns the expected data with the new billing_suspension status.

Fixed

API v4.166.0

4.166.0,

Changed

API v4.164.0

4.164.0,

Added

Changed

  • As part of our ongoing commitment to innovation and better serving our customers, we have made the strategic decision to pause the sale of our Managed Database offering for all customers who do not have an active database deployed. We recognize the need for a product that offers higher performance and the capacity to handle more complex workloads.

    If you have an existing database already deployed, you will continue to be able to deploy, provision, and manage the service exactly as you do today, and we’ll fully support your Managed Database workloads until our next-generation database solution is available. For all other customers, all Managed Databases commands are inaccessible.

  • Billing for services can now depend on the Region in which those services are deployed. Accordingly, Region-specific price data is now available in responses to the following commands:

  • GET commands that return paginated data collections now have a default rate limit of 400 requests per minute. Additionally, the Images List ( GET /images) command now has a 20 request per minute rate limit.

  • The following endpoints now generate respective Events upon successful requests:

This page was originally published on


Your Feedback Is Important

Let us know if this guide was helpful to you.