Global Level Notifications Args
The gitlab.GlobalLevelNotifications
resource allows to manage global notifications. Upstream API: GitLab REST API docs
Import
Starting in Terraform v1.5.0 you can use an import block to import gitlab_global_level_notifications
. For example: terraform import { to = gitlab_global_level_notifications.example id = "see CLI command below for ID" } Import using the CLI is supported using the following syntax: Note: You can import a global notification state using "gitlab" as the ID. The ID will always be gitlab, because the global notificatio only exists once per user
$ pulumi import gitlab:index/globalLevelNotifications:GlobalLevelNotifications example gitlab
Constructors
Properties
Enable notifications for closed issues. Can only be used when level
is custom
.
Enable notifications for closed merge requests. Can only be used when level
is custom
.
Enable notifications for failed pipelines. Can only be used when level
is custom
.
Enable notifications for fixed pipelines. Can only be used when level
is custom
.
Enable notifications for merged merge requests. Can only be used when level
is custom
.
Enable notifications for merged merge requests when the pipeline succeeds. Can only be used when level
is custom
.
Enable notifications for moved projects. Can only be used when level
is custom
.
Enable notifications for new merge requests. Can only be used when level
is custom
.
Enable notifications for push to merge request branches. Can only be used when level
is custom
.
Enable notifications for issue reassignments. Can only be used when level
is custom
.
Enable notifications for merge request reassignments. Can only be used when level
is custom
.
Enable notifications for reopened issues. Can only be used when level
is custom
.
Enable notifications for reopened merge requests. Can only be used when level
is custom
.
Enable notifications for successful pipelines. Can only be used when level
is custom
.