Releases: alliedtelesis/apteryx
Releases · alliedtelesis/apteryx
v2.01: Use platform agnostic size_t and print-modifiers
Signed-off-by: Carl Smith <[email protected]>
Apteryx is awesome
API has changed from 1.xx series
- no priv field for watch/provide
- validation is done on apteryx_set (callbacks can be registered with apteryx_validate, works like apteryx_watch but can prevent apteryx_set from completing)
- watch/provide/validate stored in /apteryx with apteryx_set
- listen on tcp/tcp6 sockets (set /apteryx/sockets/...)
- access remote apteryx servers (prefix get/set path with remote address)
- treat callback function as part of unique key for watch/provide/validate (multiple callbacks can be registered for the same path in the same process, and each will be called, previously only the last to register would be called)
- timestamp last change (and propogate timestamp upwards) to identify changes in apteryx
v1.17: Use gcc to create shared library
Signed-off-by: carlgsmith <[email protected]>
v1.16: Only ERROR to stderr when debug is enabled
Signed-off-by: carlgsmith <[email protected]>
v1.15: Use glib atomic increment to support more targets
the existing operation doesn't exist or work on some arm targets Signed-off-by: carlgsmith <[email protected]>
v1.14: add read only attribute (ro) to schema
Signed-off-by: Blair Steven <[email protected]>
v1.13: Add apteryx schema file
Signed-off-by: carlgsmith <[email protected]>
v1.12: Remove stack-protection compiler flags
combined with -fPIC they cause build issues on some platforms Signed-off-by: carlgsmith <[email protected]>
v1.11: Change counters to 32-bit
some of our platforms don't support atomic increment of 64bit integers Signed-off-by: carlgsmith <[email protected]>
v1.10: Clear cache before watch callbacks when pruning
Doing the cache clear / watch callbacks in one go was causing issues for NAT, and didn't make sense. Signed-off-by: carlgsmith <[email protected]>