Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Route53 GetHostedZoneLimit #1314

Closed
ianbotsf opened this issue May 17, 2024 Discussed in #1312 · 3 comments · Fixed by #1319
Closed

Route53 GetHostedZoneLimit #1314

ianbotsf opened this issue May 17, 2024 Discussed in #1312 · 3 comments · Fixed by #1319
Assignees
Labels
bug This issue is a bug.

Comments

@ianbotsf
Copy link
Contributor

ianbotsf commented May 17, 2024

Discussed in #1312

Originally posted by Fruan-Atlassian May 16, 2024
Just wondering whether the Route53 GetHostedZoneLimit request is working for anyone? For me, I can't use getHostedZoneLimitRequest's type parameter as I get an error saying that it's not of enum MAX_RRSETS_BY_ZONE when I use HostedZoneLimitType.MaxRrsetsByZone.
Is anyone able to do this on their end?

Repro code

Route53Client.fromEnvironment().use { r53 ->
    r53.getHostedZoneLimit {
        hostedZoneId = "<my_zone_id>"
        type = HostedZoneLimitType.MaxRrsetsByZone
    }
}

Result

InvalidInput(message=1 validation error detected: Value 'MaxRrsetsByZone' at 'type' failed to satisfy constraint: Member must satisfy enum value set: [MAX_RRSETS_BY_ZONE, MAX_VPCS_ASSOCIATED_BY_ZONE])
@ianbotsf ianbotsf added the bug This issue is a bug. label May 17, 2024
@ianbotsf ianbotsf self-assigned this May 17, 2024
@ianbotsf
Copy link
Contributor Author

Invocations of this API seem to be serializing the request parameter into the URI path incorrectly. As noted by the GetHostedZoneLimit documentation and above error message, the expected serialization is MAX_RRSETS_BY_ZONE but instead it's using the name of the enum element MaxRrsetsByZone. Sample request preamble:

GET /2013-04-01/hostedzonelimit/<my_zone_id>/MaxRrsetsByZone

Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

@ianbotsf
Copy link
Contributor Author

The fix for this has been merged and should be part of today's SDK release v1.2.22.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant