ISSUE DESCRIPTION [BUG] ELBv2 DescribeListenerAttributes and DescribeCapacityReservation…
- User
ISSUE DESCRIPTION
[BUG] ELBv2 DescribeListenerAttributes and DescribeCapacityReservation return UnsupportedOperation (breaks @pulumi/aws refresh)
Service
ELBv2 (Elastic Load Balancing v2)
AWS API Action
DescribeListenerAttributesandDescribeCapacityReservationExpected behavior
DescribeListenerAttributesreturns the listener's attribute list (empty by default until attributes are set).DescribeCapacityReservationreturns the load balancer's capacity reservation status (empty/none when no capacity is reserved).
Both are normal management-plane reads that the AWS SDKs issue during resource refresh.
Actual behavior
Both actions return:
api error UnsupportedOperation: Action DescribeListenerAttributes is not supported. api error UnsupportedOperation: Action DescribeCapacityReservation is not supported.@pulumi/aws6.66.0+ (and recent Terraform AWS provider versions) call these two actions when refreshing existingLoadBalancer/Listenerresources. Because Floci returnsUnsupportedOperation, the provider errors out on refresh. The only workaround today is pinning@pulumi/awsto a version that predates these calls (e.g.6.30.0).ELBv2 is otherwise well supported in Floci — only these two read actions are missing from
ElbV2QueryHandler's action switch.Reproduction
# Assuming a load balancer + listener already exist (CreateLoadBalancer / CreateListener): aws --endpoint-url http://localhost:4566 elbv2 describe-listener-attributes \ --listener-arn arn:aws:elasticloadbalancing:us-east-1:000000000000:listener/app/my-lb/abc/def # -> UnsupportedOperation: Action DescribeListenerAttributes is not supported. aws --endpoint-url http://localhost:4566 elbv2 describe-capacity-reservation \ --load-balancer-arn arn:aws:elasticloadbalancing:us-east-1:000000000000:loadbalancer/app/my-lb/abc # -> UnsupportedOperation: Action DescribeCapacityReservation is not supported.Environment
- Floci version / image tag:
1.5.18(floci/floci:latest); also present on currentmain - AWS provider that triggers it:
@pulumi/aws6.66.0+ (works when pinned to 6.30.0) - How you're running Floci: Docker / Docker Compose
A PR implementing
DescribeListenerAttributes,ModifyListenerAttributes, andDescribeCapacityReservation(mirroring the existing load balancer / target group attribute handlers) will reference this issue.Interface
Type: Function Name: describeListenerAttributes Path: src/main/java/io/github/hectorvent/floci/services/elbv2/ElbV2Service.java Input: region: String, arn: String Output: Map<String, String> Description: Returns a copy of the attributes map for the listener identified by the given ARN.
Type: Function Name: modifyListenerAttributes Path: src/main/java/io/github/hectorvent/floci/services/elbv2/ElbV2Service.java Input: region: String, arn: String, newAttrs: Map<String, String> Output: void Description: Merges the provided key-value pairs into the listener's existing attributes.
Type: Record Name: CapacityReservation Path: src/main/java/io/github/hectorvent/floci/services/elbv2/ElbV2Service.java Public API: CapacityReservation(Integer decreaseRequestsRemaining, Integer minimumCapacityUnits, Instant lastModifiedTime) Description: Stable representation of load-balancer capacity-reservation state. Floci returns null fields when no capacity is reserved.
Type: Function Name: describeCapacityReservation Path: src/main/java/io/github/hectorvent/floci/services/elbv2/ElbV2Service.java Input: region: String, arn: String Output: CapacityReservation Description: Validates the load balancer and returns its capacity-reservation state.
ADDITIONAL ADVICE
Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use
git checkout <file>to restore the file to its original state. You can also reset all changes in the repository usinggit reset --hardcommand. Additionally, you can usegit stashandgit stash popto temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you callsubmit) usinggit statusorgit diffcommands. However you don't need to usegit addorgit commitbefore submitting your changes. In fact,submitonly submits currently unstaged changes because it usesgit diffto get the changes that need to be submitted.CHECKLIST
Before submitting your solution, please go over the following checklist and make sure you've done everything:
- If an error was reported in the issue description, I have successfully reproduced it.
- If an error was reported in the issue description, I have confirmed that my fix resolves the error.
- I have thought about edge cases and made sure my fix handles them as well.
- I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.
Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!
(Current directory: /floci, current file: none) bash-$
- Assistant
I’ll inspect the ELBv2 service, query handler, models, and tests to understand the existing attribute-handler patterns and response serialization before implementing the missing actions.
- Assistant
The action router currently only exposes load-balancer attributes, and the central AWS Query controller also has an ELB action allowlist that may need extension. I’ll read those implementations and model lifecycles to preserve validation/error behavior and XML conventions.
- Assistant
I need the complete listener section and the listener model to decide where attributes belong. I’ll also inspect AWS XML naming for nearby newer APIs and the project’s Java version, since the requested public API specifically calls for a nested
recordusingInstant. - Assistant
The listener model already has an initialized attributes map, so the service methods can directly mirror load-balancer attributes and naturally return empty attributes for new listeners. Capacity reservation has no mutating API/state in scope; per the requested record contract, it should validate the load balancer and return a record with all-null fields. I’ll inspect listener handlers and timestamp/null XML style, then patch all three routing layers.
- Assistant
Before editing, I’ll confirm the exact wire shape from any locally cached AWS SDK service model. This avoids producing XML that routes successfully but cannot be unmarshalled by Pulumi/Terraform’s AWS SDK.
- Assistant
I’ll implement:
- Public service APIs with defensive-copy/merge semantics and existing not-found validation.
- A public nested
CapacityReservationrecord and a validated empty reservation result. - Query handlers with AWS-compatible attribute lists and an empty capacity result when fields are null.
- Both action-switch and controller allowlist entries so requests reach the handlers.
- Assistant
Python is unavailable in this image, so no files were changed. I’ll use the repository’s provided
edit/replacecommands instead, applying the same targeted changes. - Assistant
Two service insertions and the listener switch insertion did not apply because the editor requires exact whitespace; the successful changes are intact. I’ll apply the missed changes against exact snippets, then add handler bodies.
- Assistant
The switch entries are present (the editor’s later retry correctly reported no remaining old snippet). I’ll now use line-based insertion for the service methods and handler methods, which is more reliable here, and then compile to catch any API/type mistakes.
- Assistant
The service API is now complete. I’ll insert the capacity handler immediately before security-group handling and the listener attribute handlers before rule handling, using exact method/comment anchors.
- Assistant
Listener handlers are in place. The capacity anchor still failed despite being found, so I’ll insert it by line number. Maven also requires
HOMEin this shell; I’ll set it explicitly for compilation. - Assistant
Compilation passes. Next I’ll run the existing ELBv2 integration suite to ensure the additions did not regress resource creation, listener behavior, or routing. After that, I’ll launch the app temporarily and reproduce both reported API calls end-to-end, including modify/describe listener attribute persistence and not-found validation.
- Assistant
The existing ELBv2 integration suite passes. I’ll now run Floci on a temporary port and issue Query API POSTs directly. This verifies central controller classification, action dispatch, XML serialization, default-empty behavior, and listener attribute merge/copy behavior in the same path used by AWS SDKs.
- Assistant
The end-to-end reproduction now succeeds: default listener attributes deserialize from an empty list, modifications persist, and capacity reservation returns a valid empty result rather than
UnsupportedOperation. I’ll review the final diff for accidental/generated changes, confirm formatting, and inspect test reports before submitting.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →