Unable to get right primary_region runiac variable value in steps
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 19
- Avg merge
- 11m
- Merged PRs (30d)
- 2
Description
Currently, runiac_primary_region variable is populated as empty string when trying to access in steps.
EnvVars: [TF_VAR_runiac_region_group, TF_VAR_runiac_app_version, TF_VAR_runiac_target_account_id, TF_VAR_runiac_project, TF_VAR_runiac_track, TF_VAR_runiac_region_deploy_type, TF_VAR_runiac_deployment_ring, TF_VAR_runiac_primary_region, TF_VAR_runiac_namespace, TF_VAR_runiac_step, TF_VAR_runiac_environment]
runiac version
runiac 0.0.10. Commit 09105498d06af7635168ffea7c61d4313918975f. Built on 2021-10-18T23:50:56Z.
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 reproducing the issue with runiac 0.0.10 and the listed TF_VAR environment variables, especially TF_VAR_runiac_primary_region. Trace how that variable is exposed to steps; the work is done when primary_region has its expected value instead of an empty string.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, terraform
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100