Enabling and Disabling Actions¶
Some actions are enabled by default and others are disabled by default, based on the script. However, sometimes the set of default actions are biased towards developers, or a production environment, and are not the ideal set of default actions for another environment.
Action groups allow for defining other sets of defaults. For example, there could be a development, staging, or production action group for that environment. These would have to be defined in the script.
Consider the following action groups.
Action development production clobber no yes pull no yes prepare-dev-env yes no build yes yes package yes yes upload no yes notify no yes
Running the script with
--action-group development would enable the
package actions, while
--action-group production would enable all actions except for
There are also the built-in
none groups, that enable all and disable all actions, respectively.
--actions option takes a number of action names as arguments. Those actions will be enabled; all others will be disabled.
--action-group are incompatible. Currently
--actions will override
--action-group and is not an error.
For an example, see –actions in the quickstart.
--add-actions option adds a set of actions to the set of already enabled actions. In the above example,
--action-group development --add-actions notify would enable the
--skip-actions option removes a set of actions from the set of already enabled actions. In the above example,
--action-group development --skip-actions package would enable the