Creating a timer
-
In the management console
, select the folder where you want to create a connector. -
Select Serverless Integrations.
-
In the left-hand panel, click
EventRouter. -
Select the bus you need.
-
Navigate to the
Connectors tab. -
In the top-right corner, click Create connector.
-
In the Source field, select
Timer. -
Under Timer settings, specify:
- In the Cron expression field, an event generation schedule, in cron expression format.
- In the Time zone field, a time zone in tz database
format. This is an optional parameter. - In the Payload field, a message that goes to the bus if the timer goes off in the
payloadfield. This is an optional parameter.
-
Expand Additional parameters:
-
Enter a name and description for the connector. The naming requirements are as follows:
- The name must be from 3 to 63 characters long.
- It may contain uppercase and lowercase Latin and Cyrillic letters, numbers, hyphens, underscores, and spaces.
- The first character must be a letter. The last character cannot be a hyphen, underscore, or space.
-
Optionally, add labels:
- Click Add label.
- Enter a label in
key: valueformat. - Press Enter.
-
Optionally, enable deletion protection. You cannot delete a connector with this option enabled.
-
-
Click Create.
If you do not have the Yandex Cloud CLI installed yet, install and initialize it.
By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.
-
View the description of the CLI command to create a connector:
yc serverless eventrouter connector create timer --help -
Create a timer:
yc serverless eventrouter connector create timer \ --bus-id <bus_ID> \ --cron-expression <timer_schedule> \ --time-zone <time_zone> \ --payload <message> \ --name <connector_name> \ --description <connector_description> \ --labels <label_list> \ --deletion-protectionWhere:
-
--bus-id: EventRouter bus ID. -
--cron-expression: Event generation schedule in cron expression format. -
--time-zone: Time zone in tz database format. This is an optional parameter. -
--payload: Message sent to the bus if the timer fires. This is an optional parameter. -
--name: Connector name. Follow these naming requirements:- The name must be from 3 to 63 characters long.
- It may contain uppercase and lowercase Latin and Cyrillic letters, numbers, hyphens, underscores, and spaces.
- The first character must be a letter. The last character cannot be a hyphen, underscore, or space.
-
--description: Connector description. This is an optional parameter. -
--labels: List of labels. This is an optional parameter.You can specify one or more labels separated by commas in
<key1>=<value1>,<key2>=<value2>format. -
--deletion-protection: Connector deletion protection. By default, protection is disabled. You cannot delete a connector with this option enabled. To disable deletion protection, specify--no-deletion-protection. This is an optional parameter.
Result:
id: f66l8kgo20d8******** bus_id: f66qn4p7uk6p******** folder_id: b1g681qpemb4******** cloud_id: b1gia87mbaom******** created_at: "2025-02-21T09:04:33.248254Z" name: mq-via-cli description: created via cli labels: interface: yccli owner: admin source: timer: cron_expression: '*/5 * * ? * *' time_zone: Europe/Moscow payload: '{"message": "Hello, world!"}' deletion_protection: true status: RUNNING -
With Terraform
Terraform is distributed under the Business Source License
For more information about the provider resources, see the relevant documentation on the Terraform
If you do not have Terraform yet, install it and configure the Yandex Cloud provider.
To create a timer:
-
In the configuration file, describe the properties of resources you want to create:
resource "yandex_serverless_eventrouter_connector" "example_connector" { bus_id = "<bus_ID>" name = "<connector_name>" description = "<connector_description>" deletion_protection = <true|false> labels = { <key_1> = "<value_1>" <key_2> = "<value_2>" ... <key_n> = "<value_n>" } timer { cron_expression = "<schedule_for_generating_events>" timezone = "<time_zone>" payload = "<message>" } }Where:
-
bus_id: EventRouter bus ID. -
name: Connector name. Follow these naming requirements:- The name must be from 3 to 63 characters long.
- It may contain uppercase and lowercase Latin and Cyrillic letters, numbers, hyphens, underscores, and spaces.
- The first character must be a letter. The last character cannot be a hyphen, underscore, or space.
-
description: Connector description. This is an optional parameter. -
deletion_protection: Connector deletion protection,trueorfalse. You cannot delete a connector with this option enabled. This is an optional parameter. -
labels: List of labels. Provide labels in<key> = "<value>"format. This is an optional parameter. -
cron_expression: Event generation schedule in cron expression format. -
timezone: Time zone in tz database format. This is an optional parameter. -
payload: Message sent to the bus if the timer fires. This is an optional parameter.
For more information about the
yandex_serverless_eventrouter_connectorresource parameters, see the provider documentation. -
-
Create the resources:
-
In the terminal, go to the directory where you edited the configuration file.
-
Make sure the configuration file is correct using this command:
terraform validateIf the configuration is correct, you will get this message:
Success! The configuration is valid. -
Run this command:
terraform planYou will see a detailed list of resources. No changes will be made at this step. If the configuration contains any errors, Terraform will show them.
-
Apply the changes:
terraform apply -
Type
yesand press Enter to confirm the changes.
Terraform will create all the required resources. You can check the new resources using the management console
or this CLI command:yc serverless eventrouter connector list -
To create a timer, use the Create REST API method for the connector resource or the connector/Create gRPC API call.
By default, the system creates a running connector. Stop the connector to prevent it from sending messages to the bus.