feat: add AWS EC2 Elastic IP management components#5337
Open
felixgateru wants to merge 6 commits into
Open
Conversation
|
👋 Commands for maintainers:
|
4530ba7 to
1bc5371
Compare
1bc5371 to
c29ea4a
Compare
Signed-off-by: Felix Gateru <felix.gateru@gmail.com>
Signed-off-by: Felix Gateru <felix.gateru@gmail.com>
Signed-off-by: Felix Gateru <felix.gateru@gmail.com>
Signed-off-by: Felix Gateru <felix.gateru@gmail.com>
Signed-off-by: Felix Gateru <felix.gateru@gmail.com>
Signed-off-by: Felix Gateru <felix.gateru@gmail.com>
3a18285 to
8bff1d3
Compare
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 8bff1d3. Configure here.
| Type: resourceType, | ||
| Name: elasticIPResourceName(address), | ||
| ID: address.AllocationID, | ||
| }) |
Contributor
There was a problem hiding this comment.
Classic EIPs appear in pickers
Medium Severity
Elastic IP resource listers return every DescribeAddresses entry without checking domain. Components allocate and document VPC-only (domain: vpc) behavior, so pickers can surface legacy standard addresses that fail or behave unexpectedly on associate and release against VPC instances.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 8bff1d3. Configure here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


What changed
Added AWS EC2 Elastic IP management components:
Why
To support allocating, associating, disassociating, and releasing Elastic IP addresses directly from SuperPlane workflows, covering common static-IP, failover, and cleanup use cases without leaving the canvas.
How
Backend
ec2.elasticIp — pick allocated Elastic IPs (Release, Associate)
ec2.elasticIpAssociation — pick active associations (Disassociate)
ec2.publicIpv4Pool, ec2.customerOwnedIpv4Pool, ec2.ipamPool — pool pickers for Allocate
Frontend
Added mapper components and tests for allocate, release, and associate Elastic IP.
Wired Elastic IP and association pickers, plus IP source and pool metadata on the canvas.
Added execution details focused on user-friendly fields (Public IP, Operation, Region) rather than raw AWS IDs.
Registered components and associate/disassociate state badges in the AWS mapper index.
Demo