> For the complete documentation index, see [llms.txt](https://docs.silessian.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silessian.com/planapply-for-jira-cloud/admin-features/terraform-console/terraform-tab.md).

# Terraform tab

Terraform tab inputs and buttons that allows to execute Terraform operation on entire workspace files.

On the UI we can see:

1. Plan button - it executes "terraform plan -no-color" operation on entire workspace
2. Apply button - it executes "terraform apply -auto-approve -no-color" operation on entire workspace.
3. Input and button "Run own command" - it allows to execute any terraform command.&#x20;

{% hint style="warning" %}
Only Terraform operations are allowed. Arguments pointing to files might not be properly processed due to a way that request are being processed.
{% endhint %}

4. Generate config button - helper function that generate configuration code with a help of Terraform code generation feature.
5. Set TF\_LOG=DEBUG - this checkbox is equivalent to setting environment variable TF\_LOG=DEBUG.
6. *"Use public provider"* checkbox - When checked, you don't have to append provider configuration block in plain text inside Terraform scripts. During the Terraform operation (plan/apply/etc) app will append volatile file containing public provider credentials. This file will not be stored or returned from the operations.
7. Execution logs tab - it is used to display feedback messages coming from external processor.

<figure><img src="/files/IJDdgGG5Qe2PCONXLZ7X" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.silessian.com/planapply-for-jira-cloud/admin-features/terraform-console/terraform-tab.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
