This message was deleted.

sparse-intern-71089

10/30/2020, 1:05 AM

This message was deleted.

little-cartoon-10569

10/30/2020, 1:06 AM

You shouldn't need to use getQueue if you already have a queue resource. getQueue is for loading an existing queue into state.

little-cartoon-10569

10/30/2020, 1:07 AM

Hopefully all constructors of other resources that can take a queue ARN or id as a parameter, will be looking for an

Input<string>

, which you can get from the resource you've just created.

wet-hair-90323

10/30/2020, 1:11 AM

im just trying to get the URL specifically, since i need to pass it as an env var to my service.

aws.sqs.Queue

resource doesnt expose the

url

, but

getQueue

does. As a workaround i can pass the name of the queue to my service and then get its url in the service itself. Just seeing if there's a way to get it through pulumi 🙂

little-cartoon-10569

10/30/2020, 1:18 AM

You could make the name of queue an output of your stack, and then you could set your env var using aws cli?

aws sqs get-queue-url --queue-name $(pulumi stack output queueName)

or similar, should do it...

little-cartoon-10569

10/30/2020, 1:18 AM

Or if you're using the automation API, you could do it all from code.

wet-hair-90323

10/30/2020, 1:21 AM

thank you, i'll try that

3 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.