public class BrooklynNodeUpgradeEffectorBody extends EffectorBody<java.lang.Void>
| Modifier and Type | Field and Description |
|---|---|
static ConfigKey<java.lang.Boolean> |
DO_DRY_RUN_FIRST |
static ConfigKey<java.lang.String> |
DOWNLOAD_URL |
static ConfigKey<java.util.Map<java.lang.String,java.lang.Object>> |
EXTRA_CONFIG |
static Effector<java.lang.Void> |
UPGRADE |
| Constructor and Description |
|---|
BrooklynNodeUpgradeEffectorBody() |
| Modifier and Type | Method and Description |
|---|---|
java.lang.Void |
call(ConfigBag parametersO)
Does the work of the effector, either in place, or (better) by building up
subtasks, which can by added using
DynamicTasks methods
(and various convenience methods which do that automatically; see subclasses of EffectorBody
for more info on usage; or see DynamicSequentialTask for details of the threading model
by which added tasks are placed in a secondary thread) |
public static final ConfigKey<java.lang.String> DOWNLOAD_URL
public static final ConfigKey<java.lang.Boolean> DO_DRY_RUN_FIRST
public static final ConfigKey<java.util.Map<java.lang.String,java.lang.Object>> EXTRA_CONFIG
public static final Effector<java.lang.Void> UPGRADE
public java.lang.Void call(ConfigBag parametersO)
EffectorBodyDynamicTasks methods
(and various convenience methods which do that automatically; see subclasses of EffectorBody
for more info on usage; or see DynamicSequentialTask for details of the threading model
by which added tasks are placed in a secondary thread)
The associated entity can be accessed through the EffectorBody.entity() method.
call in class EffectorBody<java.lang.Void>