Releases: OADA/server
Releases · OADA/server
Release 3.1.4
- Fix for binary Content-Type
- 400 on binary GET over WebSockets
- Add
PROFILE_AQL
env var for easier query debugging
Release 3.1.3
Fix performance for path resolution
Release 3.1.2
Fix GET on strings
Release 3.1.0
OADA 3.1 is non-breaking changes barring any bugs.
The only caveat is that if there are any unhandled messages in kafka, they will be lost when upgrading from 3.0.
Major Changes (not an exhaustive list)
New
- Reworked config lib for nicer TypeScript usage and ease of reading config from environment variables
- Images now pushed to both DockerHub and GitHub Container Registry
- OADA now has a basic dashboard
- Uses grafana with prometheus
- Just shows redpanda dashboard out of the box (maybe more later?)
- Does not run by default (run
docker-compose
with--profile dashboard
for it to come up)
- Support for proper usage of
ETag
withIf-Match
andIf-None-Match
headers- Usage according to RFC7232
- Work on GET/HEAD as well now
- Old usage (i.e., what @oada/client currently does) is still supported... for now
Changed/Improved
- Switch HTTP handler code to fastify
- Switched from kafka to redpanda (services can still be used with an external kafka instead of the packaged redpanda)
- Switched from node-rdkafka to KafkaJS
- OADA is even smaller now than 3.0
- More robust checking for JSON vs non-JSON content-types
- No more zookeeper
- Reduced kafka messaging
- Fixed issue with admin CLI commands not always showing interactive prompts
- Almost all of the services and libs are in TypeScript now
- No longer erroneously creates a volume at
/oada/binary
for every oada service (only makes one forhttp-handler
now)
Release 3.1.0-rc+5
v3.1.0-rc+5 v3.1.0-rc+5
3.1.0 release candidate 4
v3.1.0-rc+4 v3.1.0-rc+4
3.1.0 release candidate 3
- Switch to yarn.BUILD
OADA 3.1.0 release candidate 2
OADA 3.1 is non-breaking changes barring any bugs.
The only caveat is that if there are any unhandled messages in kafka, they will be lost when upgrading from 3.0.
Major Changes (not an exhaustive list)
New
- OADA now has a basic dashboard
- Uses grafana with prometheus
- Just shows redpanda dashboard out of the box (maybe more later?)
- Does no run by default (run
docker-compose
with--profile dashboard
for it to come up)
- Support for proper usage of
ETag
withIf-Match
andIf-None-Match
headers- Usage according to RFC7232
- Work on GET/HEAD as well now
- Old usage (i.e., what @oada/client currently does) is still supported... for now
Changed/Improved
- Switched from kafka to redpanda (services can still be used with an external kafka instead of the packaged redpanda)
- Switched from node-rdkafka to KafkaJS
- OADA is even smaller now than 3.0
- More robust checking for JSON vs non-JSON content-types
- No more zookeeper
- Reduced kafka messaging
- Fixed issue with admin CLI commands not always showing interactive prompts
- More of the services are in TypeScript now
- No longer erroneously creates a volume at
/oada/binary
for every oada service (only makes one forhttp-handler
now)
Release 3.0.1
v3.0.1 Fixed bug w/ undefined id in user creation
Release 3.0.0
This is an update to the reference server, but there are no changes in terms of "the OADA API".
Clients are largely unaffected (i.e., they should need no changes to work with v3).
Major Changes (not an exhaustive list)
New
- releases that only require docker-compose to run (see the attached
docker-compose.yml
file) - HTTP/2 support
- support for brotli encoding
- ZeroSSL support
- Binary resources are now stored in a docker volume
- OADA services no longer run as root
- switched service logs to
pino
- services can now easily expose admin CLI commands (e.g., the
users
container hasdocker-compose run --rm users add
to add a user)
Improved
- bundled "proxy" is now a preconfigured swag image
- Improved letsencrypt support (will now handle auto-renewing)
- better support for multiple OADA instances on one host
- OADA is much smaller (and hopefully faster)
- TypeScript code is actually compiled when building the images rather than running in
ts-node
- fixed gzip encoding support
- updated arangodb, kafka, and zookeeper versions used