Use zowe.yaml as the source for the configuration
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 92
- Forks
- 81
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 46
Description
Is your feature request related to a problem? Please describe.
Users should have a more standardized way to configure all the components and should not rely on additional environment variables.
The variables used across the API Mediation Layer should be derived from the zowe.yaml instead of depending on environment variables or on provision of the variables through start.sh
Describe the solution you'd like
- Standardizing what goes into start.sh and what is kept out and updating start.sh accordingly
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 reviewing the existing start.sh flow and the zowe.yaml configuration, then inventory which API Mediation Layer variables currently come from environment variables or startup arguments. Done means the configuration sources are standardized and start.sh is updated accordingly across the affected components, with validation that components can use zowe.yaml without the additional variables.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, shell, yaml
- Domain
- backend, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100