Pipeline Schedule
The gitlab.PipelineSchedule
resource allows to manage the lifecycle of a scheduled pipeline. Upstream API: GitLab REST API docs
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as gitlab from "@pulumi/gitlab";
const example = new gitlab.PipelineSchedule("example", {
cron: "0 1 * * *",
description: "Used to schedule builds",
project: "12345",
ref: "master",
});
Content copied to clipboard
import pulumi
import pulumi_gitlab as gitlab
example = gitlab.PipelineSchedule("example",
cron="0 1 * * *",
description="Used to schedule builds",
project="12345",
ref="master")
Content copied to clipboard
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using GitLab = Pulumi.GitLab;
return await Deployment.RunAsync(() =>
{
var example = new GitLab.PipelineSchedule("example", new()
{
Cron = "0 1 * * *",
Description = "Used to schedule builds",
Project = "12345",
Ref = "master",
});
});
Content copied to clipboard
package main
import (
"github.com/pulumi/pulumi-gitlab/sdk/v6/go/gitlab"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := gitlab.NewPipelineSchedule(ctx, "example", &gitlab.PipelineScheduleArgs{
Cron: pulumi.String("0 1 * * *"),
Description: pulumi.String("Used to schedule builds"),
Project: pulumi.String("12345"),
Ref: pulumi.String("master"),
})
if err != nil {
return err
}
return nil
})
}
Content copied to clipboard
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.gitlab.PipelineSchedule;
import com.pulumi.gitlab.PipelineScheduleArgs;
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 example = new PipelineSchedule("example", PipelineScheduleArgs.builder()
.cron("0 1 * * *")
.description("Used to schedule builds")
.project("12345")
.ref("master")
.build());
}
}
Content copied to clipboard
resources:
example:
type: gitlab:PipelineSchedule
properties:
cron: 0 1 * * *
description: Used to schedule builds
project: '12345'
ref: master
Content copied to clipboard
Import
GitLab pipeline schedules can be imported using an id made up of {project_id}:{pipeline_schedule_id}
, e.g.
$ pulumi import gitlab:index/pipelineSchedule:PipelineSchedule test 1:3
Content copied to clipboard
Properties
Link copied to clipboard
The timezone.
Link copied to clipboard
The description of the pipeline schedule.
Link copied to clipboard
The pipeline schedule id.
Link copied to clipboard
Link copied to clipboard
Link copied to clipboard
Link copied to clipboard
When set to true
, the user represented by the token running Terraform will take ownership of the scheduled pipeline prior to editing it. This can help when managing scheduled pipeline drift when other users are making changes outside Terraform.