chore: remove the dead ECS deploy - #802
Conversation
The deploy targeted ECS cluster discordbot-cluster, which does not exist in any region of the account. The steps could never succeed, so the AWS credentials they consumed were liability with no upside. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe workflow removes production deployment actions from the .NET build job. It now performs dependency restore, compilation, and unit tests for all branches. ChangesCI workflow
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to The workflow continues validating the .NET project while removing obsolete production deployment actions and unnecessary administrator credentials. No merge-blocking risk is evident. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The deploy steps in this workflow target ECS cluster
discordbot-cluster, which does not exist. I enumerated every ECS cluster in all 17 regions of the account; the only one issecretpull.So these steps cannot have succeeded for some time, while still pulling
AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEYinto the job on every push to master. Those are organisation-level secrets, and the key behind them carries AdministratorAccess over the whole shared side-project account — Winpixies, secretpull, NosCoreLegend, cardscanner. A credential that broad, in a job that achieves nothing, is pure downside.Removes the three deploy steps. Build and tests are untouched.
NosCoreLambdasgets the same treatment for the same reason (itsnoscore-travisLambda is also gone). Once both merge, nothing in the org references those secrets and they can be deleted outright — which closes the finding without needing a key rotation.If the bot is ever revived, the replacement should be an OIDC role scoped to
repo:NosCoreIO/NosCoreBotwith ECR push onnoscorebotand nothing else.Summary by CodeRabbit