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 explore the ELBv2 service structure and existing attribute handlers so we can mirror them for listener attributes and capacity reservation.
- Assistant
Let me look at the existing attribute handlers in ElbV2Service and ElbV2QueryHandler to understand the patterns.
- Assistant
rg is not available, I'll use grep instead.
- Assistant
Let me read the ElbV2Service.java file around the attribute methods and the model classes.
- Assistant
I'll inspect the service attribute methods and the Listener/LoadBalancer models next.
- Assistant
I'll inspect listener helpers in the service and the attribute handlers in the query handler so we can mirror them.
- Assistant
I'll check for related stubs/tests and AWS response shape references in the repo.
- Assistant
I'll inspect listener-certificate handlers and related response XML patterns, then search docs/tests for CapacityReservation shape.
- Assistant
Checking persistence of ELB state and docs for attribute-related API coverage.
- Assistant
I'll look at ElbV2 tests and the load of the query handler switch so I can add the new actions consistently.
- Assistant
I'll check XmlBuilder's null handling, then implement the service methods and query-handler wiring.
- Assistant
Implementing service methods and wiring the query handler to the new actions.
- Assistant
I'll insert the new methods before the Helpers section.
- Assistant
Updating the query handler next: add the switch cases and the attribute/capacity handlers.
- Assistant
I'll update the switch cases and add the handler methods.
- Assistant
Locating handleModifyListener so I can insert the new attribute handlers right after it.
- Assistant
I'll insert listener attribute handlers after handleModifyListener, and capacity reservation after describe listener certificates.
- Assistant
I'll insert the attribute handlers and capacity reservation handler.
- Assistant
There's a duplicate return statement — fixing that next.
- Assistant
There's a broken method signature line — I'll fix lines 468-470.
- Assistant
Removing the remaining duplicate lines.
- Assistant
Still a duplicate
XmlBuilderline — cleaning that up. - Assistant
The edit tool keeps leaving remnants — I'll replace the entire method block cleanly.
- Assistant
Listener attribute handlers look good. Adding the capacity reservation handler next.
- Assistant
Let me read lines 774-795 and insert capacity handler.
- Assistant
I'll insert the capacity reservation handler.
- Assistant
There's another duplicate return on lines 790-791 — fixing that.
- Assistant
I'll rewrite the whole section carefully with a Python script to avoid partial-edit leftovers.
- Assistant
python3 isn't available — trying python, or I'll patch with sed.
- Assistant
I'll use perl to fix the file.
- Assistant
Verifying the handlers and updating the docs.
- Assistant
sed uses commas not colons for ranges.
- Assistant
Docs next, then I'll verify parseAttributes and compile.
- Assistant
Updating the ELB docs for the new actions.
- Assistant
Add a behavior note about capacity reservation and listener attributes.
- Assistant
Compiling and running the ElbV2 tests to verify the changes.
- Assistant
Compile succeeded. Running the ElbV2 tests next.
- Assistant
Checking surefire reports for a clear pass/fail result.
- Assistant
The grep didn't find tests= in txt - maybe different format.
- Assistant
Confirming parseAttributes never returns null, then doing a quick manual smoke of the new actions.
- Assistant
Let me find the definition of parseAttributes.
- Assistant
Starting the app briefly and curling the new actions to reproduce the original bug and confirm the fix.
- Assistant
I'll run a temporary curl-based smoke check against the test server without adding permanent tests.
- Assistant
The failure looks like action routing — checking how the integration tests invoke ELBv2.
- Assistant
The routing needs the Authorization header with the elasticloadbalancing service — re-running the smoke test with that.
- Assistant
Smoke tests passed. Checking git status and the final diff.
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 →