Releases: nmshd/backbone
Releases · nmshd/backbone
Consumer API v1.3.1
Helm Chart v1.1.0
What's Changed
New Features
- Add Azure support by @tnotheis in #231
It is now possible to deploy the Helm Chart to Azure and use things like Azure Ingress
Full Changelog: helm/v1.0.1...helm/v1.1.0
Consumer API v1.3.0
What's Changed
New Features
- Direct PNS communication by @tnotheis in #232
It is now possible to configure the Consumer API to send its push notifications directly via FCM/APNs
Bug Fixes
- DbContext tries to create untracked tier instead of using existing entity by @Dannyps in #204
- Missing CorrelationId in logs by @Dannyps in #228
- Getting file metadata leads to socket hang up by @tnotheis in #237
Full Changelog: capi/v1.2.1...capi/v1.3.0
Admin UI v1.2.0
What's Changed
New Features
- Listing of Tier Quotas by @JLSRKonk in #198
- Quota on Number of Files by @Dannyps in #218
- Deletion of Tier Quotas by @JLSRKonk in #219
- Quota on Used File Storage Space by @Dannyps in #220
- Quotas for identities by @daniel-almeida-konkconsulting in #226
- Quota on Number Of Relationships by @Dannyps in #222
- List identity quotas by @JLSRKonk in #230
- Delete identity quotas by @daniel-almeida-konkconsulting in #227
- Quota on Number of Tokens by @JLSRKonk in #235
Bug Fixes
- DbContext tries to create untracked tier instead of using existing entity by @Dannyps in #204
- Missing CorrelationId in logs by @Dannyps in #228
Full Changelog: aui/v1.1.1...aui/v1.2.0
Helm Chart v1.0.1
Consumer API v1.2.1
Admin UI v1.1.1
What's Changed
This update only contains some internal changes to stay consistent with the Consumer API.
Helm Chart v1.0.0
What's Changed
This is the first official version of the Backbone Helm chart. It contains the Consumer API, the Admin UI, as well as the Admin CLI.
Admin UI v1.1.0
What's Changed
New Features
- API key authentication by @daniel-almeida-konkconsulting in #194
The Admin UI can now be secured with an API key. To do so, set theauthentication.apiKey
configuration value to the desired key.
Consumer API v1.2.0
What's Changed
New Features
- Make configuration of a JWT Signing Certificate optional for development scenarios by @tnotheis in #101
It is now possible to omit the JWT Signing Certificate from the configuration. In this case a temporary certificate is used to sign the JWTs. It is NOT recommended to do this in production scenarios. To prevent accidental misconfiguration, the server won't start if ASPNETCORE_ENVIRONMENT is set to Production and there is no JWT Signing Certificate configured - Request cancellation support by @filipemmagalhaes in #126
If you now cancel an HTTP request to the Consumer API, any triggered actions will be cancelled at the next opportunity. - "Data" property for HTTP errors by @filipemmagalhaes in #136
Errors returned in an HTTP response now may have aData
property, which contains error specific properties. It depends on the error code whether such data is available or not.
Full Changelog: capi/v1.1.0...capi/v1.2.0