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

SNS HTTP subscription doesn't work with password containing the character "!" #10680

Open
ghost opened this issue Oct 30, 2019 · 2 comments
Open
Labels
service/sns Issues and PRs that pertain to the sns service. waiting-response Maintainers are waiting on response from community or contributor.

Comments

@ghost
Copy link

ghost commented Oct 30, 2019

This issue was originally opened by @fabbrimichele as hashicorp/terraform#23232. It was migrated here as a result of the provider split. The original body of the issue is below.


Terraform Version

Terraform v0.12.12

Terraform Configuration Files

resource "aws_sns_topic_subscription" "batch_optimisation_http" {
  topic_arn = aws_sns_topic.topic1.arn
  endpoint = "https://user1:password1@service.domain.de/endpoint"
  protocol = "https"
  endpoint_auto_confirms = true
}

Debug Output

Crash Output

Expected Behavior

Terraform should find the subscription and complete the deploy.

Actual Behavior

Terraform can't find the subscription because of the "!" in the password and the deploy process fails.

Steps to Reproduce

  1. terraform init
  2. terraform apply

Additional Context

It seems the code that retrieves the subscriptions created for SNS is not working properly when the password contains an exclamation mark. Probably the regular expression used for finding subscriptions with user and password is not correct.

References

@ghost ghost added the service/sns Issues and PRs that pertain to the sns service. label Oct 30, 2019
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Oct 30, 2019
@github-actions
Copy link

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Oct 19, 2021
@github-actions github-actions bot removed the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Oct 26, 2021
@justinretzolk
Copy link
Member

Hey @fabbrimichele 👋 Thank you for taking the time to file this issue! Given that there's been a number of AWS provider releases since you initially filed it, can you confirm whether you're still experiencing this behavior?

@justinretzolk justinretzolk added waiting-response Maintainers are waiting on response from community or contributor. and removed needs-triage Waiting for first response or review from a maintainer. labels Dec 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service/sns Issues and PRs that pertain to the sns service. waiting-response Maintainers are waiting on response from community or contributor.
Projects
None yet
Development

No branches or pull requests

1 participant