Adding Custom Container Services

The following are examples of what custom container services can be used for:

• When recording requests from a service, a local instance may be needed. The local instance of the service can be added here

• When testing, a custom container can be used to trigger the tests after all the services have initialized. An entrypoint service is provided for this purpose

To add a custom container service:

1. Each workflow provides a docker-compose.yml for the purpose of adding custom container services. For example:

$ cat .stoobly/docker/<SERVICE-NAME>/<WORKFLOW-NAME>/docker-compose.yml

services: {}

1. Custom services should be added under the services property. A custom service also needs to include the workflow name under profiles . For example, if the current workflow is record, then:

$ cat .stoobly/docker/<SERVICE-NAME>/<WORKFLOW-NAME>/docker-compose.yml

services: 
  helloWorld:
    image: hello-world
    profiles:
      - record

Optional: if your custom service requires network access to other custom services, then add them to the network as needed

There are two networks:

• app.ingress - used for allowing network access to the custom service from outside the network

• app.egress - used for allowing network access within the custom service's network

$ cat .stoobly/docker/<SERVICE-NAME>/<WORKFLOW-NAME>/docker-compose.yml

services: 
  helloWorld:
    image: hello-world
    networks:
      - app.egress
    profiles:
      - record