almaforge_jira_connector Data Source
Read an AlmaForge JiraConnector resource by name.
This data source reads existing cluster resources. It does not create, change, or delete them. Authenticate using the Terraform setup guide. Your identity needs permission to read the selected resources.
The built-in Jira integration reads the connector named jira. See Jira integration for project and workflow requirements. Secret fields are redacted by the API and returned as null.
See the configuration reference for the resource manifest and field context.
Set name to the existing object's metadata.name. The result is available in metadata and spec. A missing object produces an error.
Example Usage
Save this configuration in a new directory. Replace the example name with the existing object you want to read. Review the plan before applying it. Applying this data-only configuration saves the outputs without changing cluster resources.
terraform initterraform plan -out=plan.tfplanterraform apply plan.tfplanterraform outputterraform {
required_providers {
almaforge = {
source = "get.almaforge.com/almaforge/almaforge"
}
}
}
provider "almaforge" {}
data "almaforge_jira_connector" "existing" {
name = "jira"
}
output "name" {
value = data.almaforge_jira_connector.existing.metadata.name
}
To manage changes instead of only reading, use the resource. Read resources versus data sources before choosing ownership.
Schema
Required
name(String) Name of the resource to read.
Read-Only
metadata(Attributes) (see below for nested schema)spec(Attributes) Spec contains the resource configuration. (see below for nested schema)
Nested Schema for metadata
Read-Only:
labels(Map of String) Labels attached to the resource.name(String) Resource name. Changing this name replaces the resource.resource_version(String) Server revision used to detect concurrent changes.
Nested Schema for spec
Read-Only:
api_token(String, Sensitive) APIToken is the Jira API token. Accepts a literal value or a value-expansion reference such as "${file:/etc/jira/token}" or "${env:JIRA_API_TOKEN}".issue_type(String) IssueType is the Jira issue type to create.project(String) Project is the Jira project key under which access-request issues are created.url(String) URL is the base URL of the Jira deployment, e.g. https://example.atlassian.net.username(String) Username is the Jira account username (typically the user's email address) used to authenticate API calls.