543c9d1c26
Added checks to ensure the Minikube profile exists and is running before executing stx commands. Provided user instructions for creating the profile and starting pods when necessary. Solution: fix the log message's format string * Added a check to verify if the Minikube profile exists before executing stx commands. * Logged an error message and provided instructions to create the Minikube profile if it is missing. * Included guidance to run `./stx-init-env` from the `stx-tools` directory to create the missing profile. * Added a message to prompt the user to run `stx control start --wait` when attempting to run `stx shell` if the builder container is not running. * Ensured that execution halts if the profile is missing, avoiding potential errors. TESTS ======================== * Stop the Minikube profile and run `stx control status`, ensure the message `stx control start --wait` is shown. * Ensure that running `stx control start --wait` starts the Minikube profile and allows commands to run without errors. * Stop the Minikube profile and run `stx control stop`, ensure the profile starts and the command runs without errors. * Remove the containers with `stx control stop` and run `stx shell`, ensure the message `stx control start --wait` is displayed. * Remove the Minikube profile and ensure the `stx control start/stop/ status` commands show the message `./stx-init-env` to create the profile. * stx control start/stop/status` commands function correctly after a machine restart Closes-Bug: 2080681 Change-Id: I474ad59947fb98af434e7616859f5256a226f903 |
||
|---|---|---|
| .. | ||
| bin | ||
| dockerfiles | ||
| lib/stx | ||
| stx-build-tools-chart/stx-builder | ||
| toCOPY | ||