validation-overrides.xml

validation-overrides.xml is added to the root of an application package (i.e. next to services.xml) to allow a deployment, that otherwise fails to validate, to proceed. Validations which can be overridden in this way are returned with a dash-separated validation-id preceding the validation message. E.g. if the message is field-type-change: Changing the type of field 'foo' to 'bar' is not supported the validation id is field-type-change.

Validations protect against inadvertently corrupting a production instance. Overriding them may be useful e.g. if the application is not in production yet or if you think the consequences of inconsistencies or loss of the data in a particular field are fine.

Structure

<validation-overrides>
<allow until="iso-8601-date" [comment="any text"]>validation-id</allow>*
</validation-overrides>


Any number of allow tags is permissible. Example:

<validation-overrides>
<allow
until="2016-01-31"
comment="Reduce to needed cluster size after benchmarking">cluster-size-reduction</allow>
<allow
until="2016-02-03">field-type-change</allow>
</validation-overrides>


allow

An allow-tag disables a particular validation for a limited time. It contains a single validation-id, see ValidationId.java for validation overrides. allow-tags with unknown ids are ignored.

AttributeMandatoryValue
until Yes The last day this change is allowed, as a ISO-8601-format date in UTC, e.g. 2016-01-30. Dates may at most be 30 days in the future, but should be as close to now as possible for safety, while allowing time for review and propagation to all deployed zones. allow-tags with dates in the past are ignored.
comment No Text explaining the reason for the change to humans.