Silessian
PlanApply for Jira Cloud
PlanApply for Jira Cloud
  • Introduction
    • 🚀About PlanApply for Jira
    • 🛸Features overview
    • 📚Use cases
    • 💿Data structure and processing
    • 💡Workflow
  • Configuration
    • Get started - app configuration
      • 1. Client configuration
      • 2. Submission and provider configuration
      • 3. Remote repositories
  • Global features
    • Designer - getting started
    • 📐Designer
      • Toolbox section
        • Toolbox
        • Templates
        • Import / Export
        • Plan details
        • Submission
        • Collaboration
    • Diagram area
      • Diagram actions
      • Importing objects
      • Adding new elements
      • Updating element details
      • Linking objects
    • 🌏Plan browser
  • Admin features
    • Workspaces
    • Remote repositories
    • Plan browser
    • Terraform console
      • Workspace tab
      • Toolbox tab
      • Terraform tab
        • Generate config
        • Plan
        • Apply
      • Transform tab
    • AI Assistant
    • Execution logs
  • Terraform Provider for Jira Cloud
    • Terraform provider for Jira cloud
      • jira-cloud Provider
      • atlcloudjira_groups (Data Source)
      • atlcloudjira_issues (Data Source)
      • atlcloudjira_users (Data Source)
      • atlcloudjira_customfield (Resource)
      • atlcloudjira_dashboard (Resource)
      • atlcloudjira_field_configuration_scheme (Resource)
      • atlcloudjira_field_configuration (Resource)
      • atlcloudjira_filter (Resource)
      • atlcloudjira_issue_link_type (Resource)
      • atlcloudjira_issue_type_scheme (Resource)
      • atlcloudjira_issue_security_scheme (Resource)
      • atlcloudjira_issue_type_screen_scheme (Resource)
      • atlcloudjira_issue_type (Resource)
      • atlcloudjira_notification_scheme (Resource)
      • atlcloudjira_priority_sequence (Resource)
      • atlcloudjira_permission_scheme (Resource)
      • atlcloudjira_priority (Resource)
      • atlcloudjira_project_component (Resource)
      • atlcloudjira_project_role (Resource)
      • atlcloudjira_project (Resource)
      • atlcloudjira_screen_scheme (Resource)
      • atlcloudjira_screen (Resource)
      • atlcloudjira_status (Resource)
      • atlcloudjira_workflow_scheme (Resource)
      • atlcloudjira_workflow (Resource)
  • Support
    • How to report a bug?
  • 🔓Security statement
Powered by GitBook
On this page
  1. Admin features
  2. Terraform console
  3. Terraform tab

Apply

PreviousPlanNextTransform tab

Last updated 8 months ago

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.

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

To perform apply operation, follow steps below:

  1. Make sure plan operation is performed successfully.

  2. Click on apply button. Confirm operation by clicking Apply on popup dialog.

  3. Verify apply operation output present in Execution logs.

  4. In case of errors, that appeared during apply operation, update the Terraform code accordingly and repeat apply operation.

  5. After operation is sucessfull, you will see new files being created. They are used to store information about the current state.

Before applying make sure all changes in the plan are exactly as you intend.
Example errors not detected at the time of plan operation
Fix applied to code, based on error message.
This time apply operation was successful.
Reload workspace. You will find Terraform state files created.