Allow the definition of custom parameters with "needs".
Open
Nobody has claimed this yet.
ready
- Dominant language
- Perl
- Stars
- 737
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Description
Currently needs uses Rex::Args to get the command line parameters to call the task. It would be good to have a possibility to define custom parameters for the task.
Somethink like:
needs MyModule "setup", {
param1 => "value1",
param2 => "value",
}
Contributor guide
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 existing needs implementation and Rex::Args, which the issue identifies as the current source of command-line parameters. Trace how task parameters are passed, then verify that the proposed custom parameter form reaches the task with the supplied values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100