Updating instance settings

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

1. View the description of the CLI command for updating Managed Service for GitLab instance settings:

   yc managed-gitlab instance update --help
   

2. Update the GitLab instance settings (this example does not use all available parameters):

   yc managed-gitlab instance update <instance_name_or_ID> \
     --new-name <new_instance_name> \
     --resource-preset-id <host_class> \
     --disk-size <disk_size_in_GB> \
     --deletion-protection \
     --approval-rules <approval_rule_configuration>
   

   Where:

   • --new-name: New instance name, unique within Yandex Cloud. Follow these naming requirements:

     • Length: between 3 and 63 characters.
     • It can only contain lowercase Latin letters, numbers, and hyphens.
     • It must start with a letter and cannot end with a hyphen.

   • --resource-preset-id: Host class. It determines the configuration of the VM to host the GitLab instance. The possible values are:

     • s2.micro: 2 vCPUs, 8 GB RAM
     • s2.small: 4 vCPUs, 16 GB RAM
     • s2.medium: 8 vCPUs, 32 GB RAM
     • s2.large: 16 vCPUs, 64 GB RAM

   • --disk-size: Disk size, in GB.

   • --deletion-protection: Instance protection against accidental deletion by users.

     Note

     You can use the CLI to enable but not disable the accidental deletion protection.

   • --approval-rules: Approval rule configuration. The possible values are:

     • BASIC
     • STANDARD
     • ADVANCED

     Note

     The configuration you select affects the cost of using the instance computing resources.

   Result:

   id: c17c60tpadua********
   folder_id: b1g2slt7p9ug********
   created_at: "2025-07-20T18:34:16.078Z"
   updated_at: "2025-07-20T18:54:49.829961285Z"
   name: test-cli
   resource_preset_id: s2.small
   disk_size: "107374182400"
   status: RUNNING
   admin_login: admin-gl
   admin_email: user@example.com
   domain: test-domain-user.gitlab.yandexcloud.net
   subnet_id: e9b4rrpuu2a********
   backup_retain_period_days: "7"
   deletion_protection: true
   approval_rules_id: BASIC
   gitlab_version: 17.11.6
   

   For more information about this command, see the CLI reference.

1. Open the current Terraform configuration file describing your infrastructure.

   For more information about creating this file, see Creating a GitLab instance.

2. Change the parameter values in the GitLab instance description:

   resource "yandex_gitlab_instance" "my_gitlab_instance" {
     ...
     resource_preset_id        = "<host_class>"
     disk_size                 = <disk_size_in_GB>
     approval_rules_id         = "<approval_rule_configuration>"
     backup_retain_period_days = <backup_retention_period>
     deletion_protection       = <true_or_false>
     ...
   }
   

   Where:

   • resource_preset_id: Host class. It determines the configuration of the VM to host the GitLab instance. The possible values are:

     • s2.micro: 2 vCPUs, 8 GB RAM
     • s2.small: 4 vCPUs, 16 GB RAM
     • s2.medium: 8 vCPUs, 32 GB RAM
     • s2.large: 16 vCPUs, 64 GB RAM

   • disk_size: Disk size, in GB.

   • approval_rules_id: Approval rule configuration. The possible values are:

     • BASIC
     • STANDARD
     • ADVANCED

     Note

     The configuration you select affects the cost of using the instance computing resources.

   • backup_retain_period_days: Automatic backup retention period, in days.

   • deletion_protection: Instance protection against accidental deletion by users. The possible values are true or false.

   For more information about yandex_gitlab_instance properties, see this provider guide.

3. Make sure the settings are correct.

   1. In the command line, navigate to the directory that contains the current Terraform configuration files defining the infrastructure.

   2. Run this command:

      terraform validate
      

      Terraform will show any errors found in your configuration files.

4. Confirm updating the resources.

   1. Run this command to view the planned changes:

      terraform plan
      

      If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

   2. If everything looks correct, apply the changes:

      1. Run this command:

         terraform apply
         

      2. Confirm updating the resources.

      3. Wait for the operation to complete.

   Terraform will update all the required resources. You can check the update using the management console or this CLI command:

   yc managed-gitlab instance list
   

For more information, see this Terraform provider guide.

Use the Update REST API method for the Instance resource or the InstanceService/Update gRPC API call.