Flightcontrol changelog
Introducing Cost Budgets & Resource Tagging 🚀
Hello everyone! We're excited to announce our new cost alerts feature, which allows you to set a budget on a service, environment, or project and recieve alerts when your costs exceed (or are forecasted to exceed) your budget. We hope that this will bring you peace of mind when using Flightcontrol-managed AWS resources!
🚀 Features
Cost budgets & alerts
To use, locate the "Budget" tab in the "settings" sidepane for the entity you wish to budget
Only tracks Flightcontrol-managed resources
If using a sub AWS account, the cost reporting tags must be enabled in the root account (you should have already gotten an email about this)
Automatic tagging of all AWS resources
All AWS resources managed by Flightcontrol are now tagged with the following tags:
fc:id
fc:serviceId
fc:environmentServiceId
fc:environmentId
fc:previewEnvironmentId
fc:projectId
fc:awsAccountId
fc:organizationId
New configuration to disable auto invalidation of CloudFront on each deploy
⚙️ Improvements
Added new "Developer" user role that can create and update projects, environments, and services but cannot delete them. They can fully manage environment variables.
Add deployment reason to each card in the deployment list
Improve UX of number form fields
Major fixes and improvements to documentation of flightcontrol.json fields
🐞 Bugs
Fixed a bug where ECR images eventually became unavailable for services with many sequential failed deployments
Fix issue with preview environment env variable collision
Improved rate limiting handling
Misc fixes