As a backend dev, I want to shorten the time it takes to see local Java code changes in a running ephemeral environment (without removing the existing iqe pod), so that I can quickly make backend code changes for collaboration with QE.  QE has a script[1] that enables them to sync local changes to a running iQE pod while working.

See if we can adopt a similar approach for backend changes.

[1] https://gitlab.cee.redhat.com/smqe/smqe-tools/-/blob/master/misc/sync_swatch_qe_ee.sh 

Done

• A script(s) exists in the rhsm-subscriptions repo that does something along the lines of this:
  • I make some java code changes
  • I run some variation of ./gradlew build in order to get a .jar file
  • That .jar file can be sync'd to a running pod in EE
  • Kill the running application and restart it with the new jar file
    • example: java -jar /home/lburnett/code/rhsm-subscriptions/build/libs/rhsm-subscriptions-1.1.0-snapshot.202308011944+lburnett.mapper.exception.sync.org.fbbf3c0.jar{}

• In the event that the above approach can't be reasonably achieved, come up with a script that uses the existing bin/build-images.sh to build & push local code changes and then subsequently lands the updated image in an existing EE deployment (using either bonfire or the openshift client).
  • Note: oc patch may be useful for this... something like (WIP, not working, but close)

oc patch app swatch-tally -p '{"spec":{"deployments":[{"name":"service","podSpec":{"image":"quay.io/cloudservices/foobar:latest"}}]}}'