Profiles

Profiles are a general override mechanism where a nested map of key/value pairs can be specified in your jobdef or base. If the profile is active, then the entries in the nested map override settings of the same name. Profiles can be created in defcluster, defstep, or the base.

A profile can also influence which steps are run as part of (fire!). And which validations and hooks are executed. See details in examples/sample-jobdef.clj.

There is one implicit profile which is activated automatically. When running in local mode, the profile :local is on.

The leading colon (:) at the front of the profile name, should be considered part of the name, and is required.

Multiple profiles can be active at once. For example, running a test in local mode. In this common case, the active profiles are [:local, :test]. The right-most profiles take precedence.

Profiles can be enabled on the command line. For example, to enable the :test and :foo profiles (in order)

lemur local :test :foo jobdef.clj ...

Commonly, you would create profiles for :test values, and maybe a profile for :live or :deployed options.