bumpy-summer-9075
04/09/2021, 2:07 PMarn:aws:sns:us-east-1:1234:foo
will send a HTTP call to example.com/myservice/foo-sns-handler
Now, I need Pulumi to subscribe to that topic once that service is deployed, something like
new aws.sns.TopicSubscription(
'my-topic',
{
topic: 'arn:aws:sns:us-east-1:1234:foo',
endpoint: `${myServiceEndpoint}/foo-sns-handler`,
protocol: 'https',
},
I would like to avoid having to define the SNS topic in my service and in Pulumi, ideally there would be a single place where the "topic -> handler" relation is defined.
Does that make sense? Any ideas?
--
In other words, I'm looking for a way to have a service declare the resources it needs, and have pulumi handle those resources during deployment (doesn't have to be an SNS topic, could be S3 buckets or any other pulumi resources)millions-furniture-75402
04/09/2021, 2:34 PMbumpy-summer-9075
04/09/2021, 2:42 PMmillions-furniture-75402
04/09/2021, 2:45 PM