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 to placement_group_type. When setting up how compute instances are distributed in your placement group, use placement_group_type instead of affinity_type.
• is_strict has changed to placement_group_policy. This is also a string operation now, rather than a boolean. When defining how requests to add future compute instances should be handled, use the placement_group_policy object in place of is_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)