Send collections credential information in run options
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
Sister story to https://github.com/OpenFn/kit/issues/814
The simplest version of this is that Lightning take a collections_version as an env var and calculates its own collections_endpoint (pointing to itself), and appends those to every plan.
It's OK to send those options for runs that don't use collections. The worker will only load the collections adaptor if it needs to.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked OpenFn/kit issue and tracing where Lightning builds plans and their run options. Identify the entry point that can add collections_version and collections_endpoint to every plan. Done means both options are present for all plans, while workers still load the collections adaptor only when needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100