You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My apologies this slipped through the net here and has taken so long to get back to you. In a situation like this, we usually take care of a state migration so that the user still gets the same behaviour
In this case, the changes themselves were not breaking changes - as you said, they changed the state only and not the subscription
We will endeavour to make sure that users do not see this type of behaviour in the future. This will only have affected those people who upgraded to 0.6.16 onwards
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 10, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I recently upgraded to version
0.6.16
. Now I get changes for my sns subscriptions which look as follows:The protocol I'm subscribing to is
sqs
. From what I understand (reading the documentation: http://docs.aws.amazon.com/sns/latest/dg/SendMessageToHttp.html#SendMessageToHttp.prepare) auto confirm makes only sense for http/https endpoints. Applying the changes affects the terraform state but not the actual subscription. I recon the change was introduced by #4711Please find my actual configuration and other infos below.
Terraform Version
Terraform v0.6.16
Affected Resource(s)
aws_sns_topic_subscription
Terraform Configuration Files
The text was updated successfully, but these errors were encountered: