API - run validator ruleThis endpoint allows executing a validation rule on the pending config data set. This can be useful in case that a validator is not assigned to the config data set but there is a need to run it upon a 3rd party trigger. The validation rule can be applied to either the pending data or the current active snapshot. As an example, you can create a validator that compares configuration data in different nodes of the data set (for instance the "discovered data" versus "last deployed data" to identify any configuration items which are different than expected. The user must have the VIEW permissions on the config data set name in order to retrieve its content. Endpoint methodPOSTURI/api/v1/tenant/metadata-parser/validate Headers ! AuthorizationBearer <userToken or APIkey> Parameters ! mdsmyMdsNamethe exact name of the metadata set for which a snapshot should be taken ! parsermyValidationRulethe exact name of the validation rule to be applied!forIncomingtrue|falsedefines if the validation logic should be applied on the pending data or the current active snapshot Response The response is a JSON object which contains: validation result : true | false : true in case the validation rule passed successfully, false in case it faileddescription : the validation error message created by the validation rulepassed : true | falsefailed: true | falsecrashed : true | false The response fields 3 and 4 (passed and failed fields) in the result object are to simplify integrations The response field 4 indicates if the script was unable to finish or threw an error {"result":true,"description":"validation rule is ok","passed":true,"failed":false,"crashed":false} Tn case of insufficient permissions, the response object will contain a {"AccessDeniedException"} message Example cURL curl -X POST 'https://demo.sweagle.com/api/v1/tenant/metadata-parser/validate' -H "Authorization: bearer Xeb940d3-ea37-4766-bb6c-f0b83deafb6f" -d 'mds=myMdsName&parser=myValidationRule&forIncoming=true'