Regional steps output variables availability
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 19
- Avg merge
- 11m
- Merged PRs (30d)
- 2
Description
We have a scenario where we need to access regional step's output named 'foo' in the following step which runs only in primary region. It would be handy if we can get hold of collection of 'foo' output variable generated from each regional step or output prefixed with region name and passed on to following step.
Ex:- stepname_foo = ['bar','bar2']
Ex:- stepname_regionname_foo = "bar"
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
No files, tests, or entry points are named. Start by locating how regional steps produce outputs and how outputs are passed to subsequent steps; determine whether the project can expose collected values or region-prefixed values to a primary-region step. Done means the chosen output form works for the shown multi-region scenario and is covered by relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100