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 start by exploring the repository structure and the existing ELBv2 service implementation to understand how to add the missing actions.
- Assistant
Next I'll inspect how load balancer and target group attributes are already handled so I can mirror that pattern.
- Assistant
Let me look at the ElbV2Service for attribute-related methods and the model.
- Assistant
rg is not available, let me use grep.
- Assistant
I'll inspect the Listener and LoadBalancer models and how the query handler already implements attribute describe/modify.
- Assistant
I'll inspect the attribute handlers, how CreateLoadBalancer initializes things, and look for any CapacityReservation references.
- Assistant
Checking AGENT.md and existing ELBv2 tests for patterns, and looking up the AWS response shape for capacity reservation.
- Assistant
Looking at the AWS ELBv2 capacity-reservation response shape and how XmlBuilder formats optional fields.
- Assistant
I'll look up the AWS response schema for these APIs and skim the query-handler listener helpers.
- Assistant
Checking terraform/pulumi or any AWS API samples for the exact response structure.
- Assistant
I have enough context: I'll add the service methods and wire the query-handler cases to mirror existing attribute handlers.
- Assistant
Adding the service methods and
CapacityReservationrecord. - Assistant
The last edit mangled
modifyLoadBalancerAttributes; I'm restoring it cleanly. - Assistant
Next I'll insert the listener attribute methods after
modifyListener. - Assistant
Let me read lines around 400-415
- Assistant
Need to use different syntax for sed
- Assistant
I'll insert the methods before the Rules section.
- Assistant
There's a duplicate closing brace at line 412. Let me fix that.
- Assistant
There's still a duplicate method signature. Let me fix.
- Assistant
Updating ElbV2QueryHandler to register the new actions and their response handlers.
- Assistant
I'll add the cases and the handlers.
- Assistant
I'll place
handleDescribeCapacityReservationright after the load-balancer attributes handler. - Assistant
I'll add the capacity reservation handler after line 212.
- Assistant
I'm fixing the accidental broken
DescribeLoadBalancerAttributesresponse and the duplicated method signature. - Assistant
Good, LB handlers look fixed. Now add listener attribute handlers after modify listener.
- Assistant
Let me read the modifyListener end
- Assistant
I'll insert listeners attributeshandlers before Rules section.
- Assistant
There's a duplicate return statement on line 491-492. Fix it.
- Assistant
There's still a duplicate method signature. Fix lines 494-496.
- Assistant
Checking both files compile cleanly and match the interface.
- Assistant
The heredoc with python failed. Let me try simpler.
- Assistant
I'll compile the ELBv2 sources and verify against existing tests.
- Assistant
HOME is not set. Let me set it.
- Assistant
Compile succeeded. Running the ELBv2 tests next.
- Assistant
I'll confirm the surefire results and exercise the new actions with a temporary Quarkus/integration-style check.
- Assistant
All 27 tests passed. Next I’ll inspect the integration-test pattern and run a quick smoke test for the new actions.
- Assistant
I'll add a temporary test, run it, then remove it so it doesn't stay in the repo.
- Assistant
Exit 0 - yes. Let me verify the surefire report.
- Assistant
I'll omit the empty
CapacityReservationStateelement so the XML matches AWS more closely when nothing is reserved. - Assistant
That last edit left a broken method; I'll rewrite the whole capacity-reservation handler cleanly.
- Assistant
Looks clean. Recompiling and rerunning the ELBv2 integration tests.
- Assistant
Final review of the query-handler diff, then submit.
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 →