opendevstack / opendevstack/ods-provisioning-app
Put the openshift directory in the code repository
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14
- Forks
- 20
- Avg merge
- 3h 35m
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
Every project we are working has had to make modifications to openshift/*.yaml
Modify the priviosing app to put the templates from the openshift/* directory directly in the code that is being provided as boilerplate.
Describe the solution you'd like
We had t repeatedly explain the same situation to users:
- How do you export the currently deployed OpenShift templates
- How to revert the modifications so that, instead of the fixed strings, the template strings are used again
- How/Where to get the "original" templates for a given quickstarter
Our perception is that abstracting/hiding the OpenShift templates to the point where they are now is a tad too much. People would like to see most of the code that is being used to deploy their applications.
Describe alternatives you've considered
none -- that's our only idea
Additional context
none
Contributor guide
No contributing guide indexed for this repository
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 openshift/*.yaml templates and the provisioning app path that supplies boilerplate. Determine how the templates are currently abstracted and define verification for making the original, editable templates available directly in each provided project.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100