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

Could we have ability to export given sqs queue? #268

Open
Setitch opened this issue Sep 22, 2022 · 3 comments
Open

Could we have ability to export given sqs queue? #268

Setitch opened this issue Sep 22, 2022 · 3 comments
Labels
enhancement New feature or request

Comments

@Setitch
Copy link

Setitch commented Sep 22, 2022

Start from the Use-case

I have an issue when in one service i defined queue, but in service derived from it, i need access to one of the queues defined earlier.
Would it be possible to add exporting options to the queue(arn mostly) so it would be used in other services?

The structure

service: name1
// here we include lift and make queues
service: name2
// here i would be able to import the queue and be able to use its address in lambdas defined in this file

Example Config

No response

Implementation Idea

queueName:
   type: queue
   worker:
     timeout: 20
     handler: /file.handler
     role: SomeRole
   export:
     name: QueueExportedName

and then in other file, i would like to use Fn::ImportValue (or something) to access exported queue

@Setitch Setitch added the enhancement New feature or request label Sep 22, 2022
@mnapoli
Copy link
Member

mnapoli commented Sep 22, 2022

You can create a CloudFormation export in the resources section, as usual. I'm not sure it would make sense to reimplement that feature in Lift specifically, I'm not sure it would bring anything more and would only add more options to do the same thing.

@Setitch
Copy link
Author

Setitch commented Sep 22, 2022

Can you please share example for that queueName how to export it outside of the lift?

@Setitch
Copy link
Author

Setitch commented Sep 22, 2022

But as for why... I think it would be much better looking, if configuration for lift (and its exports) would be done in the same place not in other

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants