Releases: alliedtelesis/apteryx-xml
Releases · alliedtelesis/apteryx-xml
v3.0.42
What's Changed
- Fixes for with-defaults processing by @tony-vanderpeet in #143
Full Changelog: v3.0.41...v3.0.42
v3.0.41
What's Changed
- Allow apteryx-xml.h to be included in C++ source by @tony-vanderpeet in #142
Full Changelog: v3.0.40...v3.0.41
v3.0.40
What's Changed
- sch_apply_conditions: check data pointer before use by @tony-vanderpeet in #141
- Fix issues with "with-defaults" by @gcampbell512 in #140
Full Changelog: v3.0.39...v3.0.40
v3.0.39
Attempt to translate conditional enum names if possible Internally apteryx uses numeric values for YANG enums. This change attempts to convert an enum name used in a conditional (when or must) clause into a numeric value if possible before evaluating the condition.
v3.0.38
Prevent deletion of RO leaf-lists The checks that were in the leaf processing code need to also be in the leaf-list section. That is to check the access (rw) and also if the leaves are hidden. If the leaf-list is ro and the user has asked to delete config-only then we also need to remove the leaves of the leaf-list from the tree otherwise we end up with a strange tree with what looks like values on the leaf-list list node.
v3.0.37
Fixes to condition code When processing conditions, the original data in the request must be passed in, but when conditions are applied for REST requests, a recursive descent of the data was taking place, and it was the descending tree that was passed to the condition processing code. Fix the code that checks existence of a STEP to allow the data to be scanned for the step and that value to be used. Fix some small memory leaks discovered in testing.
v3.0.36
Fix the response to the restconf depth parameter RFC 8040 section B.3.2 gives examples of how to respond to the depth parameter on a restconf query. The current output is not consistent with the example output.
v3.0.35
Add support for read-only proxy trees This change allows a remote apteryx database to be mounted at a proxy node as a read only tree. The logical-element model has been extended to contain a read only logical element for testing purposes.
v3.0.34
Better sort lists with numerical keys
v3.0.33
Additional fields to test models for RPC delete tests