Skip to content

v0.8.0
Compare
Choose a tag to compare
@kjlippold kjlippold released this 25 Apr 20:45
· 53 commits to main since this release
v0.8.0
fa646e1
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's Changed

This release corresponds to Milestone v0.8.0.

  • #40 - Added API endpoints to create and manage user API Keys as an alternate form of authentication and authorization. Frontend management pages for API Keys and integration with other tools such as the Streaming Data Loader will be included in a future release.
  • #108 - Added a deployment setting DISABLE_ACCOUNT_CREATION that can be used to disable public account creation for HydroServer deployments.
  • #139 - Added a data visualization page. This page significantly improves users' ability to view data hosted by HydroServer.
  • #143 - Added abort controller to improve frontend performance.
  • #147 - Removed AWS dependencies in the backend codebase.
  • #149 - Added API filter option to fetch metadata for all users rather than just the authenticated user.
  • #154 - Removed OAuth controls and endpoints for deployments where OAuth is not configured.
  • #155 - Added custom SMTP deployment settings to remove dependency on AWS SES service.
  • #158 - Updated documentation to include the new visualization page.
  • #159 - Improved visualization page datastream filtering.
  • #160 - Fixed several minor backend issues related to the visualization page.
  • #161 - Fixed several minor frontend issues related to the visualiztion page.
  • #163 - Fixed an issue where some SensorThings endpoints would return a 500 code instead of a 404 code.
  • #165 - Additional minor enhancements to the visualization page.

Deployment Note

The deployment setting DEPLOYED has been changed to DEPLOYMENT_BACKEND. DEPLOYMENT_BACKEND should be a string value, and at the moment only two are supported; aws and local, with local being the default. New deployments will automatically be built with this new setting. If you already have an AWS deployment, you will need to change this setting in your ElasticBeanstalk configuration: DEPLOYED=True → DEPLOYMENT_BACKEND=aws

Assets 2
Loading