ef8b4fc767
In certain environments, we may want to customise the docker image e.g. to use a proxy to avoid docker hub rate limiting. The default behaviour remains unchanged. The `if` logic was broken because `uname -a` returns the entire uname, including OS, Kernel version, machine type and what not. The string always starts with the OS i.e. Linux or Darwin, therefore, the matching for `arm*` was always false; therefore, it was always defaulting to the `else` image, which happens to be multi-arch. However, it was using `seleniarm`, which is a community driven effort, not the official Selenium account. In the official OSS image, version 123.0 is too old. The oldest available is 127.0. This commit bumps to the latest available. We could consider depending on version `4`. Version `4` refers to Selenium version, whilst version 123.0/133.0 refer to the browser version. |
||
|---|---|---|
| .. | ||
| README.md | ||
| devkeycloak | ||
| fakeportal | ||
| fakeproxy | ||
| keycloak | ||
| mock-auth-backend-http | ||
| mock-auth-backend-ldap | ||
| prodkeycloak | ||
| proxy | ||
| rabbitmq | ||
| selenium | ||
| uaa | ||
README.md
These shell scripts are not meant to be executed directly. Instead they are imported by bin/suite_template script.
Each component required to run a test, for instance, uaa or keycloak, has its own script with its corresponding function: start_()
Although there is a convention to have two functions, the entrypoint start_<ComponentName>(),
and init_<ComponentName>(). The latter is called by the former to initialize
environment variables.
There is a third entry point for third party components (i.e. all except rabbitmq), the ensure_<ComponentName>().
This function starts the component if it is not running. Whereas start_<ComponentName>() kills the
component's container if it is running and start it again.