hadolint
Description
This provider creates a hadolint
Test action type, and (by default) generates one such action for each container
Build that contains a Dockerfile in your project. Each Test runs hadolint against the Dockerfile in question, in order to ensure that the Dockerfile is valid and follows best practices.
To configure hadolint
, you can use .hadolint.yaml
config files. For each Test, we first look for one in the relevant action's root. If none is found there, we check the project root, and if none is there we fall back to default configuration. Note that for reasons of portability, we do not fall back to global/user configuration files.
See the hadolint docs for details on how to configure it, and the hadolint example project for a usage example.
Below is the full schema reference for the provider configuration. For an introduction to configuring a Garden project with providers, please look at our configuration guide.
The reference is divided into two sections. The first section contains the complete YAML schema, and the second section describes each schema key.
Complete YAML Schema
The values in the schema below are the default values.
Configuration Keys
providers[]
providers[]
providers[].name
providers[].name
providers > name
The name of the provider plugin to use.
providers[].dependencies[]
providers[].dependencies[]
providers > dependencies
List other providers that should be resolved before this one.
Example: ["exec"]
providers[].environments[]
providers[].environments[]
providers > environments
If specified, this provider will only be used in the listed environments. Note that an empty array effectively disables the provider. To use a provider in all environments, omit this field.
Example: ["dev","stage"]
providers[].autoInject
providers[].autoInject
providers > autoInject
By default, the provider automatically creates a hadolint
Test for every container
Build in your project. Set this to false
to disable this behavior.
providers[].testFailureThreshold
providers[].testFailureThreshold
providers > testFailureThreshold
Set this to "warning"
if you'd like tests to be marked as failed if one or more warnings are returned. Set to "none"
to always mark the tests as successful.
Last updated