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

Queue Url inside the Job #734

Open
3 tasks done
djolereject opened this issue Oct 19, 2024 · 0 comments
Open
3 tasks done

Queue Url inside the Job #734

djolereject opened this issue Oct 19, 2024 · 0 comments
Labels

Comments

@djolereject
Copy link

Checklist

  • Upgrade Jets: Are you using the latest version of Jets? This allows Jets to fix issues fast.
  • Reproducibility: Are you reporting a bug others will be able to reproduce and not asking a question. If you're unsure or want to ask a question, do so on https://community.boltops.com
  • Code sample: Have you put together a code sample to reproduce the issue and make it available? Code samples help speed up fixes dramatically. If it's an easily reproducible issue, then code samples are not needed. If you're unsure, please include a code sample.

My Environment

Software Version
Operating System MacOS 14.6
Jets 6.0.3
Ruby 3.2.1

Expected Behaviour

When I try to run a Job from another Job (or the same one) I should be able to run it with perform_later and start another function. Basically the same behavior like we have from controller.

Current Behavior

The function crashes.

Step-by-step reproduction instructions

This is the error I'm getting:

WARN: JETS_QUEUE_URL_LINKEDIN not set. Unable to get queue url.

When I got a little bit into it, I noticed that in controller Lambda function we have ENV for all the functions:

JETS_QUEUE_URL_DEFAULT=...
besides DEFAULT, we have all the URLs from config.job.additional_queues, e.g. JETS_QUEUE_URL_ANY_NAME. This URLs are not present in the functions created from Jobs.

Code Sample

Solution Suggestion

It would be great to have those ENV values everywhere or at least to have somewhere in docs an explanation of how we could add them on our own in a project. Calling a Job from another Job is not that exotic request and it simplifies some processes.

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

No branches or pull requests

1 participant