[AAP-15757] - [API] Improve our development env for OpenShift

[msmagnanijr]

Please see: https://issues.redhat.com/browse/AAP-15757

[msmagnanijr]

I still need to handle this in the playbook: 66a3007#diff-d7ecd0564dd20df7257c250e200a664fe59b3149a5c9e447cb768059a1589fc6R59

[bzwei]

@msmagnanijr In the docs folder can you add step by step instructions how to run this?

[msmagnanijr]

@msmagnanijr In the docs folder can you add step by step instructions how to run this?

Yep! Please check again. I created a README.

[hsong-rh]

@msmagnanijr The files folders were missed in both roles/eda-deploy-operator/ and roles/eda-deploy-server/, which caused ansible-playbook to fail.

[msmagnanijr]

@msmagnanijr The files folders were missed in both roles/eda-deploy-operator/ and roles/eda-deploy-server/, which caused ansible-playbook to fail.

Fixed! thanks. I forgot that it's an empty directory... I'll think about how to deal with that later.

[msmagnanijr]

I still need to handle this in the playbook: 66a3007#diff-d7ecd0564dd20df7257c250e200a664fe59b3149a5c9e447cb768059a1589fc6R59

Fixed!

[dhaustein]

@msmagnanijr Hi, I have a couple of questions:

1. Is this going to replace the old task minikube: commands? (using minikube as an example)
2. Could we switch the ansible_python_interpreter: to /usr/bin/env python so it works with poetry/venv instead of calling the system-wide interpreter?
3. Is the user expected to manage the rest of the lifecycle of the cluster using the tooling of their choice? In other words, if I use minikube am I expected then to destroy the cluster once I am done working with it myself instead of running some other playbook?

[ttuffin]

I'm noticing that PV claims are getting stuck in pending state in OCP. Im still troubleshooting the cause. I didn't see the issue in minikube.

[ttuffin]

The reason it was failing in OCP is because I was using a dev cluster instead of running OCP locally and thus the postgres PVC was failing to create due to missing crc-csi-hostpath-provisioner. Since the scope for this PR is to setup a dev environment locally I think we can ignore this error, unless we do want to support deploying on OCP clusters.

[msmagnanijr]

@msmagnanijr Hi, I have a couple of questions:

1. Is this going to replace the old task minikube: commands? (using minikube as an example)
2. Could we switch the ansible_python_interpreter: to /usr/bin/env python so it works with poetry/venv instead of calling the system-wide interpreter?
3. Is the user expected to manage the rest of the lifecycle of the cluster using the tooling of their choice? In other words, if I use minikube am I expected then to destroy the cluster once I am done working with it myself instead of running some other playbook?

1. Is this going to replace the old task minikube: commands? (using minikube as an example)

Maybe in the future but not now. I'm guided by the team's ideas. We can implement whatever the team thinks is best :)

2. Could we switch the ansible_python_interpreter: to /usr/bin/env python so it works with poetry/venv instead of calling the system-wide interpreter?

Yes, that makes perfect sense.

3. Is the user expected to manage the rest of the lifecycle of the cluster using the tooling of their choice? In other words, if I use minikube am I expected then to destroy the cluster once I am done working with it myself instead of running some other playbook?

I've been considering automating everything feasible, including this cleanup task. I already have some ideas and plan to incorporate additional roles. I would appreciate your feedback on them

[msmagnanijr]

@ansible/eda-maintainers Hey team, whenever you get a chance, could you take a look at this PR? Thanks

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov-commenter]

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

Thanks for integrating Codecov - We've got you covered ☂️