I would like to check if it is valid operation to use maapi_start_trans_in_trans in validation callpoint. The idea is to update a field during the time of validation in the transaction. For example encrypt data.
It seems not specified in document, even though we found it works quite well. However, we have concern it will be blocked by confd in coming release.
Here is the description
The changes in this transaction can be validated by calling
maapi_validate_trans()with a non-zero value for
forcevalidation, but calling
maapi_apply_trans()will not do any validation - in either case, the resulting configuration will be validated when the backend transaction is committed to the running data store. Note though that unlike the case with a transaction directly towards a data store, no transaction lock is taken on the underlying data store when doing validation of this type of transaction - thus it is possible for the contents of the data store to change (due to commit of another transaction) during the validation.