Skip to main content

DevOps Governance Tickets

Committee Formation​

📋 JIRA-DEVOPS-001: Establish DevOps Governance Committee​

Status: DRAFT - Not Created Description: As the project has grown into multiple codebases and deployment pipelines, so has the number of DevOps-related failures and downtime. A formal committee is needed to standardize processes and act as a decision-making body.

Tasks:

  • Draft committee charter and responsibilities
  • Confirm members: Management (Thomas - optional), SWE (Chip), UI (Lena - optional), HAE (Iannick)
  • Create #devops-governance Slack channel
  • Set up recurring calendar invites
  • Create documentation repository
  • Document decisions and rationales

📋 JIRA-DEVOPS-002: Define DevOps Best Practices​

Status: DRAFT - Not Created Description: Document standardized processes for CI/CD, architecture, infrastructure management, and release strategies, ensuring alignment across all services.

Tasks:

  • Document CI/CD pipeline standards
  • Create architecture decision record (ADR) template
  • Define infrastructure management guidelines
  • Document release strategy standards
  • Create emergency change process
  • Make documentation available to all developers

Environment Standardization​

✅ JIRA-DEVOPS-003: Standardize Dev/Staging/Production Environments​

Status: CREATED - In Progress Jira Ticket: ED-12 Description: We don't have dev, staging, production which are exactly identical from a DevOps perspective. Really really identical - that is the issue we faced recently. They were set up manually differently. Some of it was done by code and some was done manually which caused problems.

Tasks:

  • Audit current environment configurations
  • Document all manual configurations
  • Convert manual configs to Infrastructure as Code
  • Implement environment parity validation
  • Create environment sync process
  • Test environment consistency
  • Create runbook for environment setup

✅ JIRA-DEVOPS-004: Implement GCP Log-Based Alerting​

Status: CREATED - In Progress Jira Ticket: ED-6 Description: Implement an alerting mechanism on GCP based on logs so that way we know immediately if we have an issue.

Tasks:

  • Define alert criteria and thresholds
  • Configure log-based metrics in GCP
  • Set up alerting policies
  • Create alert routing rules
  • Implement alert escalation
  • Test alert delivery channels

✅ JIRA-DEVOPS-005: Implement Comprehensive Health Check System​

Status: CREATED - In Progress Jira Tickets:

  • ED-3 - Uptime and Database Health Checks
  • ED-4 - PubSub Health Check
  • ED-5 - Email Service Health Check Description: Implement a full health check monitoring system for everything - database, pub/sub, emailing, logging. Currently there's no unified way to verify operational status.

Tasks:

  • Create /health endpoints for all services
  • Add database connectivity checks
  • Implement pub/sub health validation
  • Add email service health checks
  • Create logging system health checks
  • Build centralized health dashboard
  • Implement health-based alerting

📋 JIRA-DEVOPS-006: Implement Infrastructure as Code​

Status: DRAFT - Not Created Description: Eliminate manual configuration drift between environments by codifying all infrastructure.

Tasks:

  • Inventory all manually configured resources
  • Write Terraform for all infrastructure
  • Create environment-specific tfvars files
  • Implement state management per environment
  • Add validation tests
  • Document deployment procedures
  • Train team on IaC practices