-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Cannot create R53 entries anymore #1550
Comments
Is this in anyway related to the latest release? This exact code was working perfectly last week / yesterday |
Thanks for reaching out to us I'll take a look at this. Would you be able to enable logging with you can do this with awsConfig := aws.Config{
Region: aws.String("us-west-2"),
Credentials: creds,
LogLevel: aws.LogLevel(aws.LogDebugWithHTTPBody),
} |
|
Thanks for the update @andrewmeissner i've been able to reproduce this on my end, and and working to correct the bug. |
@jasdel thanks so much! |
I've created #1551 reverting the new marshalers in the short term until this bug can be fixed. I'll create a new version and recall v1.11.0 once the PR is merged in. |
Thanks so much! Hope this bug isn't too problematic in bringing back the marshalers! |
* Revert "API Marshaler: Add generated marshalers for RESTJSON protocol (#1547)" This reverts commit 1a10a10. Reverts RESTJSON marshaler improvement due to bug in RESTXML * Revert "API Marshaling: Add generated marshalers for RESTXML protocol (#1409)" This reverts commit 37448a9. Reverts RESTXML due to #1550
In a future release we'll that add back in the code generated API marshallers after more verification is done to make sure there are no additional edge cases the new marshallers are missing. |
I have a fix locally that correct the Route 53 issue. It turns out this specific condition was not included in the SDKs protocol tests that I used to verify the changes. Causing the bug to get released. Before releasing the marshallers again I think a utility is needed verify they marshaled output/request matches the current SDKs output. Protocol tests should also be updated. |
Thanks again @andrewmeissner for posting this issue. Since the RESTXML change as been reverted and Route 53 request are working correction I'm going to close this issue as fixed. I have PR #1554 that will reenable the generated marshalers that can be accepted once more verification is completed. |
@jasdel Thanks so much for getting me up and running again! |
Please fill out the sections below to help us address your issue.
Version of AWS SDK for Go?
1.11.0
Version of Go (
go version
)?go1.9 darwin/amd64
What issue did you see?
When trying to upsert a route53, I get the following error:
MalformedInput: ChangeBatch is not valid, expected ChangeResourceRecordSetsRequest
This error seems to have just started happenining within the past few hours.
Steps to reproduce
update the aws-sdk, and run the same code to generate a route53 entry
If you have have an runnable example, please include it.
The text was updated successfully, but these errors were encountered: