Skip to content

LCM - Pool week March 2026 #303

@sebastianvitterso

Description

@sebastianvitterso

Checklist

NOTE: Don't delete the production database

Dependencies

IMPORTANT: Test the relevant parts of the application to ensure compatibility with the new updated versions.

  • Update dependencies (poetry, npm, etc.)
    • api/pyproject.toml
    • web/package.json
  • Update pre-commit
  • Update GitHub Actions
  • Update docker images (base image and interpreter, build without cache, Radix component images)
  • Update python-version to 3.14

Secrets

  • Please check for any secrets that require rotation and update as needed.
  • Identify any secrets missing or outdated in the Key Vault
  • Check GitHub security for issues
    • Check CodeQL is enabled

Access control

Use these groups to give access to Team Hermes members.

  • Review the list of users and remove those who should not have access.
    • Azure App Registrations
    • Azure Subscriptions
    • Radix Admin Group
    • Github Repository Access

Runbook

NOTE: Do not test out the procedures described in the runbook unless you have available time.

  • Shown in Varia
  • Update the runbook to follow the Runbook template
  • Review the runbook documentation for outdated content and update any steps or documentation that are no longer accurate.
  • Check that the procedures described in the Runbook work (e.g. Bicep, scripts, backup, etc.)

Readme.md

  • Review for outdated content and update any steps or documentation that are no longer accurate.

Project

NOTE: Do not prioritize bug fixes or reduce technical debt (unless you have available time).

  • Check for any open issues that can be closed or require action.
  • Do simple bug fixes
  • Reduce technical debt

Repository

Data

  • Confirm regular backups are occurring without issues

Cost Management

  • Check for underutilized resources and consider downscaling or removal to reduce costs.
  • Review current spending against the budget and adjust forecasts as necessary

System Health

  • Check the performance metrics and ensure they are within acceptable thresholds
  • Ensure that monitoring and alerting systems are operational and configured to notify the team of any potential issues promptly.
    • Add AppInsights to frontend.

Short summary

General impression of project status (technical debt)
Project still runs a Flask api, which we could consider replacing with FastAPI, since we use that for all our other projects. Could be done as a main task for next pool week.

Issue board has old issues, but we don't know if they are "outdated" in the sense that the stakeholders no longer want them done.

Any actions identified that need to be taken later

  • Replace Flask with FastAPI (?)
  • Ask TCP about issues on the board

Metadata

Metadata

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

Status

In progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions