openshift / openshift/oadp-operator
Create templates `tests/e2e/sample-applications`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 92
- Forks
- 93
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 43
Description
To avoid duplication, we need to create OpenShift Templates for tests/e2e/sample-applications. This will also make it easier to create the applications for manual tests
Example
Today, developer must run two command to deploy an application, one to create application's PVCs (https://github.com/openshift/oadp-operator/blob/master/tests/e2e/sample-applications/mysql-persistent/pvc-twoVol/aws.yaml) and other for the other objects (https://github.com/openshift/oadp-operator/blob/master/tests/e2e/sample-applications/mysql-persistent/mysql-persistent-twovol-csi.yaml). And if developer want to use an different storageClassName, it need to manually edit the YAML files.
With OpenShift Template, it easy to create all object at once and easy modify its parameters. Example https://github.com/migtools/oadp-non-admin/blob/master/hack/samples/apps/mysql.yaml
Failed approach
Tried in https://github.com/openshift/oadp-operator/pull/1364, but approach would make developers running it harder (they would need to change replace strings manually).
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 files under tests/e2e/sample-applications, especially the mysql-persistent YAML files linked in the issue, and compare them with the example template in the oadp-non-admin repository. Create OpenShift Templates that deploy each sample application and expose storageClassName and related values as parameters, so one template creates all required objects without manual string replacement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100