com.mesosphere.sdk.config.validate

Interface ConfigValidator<C extends Configuration>

Type Parameters:

C - the type of configuration to be validated

All Known Implementing Classes:

DomainCapabilityValidator, PodSpecsCannotChangeNetworkRegime, PodSpecsCannotShrink, PodSpecsCannotUseUnsupportedFeatures, PreReservationCannotChange, ServiceNameCannotContainDoubleUnderscores, TaskEnvCannotChange, TaskVolumesCannotChange, TLSRequiresServiceAccount, UserCannotChange

public interface ConfigValidator<C extends Configuration>

The ConfigurationValidation interface should be implemented by any class which intends to validate a new Configuration, either on its own, or w.r.t. a prior Configuration.

Method Summary

Modifier and Type	Method and Description
java.util.Collection<ConfigValidationError>	validate(java.util.Optional<C> oldConfig, C newConfig) Returns List of ConfigurationValidationErrors for the newly supplied Configuration object.

Method Detail

validate

java.util.Collection<ConfigValidationError> validate(java.util.Optional<C> oldConfig,
                                                     C newConfig)

Returns List of ConfigurationValidationErrors for the newly supplied Configuration object. A validation can validate a newConfig in following ways: 1. Validate newConfig parameters against the oldConfig paramater. Ex: If DiskType was ROOT in oldConfig, then it cannot be changed to, ex: MOUNT, in the newConfig. 2. Validate just newConfig parameter(s). Ex: CPU value > 0

Parameters:

oldConfig - Currently persisted Configuration, or an empty Optional if none is available (first launch of service)

newConfig - Proposed new Configuration

Returns:

List of errors, or an empty list if validation passed