Jun 25, 2024 — Linode API
4 months ago by cverner@akamai.com
v4.177.1
Changed
Various updates to Placement Group-specific operation objects.
This may impact your environment
If you have an automation environment in place for Placement Groups via the API, you'll need to update it based on these changes.
Create placement group (POST /placement/groups)
The following values have changed for this operation:
affinity_type
has changed toplacement_group_type
. When setting up how compute instances are distributed in your placement group, useplacement_group_type
instead ofaffinity_type
.is_strict
has changed toplacement_group_policy
. This is also astring
operation now, rather than aboolean
. When defining how requests to add future compute instances should be handled, use theplacement_group_policy
object in place ofis_strict
.
See the Create placement group documentation for complete usage details.
Other operations
The response output for various operations has also been changed to use these same object values:
- List placement groups (GET /placement/groups)
- Get a placement group (GET /placement/groups/{groupId})
- Update a placement group (PUT /placement/groups/{groupId})
- Assign a placement group (POST /placement/groups/{groupId}/assign
- Unassign a placement group (POST /placement/groups/{groupId}/unassign)