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

Initial SNS topic / subscription support #1974

Merged
merged 4 commits into from
May 26, 2015
Merged

Conversation

johnewart
Copy link
Contributor

Initial SNS topic and subscription support

@radeksimko
Copy link
Member

Thanks, did you have any chance to look at #1952 ?
Is there any particular reason why not review & test & merge that one?

@catsby
Copy link
Contributor

catsby commented May 15, 2015

Yet another coincidence .. John tells me he's working on something, and a separate PR lands for that thing days/hours before John sends his 😄

Sorry for the trouble @johnewart – one way or the other we'll get SNS and SQS in :P

@johnewart
Copy link
Contributor Author

@radeksimko Mine uses the ARN as the ID, which is arguably better since it's guaranteed to be unique, and also supports subscriptions.

@johnewart
Copy link
Contributor Author

@catsby I think I'm somehow controlling the universe with my mind; maybe I'm secretly Professor X and I just don't know it yet...

@ctiwald
Copy link
Contributor

ctiwald commented May 16, 2015

Errr, @johnewart -- what? Mine uses ARN as the ID: https://github.com/hashicorp/terraform/pull/1952/files#diff-d2b599683afe94c602d86b9526c9b552R52. Check line 52 of the resource. It wouldn't make a whit of sense to use anything else.

Regardless go ahead and use this. It provides support for subscriptions and various other SNS topic properties.

@ctiwald
Copy link
Contributor

ctiwald commented May 16, 2015

Also are you adding support to AS groups for SNS notifications? I've got that tentatively in flight but have no real interest in mucking with it if someone's already on it.

@johnewart
Copy link
Contributor Author

@ctiwald Sorry, I misread it when I was looking over your PR briefly; I (incorrectly) interpreted that the "seeker" as a way to fetch the ARN for a topic name. I hadn't gotten to ASG integration but it should be pretty easy to add for both SNS and SQS now that there's the SQS resource that has been merged.

@ctiwald
Copy link
Contributor

ctiwald commented May 17, 2015

No worries at all. I feel foolish not seeing that "GetTopicAttributes" API endpoint.

Would love to see the ASG stuff added. I'm happy to contribute it but probably won't get around to it until late this week. If you all are devoting resources to it, that's cool too.

@catsby
Copy link
Contributor

catsby commented May 20, 2015

Thanks @johnewart – is this good to go from your end, then? The code looks great 👍

Can you please rebase and make sure to run make updatedeps? There's been a change upstream with errors:

@johnewart
Copy link
Contributor Author

Updated with the new AWS SDK error changes, plus added .arn support to SQS and SNS bits, updated docs and tests as well.


d.SetId(*output.TopicARN)

// Write the ARN to the 'arn' field for export
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AFAIK id is being exported by default, therefore this seems to be a bit superfluous, or am I wrong?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which part? Exporting ARN?

@catsby
Copy link
Contributor

catsby commented May 26, 2015

LGTM, thanks everyone!

catsby added a commit that referenced this pull request May 26, 2015
Initial SNS topic / subscription support
@catsby catsby merged commit 8764205 into hashicorp:master May 26, 2015
@ghost
Copy link

ghost commented May 2, 2020

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 ghost locked and limited conversation to collaborators May 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants