Clock
2
min read

3 ways to use Terraform Module and Provider Reports

Heading

This is some text inside of a div block.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Reporting decreases the time it takes to find the information you need to make decisions resulting in a cleaner and more compliant Terraform ecosystem. Now that you have removed older versions of Terraform with the versions report, lets move on to understanding which modules and providers are being used in your organization.

A image of Scalr's Modules in Use Report
Example of the Module Report

Depending on the scale you are currently operating at, you have either run into issues that reporting would have solved or you may ask why reports are needed:

  • Ensure compliance: Depending on your industry and regulatory environment, you may be required to keep track of changes to your infrastructure for compliance purposes. Knowing exactly what modules and providers are used, the versions that are used, the source they are pulled from and drilling into the workspaces that depend on them will be critical to ensuring compliance.
  • Troubleshoot issues: Things break. An easy fix might be identifying that the DevOps team who reported the issue is using an out of date module that your platform team no longer supports.
  • Make decisions faster. Know how and when your modules and providers are being used. Know which modules or providers you need to prioritize and those that are barely being used. Know who is making changes and when. Know how many versions you actually need to support or deprecate. 

All reports are actionable and allow you to drill down into individual workspaces. Log in or Sign Up to try it now or learn more below!