Releases: camaraproject/TrafficInfluence
r1.3
This public release contains the definition and documentation of:
- traffic-influence v0.10.0
The API definition(s) are based on
- Commonalities v0.6.0
- Identity and Consent Management v0.4.0
traffic-influence v0.10.0
This is a public release for the CAMARA Traffic Influence API. This version provides the ability to influence the traffic flow from the user device toward the Edge instance of the Application providing the optimal routing.
The traffic can be influenced even when the user device moves to a different geographical location to always get the optimal routing toward the nearer instance of an Application.
- API definition with inline documentation:
Please note:
- The release is suitable for implementers, but it is not recommended to use the API with customers in productive environments
- The release scope is defined here: #14
- This is the first public release of the API, the modification reported below ("Changed" and "Fixed" sections) are with respect to v0.10.0-rc.1 in r1.2.
Added
- Support for the following use cases: #15
Changed
- x-correlator update: #49
- Alignment with the CAMARA Error codes: #53 and #73
- Updated the name of the test file to be coherent with the operationId: #53
- ErrorInfo scheme updated: #65 and #73
- 409 error code in patch operation: #77
Fixed
- Backslash \ is not standard markdown syntax for paragraph: #53
- info.description reordering: #62
- Path in Background section: #62
- DeviceResponse description updated: #65
Removed
Full Changelog: https://github.com/camaraproject/TrafficInfluence/commits/r1.3
r1.2
r1.2
Release Notes
This pre-release contains the definition and documentation of:
- traffic-influence v0.10.0-rc.1
The API definition(s) are based on
- Commonalities v0.6.0-rc.1
- Identity and Consent Management v0.4.0-rc.1
traffic-influence v0.10.0-rc.1
This is the release candidate for the CAMARA Traffic Influence API. This version provides the ability to influence the traffic flow from the user device toward the Edge instance of the Application providing the optimal routing.
The traffic can be influencend even when the user device moves to a different geographical location to always get the optimal routing toward the nearer instance of an Application..
- API definition with inline documentation:
Please note:
- This pre-release contains a release-candidate API version, there are bug fixes to be expected and incompatible changes in upcoming versions
- The release is suitable for implementers, but it is not recommended to use the API with customers in productive environments
- The release scope is defined here: #14
Added
Changed
- Renamed operations: camaraproject/EnergyFootprintNotification#83
- Changed OAuth2 with OpenId: camaraproject/EnergyFootprintNotification#83
- Updated the name of the test file to be coherent with the operationId: camaraproject/EnergyFootprintNotification#83
- x-correlator update: #49
- Alignment with the CAMARA Error codes: #53
- Updated the name of the test file to be coherent with the operationId: #53
Fixed
Removed
Full Changelog: r1.1...r1.2
r1.1
This release contains the definition and documentation of:
- traffic-influence v0.9.0-alpha.1
The API definition(s) are based on
- Commonalities v0.6.0-alpha.1
- Identity and Consent Management v0.4.0-alpha.1
traffic-influence v0.9.0-alpha.1
This is a pre-release of the CAMARA Traffic Influence API. This version provides the ability to influence the traffic flow from the user device toward the Edge instance of the Application providing the optimal routing.
The traffic can be influenced even when the user device moves to a different geographical location to always get the optimal routing toward the nearest instance of an Application.
- API definition with inline documentation:
Please note:
- This pre-release contains a release-candidate API version, there are bug fixes to be expected and incompatible changes in upcoming versions
- The release is suitable for implementers, but it is not recommended to use the API with customers in productive environments
- The release scope is defined here: #14
What's New
- Support for the following use cases: #15
New Contributors
Full Changelog: https://github.com/camaraproject/TrafficInfluence/commits/r1.1