Closed samuelbernardolip closed 4 years ago
The services setting will not be implemented since we will leverage entirely in the capabilities of the underlying container orchestrator, i.e. Docker Compose (or k8s in the future).
What we need to provide is elaborated examples on how to manage specific types of services using docker-compose.yml
such as the ones in the example (postgres, dataverse, ..)
For common services like database, dataverse, workload managers, they can be automatically added to the Compose agent as available components. To use this concept, it needs to be defined a special context in config called service that will be added to the compose configuration. They will use available docker images from dockerhub registry. It can be implemented answering to the follow example:
In the previous example the service hostnames would be:
When using config.services this will not be available to run commands or referencing as container in sqa_criteria. The user can use the environment variables to configure the services as defined by referenced images. The environment variables can be defined at two different levels:
For current Docker Compose Agent is possible to use extends to merge the configurations as overrides or importing multiple configuration files: https://docs.docker.com/compose/extends/