Use environment variables in Docker

For example, while building a demo in AWS CodeCommit, CodeBuild, & CodePipeline, imagine that your workflow requires you to pass in custom log data to build a friendlier dashboard in Grafana. Using the LIQUIBASE_CUSTOM_LOG_DATA_FILE environment variable will result in custom log data being omitted from the log, but passing the file in using the --custom-log-data-file argument, the custom log data is present as expected.

To pass environment variables to the Docker image, you must either use the Docker argument -e var=value or --env var=value. For example:

-e LIQUIBASE_CUSTOM_LOG_DATA_FILE="/liquibase/changelog/demo.yml"--env LIQUIBASE_CUSTOM_LOG_DATA_FILE="/liquibase/changelog/demo.yml"

Note: Be aware the syntax requires a single dash for -e and a double dash for --env.