Magic variables in yaml files
Open
Nobody has claimed this yet.
complexity:easy
feature
proposal
status:under discussion
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
There are already some environment variables available to the actions.
Most probably there will be more and more useful of these during time.
The proposal is to make those variables available in yaml files too, bringing more flexibility.
---
name: example_action
runner_type: local-shell-cmd
entry_point: ""
enabled: true
parameters:
cwd:
default: "/opt/stackstorm/virtualenvs/{{ ST2_ACTION_PACK_NAME }}/bin"
immutable: true
cmd:
...
Btw, this approach is pretty obvious thing in Ansible, which operates with yaml files too.
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 with the action environment-variable documentation in actions.html and the YAML action definition shown in the issue. Trace how those definitions are loaded and rendered, then verify that the documented action variables are available in YAML values and that existing action behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100