rabbitmq-server/selenium/bin/components
Marcial Rosales a64f245e0a Fix ca location 2024-11-28 15:42:30 +01:00
..
README.md
devkeycloak Fix ca location 2024-11-28 15:42:30 +01:00
fakeportal
fakeproxy
keycloak Fix ca location 2024-11-28 15:42:30 +01:00
mock-auth-backend-http
mock-auth-backend-ldap
prodkeycloak Fix ca location 2024-11-28 15:42:30 +01:00
proxy
rabbitmq Generate certs 2024-11-28 11:34:39 +01:00
selenium
uaa Generate certs 2024-11-28 11:34:39 +01:00

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.