@turbot/aws-elasticbeanstalk

Recommended Version

Version

5.2.0

Released On

Apr 16, 2021

Depends On

We've improved the state reasons and details tables in various Approved and Active controls to be more helpful, especially when a resource is unapproved or inactive. Previously, to understand why one of these controls is in Alarm state, you would need to find and read the control's process logs. This felt like too much work for a simple task, so now these details are visible directly from the control page.

The AWS > Elastic Beanstalk > Environment > Approved control will now not attempt to delete an environment if the environment's Status is not Ready.
For an application that had a version deployed to a running environment, the AWS > Elastic Beanstalk > Application > Approved control would incorrectly try to delete that application if the AWS > Elastic Beanstalk > Application > Approved policy was set to Enforce: Delete unapproved if new. This is now fixed.

Controls run faster now when in the tbd and skipped states thanks to the new Turbot Precheck feature (not to be confused with TSA PreCheck). With Turbot Precheck, controls avoid running GraphQL input queries when in tbd and skipped, resulting in faster and lighter control runs.

We've made some improvements to our real-time event handling that reduces the risk of creating resources in CMDB with malformed AKAs. There's no noticeable difference, but things should run more reliably now.

Discovery controls now have their own control category, CMDB > Discovery, to allow for easier filtering separately from other CMDB controls.
We've renamed the service's default regions policy from Regions [Default] to Regions to be consistent with our other regions policies.

In various Active controls, we were outputting log messages that did not properly show how many days were left until we'd delete the inactive resources (we were still deleting them after the correct number of days). These log messages have been fixed and now contain the correct number of days.

Sometimes when updating CMDB for resources with tags that have empty string values, e.g., [{Key: "Empty", Value: ""}, {Key: "Turbot is great", Value: "true"}], we would not store all of the tags correctly. This has been fixed and now all tags are accounted for.

Deleting an Elastic Beanstalk application from the AWS console did not remove it from the CMDB. This issue has now been fixed.
Links to documentation in the descriptions for several controls and policies were broken. These links have now been fixed.