Created an ECS task definition for cleanup job and used AWS EventBridge Scheduler to run it every 24 hours.
Depends on D9414
Details
Details
- Reviewers
varun michal • jon - Commits
- rCOMM053da35e00ba: [terraform] Add blob cleanup cron task
Tested on staging during the weekend. The cleanup job is being run periodically and succeeds.
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
| services/terraform/remote/service_blob.tf | ||
|---|---|---|
| 2 ↗ | (On Diff #31792) | This is only to reflect current terraform state on staging. I'll revert this in favor of D9416 |
| services/terraform/remote/task_blob_cleanup.tf | ||
| 18 ↗ | (On Diff #31792) | This can be reverted to just "info" although I consider it helpful when testing on staging |
| services/terraform/remote/task_blob_cleanup.tf | ||
|---|---|---|
| 18 ↗ | (On Diff #31792) | What does the info in info,blob=trace mean? |
| services/terraform/remote/task_blob_cleanup.tf | ||
|---|---|---|
| 18 ↗ | (On Diff #31792) | Set global log level to info, but for blob crate only override level to trace. And for comm_services_lib namespace logs set the level to debug. This lets us see only blob service debug logs, without spam from aws-sdk-*, hyper and all these libs. |
| services/terraform/remote/task_blob_cleanup.tf | ||
|---|---|---|
| 18 ↗ | (On Diff #31792) | Ohh it's not one info,blob=trace expression but separate info and blob=trace expressions, got it 🤦 |