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
  • Pull operation
  • Push operation
  1. Admin features

Remote repositories

PreviousWorkspacesNextPlan browser

Last updated 9 months ago

Remote workspace configuration is described under link below

Remote repositories are useful if you want to store and version your configuration inside Git repository.

Pull operation

Pull operation will replace all data inside given workspace. Files would be added / removed. By clicking "Pull" button inside dialog you are confirming the operation.

Remote processor is doing following operation:

  1. Git clone (based on provided connection configuration and branch)

  2. Overwrite workspace files (add / update / remove)

  3. Upload updated files to Forge storage

  4. Destroy virtual environment

Push operation

Push operation will replace all data inside given repository. Files would be added / removed. Remote processor is doing following operation:

  1. Git clone (based on provided connection configuration and branch)

  2. Overwrite data with workspace files (add / update / remove)

  3. Git add *

  4. Git commit -m "Provided message"

  5. Git push (based on provided connection configuration and branch)

  6. Destroy virtual environment

Type commit message that you want to use to push into repo. By clicking "Push" button inside dialog you are confirming the operation.

Status operation

Status operation will compare repository and workspace data. Remote processor is doing following operation:

  1. Git clone (based on provided connection configuration and branch)

  2. Overwrite data with workspace files (add / update / remove)

  3. Git status

  4. Send results to UI

  5. Destroy virtual environment

3. Remote repositories