Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Terraform in Yandex Cloud
  • Getting started
  • Solution library
    • Overview
    • Release notes
          • gitlab_instance

In this article:

  • Example usage
  • Schema
  • Required
  • Optional
  • Read-Only
  • Nested Schema for timeouts
  • Import
  1. Terraform reference
  2. Resources
  3. Managed Service for GitLab
  4. Resources
  5. gitlab_instance

yandex_gitlab_instance (Resource)

Written by
Yandex Cloud
Updated at August 7, 2025
  • Example usage
  • Schema
    • Required
    • Optional
    • Read-Only
    • Nested Schema for timeouts
  • Import

Managed Gitlab instance.

Example usageExample usage

//
// Create a new GitLab instance.
//
resource "yandex_gitlab_instance" "my_gitlab_instance" {
  name                      = "gitlab-created-with-terraform"
  resource_preset_id        = "s2.micro"
  disk_size                 = 30
  admin_login               = "gitlab-user"
  admin_email               = "gitlab-user@example.com"
  domain                    = "gitlab-terraform.gitlab.yandexcloud.net"
  subnet_id                 = yandex_vpc_subnet.a.id
  backup_retain_period_days = 7
}

SchemaSchema

RequiredRequired

  • admin_email (String) An email of admin user in Gitlab.
  • admin_login (String) A login of admin user in Gitlab.
  • approval_rules_id (String) Approval rules configuration. One of: NONE, BASIC, STANDARD, ADVANCED.
  • backup_retain_period_days (Number) Auto backups retain period in days.
  • disk_size (Number) Amount of disk storage available to a instance in GB.
  • domain (String) Domain of the Gitlab instance.
  • name (String) The resource name.
  • resource_preset_id (String) ID of the preset for computational resources available to the instance (CPU, memory etc.). One of: s2.micro, s2.small, s2.medium, s2.large.
  • subnet_id (String) ID of the subnet where the GitLab instance is located.

OptionalOptional

  • approval_rules_token (String, Sensitive) Approval rules token.
  • deletion_protection (Boolean) The true value means that resource is protected from accidental deletion.
  • description (String) The resource description.
  • folder_id (String) The folder identifier that resource belongs to. If it is not provided, the default provider folder-id is used.
  • labels (Map of String) A set of key/value label pairs which assigned to resource.
  • maintenance_delete_untagged (Boolean) The true value means that untagged images will be deleted during maintenance.
  • timeouts (Block, Optional) (see below for nested schema)

Read-OnlyRead-Only

  • created_at (String) The creation timestamp of the resource.
  • gitlab_version (String) Version of Gitlab on instance.
  • id (String) The resource identifier.
  • status (String) Status of the instance.
  • updated_at (String) The timestamp when the instance was updated.

Nested Schema for Nested Schema for timeouts

Optional:

  • create (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).
  • delete (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Setting a timeout for a Delete operation is only applicable if changes are saved into state before the destroy operation occurs.
  • update (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).

ImportImport

The resource can be imported by using their resource ID. For getting the resource ID you can use Yandex Cloud Web Console or YC CLI.

# terraform import yandex_gitlab_instance.<resource Name> <resource Id>
terraform import yandex_gitlab_instance.my_gitlab_instance c172a**********ubpme

Was the article helpful?

Previous
gitlab_instance
Next
mdb_greenplum_cluster
© 2025 Direct Cursus Technology L.L.C.