Skip to content

chore: support newer compose-go library with lagoon workarounds#304

Draft
shreddedbacon wants to merge 1 commit intomainfrom
compose-go-latest-lagoon-fixes
Draft

chore: support newer compose-go library with lagoon workarounds#304
shreddedbacon wants to merge 1 commit intomainfrom
compose-go-latest-lagoon-fixes

Conversation

@shreddedbacon
Copy link
Member

Updates the compose-go library to the latest version with lagoon workarounds for the more common issues.

Unfortunately, the duplicate mapping error is not a lagoon workaround, so introducing this into the build-deploy-tool will result in builds failing if those duplicate mapping keys error is encountered.

Also, env_file got an update to allow for these to be optionally required by changing the structure of the yaml to support a path and required field. This will be handy in the future for when we eventually decide to fail builds and move towards consuming the upstream compose-go library directly. See workarounds in shreddedbacon/compose-go#5

Closes

closes #252

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Validation false positive for nested interpolation in docker-compose

1 participant