docs: add Angular signals troubleshooting and template guide
docs: add Keycloak auth, rproxy details, penguin-analytics to architecture diagram
docs: add MongoDB migration patterns and troubleshooting
docs: add Reverse Proxy Configuration page
docs: add penguin-analytics GeoIP and database password troubleshooting
docs: add quick reference for version tag format in deployments
docs: add ANALYTICS_TRAFFIC_TRACKING to analytics documentation - Add traffic tracking flag to Analytics-Architecture.md - Document 7 traffic channels: chatbot, direct, email, internal, referral, search, social, other - Add traffic source properties table (traffic_channel, traffic_source, traffic_medium, etc.) - Update privacy flags table to include traffic tracking - Update environment configuration matrix with traffic tracking defaults
docs: add Keycloak client ID troubleshooting for eagle-admin
docs: simplify eao-nginx sections, remove redundancy
docs: add eao-nginx 504 network policy troubleshooting Document 504 Gateway Timeout issue on admin routes caused by incorrect pod labels not matching NetworkPolicy requirements. Includes diagnosis steps, solution, and verification commands.
docs: add rproxy 503 config missing troubleshooting section
docs: split Configuration-Management, add Keycloak-Configuration
docs: update analytics documentation with two-tier privacy system - Add comprehensive Two-Tier Privacy System documentation - Document initContainer architecture for GeoIP databases - Update GEO_ENRICHMENT_ENABLED section with database update commands - Add Mermaid diagrams for privacy flow - Add data collected examples for each privacy mode - Link to penguin-analytics wiki for implementation details Analytics now uses: - Client tier: ANALYTICS_ENHANCED_TRACKING (eagle-api) - Server tier: GEO_ENRICHMENT_ENABLED (penguin-analytics) Both must be true for full enrichment (dev/test defaults).
docs: update Configuration-Management with enhanced analytics - Document ANALYTICS_ENHANCED_TRACKING flag (client-side browser context) - Document GEO_ENRICHMENT_ENABLED flag (server-side IP geolocation) - Add full property examples for enhanced vs privacy mode - Explain two-tier privacy model: client opt-in + server enrichment - Add implementation details for eagle-public and penguin-analytics - Link to penguin-analytics GeoIP documentation
docs: streamline Analytics-Architecture for EPIC focus - Move detailed Penguin Analytics docs to penguin-analytics wiki - Keep only EPIC-specific integration patterns - Focus on why /analytics is separate from /api - Document eagle-admin and eagle-public configuration - Link to Penguin Analytics wiki for complete docs
docs: add smartscalar duration formatting pattern - Document that number_style: duration doesn't work with smartscalar - Add solution: convert to minutes in SQL, use suffix formatting - Note applies to Metabase v0.58 Trend visualizations
docs: add Trend visualization documentation Add section explaining smartscalar (Trend) visualizations: - How Trend compares most recent row to previous row - GROUP BY granularity controls comparison period - Week-over-week, month-over-month examples - Critical requirement: no date filters (need all data for comparison) - Configuration patterns and best practices
docs: update Metabase dashboard configuration examples - Document 24-column grid layout (sizeX: 6 = quarter width) - Show app.prefix as optional (empty string for no prefix) - Add default filter value examples (past7days) - Include complete dashboard card layout example
docs: update Metabase configuration patterns for date shortcuts - Document dimension-type template tags for date/all-options support - Add table showing filter types and template tag requirements - Update YAML examples with dimension type and field lookups - Explain array value parsing for dashboard shortcuts
chore: remove claude.md from gitignore
docs: add Keycloak configuration and troubleshooting - Document Keycloak realm (eao-epic) and client IDs - Explain ConfigService client ID preservation pattern - Add troubleshooting for 'Client not found' and realm errors - Include Helm configuration examples for eagle-api
chore: update gitignore
Merge branch 'master' of https://github.com/bcgov/eagle-dev-guides.wiki
docs: fix technical inaccuracies from audit - Fix penguin-analytics port: 3001 → 3000 (verified against Helm charts) - Correct eagle-admin Node version: 24.x → 22.x (matches CI/CD) - Update eagle-api package manager: npm → Yarn 4.12.0 - Add Node version specifications to Architecture-Overview.md - Clarify test framework differences (Vitest/Karma/Mocha) per repo - Add penguin-analytics to sidebar navigation All changes verified against actual codebase configuration.
Document rproxy 502 issue after Service recreation
Document Helm upgrade in test workflows for reproducibility
Document migrations disabled by default for eagle-api Updated documentation to reflect that migrations are disabled by default since all existing migrations (2019-2020) have been applied in production. Changes: - Helm-Charts.md: Expanded migration section with when/how to enable - Troubleshooting.md: Updated to note migrations are disabled by default - Added instructions for enabling migrations when adding NEW migration files - Clarified one-time operation vs routine deployments
Revert Node version to 22 for eagle-api - Packages were already upgraded to support Node 22 - Updated Deployment-Pipeline.md and Helm-Charts.md with correct version
Update documentation for eagle-api modernization - Added migration job documentation to Helm-Charts.md - Added database migration troubleshooting to Troubleshooting.md - Documented pre-upgrade hook pattern for MongoDB migrations - Removed outdated DeploymentConfig/S2I references for eagle-api
docs: update for eagle-api Node 22 upgrade and Helm migration - Update eagle-api Node version from 16 to 22 LTS - Document Helm chart adoption (Feb 2026 migration) - Add eagle-api local development setup instructions - Document key dependencies: axios, sharp 0.33.5, jwks-rsa 3.2.2 - Mark API-Deployment.md as legacy (use Deployment-Pipeline instead) - Add eagle-api specific Helm configuration details