- upgrade the runtime to version 1.2.4
- upgrade the runtime to version 1.0.8
- the
httpServer
configuration moved frommodules
toinfrastructure
- the
apiKey
in thehttpServer
infrastructure is now mandatory
-> SDK 1.1.5
- open source release
-> SDK 1.1.4
- preparations for open source release
- update OpenAPI docs
- use DATABASE__DB_NAME (aliased to DATABASE_NAME) instead of ACCOUNT for configuring the MongoDB database
for backwards compatibilitiy you can still use ACCOUNT
- the
httpEndpointEventPublisher
module was renamed towebhooks
- upgrade NodeJS to version 16.13.0 (LTS)
- send CORS header for invalidJsonInPayload error
- simplify CORS policy and disable it by default (allow everthing by setting env var
MODULES__HTTP_SERVER__CORS__ORIGIN
totrue
) - upgrade the runtime to version 1.0.4
-> SDK 1.1.3
- upgrade the runtime to version 1.0.2
-> SDK 1.1.2
- the
Monitoring/Support
endpoint now additionally returns the runtime version as part of itsversion
property - the
Monitoring/Version
endpoint now additionally returns the runtime version
- upgrade the runtime to open source version 1.0.1
- upgrade Node.js to 16.10.0
breaking changes
- the structure of some data has changed significantly => the connector has to be deleted and recreated from scratch
- renamed coreSync module to sync
- the coreLibrary part of the configuration was renamed to transportLibrary (only affected when using a custom config file)
- upgrade the runtime version to 2.0.6
-> SDK 1.1.1
- upgrade the runtime version to 2.0.5
-> SDK 1.1.0
- upgrade the runtime version to 2.0.1
- tokens can now be ephemeral (not saved in DB)
- upgrade the runtime version to 1.8.4
- exceptions in modules will not crash the connector anymore
- upgrade the runtime version to 1.7.13
- errors in the CoreSync module will not crash the connector anymore
- upgrade the runtime version to 1.7.11
- upgrade the runtime version to 1.7.10
- upgrade the mongodb library to 1.0.4. Authentication without username an password fails if you pass an
authSource
in the database connection string
-> SDK 1.0.5
- return status-code 201 for the routes
/api/v1/RelationshipTemplates/:id/Token
and/api/v1/Files/:id/Token
with accept set toimage/png
andapplication/json
- upgrade the runtime version to 1.7.1
- added the possibility to provide a custom config file
- mount the file inside the container and specify the file location in the
CUSTOM_CONFIG_LOCATION
environment variable
- mount the file inside the container and specify the file location in the
-> SDK 1.0.4
- upgrade runtime version to 1.7.0
/api/v1/Files/:id/Token
supports an expiresAt query parameter to override the default behaviour/api/v1/RelationshipTemplates/:id/Token
supports an expiresAt query parameter to override the default behaviour
-> SDK 1.0.3
/Monitoring/Support
is now showing the identityInfo of the connector
/Monitoring/Support
is not showing the platformClientSecret anymore
/health
checks if the Connector is authorized on the Enmeshed backend
-> SDK 1.0.2
- upgrade the runtime to version 1.6.4
- clientId and clientId are checked on connector startup
/api/v1/Account/LastCompletedSyncRun
renamed to/api/v1/Account/SyncInfo
- provided
Auto Accept Relationship Creation Changes
module.- enable by setting
MODULES__AUTO_ACCEPT_RELATIONSHIP_CREATION_CHANGES__ENABLED
to "true"
- enable by setting
- upgrade the runtime to version 1.5.6
- required setting the PLATFORM_CLIENT_ID and PLATFORM_CLIENT_SECRET
- upgrade the runtime to version 1.5.5
- upgrade the runtime to version 1.5.4
- provided openapi docs for the
/api/v1/Account/LastCompletedSyncRun
Route
- upgrade the runtime to version 1.2.0
-> SDK 1.0.1
- Added /api/v1/Account/LastCompletedSyncRun Route
- upgrade nodejs to 16.5.0
- tested on the new backend
- fix concurrent requests on the
/api/v1/Account/Sync
route