The docker compose script engine binds and replaces variables on its own.
Since docker compose 1.5+ variables are replaced by docker compose itself (https://github.com/docker/compose/releases/tag/1.5.0rc2). In order for docker compose to replace variables inside docker-compose files, they must be defined in the shell/bash which executes the docker compose up command.
So the docker compose script engine can execute docker-compose up in a bash script engine (something which is known to handle the variable bindings). That way the variable bindings are handled in the "standard" docker-compose way with the standard ProActive way. Removing custom code from the docker-compose script engine.
The docker compose script engine binds and replaces variables on its own.
Since docker compose 1.5+ variables are replaced by docker compose itself (https://github.com/docker/compose/releases/tag/1.5.0rc2). In order for docker compose to replace variables inside docker-compose files, they must be defined in the shell/bash which executes the docker compose up command.
So the docker compose script engine can execute docker-compose up in a bash script engine (something which is known to handle the variable bindings). That way the variable bindings are handled in the "standard" docker-compose way with the standard ProActive way. Removing custom code from the docker-compose script engine.