Releases: open-horizon/exchange-api
Releases · open-horizon/exchange-api
v2.87.0
Automatic DB init or upgrade
Merge pull request #73 from open-horizon/max-threads-warning Configure AsyncExecutor to prevent warning
Pattern check fixed
- and added services sub-resource called dockerauths for docker image auth tokens
DB upgrade fixed
Merge pull request #65 from bmpotter/fix-upgrade-problem Fix upgrade problem
Services support and fix for IBM agbot special access
Changes in 1.49.0 (since 1.44.0):
- allow IBM agbots to access private ms/wl/svc/pat via get /workloads etc.
- explicitly set http response code of 200 for successful GETs to avoid occasional 404's
- clean up variables in nodes suite tests
- add back in a few tests for workloads and microservices in pattern and node search
- pattern node search api now validates the serviceUrl
- change agbot agreement to service
- change put node status to service
- change name of service package field to imageStore
- test built image with compose db and verify exchange version output
- change node search to service
- change node, node agreement, pattern search
- changed pattern to support service
- added keys to ms, wk, service, pattern (anax issue 498)
- Figured out how to set the Response codes in swagger
- Fixed the swagger 2 level resource problem
- fixed some library versions to make the build work again
- added service resource (issue #51)
- detect if svc requires other svc with different arch
Allow empty torrent field
Merge pull request #54 from bmpotter/allow-empty-torrent Allow empty torrent
Small fixes, including swagger
- Compatible with Horizon agent and agbot 2.13.3
- Made swagger work again, with these limitations:
- "Try it out" button still doesn't work
- The longer "description" field of each method is not appearing
- Added dbSchemaVersion field to the output of /admin/status
- Upgraded:
- scala from 2.12.1 to 2.12.4
- scalatra from 2.5.1 to 2.6.2
- from scalatra-sbt 0.5.1 to sbt-scalatra 1.0.1
- Allowed node in other org to access agbot in IBM org
- When creating/updating a workload and verifying the existence of the apiSpecs, it now treats the MS versions as ranges
- (No need to upgrade the db if coming from version 1.38 or later, altho it won't hurt either)
Consistency checking and optional fields
- Added GET /admin/version
- Docker tag for exchange docker image no longer has the "v" before the version number
- For the references between resources that are not enforced by DB foreign keys, added checking when the resource is created, updated, or patched:
- microservices referenced by a workload
- workloads referenced by a pattern
- patterns referenced by an agbot
- pattern referenced by a node
- Made the following resource fields optional:
- pattern: dataVerification can be omitted or specified as
{}
- microservice: downloadUrl can be omitted, matchHardware can be omitted or specified as
{}
- workload: downloadUrl can be omitted
- pattern: dataVerification can be omitted or specified as
(No need to upgrade the db if coming from version 1.38 or later, altho it won't hurt either)