Ability to separate configuration from runtime parameters
- Dominant language
- Scala
- Stars
- 6.8k
- Forks
- 1.2k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 2
Description
I have added a number of configuration parameters to my actions and packages using `-p` for things like API keys that my actions need.
These end up in the the first argument to the action (`function main(params) {}`).
The problem I have is that I've created a sequence consisting of `whisk.system/cloudant/read` and then my action. The document that I'm reading happens to have an element that's the same name as one of my settings and my setting is overridden by the data in the Cloudant document.
It would be much more helpful if I could put the configuration setup that my actions require into a different dictionary that's a second parameter to the action function so that it looked something like this: `function main(params, config) {}`.
(I thought that there was an issue for this already open, but I couldn't see it)
Contributor guide
Research direction
No files or tests are named in the issue. Start by tracing how OpenWhisk invokes actions and how sequence results are merged into action parameters; the change is complete when configuration remains separate from runtime data and is available through the proposed second action argument.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100