How to Fix the bash: terraform: command not found Error in Bitbucket Pipelines

Discover how to solve the `terraform not found` error in your Bitbucket pipeline with this step-by-step guide.
---

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: terraform not found in bitbucket

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Troubleshooting the terraform: command not found Error in Bitbucket Pipelines

When working with deployment and infrastructure management, Terraform serves as an essential tool for creating and managing infrastructure resources. However, if you've recently set up a pipeline in Bitbucket and encountered the frustrating error stating bash: terraform: command not found, you may be wondering how to resolve this issue.

In this guide, we’ll delve into the underlying problem and walk you through a step-by-step solution to ensure that your Bitbucket pipeline runs smoothly with Terraform.

The Problem: Command Not Found

You might be familiar with the following scenario:

Locally, you successfully navigate to your Terraform directory (cd terraform/environments/dev) and run terraform init without any issues.

However, when you try to execute the same pipeline in Bitbucket, it fails at the second action because the command for Terraform is not recognized, leading to the error message bash: terraform: command not found.

Why You Encounter This Error

The error occurs because the Bitbucket build agent used for your pipeline is not configured to have Terraform installed by default. This means that when your pipeline attempts to run the terraform command, it cannot find the executable in the environment.

The Solution: Use the Correct Docker Image

To resolve this issue, you need to ensure that your Bitbucket pipeline uses a Docker image that already has Terraform installed. Here’s how to update your pipeline configuration:

Step 1: Update Your Bitbucket Pipeline Configuration

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Why Use a Specific Image?

Using the hashicorp/terraform image ensures that you have the necessary environment to run Terraform commands seamlessly. If you're utilizing a particular version of Terraform, you can specify that version in the image, like so:

[[See Video to Reveal this Text or Code Snippet]]

This change guarantees that your pipeline always runs with the specified version of Terraform, avoiding potential discrepancies between environments.

Additional Considerations

Testing Versions: Always test your pipeline after making changes to ensure everything runs as expected.

Maintaining Dependencies: If your Terraform scripts depend on other tools, consider adding them to your pipeline as well.

Conclusion

By changing your Bitbucket pipeline’s Docker image to use the official hashicorp/terraform image, you can easily eliminate the bash: terraform: command not found error. This adjustment allows you to run commands without any issues, streamlining your deployment process.

Now that you know how to configure your Bitbucket pipeline for Terraform, feel free to explore further possibilities with infrastructure as code and enjoy the automation that comes with it.

If you have any questions or need further assistance, please don’t hesitate to reach out!