deviation#
Collection Note
This module is part of the nokia.eda_apps_core_v1 collection. To install the collection, use:
Added in version0.3.0. Synopsis#
- Deviations are used to represent differences between the intended and actual state of a target. They indicate the intended state - or the computed configuration EDA expects, and compare this to the actual or running state, or the configuration retrieved from the target. Deviations are most often generated by out-of-band changes to a target by an external system or user, and can be accepted or rejected. Rejecting a Deviation will result in the intended configuration being re-applied, undoing the out-of-band change. Deviations are raised per table, meaning a single change on a target may result in more than one Deviation.
Parameters#
| Parameter | Defaults / Choices | Comments |
|---|---|---|
| auth_token str required | HTTP authentication (Bearer authentication) string in the format of "Bearer TOKEN". Required unless state is cronly. | |
| base_url str required | EDA API URL including the schema and port (if non standard for the provided schema). Example - https://try.eda.demo:9443. Required unless state is cronly. | |
| ca_path str required | A path to the PEM-encoded CA certificate to use for TLS verification. Required unless state is cronly. | |
| hash str | Resource content will be returned as it was at the time of this git hash | |
| name str required | Name of the Deviation. Required when state is query. | |
| namespace str required | The namespace to use when querying the resource. Required when state is query. | |
| state str required | Choices: query | State of the requested resource object. |
| tls_skip_verify bool required | A flag to control the TLS verification of the session. Required unless state is cronly. |
Authors#
- Roman Dodin (@hellt)