All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Development environment settings
- Error handling in the Storage Service
- Resubscription logic in the abstract MQTT client
- Database
TIMESTAMPtypes (changed toTIMESTAMP WITH TIME ZONE) - Protobuf contracts
- Project dependencies
- .NET runtime version (upgrade from .NET 5 to .NET 6)
- Project dependencies
- Router contract package
- Project dependencies
- Gateway controller
- Router integration
- Authorization services
- Project dependencies
- Project dependencies
- Router project
- Unused code
- Unused dependency's
- Subscription count tracking
- Log scopes to the Live Data Service log template
- Subscription management service in the Live Data Service
- Project dependency's
- Live Data Service log statement template
- Exception handing to services
- Fatal to the background service when exceptions are not handled
- Timestamps to the live data service log statements
- Access modifier of the background servic execute method
- Live data service logging statements
- Project dependency's
- Caching of trigger actions in the Trigger Service
- Additional statistics types
- Statistics logging
- Logging in the Storage Service
- Router initialization routine
- The database function
generic_getblobs
- Unused code
- TriggerInvocations table
- TriggerInvocation pgsql functions
- Ability to disable data reloads in the message router
- Sensor commands when removing a user
- Trigger related repository's
- Trigger invocation creation database function
- Project dependency's
- The ability of the Network API to create trigger invocations
- Unused code
- Storage histogram
- Router command statistics/monitoring
- Trigger execution histogram
- Management SQL functions
- Improved router configuration
- Git ignore definition
- Live data service dependency's
- Development configurations
- Network API request auditting
- Unused code
- Unused configuration
- Timestamp variable to trigger message's
- Data contexts using native Npgsql functionality
- Retarget the authorization context to Npgsql
- Retarget the networking context to Npgsql
- Logging package references
- Hosting package references
- Remove references to Entity Framework Core
- Unused code
- Package dependency's
- Live data service authorization logging
- Live data authorization flow
- Live data sensor links
- Networking dabase integration in the live data service
- Routing cache
- Internal queue metrics
- Command subscription QoS levels (from 1 to 3)
- Load tests for new caches
- Ingress projects
- API projects (except the network API)
- Common projects (caching)
- Measurement query result JSON deserialization
- MeasurementQueryResult model annotations
- Unused configuration files
- Unused deployment configuration
- Hardcode swagger and/or open API scheme's
- Set HTTP as possible scheme
- Set HTTPS as possible scheme
- HTTPS swagger support
- Network API swagger
- Auth API swagger
- Data API swagger
- Auth API swagger
- Dashboard API swagger
- Encoding storage conversion
- Sensor creation flow: publish sensor keys on the MQTT broker
- Ingress router request metrics
- Egress router request metrics
- Script directory name
- MQTT service project files
- CI/CD pipelines
- Security policy
- CAKE build system
- Unused API code
- Update the versioning schema:
- Update version of the MQTT service
- Update the version of the core API's
-
Network:
- Network project setup
- Contracts project
- Solution folders for:
- Database project
- General files
- Message router
- Network API + Gateway
- Networking database:
- Trigger administration
- Sensor link administration
- Live data service
-
Platform:
- Moved MQTT ingress service
- Forward MQTT ingress to the HTTP gateway
-
API:
- Refactor SensateService into SensateIoT.API
- Upgrade API's to .NET 5
- Improve swagger documentation
- Trigger administration (moved to network project)
- Network API (moved to network project)
- Trigger service (moved to network project)
- Live data service (moved to network project)
-
API's:
- Network API
- Data API
- Authorization API
- Blob API
- Dashboard API
-
Ingress services
-
Data processing