# 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.

Comment out impor to check how it impact the plan operation.

Now instead of 2 resources to import, 1 resources is going to be created.

--- # Agent Instructions: 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: ``` GET https://docs.silessian.com/planapply-for-jira-cloud/admin-features/terraform-console/terraform-tab/plan.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.