2026-08-24 CDA Doc Endpoints Meeting

Intro

  • Dev CDA instance has login page now and listing of users endpoint
  • List of emails for a given office for user lists.
    • These are authenticated / private
    • Can be established on an office basis, can be viewed cross-offices.
    • Dependent on dev database update
    • Ex uses, list of admins, web devs, internal lists of users. External app can use list of users to obtain emails to be sent out via batch.
      • Question on mailer daemon used: getting email can be a problem, does this solve that? Able to mail to public and usace?
        • Intended to run on CWMS Batch, a few layers away from DB.
        • Not public given it pulls emails from CAC listing
        • Charles has another mechanism for adding in public users.
        • CWMS batch pull 186.
        • Target is Q2 of next year, waiting on changes on dev infrastructure.
    • /user/list series of endpoints
      • Can the version of CWMS DB schema be exposed?
    • Feature Flag (FF) enabled

Field Issues

  • Question to Ivan N on status. 
    • Saturday night report (~10PM) not working, synch to prod issue. Already resolved this morning. This is the second instance of this issue. 
    • Gap in data? Not sure. 
    • Eric N: Confirmed that some may have been down over the weekend.
      • The files are saved such that when the system is brought back up there is no gap.
      • Sometimes there is a larger issue that does cause a gap.
  • T7 use of current CDA release? Anyone using 8/14 release? Mitch W asked.
    • Mitch hasnt tried it asking if others have.
    • Charles' version
    • Swagger shows version on header
    • Wiki includes update instructions.
      • Also requires new keys, this was updated into Wiki instructions.
    • Troy W, stating that new keys need to be generated with this new version of CDA after May 2026. 
      • If you have already updated your keys, you do not necessarily need to do this. Doesn't hurt though.
    • Server versions run are sent out, apache, python, mod_wsgi, php, openssl.
      • Versions is authenticated as it can allow targeting of vulnerabilities
  • Tracy F: When to update CDA version?
    • To get access to newer features. 
    • Database API can dictate slower pace to match stable CDA releases.
    • Not everything is running in dev yet.
    • T7 is production database access. Supports usage of CDA locally to run against prod.
  • Troy W: Outage, general update caused a version conflict in feature not ready to go. Resulted in failure of system that was too late to avoid. 
    • Best version to do update with is important and needs to be marked clearly. Avoid test versions.
      • Better versioning standards are needed to inform userbase on risk related to version usage?
    • Look at cwms-data version to determine what to use. Can also rollback.
      • Warning: before updating, note what you are currently using.
      • From releases→choose version->assets→war file url copy link, go to wiki → installing CDA → should have the WAR file link at end of update_cda.sh.
    • Warning: Latest is used by default, which can be unwanted. Instead grab a explicit version.
      • Revise script to examine whether latest should be default.
    • Deploy script does make a backup of current version.

Endpoint and Documentation Review

  • Ratings documentation PR reviewed, CDA Issue 1513.
  • Question on linking to docs on Swagger? Can this be done?
    • Can naming be used to infer linkage between Read the Doc and Swagger?
    • CDA issue created: 1892 for this.
    • Example shown on Offices Swagger, "Feature #321", CSS blocking it being shown as link.
      • CSS being blocked needs to be captured as an issue.

Issues

  • Issue 1804: 500 error for post ratings (T7 only)
      • Adam Korynta  post update on issue status to ticket please.
    • Priority update to blocker, this is preventing operations for him.
    • Ivan and Mitch are looking into this.
    • Alan ? having issue pulling USGS rating and saving to DB.
    • Ivan uses this endpoint to update rating to control active flag.
  • Issue 1874: post multiple stream locations in a single request.
    • Is there a multi-store for this?
    • /stream/locations endpoint get returns a set, why cant a set be posted back using the get endpoint results
    • Theresa wrote a script to accomplish this.
      • Confusion over get one vs get all
    • Clarification on AQJMS Queue being used for retrieving events.
      • Events might be created, deleted, etc.
      • ADR PR 1883 being authored by Mike P right now. Asked community to look at PR and provide suggestions on events desired.
  • Move notes to Confluence?
    • Would need to be public space.
    • Community would not be able to edit in Confluence, can edit in Wiki.
    • Charles would bring existing notes over to public space.



=== previous meeting ===

07/27/2026 - LRTS, Stream Locations

  • How to ensure your TS is setup if it is LRTS so you will not have to rename it
    • PRTS to LRTS transition
      • is there a timeline for this implementation? are offices going to be required to switch? Pending HEC timeline/decision
      • Local means the timeseries LRTS will follow a given location's timezone. Will want to make sure you have location TZ set in CWMSVue.
    • Should JSON tell if it's seconds or minutes?
    • Future potential to have a district show how they use LRTS (SWF)
  • Notes about PRTS / LRTS with the recent 1Mil PR
  • Converting SITE to STREAM LOCATION
    • POST to /stream-location would ideally (or should) convert a base site over for you to that kind
    • /stream-location is a different table, to go back to SITE you would delete the STREAM LOCATION entry (with options to be specific on delete)
    • Not 100% if work was added/done yet for the ability to create location-kind (i.e. not SITE) in the creation of a location (POST) but not the entry in the table (yet) : Term is "marker", marked as being this kind
  • Bump issues #1818 and #1802