[Yandex Cloud documentation](../../index.md) > [Yandex Serverless Containers](../index.md) > [Step-by-step guides](index.md) > Managing a trigger > Updating a trigger

# Updating a trigger in Serverless Containers

You can update any settings except for the trigger type and target resource.

{% note info %}

Your changes will apply within five minutes.

{% endnote %}

{% list tabs group=instructions %}

- Management console {#console}

  1. In the [management console](https://console.yandex.cloud), navigate to the folder containing the trigger.
  1. Navigate to **Serverless Containers**.
  1. In the left-hand panel, select ![image](../../_assets/console-icons/gear-play.svg) **Triggers**.
  1. Select the trigger whose settings you want to update.
  1. In the top-right corner of the page, click **Edit**.
  1. Edit the trigger settings and click **Save**.

- CLI {#cli}

  If you do not have the Yandex Cloud CLI yet, [install and initialize it](../../cli/quickstart.md#install).

  The folder used by default is the one specified when [creating](../../cli/operations/profile/profile-create.md) 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.

  To find out the name or ID of a trigger, [get](trigger-list.md) the list of triggers in the folder.

  1. See the description of the CLI command for updating trigger settings:

      ```bash
      yc serverless trigger update <trigger_type> --help
      ```

  1. Update the trigger settings, e.g., rename the trigger:

      ```bash
      yc serverless trigger update <trigger_type> <trigger_name> \
        --new-name <new_trigger_name> 
      ```

      Result:

      ```text
      id: a1s5msktijh2********
      folder_id: b1gmit33hgh2********
      created_at: "2022-10-24T15:19:15.353909857Z"
      name: my-trigger
      rule:
        object_storage:
          event_type:
          - OBJECT_STORAGE_EVENT_TYPE_CREATE_OBJECT
          - OBJECT_STORAGE_EVENT_TYPE_DELETE_OBJECT
          - OBJECT_STORAGE_EVENT_TYPE_UPDATE_OBJECT
          bucket_id: s3-for-trigger
          prefix: dev
          suffix: 12.jpg
          invoke_container:
            container_id: bba5jb38o8h2********
            service_account_id: aje3932acdh2********
            retry_settings:
              retry_attempts: "1"
              interval: 10s
            dead_letter_queue:
              queue-id: yrn:yc:ymq:ru-central1:aoek49ghmkh2********:dlq
              service-account-id: aje3932acdh2********
      status: ACTIVE
      ```

- Terraform {#tf}

  With [Terraform](https://www.terraform.io/), you can quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. These files store the infrastructure description written in HashiCorp Configuration Language (HCL). If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.
  
  Terraform is distributed under the [Business Source License](https://github.com/hashicorp/terraform/blob/main/LICENSE). The [Yandex Cloud provider for Terraform](https://github.com/yandex-cloud/terraform-provider-yandex) is distributed under the [MPL-2.0](https://www.mozilla.org/en-US/MPL/2.0/) license.
  
  For more information about the provider resources, see the guides on the [Terraform](https://www.terraform.io/docs/providers/yandex/index.html) website or [its mirror](../../terraform/index.md).

  If you do not have Terraform yet, [install it and configure the Yandex Cloud provider](../../tutorials/infrastructure-management/terraform-quickstart.md#install-terraform).
  
  
  To manage infrastructure using Terraform under a service account or user accounts (a Yandex account, a federated account, or a local user), [authenticate](../../terraform/authentication.md) using the appropriate method.

  1. Open the Terraform configuration file and edit the `function_trigger` resource settings:

      ```hcl
      resource "yandex_function_trigger" "my_trigger" {
        name        = "<timer_name>"
        timer {
          cron_expression = "<cron_expression>"
          payload         = "<message>"
        }
        container {
          id                 = "<container_ID>"
          service_account_id = "<service_account_ID>"
          retry_attempts     = <number_of_retry_attempts>
          retry_interval     = <time_between_retry_attempts>
        }
        dlq {
          queue_id           = "<dead-letter_queue_ID>"
          service_account_id = "<service_account_ID>"
        }
      }
      ```

      Where:

      * `name`: Timer name. The name format is as follows:

          * 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.

      * `timer`: Trigger settings:
          * `cron_expression`: Container invocation schedule specified as a [cron expression](../concepts/trigger/timer.md#cron-expression).
          * `payload`: Message to send to the function when the timer fires. The string length must not exceed 4,096 characters.

      * `container`: Settings for the container that will be activated by the trigger:

          * `id`: Container ID.
          * `service_account_id`: ID of the service account with permissions to invoke the container.

          * `retry_attempts`: Number of invocation retries before the trigger moves a message to the dead-letter queue. This is an optional setting. The values may range from 1 to 5. The default value is 1.
          * `retry_interval`: Time to wait before retrying the container invocation if it fails. This is an optional setting. The values may range from 10 to 60 seconds. The default value is 10 seconds.

      * `dlq`: Dead-letter queue settings:
          * `queue_id`: Dead-letter queue ID.
          * `service_account_id`: ID of the service account with write permissions for the dead-letter queue.

      For more on the properties of the `function_trigger` resource, see [this provider guide](../../terraform/resources/function_trigger.md).

  1. Create the resources:

      1. In the terminal, navigate to the configuration file directory.
      1. Make sure the configuration is correct using this command:
      
         ```bash
         terraform validate
         ```
      
         If the configuration is valid, you will get this message:
      
         ```bash
         Success! The configuration is valid.
         ```
      
      1. Run this command:
      
         ```bash
         terraform plan
         ```
      
         You will see a list of resources and their properties. No changes will be made at this step. Terraform will show any errors in the configuration.
      1. Apply the configuration changes:
      
         ```bash
         terraform apply
         ```
      
      1. Type `yes` and press **Enter** to confirm the changes.

      You can check the updates using the [management console](https://console.yandex.cloud) or this [CLI](../../cli/quickstart.md) command:

      ```bash
      yc serverless trigger list
      ```

- API {#api}

  To update trigger settings, use the [update](../triggers/api-ref/Trigger/update.md) REST API method for the [Trigger](../triggers/api-ref/Trigger/index.md) resource or the [TriggerService/Update](../triggers/api-ref/grpc/Trigger/update.md) gRPC API call.

{% endlist %}