API v4.0.23

Added

Changed

  • Changed validation criteria when updating (PUT /linode/instances/{linodeId}/configs/{configId}) the devices property for a Linode’s configuration profile.

    • An empty devices object or a devices object with empty values for device slots is allowed on PUT only if an empty device map already exits. An error will result if a non-empty device map exists for the Linode’s configuration profile.
    • If no devices are specified, booting from this configuration will hold waiting for a device to exist before being able to boot.
    • Previous validation produced an error in all cases when an empty device object or a devices object with empty values for device slots was passed on PUT.
  • Changed validation criteria and behavior when creating (POST /linode/instances/{linodeId}/configs) and updating (PUT /linode/instances/{linodeId}/configs/{configId})the root_device property for a Linode’s configuration profile.

    • If no value or an invalid value is provided, root_device will default to /dev/sda.
    • Previous validation for PUT would result in an error when no value was provided for root_device and an empty device map existed for the Linode’s configuration profile.
    • If the device specified at the root device location is not mounted, the Linode will not boot until a device is mounted.

Fixed

  • page query string parameter no longer errors on large page number values. If the value of page exceeds 2^64/page_size, the last possible page will be returned.
  • swap_size property no longer enforces a max limit when creating a Linode (POST /linode/instances).
  • account:read_only scope is now enforced when listing Account notifications (GET /account/notifications).
  • Fix pagination metadata when listing Volumes (GET /volumes) for accounts that have 100+ Volumes.