I am trying to delete and create the same record with different values in a single commit transaction in confd.
- is there any confd commit order which guarantees the final result as final record with updated values?
- How the call back ordering is defined by default - delete first and create call back or can it be out of sequence?
I have a validation call back handler which gets called.
The validation handler checks for a particular value and if its already configured then it wont allow to change it.
When I do this on cli or even through single editConfig through netconf the result is same and the validation callback for create is failing because it checks for configured value for a particular attribute and doesnt allow to change it.
In this particular delete/create case, is there any order of validation handler callbacks?
If its not and validation for both commands can be called in any order then how to avoid this validation check before commit to identify that the value is configured already but validation is part of transaction where the previous record is getting deleted and this will be new record so ignore the configured value in this case.
Not sure if there is any way to achieve this.