My assumption is that when notes are added to the CLI via an ongoing commit, scripts executed via call_depends() DO NOT have access to the newly added data in the CLI.
This can be observed with the bug described here https://vyos.dev/T7299#219881
My assumption is that when notes are added to the CLI via an ongoing commit, scripts executed via call_depends() DO NOT have access to the newly added data in the CLI.
This can be observed with the bug described here https://vyos.dev/T7299#219881
The assumption stated in the description is true, as discussed with @c-po at the time. The following invariant is fundamental to the operation of the commit algorithm (legacy and modern) and the config daemons: during a commit, the active and proposed configs are fixed --- no updates during the commit are reflected in any script's config dict, including those called by config dependencies. Evolution of this model will require a refinement of config dependencies, which is not possible until the legacy backend is retired.
Based on the comments above, I am moving this to 'wishlist' for consideration after the legacy backend is retired. My expectation is that we will not want to drop the invariant as such, however, we will be in a position to consider refinements of the model, radical or conservative, once freed from the legacy constraints.