-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
resource/aws_sns_topic: Fix exit after updating first attribute #3360
Conversation
_, terraformAttrValue := d.GetChange(terraformAttrName) | ||
err := updateAwsSnsTopicAttribute(d.Id(), snsAttrName, terraformAttrValue, conn) | ||
if err != nil { | ||
return err |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, this looks so much cleaner! 👍 🚿
"sqs_failure_feedback_role_arn": "SQSFailureFeedbackRoleArn", | ||
"sqs_success_feedback_role_arn": "SQSSuccessFeedbackRoleArn", | ||
"sqs_success_feedback_sample_rate": "SQSSuccessFeedbackSampleRate", | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I kind of wish this map wasn't here at all, but there's only so much refactoring that can be done in a single PR... 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, do you mind attaching a test with the config from #3354 ? Then it's 👌
No problem, certainly a valid ask! |
…lper and verify TestAccAWSSNSTopic_deliveryStatus fix
@radeksimko I've now made it so Previously (note 11 errors with 12 attributes submitted, I also need to submit a PR to go-multierror to make it sortable 😉 ):
Now:
|
This has been released in version 1.10.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Closes #3354
😬 This bug was very subtle as nothing was calling
d.Set(attribute, "")
on attributes not existing in AWS. This bug has been in the codebase since v1.0.0 of the provider. Also did some other random cleanup here.