...
The Napa release is EdgeX version 3.1 (the 13th overall release and the first dot release off EdgeX 3.0). It is a stabilization of the version 3 and is our current Long Term Support (LTS) release, replacing Jakarta (EdgeX 2.1) in having current LTS status.
Release Major Themes
- URIs URI for Files
- Added support for loading EdgeX configuration files from a remote location via a URI. This includes configurations, unit of measurements, device profiles, device definitions and provision watchers
- An important benefit of this is to allow services to share more of the configuration and start-up information in a single location, rather than users needing to duplicate and have multiple sources for the same information
- See here for full details: https://docs.edgexfoundry.org/3.1/microservices/general/#uri-for-files
- Note that this feature is not yet available in the C Device Service SDK and is aimed for completion in the next release (Odessa)
- Common Configuration - Added support for C Device Services
- The Common Configuration pattern added in EdgeX 3.0 is now also supported in the C Device Service SDK meaning that all services now support this feature
- Major Documentation Improvements
- Overhaul, refactor and general improvement of the EdgeX documentation - especially as part of the V3 stabilization work
- The documentation for each service has a standard structure (e.g., purpose, getting started, configuration, API reference, source code and additional details)
- Also added easier access for new users with a tiled home page directing people to key or common parts of the documentation
- See the updated documentation here: https://docs.edgexfoundry.org/3.1/
- Core Data Retention
- Added capability for Core Data to retain a configurable maximal number of readings with data automatically purged to maintain the maximum amount of data that is held
- See here for full details: https://docs.edgexfoundry.org/3.1/microservices/core/data/details/DataRetention/
- Record and Replay Service
- Added new Record and Replay capability as an Application Service that will record EdgeX events received by the internal message bus, and replay them back to the message bus at a later time
- This is particularly useful to help test that new/existing EdgeX services receive and process EdgeX events correctly, without needing device services and real physical devices to always be present
- See here for full details: https://docs.edgexfoundry.org/3.1/microservices/application/services/AppRecordReplay/
...