We are using NSO 22.214.171.124 in our project. We have defined service point inside yang model container and has written the call back methods with call back type = PRE_MODIFICATION and CREATE. These methods are triggered for any commit or commit-dry run to this container.
Inside the call back methods, is there a way to differentiate between the commit and commit-dry run commands. We need to take different actions inside the PRE_MODIFICATION call back method if it is commit-dry run.
Kindly advice and please let me know if you need more information.
If we wrap the action that needs to be taken during commit dry run as a part of Generic ned code, will it be possible. Will a class part of Generic Ned gets to know if it is a commit or commit dry-run.
No, you're going to have to rethink what you're designing now. And the problem is actually worse, a transaction may get restarted during certain lock scenarios. I.e your create() code might run twice for the same transaction !!
So, no non-transactional side effects or dirty tricks are allowed in the create() code.