ConfigChangeAction (config-model-api 7.509.14 API)

All Known Subinterfaces:

ConfigChangeRefeedAction, ConfigChangeReindexAction, ConfigChangeRestartAction
```
public interface ConfigChangeAction
```
Contains the action to be performed on the given services to handle a config change between the current active model and the next model to prepare.

Author:

geirst

Nested Class Summary

Nested Classes
Modifier and Type Interface Description

static class ConfigChangeAction.Type

Method Summary

All Methods Instance Methods Abstract Methods Default Methods
Modifier and Type	Method	Description
`com.yahoo.config.provision.ClusterSpec.Id`	`clusterId()`	The id of the cluster that needs this action applied
`String`	`getMessage()`	Returns a message describing the config change in detail
`List<ServiceInfo>`	`getServices()`	Returns the list of services where the action must be performed
`ConfigChangeAction.Type`	`getType()`	Returns what type of action is required to handle this config change
`default boolean`	`ignoreForInternalRedeploy()`	Returns whether this change should be ignored for internal redeploy
`default Optional<ValidationId>`	`validationId()`	When this is non-empty, validation may fail unless this validation id is allowed by validation overrides.

- Method Detail
  - getType
```
ConfigChangeAction.Type getType()
```
    Returns what type of action is required to handle this config change
  - getMessage
```
String getMessage()
```
    Returns a message describing the config change in detail
  - getServices
```
List<ServiceInfo> getServices()
```
    Returns the list of services where the action must be performed
  - validationId
```
default Optional<ValidationId> validationId()
```
    When this is non-empty, validation may fail unless this validation id is allowed by validation overrides.
  - clusterId
```
com.yahoo.config.provision.ClusterSpec.Id clusterId()
```
    The id of the cluster that needs this action applied
  - ignoreForInternalRedeploy
```
default boolean ignoreForInternalRedeploy()
```
    Returns whether this change should be ignored for internal redeploy