Posted March 4, 2022 by Viash Team ‐ 2 min read
You can now define a container's organization for the Docker platform and single values can be used in place of lists
See the full changelog below as examples have been added to most changes.
DockerPlatform: Allow defining a container's organisation. Example:
- type: docker registry: ghcr.io organisation: viash-io image: viash tag: "1.0" target_registry: ghcr.io target_organization: viash-io
DockerRequirement: Add label instructions. Example:
setup: [ [ type: docker, label: [ "foo BAR" ]]]
Config: In specific places, allow parsing a value as a list of values. Fixes #97. This mostly applies to list values in
DockerPlatform, but also to author roles. Examples:
functionality: name: foo authors: - name: Alice role: author # can be a string or a list platforms: - type: docker port: "80:80" # can be a string or a list setup: - type: r packages: incgraph # can be a string or a list
viash test: This command doesn't automatically add the resources dir to the path.
.functionality.add_resources_to_pathnot being picked up correctly.
DEBIAN_FRONTEND=noninteractiveby default. This can be turned off by specifying:
- type: apt packages: [ foo, bar ] interactive: true
Main: Slightly better error messages when parsing of viash yaml file fails. Before:
$ viash test src/test/resources/testbash/config_failed_build.vsh.yaml Exception in thread "main" DecodingFailure(Unexpected field: [package]; valid fields: packages, interactive, type, List(DownField(apt), DownArray, DownField(platforms)))
$ viash test src/test/resources/testbash/config_failed_build.vsh.yaml Error parsing 'file:///path/to/viash/src/test/resources/testbash/config_failed_build.vsh.yaml'. Details: Unexpected field: [package]; valid fields: packages, interactive, type: DownField(apt),DownArray,DownField(platforms)