Introduction:

The issue has been spotted and reported before XP3 CR1 dev tag, but somehow it managed to avoid the attention.

Issue description:

jboss-eap-xp-3.0.0.GA-quickstarts/todo-backend/README.html contains the following incorrect or outdated values:

Run the Backend on OpenShift -> Build and Deploy the Backend on OpenShift with Bootable Jar section:

1. --set build.ref=EAP_7.4.0.Final - this parameter value itself is not correct (the "right" one is XP_3.0.0.GA,). In addition, from the user POV it would be clearer if we omit this parameter - as soon as the XP3 quickstarts are out, we are able to release https://raw.githubusercontent.com/jbossas/eap-charts/main/examples/eap-xp3/todo-backend/todo-backend-bootable-jar.yaml with correct build.ref value - there will be no reason to keep it in Helm command.

Run the Backend on OpenShift -> Build and Deploy the Backend on OpenShift with JBoss EAP XP S2I section:

1. --set build.ref=EAP_7.4.0.Final - see the previous point.
2. wrong build.uri value (https://github.com/wildfly/quickstart.git) - it should be https://github.com/jboss-developer/jboss-eap-quickstarts.git - as it is in a previous Bootable jar section.

Architecture with S2I section:

1. As I understood from analysis document and from readme previous section (Architecture with Bootable Jar) - there should be https://github.com/jbossas/eap-datasources-galleon-pack URL instead of https://github.com/wildfly-extras/wildfly-datasources-galleon-pack (since we are using org.jboss.eap:eap-datasources-galleon-pack feature pack).

Summary:

While the incorrect URLs do not break QS backend build/deploy functionality, the incorrect build.ref value will fail a Helm Chart build - i.e. following readme's instructions does not lead to the successful QS backend build and deployment on OpenShift, thus setting the issue priority as blocker.