rabbitmq-server/deps/rabbitmq_management/selenium/bin/components
Marcial Rosales 22aa5172b9 Fix issue waiting for oauth2 section 2024-02-10 20:12:20 +01:00
..
README.md Warn when some oauth resource is not available 2024-02-10 20:12:18 +01:00
devkeycloak Fix issue waiting for oauth2 section 2024-02-10 20:12:20 +01:00
fakeportal Add ensure-others command 2024-02-10 20:12:17 +01:00
fakeproxy Add ensure-others command 2024-02-10 20:12:17 +01:00
keycloak Fix issue waiting for oauth2 section 2024-02-10 20:12:20 +01:00
mock-auth-backend-http Add ensure-others command 2024-02-10 20:12:17 +01:00
mock-auth-backend-ldap Add ensure-others command 2024-02-10 20:12:17 +01:00
prodkeycloak Fix issue waiting for oauth2 section 2024-02-10 20:12:20 +01:00
proxy Add ensure-others command 2024-02-10 20:12:17 +01:00
rabbitmq Fix issue mounting certs and import folders 2024-02-10 20:12:19 +01:00
selenium Create Oauth2 client 2024-02-10 20:12:04 +01:00
uaa Add ensure-others command 2024-02-10 20:12:17 +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.