Turbot v5 Update Digest for 20 Oct to 26 Oct 2020

Current Recommended Versions

  • Turbot Enterprise (TE) 5.30.5
  • Turbot Enterprise Database (TED) 1.11.0
  • Turbot Enterprise Foundation (TEF) 1.26.3
  • Turbot Terraform Provider 1.6.3
  • Turbot CLI 1.24.2
  • Turbot Mod 5.27.0

Note: Turbot Customer Support recommends running the above versions as a “known good” configuration that incorporates the latest bug fixes and optimizations.

Highlights

  • Faster summary data loading for smoother browsing of resources, controls and policies.
  • Resource deletion is much faster, and scales to much larger environments.
  • Optimized performance across many GraphQL APIs and operations through careful analysis of queries and better data models introduced in v5.29.0.

Enterprise Highlights

  • Workspace upgrades can now check that they are coming from a minimum required version, smoothing the process for key release milestones when a workspace is far behind.
  • Worker lambdas now handle four tasks in parallel instead of 2, optimizing utilization.
  • Terraform stack container is much smaller, for faster startup and improved performance.

Alerts

Upgrade path to get to 5.30.5 from a TE version before 5.29.12:

  1. TEF 1.26.3
  2. TE 5.29.14
  3. Make sure that Turbot > Workspace > Migration control is in ok. Pause on this TE version till the migration control indicates “Migration Complete”, see screenshot.
  4. TE 5.30.2
  5. Make sure that Turbot > Workspace > Migration control is in ok. Pause on this TE version till the migration control indicates “Migration Complete”, see screenshot.
  6. TE 5.30.5
  7. Turbot Mod 5.27.0 (For customers already on a more recent version of the turbot mod, there is no need to downgrade. There are two new controls that depend on TE 5.31.0+. On previous TE versions, they will be in an error state but do no harm.)

AWS Mods

Highlights

  • In aws-iam: We’ve improved a few queries for the AWS > IAM > Group > Policy Attachments > Required, AWS > IAM > Role > Policy Attachments > Required and AWS > IAM > User > Policy Attachments > Required controls. There’s no noticeable difference, but things should run more smoothly now.
  • In aws-route53resolver: The AWS > Route 53 Resolver > Resolver Rule > Approved control would fail to delete an unapproved resolver rule if AWS > Route 53 Resolver > Resolver Rule > Approved policy was set to Enforce: Detach and delete unapproved if new. This issue has now been fixed.

Alerts

  • None

Release Notes

Azure Mods

Highlights

  • We’ve made improvements to how Approved controls interact with CMDB policies and controls for more reliable approved checks. Now, if a resource’s CMDB policy is set to Skip, its Approved control will move to invalid to prevent the Approved control from making a decision based on outdated information. Also, Approved controls will now wait until the resource’s CMDB control has run at least once to ensure the required data is available.

Alerts

  • None

Release Notes

Was this article helpful?
0 out of 0 found this helpful