0.9.0 Released 2017-06-11

• Issue #269 - set Trusted Advisor limit name overrides for some RDS limits that were recently added to TA, but with different names than what awslimitchecker uses.
• Fix bug Issue #270 -do not count propagated routes towards the VPC “Entries per route table” limit, per clarification in VPC service limits documentation (“This is the limit for the number of non-propagated entries per route table.”)
• PR #276 / Issue #275 - Add new --skip-service CLI option and :py~.AwsLimitChecker.remove_services to allow skipping of one or more specific services during runs. (Thanks to tamsky) for this contribution.)
• PR #274 / Issue #273 - Add support for new i3 EC2 Instance types. (Thanks to tamsky) for this contribution.)
• Fix broken docs build due to changes Intersphinx reference to ValueError in python2 docs
• Add hack to docs/source/conf.py as workaround for sphinx-doc/sphinx#3860
• Issue #267 - Firehose is only available in us-east-1, us-west-2 and eu-west-1. Omit the traceback from the log message for Firehose EndpointConnectionError and log at warning instead of error.

0.8.0 Released 2017-03-11

This release includes a breaking API change. Please see the first bullet point below. Note that once 1.0.0 is released (which should be relatively soon), such API changes will only come with a major version increment.

This release requires new IAM permissions: redshift:DescribeClusterSnapshots and redshift:DescribeClusterSubnetGroups.

This release removes Python 3.2 support. This was deprecated in 0.7.0. As of this release, awslimitchecker may still work on Python 3.2, but it is no longer tested and any support tickets or bug reports specific to 3.2 will be closed.

• PR #250 - Allow the --service command line option to accept multiple values. This is a breaking public API change; the awslimitchecker.checker.AwsLimitChecker check_thresholds, find_usage, and get_limits methods now take an optional service list keyword argument instead of a string for a single service name.
• PR #251 - Handle GovCloud-specific edge cases; specifically, UnsupportedOperation errors for EC2 Spot Instance-related API calls, and limits returned as 0 by the DescribeAccountAttributes EC2 API action.
• PR #249 - Add support for RedShift limits (Redshift subnet groups and Redshift manual snapshots). This requires the redshift:DescribeClusterSnapshots and redshift:DescribeClusterSubnetGroups IAM permissions.
• Issue #259 - remove duplicates from required IAM policy returned by awslimitchecker.checker.AwsLimitChecker.get_required_iam_policy and awslimitchecker --iam-policy.
• Various TravisCI/tox build fixes:
  • Fix pip caching; use default pip cache directory
  • Add python 3.6 tox env and Travis env, now that it’s released
  • Switch integration3 tox env from py3.4 to py3.6
• PR #256 - Add example of wrapping awslimitchecker in a script to send metrics to Prometheus.
• Issue #236 - Drop support for Python 3.2; stop testing under py32.
• Issue #257 - Handle ElastiCache DescribeCacheCluster responses that are missing CacheNodes key in a cluster description.
• Issue #200 - Remove EC2 Spot Instances/Fleets limits fro

0.7.0

This release deprecates support for Python 3.2. It will be removed in the next release.

This release introduces support for automatically refreshing Trusted Advisor checks on accounts that support this. If you use this new feature, awslimitchecker will require a new permission, trustedadvisor:RefreshCheck. See Getting Started - Trusted Advisor for further information.

• #231 - add support for new f1, r4 and t2.(xlarge|2xlarge) instance types, introduced in November 2016.
• #230 - replace the built-in versioncheck.py with versionfinder. Remove all of the many versioncheck tests.
• #233 - refactor tests to replace yield-based tests with parametrize, as yield-based tests are deprecated and will be removed in pytest 4.
• #235 - Deprecate Python 3.2 support. There don’t appear to have been any downloads on py32 in the last 6 months, and the effort to support it is too high.
• A bunch of Sphinx work to use README.rst in the generated documentation.
• Changed DEBUG-level logging format to include timestamp.
• #239 - Support refreshing Trusted Advisor check results during the run, and optionally waiting for refresh to finish. See Getting Started - Trusted Advisor for further information.
• #241 / PR #242 -Fix default ElastiCache/Nodes limit from 50 to 100, as that’s now what the docs say.
• #220 / PR #243 / PR #245 - Fix for ExpiredTokenException Errors. awslimitchecker.connectable.credentials has been removed. In previous releases, awslimitchecker had been using a Connectable.credentials class attribute to store AWS API credentials and share them between Connectable subclass instances. The side-effect of this was that AWS credentials were set at the start of the Python process and never changed. For users taking advantage of the Python API and either using short-lived STS credentials or using long-running or threaded implementations, the same credentials persisted for the life of the process, and would often result in ExpiredTokenExceptions. The fix was to move `_boto_conn_kwargs <http://awslimit