> 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/plan.md).

# Plan

{% hint style="success" %}
If you don't want to append provider block with credentials inside Terraform script files, you can check  "Use public provider".\
App will append volatile file with provider block and public provider credentials. This file will not be stored or returned as the result of any operation. 
{% endhint %}

{% hint style="info" %}
If you are not using "Public provider" credentials, it is required to add two Terraform code blocks:

* terraform
  * specify atlcloudjira provider
* provider
  * inside provider, specify credentials used to authenticate Terraform provider in given instance
    {% endhint %}

To perform plan operation follow the steps below:

1. Make sure that all imported resources have corresponding code fragments. Use code generation if needed.
2. Click on Plan button
3. Await process to be completed. Verify logs being displayed in Execution logs tab.
4. Check the output to verify the plan before plan operation.

<figure><img src="/files/6xmG93a94ISvtxvpdy6P" alt=""><figcaption><p>Plan operation output.</p></figcaption></figure>

<figure><img src="/files/8zDTa4o9mJq5l40QbZ8j" alt=""><figcaption><p>Comment out impor to check how it impact the plan operation.</p></figcaption></figure>

<figure><img src="/files/ccnq4qd1JH2FhKFeeOwm" alt=""><figcaption><p>Now instead of 2 resources to import, 1 resources is going to be created.</p></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/plan.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.