aprs.me/k8s
Graham McIntire 7e4bbbaff5
Fix deployment timestamp always showing 'less than a minute ago' in k8s
Previously, the deployment timestamp was set to DateTime.utc_now() when
the application started, which meant it would always show as recent in
k8s environments where pods are recreated on each deployment.

This commit:
- Updates Release.init() to check for DEPLOYED_AT environment variable
- Falls back to current time if env var is not set (backwards compatible)
- Adds proper ISO8601 timestamp parsing with error handling
- Updates GitHub Actions deploy workflow to set DEPLOYED_AT during deployment
- Creates k8s patch file for future manual deployments

The deployment timestamp will now persist across pod restarts in k8s,
showing the actual deployment time rather than pod startup time.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-07-28 12:06:12 -05:00
..
poddisruptionbudget.yaml Remove hardcoded Redis configuration from config.exs 2025-07-27 10:14:38 -05:00
README-migrations.md Implement distributed migration locking for cluster deployments 2025-07-27 10:41:36 -05:00
statefulset-deployed-at-patch.yaml Fix deployment timestamp always showing 'less than a minute ago' in k8s 2025-07-28 12:06:12 -05:00
statefulset-init-container-patch.yaml Implement distributed migration locking for cluster deployments 2025-07-27 10:41:36 -05:00
statefulset-patch.yaml Remove hardcoded Redis configuration from config.exs 2025-07-27 10:14:38 -05:00
statefulset-startup-probe-patch.yaml Remove hardcoded Redis configuration from config.exs 2025-07-27 10:14:38 -05:00