gitlab.ServiceJira
Explore with Pulumi AI
The gitlab.ServiceJira
resource allows to manage the lifecycle of a project integration with Jira.
This resource is deprecated. use
gitlab.IntegrationJira
instead!
Upstream API: GitLab REST API docs
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as gitlab from "@pulumi/gitlab";
const awesomeProject = new gitlab.Project("awesome_project", {
name: "awesome_project",
description: "My awesome project.",
visibilityLevel: "public",
});
const jira = new gitlab.ServiceJira("jira", {
project: awesomeProject.id,
url: "https://jira.example.com",
username: "user",
password: "mypass",
});
import pulumi
import pulumi_gitlab as gitlab
awesome_project = gitlab.Project("awesome_project",
name="awesome_project",
description="My awesome project.",
visibility_level="public")
jira = gitlab.ServiceJira("jira",
project=awesome_project.id,
url="https://jira.example.com",
username="user",
password="mypass")
package main
import (
"github.com/pulumi/pulumi-gitlab/sdk/v8/go/gitlab"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
awesomeProject, err := gitlab.NewProject(ctx, "awesome_project", &gitlab.ProjectArgs{
Name: pulumi.String("awesome_project"),
Description: pulumi.String("My awesome project."),
VisibilityLevel: pulumi.String("public"),
})
if err != nil {
return err
}
_, err = gitlab.NewServiceJira(ctx, "jira", &gitlab.ServiceJiraArgs{
Project: awesomeProject.ID(),
Url: pulumi.String("https://jira.example.com"),
Username: pulumi.String("user"),
Password: pulumi.String("mypass"),
})
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using GitLab = Pulumi.GitLab;
return await Deployment.RunAsync(() =>
{
var awesomeProject = new GitLab.Project("awesome_project", new()
{
Name = "awesome_project",
Description = "My awesome project.",
VisibilityLevel = "public",
});
var jira = new GitLab.ServiceJira("jira", new()
{
Project = awesomeProject.Id,
Url = "https://jira.example.com",
Username = "user",
Password = "mypass",
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.gitlab.Project;
import com.pulumi.gitlab.ProjectArgs;
import com.pulumi.gitlab.ServiceJira;
import com.pulumi.gitlab.ServiceJiraArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
var awesomeProject = new Project("awesomeProject", ProjectArgs.builder()
.name("awesome_project")
.description("My awesome project.")
.visibilityLevel("public")
.build());
var jira = new ServiceJira("jira", ServiceJiraArgs.builder()
.project(awesomeProject.id())
.url("https://jira.example.com")
.username("user")
.password("mypass")
.build());
}
}
resources:
awesomeProject:
type: gitlab:Project
name: awesome_project
properties:
name: awesome_project
description: My awesome project.
visibilityLevel: public
jira:
type: gitlab:ServiceJira
properties:
project: ${awesomeProject.id}
url: https://jira.example.com
username: user
password: mypass
Create ServiceJira Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new ServiceJira(name: string, args: ServiceJiraArgs, opts?: CustomResourceOptions);
@overload
def ServiceJira(resource_name: str,
args: ServiceJiraArgs,
opts: Optional[ResourceOptions] = None)
@overload
def ServiceJira(resource_name: str,
opts: Optional[ResourceOptions] = None,
password: Optional[str] = None,
url: Optional[str] = None,
project: Optional[str] = None,
jira_issue_transition_id: Optional[str] = None,
issues_enabled: Optional[bool] = None,
jira_issue_prefix: Optional[str] = None,
jira_issue_regex: Optional[str] = None,
jira_issue_transition_automatic: Optional[bool] = None,
api_url: Optional[str] = None,
merge_requests_events: Optional[bool] = None,
jira_auth_type: Optional[int] = None,
commit_events: Optional[bool] = None,
project_key: Optional[str] = None,
project_keys: Optional[Sequence[str]] = None,
comment_on_event_enabled: Optional[bool] = None,
use_inherited_settings: Optional[bool] = None,
username: Optional[str] = None)
func NewServiceJira(ctx *Context, name string, args ServiceJiraArgs, opts ...ResourceOption) (*ServiceJira, error)
public ServiceJira(string name, ServiceJiraArgs args, CustomResourceOptions? opts = null)
public ServiceJira(String name, ServiceJiraArgs args)
public ServiceJira(String name, ServiceJiraArgs args, CustomResourceOptions options)
type: gitlab:ServiceJira
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args ServiceJiraArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args ServiceJiraArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args ServiceJiraArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args ServiceJiraArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args ServiceJiraArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var serviceJiraResource = new GitLab.ServiceJira("serviceJiraResource", new()
{
Password = "string",
Url = "string",
Project = "string",
JiraIssueTransitionId = "string",
IssuesEnabled = false,
JiraIssuePrefix = "string",
JiraIssueRegex = "string",
JiraIssueTransitionAutomatic = false,
ApiUrl = "string",
MergeRequestsEvents = false,
JiraAuthType = 0,
CommitEvents = false,
ProjectKey = "string",
ProjectKeys = new[]
{
"string",
},
CommentOnEventEnabled = false,
UseInheritedSettings = false,
Username = "string",
});
example, err := gitlab.NewServiceJira(ctx, "serviceJiraResource", &gitlab.ServiceJiraArgs{
Password: pulumi.String("string"),
Url: pulumi.String("string"),
Project: pulumi.String("string"),
JiraIssueTransitionId: pulumi.String("string"),
IssuesEnabled: pulumi.Bool(false),
JiraIssuePrefix: pulumi.String("string"),
JiraIssueRegex: pulumi.String("string"),
JiraIssueTransitionAutomatic: pulumi.Bool(false),
ApiUrl: pulumi.String("string"),
MergeRequestsEvents: pulumi.Bool(false),
JiraAuthType: pulumi.Int(0),
CommitEvents: pulumi.Bool(false),
ProjectKey: pulumi.String("string"),
ProjectKeys: pulumi.StringArray{
pulumi.String("string"),
},
CommentOnEventEnabled: pulumi.Bool(false),
UseInheritedSettings: pulumi.Bool(false),
Username: pulumi.String("string"),
})
var serviceJiraResource = new ServiceJira("serviceJiraResource", ServiceJiraArgs.builder()
.password("string")
.url("string")
.project("string")
.jiraIssueTransitionId("string")
.issuesEnabled(false)
.jiraIssuePrefix("string")
.jiraIssueRegex("string")
.jiraIssueTransitionAutomatic(false)
.apiUrl("string")
.mergeRequestsEvents(false)
.jiraAuthType(0)
.commitEvents(false)
.projectKey("string")
.projectKeys("string")
.commentOnEventEnabled(false)
.useInheritedSettings(false)
.username("string")
.build());
service_jira_resource = gitlab.ServiceJira("serviceJiraResource",
password="string",
url="string",
project="string",
jira_issue_transition_id="string",
issues_enabled=False,
jira_issue_prefix="string",
jira_issue_regex="string",
jira_issue_transition_automatic=False,
api_url="string",
merge_requests_events=False,
jira_auth_type=0,
commit_events=False,
project_key="string",
project_keys=["string"],
comment_on_event_enabled=False,
use_inherited_settings=False,
username="string")
const serviceJiraResource = new gitlab.ServiceJira("serviceJiraResource", {
password: "string",
url: "string",
project: "string",
jiraIssueTransitionId: "string",
issuesEnabled: false,
jiraIssuePrefix: "string",
jiraIssueRegex: "string",
jiraIssueTransitionAutomatic: false,
apiUrl: "string",
mergeRequestsEvents: false,
jiraAuthType: 0,
commitEvents: false,
projectKey: "string",
projectKeys: ["string"],
commentOnEventEnabled: false,
useInheritedSettings: false,
username: "string",
});
type: gitlab:ServiceJira
properties:
apiUrl: string
commentOnEventEnabled: false
commitEvents: false
issuesEnabled: false
jiraAuthType: 0
jiraIssuePrefix: string
jiraIssueRegex: string
jiraIssueTransitionAutomatic: false
jiraIssueTransitionId: string
mergeRequestsEvents: false
password: string
project: string
projectKey: string
projectKeys:
- string
url: string
useInheritedSettings: false
username: string
ServiceJira Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
The ServiceJira resource accepts the following input properties:
- Password string
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token.
- Project string
- ID of the project you want to activate integration on.
- Url string
- The URL to the JIRA project which is being linked to this GitLab project. For example, https://jira.example.com.
- Api
Url string - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com.
- Comment
On boolEvent Enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- Commit
Events bool - Enable notifications for commit events
- Issues
Enabled bool - Enable viewing Jira issues in GitLab.
- Jira
Auth intType - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. Defaults to 0.
- Jira
Issue stringPrefix - Prefix to match Jira issue keys.
- Jira
Issue stringRegex - Regular expression to match Jira issue keys.
- Jira
Issue boolTransition Automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false.
- Jira
Issue stringTransition Id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2. Note*: importing this field is only supported since GitLab 15.2.
- Merge
Requests boolEvents - Enable notifications for merge request events
- Project
Key string - The short identifier for your JIRA project, all uppercase, e.g., PROJ.
- Project
Keys List<string> - Keys of Jira projects. When issues_enabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- Use
Inherited boolSettings - Indicates whether or not to inherit default settings. Defaults to false.
- Username string
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0).
- Password string
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token.
- Project string
- ID of the project you want to activate integration on.
- Url string
- The URL to the JIRA project which is being linked to this GitLab project. For example, https://jira.example.com.
- Api
Url string - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com.
- Comment
On boolEvent Enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- Commit
Events bool - Enable notifications for commit events
- Issues
Enabled bool - Enable viewing Jira issues in GitLab.
- Jira
Auth intType - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. Defaults to 0.
- Jira
Issue stringPrefix - Prefix to match Jira issue keys.
- Jira
Issue stringRegex - Regular expression to match Jira issue keys.
- Jira
Issue boolTransition Automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false.
- Jira
Issue stringTransition Id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2. Note*: importing this field is only supported since GitLab 15.2.
- Merge
Requests boolEvents - Enable notifications for merge request events
- Project
Key string - The short identifier for your JIRA project, all uppercase, e.g., PROJ.
- Project
Keys []string - Keys of Jira projects. When issues_enabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- Use
Inherited boolSettings - Indicates whether or not to inherit default settings. Defaults to false.
- Username string
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0).
- password String
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token.
- project String
- ID of the project you want to activate integration on.
- url String
- The URL to the JIRA project which is being linked to this GitLab project. For example, https://jira.example.com.
- api
Url String - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com.
- comment
On BooleanEvent Enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- commit
Events Boolean - Enable notifications for commit events
- issues
Enabled Boolean - Enable viewing Jira issues in GitLab.
- jira
Auth IntegerType - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. Defaults to 0.
- jira
Issue StringPrefix - Prefix to match Jira issue keys.
- jira
Issue StringRegex - Regular expression to match Jira issue keys.
- jira
Issue BooleanTransition Automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false.
- jira
Issue StringTransition Id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2. Note*: importing this field is only supported since GitLab 15.2.
- merge
Requests BooleanEvents - Enable notifications for merge request events
- project
Key String - The short identifier for your JIRA project, all uppercase, e.g., PROJ.
- project
Keys List<String> - Keys of Jira projects. When issues_enabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- use
Inherited BooleanSettings - Indicates whether or not to inherit default settings. Defaults to false.
- username String
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0).
- password string
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token.
- project string
- ID of the project you want to activate integration on.
- url string
- The URL to the JIRA project which is being linked to this GitLab project. For example, https://jira.example.com.
- api
Url string - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com.
- comment
On booleanEvent Enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- commit
Events boolean - Enable notifications for commit events
- issues
Enabled boolean - Enable viewing Jira issues in GitLab.
- jira
Auth numberType - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. Defaults to 0.
- jira
Issue stringPrefix - Prefix to match Jira issue keys.
- jira
Issue stringRegex - Regular expression to match Jira issue keys.
- jira
Issue booleanTransition Automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false.
- jira
Issue stringTransition Id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2. Note*: importing this field is only supported since GitLab 15.2.
- merge
Requests booleanEvents - Enable notifications for merge request events
- project
Key string - The short identifier for your JIRA project, all uppercase, e.g., PROJ.
- project
Keys string[] - Keys of Jira projects. When issues_enabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- use
Inherited booleanSettings - Indicates whether or not to inherit default settings. Defaults to false.
- username string
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0).
- password str
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token.
- project str
- ID of the project you want to activate integration on.
- url str
- The URL to the JIRA project which is being linked to this GitLab project. For example, https://jira.example.com.
- api_
url str - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com.
- comment_
on_ boolevent_ enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- commit_
events bool - Enable notifications for commit events
- issues_
enabled bool - Enable viewing Jira issues in GitLab.
- jira_
auth_ inttype - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. Defaults to 0.
- jira_
issue_ strprefix - Prefix to match Jira issue keys.
- jira_
issue_ strregex - Regular expression to match Jira issue keys.
- jira_
issue_ booltransition_ automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false.
- jira_
issue_ strtransition_ id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2. Note*: importing this field is only supported since GitLab 15.2.
- merge_
requests_ boolevents - Enable notifications for merge request events
- project_
key str - The short identifier for your JIRA project, all uppercase, e.g., PROJ.
- project_
keys Sequence[str] - Keys of Jira projects. When issues_enabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- use_
inherited_ boolsettings - Indicates whether or not to inherit default settings. Defaults to false.
- username str
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0).
- password String
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token.
- project String
- ID of the project you want to activate integration on.
- url String
- The URL to the JIRA project which is being linked to this GitLab project. For example, https://jira.example.com.
- api
Url String - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com.
- comment
On BooleanEvent Enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- commit
Events Boolean - Enable notifications for commit events
- issues
Enabled Boolean - Enable viewing Jira issues in GitLab.
- jira
Auth NumberType - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. Defaults to 0.
- jira
Issue StringPrefix - Prefix to match Jira issue keys.
- jira
Issue StringRegex - Regular expression to match Jira issue keys.
- jira
Issue BooleanTransition Automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false.
- jira
Issue StringTransition Id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2. Note*: importing this field is only supported since GitLab 15.2.
- merge
Requests BooleanEvents - Enable notifications for merge request events
- project
Key String - The short identifier for your JIRA project, all uppercase, e.g., PROJ.
- project
Keys List<String> - Keys of Jira projects. When issues_enabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- use
Inherited BooleanSettings - Indicates whether or not to inherit default settings. Defaults to false.
- username String
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0).
Outputs
All input properties are implicitly available as output properties. Additionally, the ServiceJira resource produces the following output properties:
- active bool
- Whether the integration is active.
- created_
at str - Create time.
- id str
- The provider-assigned unique ID for this managed resource.
- title str
- Title.
- updated_
at str - Update time.
Look up Existing ServiceJira Resource
Get an existing ServiceJira resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: ServiceJiraState, opts?: CustomResourceOptions): ServiceJira
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
active: Optional[bool] = None,
api_url: Optional[str] = None,
comment_on_event_enabled: Optional[bool] = None,
commit_events: Optional[bool] = None,
created_at: Optional[str] = None,
issues_enabled: Optional[bool] = None,
jira_auth_type: Optional[int] = None,
jira_issue_prefix: Optional[str] = None,
jira_issue_regex: Optional[str] = None,
jira_issue_transition_automatic: Optional[bool] = None,
jira_issue_transition_id: Optional[str] = None,
merge_requests_events: Optional[bool] = None,
password: Optional[str] = None,
project: Optional[str] = None,
project_key: Optional[str] = None,
project_keys: Optional[Sequence[str]] = None,
title: Optional[str] = None,
updated_at: Optional[str] = None,
url: Optional[str] = None,
use_inherited_settings: Optional[bool] = None,
username: Optional[str] = None) -> ServiceJira
func GetServiceJira(ctx *Context, name string, id IDInput, state *ServiceJiraState, opts ...ResourceOption) (*ServiceJira, error)
public static ServiceJira Get(string name, Input<string> id, ServiceJiraState? state, CustomResourceOptions? opts = null)
public static ServiceJira get(String name, Output<String> id, ServiceJiraState state, CustomResourceOptions options)
Resource lookup is not supported in YAML
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Active bool
- Whether the integration is active.
- Api
Url string - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com.
- Comment
On boolEvent Enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- Commit
Events bool - Enable notifications for commit events
- Created
At string - Create time.
- Issues
Enabled bool - Enable viewing Jira issues in GitLab.
- Jira
Auth intType - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. Defaults to 0.
- Jira
Issue stringPrefix - Prefix to match Jira issue keys.
- Jira
Issue stringRegex - Regular expression to match Jira issue keys.
- Jira
Issue boolTransition Automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false.
- Jira
Issue stringTransition Id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2. Note*: importing this field is only supported since GitLab 15.2.
- Merge
Requests boolEvents - Enable notifications for merge request events
- Password string
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token.
- Project string
- ID of the project you want to activate integration on.
- Project
Key string - The short identifier for your JIRA project, all uppercase, e.g., PROJ.
- Project
Keys List<string> - Keys of Jira projects. When issues_enabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- Title string
- Title.
- Updated
At string - Update time.
- Url string
- The URL to the JIRA project which is being linked to this GitLab project. For example, https://jira.example.com.
- Use
Inherited boolSettings - Indicates whether or not to inherit default settings. Defaults to false.
- Username string
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0).
- Active bool
- Whether the integration is active.
- Api
Url string - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com.
- Comment
On boolEvent Enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- Commit
Events bool - Enable notifications for commit events
- Created
At string - Create time.
- Issues
Enabled bool - Enable viewing Jira issues in GitLab.
- Jira
Auth intType - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. Defaults to 0.
- Jira
Issue stringPrefix - Prefix to match Jira issue keys.
- Jira
Issue stringRegex - Regular expression to match Jira issue keys.
- Jira
Issue boolTransition Automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false.
- Jira
Issue stringTransition Id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2. Note*: importing this field is only supported since GitLab 15.2.
- Merge
Requests boolEvents - Enable notifications for merge request events
- Password string
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token.
- Project string
- ID of the project you want to activate integration on.
- Project
Key string - The short identifier for your JIRA project, all uppercase, e.g., PROJ.
- Project
Keys []string - Keys of Jira projects. When issues_enabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- Title string
- Title.
- Updated
At string - Update time.
- Url string
- The URL to the JIRA project which is being linked to this GitLab project. For example, https://jira.example.com.
- Use
Inherited boolSettings - Indicates whether or not to inherit default settings. Defaults to false.
- Username string
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0).
- active Boolean
- Whether the integration is active.
- api
Url String - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com.
- comment
On BooleanEvent Enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- commit
Events Boolean - Enable notifications for commit events
- created
At String - Create time.
- issues
Enabled Boolean - Enable viewing Jira issues in GitLab.
- jira
Auth IntegerType - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. Defaults to 0.
- jira
Issue StringPrefix - Prefix to match Jira issue keys.
- jira
Issue StringRegex - Regular expression to match Jira issue keys.
- jira
Issue BooleanTransition Automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false.
- jira
Issue StringTransition Id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2. Note*: importing this field is only supported since GitLab 15.2.
- merge
Requests BooleanEvents - Enable notifications for merge request events
- password String
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token.
- project String
- ID of the project you want to activate integration on.
- project
Key String - The short identifier for your JIRA project, all uppercase, e.g., PROJ.
- project
Keys List<String> - Keys of Jira projects. When issues_enabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- title String
- Title.
- updated
At String - Update time.
- url String
- The URL to the JIRA project which is being linked to this GitLab project. For example, https://jira.example.com.
- use
Inherited BooleanSettings - Indicates whether or not to inherit default settings. Defaults to false.
- username String
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0).
- active boolean
- Whether the integration is active.
- api
Url string - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com.
- comment
On booleanEvent Enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- commit
Events boolean - Enable notifications for commit events
- created
At string - Create time.
- issues
Enabled boolean - Enable viewing Jira issues in GitLab.
- jira
Auth numberType - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. Defaults to 0.
- jira
Issue stringPrefix - Prefix to match Jira issue keys.
- jira
Issue stringRegex - Regular expression to match Jira issue keys.
- jira
Issue booleanTransition Automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false.
- jira
Issue stringTransition Id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2. Note*: importing this field is only supported since GitLab 15.2.
- merge
Requests booleanEvents - Enable notifications for merge request events
- password string
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token.
- project string
- ID of the project you want to activate integration on.
- project
Key string - The short identifier for your JIRA project, all uppercase, e.g., PROJ.
- project
Keys string[] - Keys of Jira projects. When issues_enabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- title string
- Title.
- updated
At string - Update time.
- url string
- The URL to the JIRA project which is being linked to this GitLab project. For example, https://jira.example.com.
- use
Inherited booleanSettings - Indicates whether or not to inherit default settings. Defaults to false.
- username string
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0).
- active bool
- Whether the integration is active.
- api_
url str - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com.
- comment_
on_ boolevent_ enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- commit_
events bool - Enable notifications for commit events
- created_
at str - Create time.
- issues_
enabled bool - Enable viewing Jira issues in GitLab.
- jira_
auth_ inttype - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. Defaults to 0.
- jira_
issue_ strprefix - Prefix to match Jira issue keys.
- jira_
issue_ strregex - Regular expression to match Jira issue keys.
- jira_
issue_ booltransition_ automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false.
- jira_
issue_ strtransition_ id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2. Note*: importing this field is only supported since GitLab 15.2.
- merge_
requests_ boolevents - Enable notifications for merge request events
- password str
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token.
- project str
- ID of the project you want to activate integration on.
- project_
key str - The short identifier for your JIRA project, all uppercase, e.g., PROJ.
- project_
keys Sequence[str] - Keys of Jira projects. When issues_enabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- title str
- Title.
- updated_
at str - Update time.
- url str
- The URL to the JIRA project which is being linked to this GitLab project. For example, https://jira.example.com.
- use_
inherited_ boolsettings - Indicates whether or not to inherit default settings. Defaults to false.
- username str
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0).
- active Boolean
- Whether the integration is active.
- api
Url String - The base URL to the Jira instance API. Web URL value is used if not set. For example, https://jira-api.example.com.
- comment
On BooleanEvent Enabled - Enable comments inside Jira issues on each GitLab event (commit / merge request)
- commit
Events Boolean - Enable notifications for commit events
- created
At String - Create time.
- issues
Enabled Boolean - Enable viewing Jira issues in GitLab.
- jira
Auth NumberType - The authentication method to be used with Jira. 0 means Basic Authentication. 1 means Jira personal access token. Defaults to 0.
- jira
Issue StringPrefix - Prefix to match Jira issue keys.
- jira
Issue StringRegex - Regular expression to match Jira issue keys.
- jira
Issue BooleanTransition Automatic - Enable automatic issue transitions. Takes precedence over jiraissuetransition_id if enabled. Defaults to false.
- jira
Issue StringTransition Id - The ID of a transition that moves issues to a closed state. You can find this number under the JIRA workflow administration (Administration > Issues > Workflows) by selecting View under Operations of the desired workflow of your project. By default, this ID is set to 2. Note*: importing this field is only supported since GitLab 15.2.
- merge
Requests BooleanEvents - Enable notifications for merge request events
- password String
- The Jira API token, password, or personal access token to be used with Jira. When your authentication method is basic (jiraauthtype is 0), use an API token for Jira Cloud or a password for Jira Data Center or Jira Server. When your authentication method is a Jira personal access token (jiraauthtype is 1), use the personal access token.
- project String
- ID of the project you want to activate integration on.
- project
Key String - The short identifier for your JIRA project, all uppercase, e.g., PROJ.
- project
Keys List<String> - Keys of Jira projects. When issues_enabled is true, this setting specifies which Jira projects to view issues from in GitLab.
- title String
- Title.
- updated
At String - Update time.
- url String
- The URL to the JIRA project which is being linked to this GitLab project. For example, https://jira.example.com.
- use
Inherited BooleanSettings - Indicates whether or not to inherit default settings. Defaults to false.
- username String
- The email or username to be used with Jira. For Jira Cloud use an email, for Jira Data Center and Jira Server use a username. Required when using Basic authentication (jiraauthtype is 0).
Import
You can import a gitlab_service_jira state using the project ID, e.g.
$ pulumi import gitlab:index/serviceJira:ServiceJira jira 1
To learn more about importing existing cloud resources, see Importing resources.
Package Details
- Repository
- GitLab pulumi/pulumi-gitlab
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
gitlab
Terraform Provider.