Juju Lint

Learn about configurations >

• controller-cacert | string

  The controller CA certificate. Value should be base64 encoded.

• controller-endpoint | string

  'A controller API endpoint. (Syntax: "<hostname>:<port>")'

• controller-password | string

  The respective controller user's password.

• controller-username | string

  A controller user's username.

• lint-cloud-type | string

  Specifies the cloud type that will be passed to juju-lint . See juju-lint documentation for more details but the following are typical valid types: openstack, kubernetes. . An empty string (the default) only performs general checks

• lint-config | string

  Default: /snap/juju-lint/current/contrib/canonical-rules.yaml

  Juju Lint rules file path.

• lint-frequency | int

  Default: 30

  Specifies how often Juju Lint is run, in minutes.

• lint-logfile | string

  Log file path.

• lint-loglevel | string

  Default: INFO

  'Logging level, either "CRITICAL", "ERROR", "WARNING", "INFO", "DEBUG", or "NOTSET".'

• lint-override | string

  'Hash separated subordinate rule overrides. (Syntax: "<name>:<location>#<name>:<location>")'

• model-uuid | string

  The model UUID.

• nagios_context | string

  Default: juju

  A string that will be prepended to instance name to set the host name in nagios. So for instance the hostname would be something like: juju-myservice-0 If you're running multiple environments with the same services in them this allows you to differentiate between them.

• split-nagios-checks | string

  A JSON list of check objects with names and filter rules to be used to create multiple nagios checks instead of a single check with all the juju-lint results. . The default empty string, will generate a single check: "juju_lint_results", that covers all the errors reported by juju-lint. . This requires a version of juju-lint that supports JSON output, and the filtering will happen on the relevant key in the error. Currently only the 'id' and 'tags' fields can be used for filtering. each check is a combination of a nagios check name, a field and a target value to be used for filtering. It is possible have more than one target pattern by separating them using a comma. . Example: [ { "name": "config", "field": "tags", "filter": "config" }, { "name": "misc", "field": "id", "filter": "ops-subordinate-missing,config-isset-check-true" } ]

  . This would create two checks: juju_lint_results-config (filtering on the 'tags' field, single target) juju_lint_results-misc (filtering on the 'id' field, with two targets)

• warn-only | boolean

  Report any issues as WARNING level. This is helpful on initial deployment.