Skip to content

feat: support dynamic EC2 placement and block device overrides#5178

Open
edersonbrilhante wants to merge 2 commits into
mainfrom
fix-missing-ec2-labels
Open

feat: support dynamic EC2 placement and block device overrides#5178
edersonbrilhante wants to merge 2 commits into
mainfrom
fix-missing-ec2-labels

Conversation

@edersonbrilhante

@edersonbrilhante edersonbrilhante commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Description

Add missing dynamic EC2 override labels for placement and block device mappings, and align parseEc2OverrideConfig conditional ordering with the AWS SDK request property order.

This adds parser support for:

  • ghr-ec2-placement-group-name
  • ghr-ec2-placement-group-id
  • ghr-ec2-placement-availability-zone-id
  • ghr-ec2-block-device-name

When dynamic EBS or block device labels create an override without an explicit device name, scale-up now loads the default launch template version and uses its block device name for the CreateFleet override. The scale-up Lambda policy now includes ec2:DescribeLaunchTemplateVersions for that lookup.

Test Plan

Related Issues

#5173

Add missing dynamic labels for EC2 placement and block device mappings, and align parseEc2OverrideConfig conditional order with the AWS SDK request property order.
@github-actions

github-actions Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

When dynamic EBS or block-device labels create an override without an explicit DeviceName, load the default launch template version by name and use its block device name for the CreateFleet override.
@edersonbrilhante edersonbrilhante force-pushed the fix-missing-ec2-labels branch from 75e774f to ef6ce1a Compare June 16, 2026 16:17
@edersonbrilhante edersonbrilhante changed the title feat: add dynamic EC2 override labels feat: support dynamic EC2 placement and block device overrides Jun 16, 2026
@edersonbrilhante edersonbrilhante marked this pull request as ready for review June 16, 2026 17:05
@edersonbrilhante edersonbrilhante requested a review from a team as a code owner June 16, 2026 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant