v4.168.0

Added

• Added the NodeBalancer Firewalls List command

Changed

• Updated Cloud Firewall commands to include the nodebalancer entity type

v4.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.

v4.167.1

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

• Fixed a bug that caused live migrations of Linode compute instances to fail if an assigned Firewall was established or updated during the migration. Now, the following Firewall operations return an error if assigned Linodes have any ongoing live migrations:
  • Firewall Create
  • Firewall Update
  • Firewall Delete
  • Firewall Device Create
  • Firewall Device Delete
  • Firewall Rules Update

v4.166.0

Changed

• When creating or updating MX Domain Records, name (subdomain) and target (domain) values submitted in requests must now pass respective validation criteria. This change affects the following commands:
  • Domain Record Create (POST /domains/{domainId}/records)
  • Domain Record Update (PUT /domains/{domainId}/records/{recordId})

v4.165.0

Internal updates only.

v4.164.2

Internal updates only.

v4.164.1

Added

• Customers now have the ability to view and self-enroll in our Cloud Beta Programs with the following new commands:
  • Beta Programs List (GET /betas)
  • Beta Program View (GET /betas/{betaId})
  • Beta Program Enroll (POST /account/betas)
  • Enrolled Beta Programs List (GET /account/betas)
  • Enrolled Beta Program View (GET /account/betas/{betaId})

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:

  • Linode Types List (GET /linode/types)
  • Linode Type View (GET /linode/types/{typeId})
  • Network Utilization View (GET /account/transfer)
  • Invoice Items List (GET /account/invoices/{invoiceId}/items)

• 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:

  • Object Storage Key Create (POST /object-storage/keys)
  • Object Storage Key Revoke (DELETE /object-storage/keys/{keyId})
  • Object Storage Key Update (PUT /object-storage/keys/{keyId})

v4.163.1-patch.1

• Managed Databases EOS
• Examples udpates

v4.163.0

Changed

• Our new Metadata service has completed its Beta phase and is now generally available to all customers!

  This new feature utilizes cloud-config to automatically configure and install software to compute instances when using the following commands:

  • Linode Create (POST /linode/instances)
  • Linode Clone (POST /linode/instances/{linodeId}/clone)
  • Linode Rebuild (POST /linode/instances/{linodeId}/rebuild)

Fixed

• IP Addresses Assign (POST /networking/ips/assign)
  • Fixed a bug that allowed shared IP addresses to be swapped between Linodes with this command, resulting in a Linode with the same IP address listed twice. Now, an error is thrown when trying to swap shared IP addresses between two Linodes.

v4.162.0

Changed

• Backup Restore (POST /linode/instances/{linodeId}/backups/{backupId}/restore)

  • Now, certain distributions assign block devices using UUIDs. This causes a potential UUID collision issue when restoring a disk to the same Compute Instance without overwriting it. If you need access to files on both the original disk and the restored disk simultaneously (such as needing to copy files between them), we suggest either restoring the backup to a separate Compute Instance or creating a new Compute Instance with the desired backup_id.

• Domain Record Create (POST /domains/{domainId}/records)

  Domain Record Update (PUT /domains/{domainId}/records/{recordId})

  • In accordance with the new RFC 8659, CAA records with the "issue" tag can now accept additional parameters when using these commands. New parameters are entered via the record's target, following the domain and separated with semicolons (;), for example: www.example.com; foo=bar

Fixed

• Fixed a bug that caused a 222 response when creating or updating a Linode Configuration Profile with a VLAN "ipam_address" set to null or "". Now, "" is returned for the "ipam_address" in this case for vlan purpose interfaces, and null is always returned for both the "ipam_address" and "label" for public purpose interfaces.

• Firewall Create (POST /networking/firewalls)

  Firewall Rule Update (PUT /networking/firewalls/{firewallId}/rules)

  • This release includes documentation fixes regarding creating and updating Cloud Firewall rules with these commands. Previously, we stated that inbound and outbound rules required defined ports except for the ICMP and IPENCAP protocols. However, ports is optional for the TCP and UDP protocols and disallowed for the ICMP and IPENCAP protocols. Additionally, if ports is undefined, then all ports are affected by the Firewall rule.

  • These commands also now provide additional details for configuring Cloud Firewall rules, including instructions on how to apply rules to all IPv4 and IPv6 addresses.