Skip to content

Release Branch 4.170.2 #907

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jan 12, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 32 additions & 2 deletions openapi.yaml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
openapi: 3.0.1
info:
version: 4.170.0
version: 4.170.2
title: Linode API
license:
name: Apache 2.0
Expand Down Expand Up @@ -8960,6 +8960,21 @@ paths:
will not be performed.
example: false
default: false
type:
type: string
enum:
- warm
- cold
description: |
Type of migration used in moving to a new host or Linode type.

`warm`: the Linode will not power down until the migration is complete.
Warm migrations are not available for DC migrations.

`cold`: the Linode will be powered down and migrated. When the migration
is complete, the Linode will be powered on.
example: warm
default: cold
responses:
'200':
description: Scheduled migration started
Expand Down Expand Up @@ -9451,6 +9466,21 @@ paths:
data must fit within the smaller disk size.
example: true
default: true
migration_type:
type: string
enum:
- warm
- cold
description: |
Type of migration used in moving to a new host or Linode type.

`warm`: the Linode will not power down until the migration is complete.
Warm migrations are not available for DC migrations.

`cold`: the Linode will be powered down and migrated. When the migration
is complete, the Linode will be powered on.
example: warm
default: cold
responses:
'200':
description: Resize started.
Expand Down Expand Up @@ -13779,7 +13809,7 @@ paths:
* A Firewall can be assigned during Linode creation by utilizing the `firewall_id` [Linode Create Request](/docs/api/linode-instances/#linode-create__request-body-schema) property.

* A service can have one active, assigned Firewall at a time.

Additional disabled Firewalls can be assigned to a service, but they cannot be enabled if another active Firewall is already assigned to the same service.

* Firewalls apply to all of a Linode's non-`vlan` purpose Configuration Profile Interfaces.
Expand Down