Service
The gitlab.ServiceJira resource allows to manage the lifecycle of a project integration with Jira. Upstream API: GitLab REST API docs
Example Usage
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()
.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());
}
}Import
You can import a service_jira state using the project ID, e.g.
$ pulumi import gitlab:index/serviceJira:ServiceJira jira 1Properties
Enable comments inside Jira issues on each GitLab event (commit / merge request)
Enable notifications for commit events
Enable notifications for issues events.
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.
Enable notifications for merge request events
Enable notifications for note events.
Enable notifications for pipeline events.
The short identifier for your JIRA project, all uppercase, e.g., PROJ.
Enable notifications for push events.
Enable notifications for tag_push events.