yipit/awslimits

awslimits's Issues

Deployment docs?

So... I think I really want to take this project for a spin, and possibly start using it at $WORK instead of raw awslimitchecker. We've been toying with the idea of adding support to open limit increase tickets automatically, but the fact that awslimits has a pretty UI and updates limit values by parsing tickets is pretty cool.

Would it be possible to get some docs - even just an unofficial quick explanation - of how you're deploying and running this?

Also, just for clarification, am I correct that:

1. this currently only supports a single account, and
2. sendgrid is the only supported email provider?

Thanks!
-jantman

Assume role for boto client and AwsLimitChecker

Add support to use multiple AWS accounts

We currently support one region and one AWS account. It'd be nice to support multiple accounts and eventually multiple regions.

Create manager command for refresh_data

@spulec @hltbra Do you think we should get rid of the Refresh Data button and route entirely or would you still like the option to manually refresh in addition to a cron job?

Send alerts for limits with high percent_used

limit source information

This project looks really cool - I looked at the screenshots in #1, and it looks quite interesting.

Before this gets too mature, though, could you please place a notice on any pages that show data derived from awslimitchecker (ideally linking back to the project), as required by the license? I'd be happy to open a PR for this if desired... my gut reaction would be a footer with something to the effect of "Limit values and usage calculated by awslimitchecker version ", but obviously the wording is up to you.

Thanks,
Jason

Refresh data resets the current_limit

It should only reset the current_usage if the limit is already in the database

Support tickets don't refresh

They stay in the state as when they were initially loaded. See here.

One solution is to just remove that line and always repost updated ticket data. Another would be to check if anything has changed and conditionally repost.

Add way to ignore support ticket

Some support tickets get closed without increasing any limits. It would be nice to have an option to ignore these. Maybe as simple as another option in the dropdown?

ZeroDivisionError when current_limit == 0