v3.4.3

What's Changed

• Use custom migrate binary to resolve Flyway vulnerability

• Enhancement/embedded migrations by @dennisgsmith in #240

Full Changelog: v3.4.2...v3.4.3

v3.4.2

What's Changed

• Keycloak Token Claim Hotfix by @dennisgsmith in #236
• Fix New Profile Creation Regression by @dennisgsmith in #237
• Add build-time tags by @dennisgsmith in #238

Full Changelog: v3.4.1...v3.4.2

v3.4.1

What's Changed

• limit keycloak login account email by @dennisgsmith in #233
• Patch: Whitelist allowed email from Keycloak token claims by @dennisgsmith in #234
• Enforce email suffix by @dennisgsmith in #235

Full Changelog: v3.4.0...v3.4.1

v3.4.0

What's Changed

• Fix Instrument Uploader; Instrument Assignment Validation Bug Fixes by @dennisgsmith in #219
• update CreateUser to use cacUID for EDIPI lookup by @dennisgsmith in #222
• Enhancement/request id logging by @dennisgsmith in #225
• Add Plot Types by @dennisgsmith in #226
• Fix new plot type bugs by @dennisgsmith in #230
• Add CWMS Data API Timeseries Integration by @dennisgsmith in #227
• Release v3.4.0 by @dennisgsmith in #231

Changes pending infrastructure updates

• add report config database models and crud apis by @dennisgsmith in #216
• PDF Report Renderer Feature by @dennisgsmith in #220
• Enhance Report Renderer Template by @dennisgsmith in #221

Technical updates

• Mock login.gov auth with local Keycloak instance by @dennisgsmith in #224
• Bump golang.org/x/image from 0.15.0 to 0.18.0 in /api by @dependabot in #223
• update to aws-sdk-v2; update dcsloader test by @dennisgsmith in #218

Full Changelog: v3.0.1...v3.4.0

v3.0.1

What's Changed

• Remove timeseries measurement BTREE/BRIN indexes by @dennisgsmith in #211
• Fix Telemetry API empty table bug; Add alert check image certs; Remove stable dev environment references by @dennisgsmith in #212

Full Changelog: v3.0...v3.0.1

v3.0

What's Changed

• update ipi fields by @dennisgsmith in #195
• fix bug with duplicate initial time in saa/ipi by @dennisgsmith in #196
• fix linting (type hinting) in python script by @dennisgsmith in #197
• Feature/multiple equivalency table v2 by @dennisgsmith in #198
• fix/equivalency table datalogger responses by @dennisgsmith in #199
• fix invalid swaggerdoc generation by @dennisgsmith in #202
• enhancement/domain map by @dennisgsmith in #201
• fix plot config update bug by @dennisgsmith in #203
• add ./compose.sh watch command for core api development by @dennisgsmith in #205
• feature/api image upload by @dennisgsmith in #206
• add default mdi icon mappings by @dennisgsmith in #207
• Enhancement/query project by user role by @dennisgsmith in #208
• feature/instrument project decouple by @dennisgsmith in #204
• Fix/instrument project create assign by @dennisgsmith in #209
• MIDAS 3.0 Release by @dennisgsmith in #210

Full Changelog: v2.1.0...v3.0

v2.1.0

What's Changed

• Feature/depth based instruments v2 by @dennisgsmith in #192
• 2.1.0 Release by @dennisgsmith in #194

Full Changelog: v2.0.0...v2.1.0

v2.0.0

Major release 2.0.0 signifies a significant restructuring of the codebase and application architecture in order to overcome technical debt. See #191 for complete release notes

What's Changed

• Add aarch64 compatibility by @dennisgsmith in #185
• Scaffold/restructure go by @dennisgsmith in #186
• SAA Timeseries Mapping by @dennisgsmith in #187
• MIDAS API 2.0 by @dennisgsmith in #191

Full Changelog: v1.9.1...v2.0.0

v1.9.1

Description

• Added "Submittals" concept for tracking historical intervals within alert configs
  • Users have the ability to fulfill submittals when submitting evaluations
  • "Submittals" for time series measurements will be automatically completed at their due date based on the condition defined within the "Alert Configuration"
  • If an "Alert Config" interval is updated, and the new due date is in the past, the API will return an error and the transaction will rollback
• Added /district_rollup/* API endpoints for Evaluation and Measurement submittals
• Added /districts endpoints
• Added "Mute Consecutive Alerts" option to alert config
• Removed "Number of Missed Intervals Before Alert" as it's purpose is replaced with the above option
• Fixed bug causing consecutive alerts after a reminder is triggered

What's Changed

• Fix Alert Check Measurement Regression by @dennisgsmith in #182
• Feature/district rollup by @dennisgsmith in #184

Full Changelog: v1.9.0...v1.9.1

v1.9.0

QA/QC Tab: Evaluations and Alerts

Summary

This release adds the ability for users to:

• Create "Evaluations" for quality assurance
• Create and update (Project Admin Only) "Alert Configs" with trigger conditions for the timely submittal of timeseries measurements and evaluations
  • Assign email warnings/alerts/reminders to users when evaluations or measurements are passed the prescribed interval

Alert Config Description

• When a Warning is triggered, the Alert Config status is set to Yellow.
• When an Alert is triggered, the Alert Config status is set to Red.
• Otherwise, the Alert Config status will be Green.
• The Reminder will only be triggered after an alert maintains the Red status for a time period greater than or equal to the Reminder Interval setting. The reminder email time is determined based on the Alert Check Start Date time, plus the Schedule Interval.
• To turn off Warnings or Reminders, set the interval quantity to 0. A Schedule Interval greater than 0 is required.
• To extend an alert interval to allow for missed conditions, use the Number of Missed Intervals to Trigger Alert setting as a multiplier for the Schedule Interval.
• At least one stored MIDAS email must be used in order to complete an Alert Config.
• The scheduler “ticker” resolution is currently set to 15-minute intervals. This means that an alert status may take up to 15 minutes to update after measurements or evaluations are submitted or missed. This interval is externally triggered and can be set for an arbitrary amount of desired time if there is a more appropriate interval
• Currently, Timeseries Measurement Submittals will NOT sent alerts if NO timeseries exist within the assigned instrument(s). A timeseries must exist for the system to check if it has measurements uploaded or not.

Example:

Schedule Interval: 1 day after the Alert Config creation time, if no evaluation has been submitted, send an alert email.
Warning Interval: 6 hours prior to when the alert will be sent, a warning email will send.
Reminder Interval: 0 days (no reminders will be sent)
Number of Missed Intervals to Trigger Alert: 1x (default, this is the most common case)

Evaluation Sumbittal

A warning and alert will be triggered if an Evaluation tagged with this Alert Config has not been submitted within the defined intervals.

Timeseries Measurement Submittal

Works similarly to an Evaluation Submittal, with the difference being that the status is determined by the timely upload of ALL timeseries measurements for the instruments selected below, within the prescribed Schedule Interval. If any of the timeseries measurements within an instrument do not meet this criteria, an email warning and/or alert will be triggered with the offending timeseries in the body of the email. For automated uploads, this schedule interval may be shorter, whereas manual uploads may generally have larger schedule intervals and include warnings.

What's Changed

• add build process for ironbank images by @dennisgsmith in #179
• Feature/quality check tab by @dennisgsmith in #176
• Migrate from AWS SES SDK to net/smtp by @dennisgsmith in #181
• QC/Alert Feature; Ironbank builder script by @dennisgsmith in #180

Full Changelog: v1.8.1...v1.9.0