cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: eccc4d59-74b9-4974-86f1-74386e0c7f33.md

title: BOM - AWS SNS hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: eccc4d59-74b9-4974-86f1-74386e0c7f33 Query name: BOM - AWS SNS Platform: Terraform Severity: <span style="color:#CCCCCC">Trace</span> Category: Bill Of Materials URL: A list of SNS resources specified. Amazon Simple Notification Service (Amazon SNS) is a fully managed messaging service for both application-to-application (A2A) and application-to-person (A2P) communication.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awssnstopic" "positive1" { name = "user-updates-topic" } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="1" resource "awssnstopic" "positive2" { name = "user-updates-topic" } resource "awssnstopic_policy" "positive2" { arn = awssnstopic.positive2.arn policy = <<EOF { "Version": "2012-10-17", "Statement": [ { "Sid": "AWSConfigSNSPolicy20180202", "Action": [ "*" ], "Effect": "Allow", "Resource": "awssnstopic.positive2.arn", "Principal": { "AWS": "*" } } ] } EOF } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="1" resource "awssnstopic" "positive3" { name = "user-updates-topic" } resource "awssnstopic_policy" "positive3" { arn = awssnstopic.positive3.arn policy = <<EOF { "Version": "2012-10-17", "Statement": [ { "Sid": "AWSConfigSNSPolicy20180202", "Action": [ "*" ], "Effect": "Allow", "Resource": "awssnstopic.positive3.arn", "Principal" : { "AWS": [ "arn:aws:iam::123456789012:root", "arn:aws:iam::555555555555:root" ] } } ] } EOF } ``` <details><summary>Positive test num. 4 - tf file</summary> ```tf hl_lines="1" resource "awssnstopic" "positive4" { name = "user-updates-topic" policy = <<EOF { "Version": "2012-10-17", "Statement": [ { "Sid": "AWSConfigSNSPolicy20180202", "Action": [ "*" ], "Effect": "Allow", "Resource": "awssnstopic.positive4.arn", "Principal": { "AWS": "*" } } ] } EOF } ``` </details> <details><summary>Positive test num. 5 - tf file</summary> ```tf hl_lines="1" resource "awssnstopic" "positive5" { tags = { Name = "SNS Topic" } kmsmasterkey_id = "alias/aws/sns" policy = <<EOF { "Version": "2012-10-17", "Statement": [ { "Sid": "AWSConfigSNSPolicy20180202", "Action": [ "*" ], "Effect": "Allow", "Resource": "awssnstopic.positive5.arn", "Principal" : { "AWS": [ "arn:aws:iam::123456789012:root", "arn:aws:iam::555555555555:root" ] } } ] } EOF } ``` </details> ```tf title="Negative test num. 1 - tf file" module "sns_topic" { source = "terraform-aws-modules/sns/aws" version = "~> 3.0" name = "my-topic" } ```
Project: KICS (Provisioning / Security & Compliance)
File: 982aa526-6970-4c59-8b9b-2ce7e019fe36.md

title: API Gateway With CloudWatch Logging Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 982aa526-6970-4c59-8b9b-2ce7e019fe36 Query name: API Gateway With CloudWatch Logging Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: AWS CloudWatch Logs for APIs should be enabled and using the naming convention described in documentation<br> ```tf title="Positive test num. 1 - tf file" hl_lines="14" variable "stage_name" { default = "example" type = string } variable "stage_names" { default = "examples" type = string } resource "awsapigatewayrestapi" "example" { } resource "awsapigateway_stage" "example" { dependson = [awscloudwatchloggroup.example] stagename = var.stagename } resource "awscloudwatchlog_group" "example" { name = "API-Gateway-Execution-Logs${awsapigatewayrestapi.example.id}/${var.stagenames}" retentionindays = 7 } ``` ```tf title="Negative test num. 1 - tf file" variable "stage_name" { default = "example" type = string } resource "awsapigatewayrestapi" "example" { } resource "awsapigateway_stage" "example" { dependson = [awscloudwatchloggroup.example] stagename = var.stagename } resource "awscloudwatchlog_group" "example" { name = "API-Gateway-Execution-Logs${awsapigatewayrestapi.example.id}/${var.stagename}" retentionindays = 7 } ``` ```tf title="Negative test num. 2 - tf file" module "env" { source = "./env" } resource "awsapigatewayrestapi" "example" { } resource "awsapigateway_stage" "example" { dependson = [awscloudwatchloggroup.example] stagename = module.env.vars.stagename } resource "awscloudwatchlog_group" "example" { name = "API-Gateway-Execution-Logs${awsapigatewayrestapi.example.id}/${module.env.vars.stagename}" retentionindays = 7 } ```
Project: MongoDB (App Definition and Development / Database)
File: yaml-cpp.natvis.md

Add yaml-cpp.natvis to your Visual C++ project like any other source file. It will be included in the debug information, and improve debugger display on YAML::Node and contained types. This has been tested for MSVC 2017. It is expected to be compatible with VS 2015 and VS 2019. If you have any problems, you can open an issue here: https://github.com/peterchen-cp/yaml-cpp-natvis
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_instance_groups.md

+++ title = "googlecomputeinstance_groups resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputeinstance_groups" identifier = "inspec/resources/gcp/googlecomputeinstancegroups.md googlecomputeinstancegroups resource" parent = "inspec/resources/gcp" +++ A `googlecomputeinstance_groups` is used to test a Google InstanceGroup resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputeinstance_groups(project: 'chef-gcp-inspec', zone: 'zone') do its('instancegroupnames') { should include 'inspec-instance-group' } end ``` describe googlecomputeinstance_groups(project: 'chef-inspec-gcp') do its('count') { should be <= 100} end describe googlecomputeinstance_groups(project: 'chef-inspec-gcp', zone: 'europe-west2-a') do its('instancegroupnames') { should include "my-instance-group-name" } end googlecomputeinstancegroups(project: 'chef-inspec-gcp', zone: 'europe-west2-a').where(instancegroupname: /^mig/).instancegroupnames.each do |instancegroup_name| describe googlecomputeinstancegroup(project: 'chef-inspec-gcp', zone: 'europe-west2-a', name: instancegroup_name) do it { should exist } its('size') { should be > 0 } end end Properties that can be accessed from the `googlecomputeinstance_groups` resource: See the resource for more information. `creation_timestamps` : an array of `googlecomputeinstancegroup` creationtimestamp `descriptions` : an array of `googlecomputeinstance_group` description `instancegroupids` : an array of `googlecomputeinstance_group` id `instancegroupnames` : an array of `googlecomputeinstance_group` name `named_ports` : an array of `googlecomputeinstancegroup` namedports `networks` : an array of `googlecomputeinstance_group` network `regions` : an array of `googlecomputeinstance_group` region `subnetworks` : an array of `googlecomputeinstance_group` subnetwork `zones` : an array of `googlecomputeinstance_group` zone This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.
Project: ThreatMapper (Provisioning / Security & Compliance)
File: VENDORED_CODE.md

Weave Scope is licensed under the . Some vendored code is under different licenses though, all of them ship the entire license text they are under. https://github.com/weaveworks/go-checkpoint https://github.com/weaveworks/go-cleanhttp https://github.com/certifi/gocertifi can be found in the ./vendor/ directory, is under MPL-2.0. Pulled in by dependencies are https://github.com/hashicorp/go-version (MPL-2.0) https://github.com/hashicorp/golang-lru (MPL-2.0) One file pulled in by a dependency is under CDDL: ./vendor/github.com/howeyc/gopass/terminal_solaris.go The docs of a dependency that's pulled in by a dependency are under CC-BY 4.0: ./vendor/github.com/docker/go-units/ is under LGPL-3, that's why we ship the license text in this repository.
Project: Matano (Provisioning / Security & Compliance)
File: SECURITY.md

We appreciate your help in making Matano secure. We take security issues very seriously and strive to fix all security issues as soon as they're reported. | Version | Supported | | - | | | All | :whitecheckmark: | Please do not open a Github Issue for security issues you encounter. Instead, please send an email to security@matano.dev describing the issue and we'll respond as soon as possible. You may use the following PGP public key when contacting to report a vulnerability. <details><summary>Matano PGP Public Key</summary> ``` --BEGIN PGP PUBLIC KEY BLOCK-- mQGNBGMcl30BDACzxi8NnBaZze5uMfsIKQb2m9bsAigQER7SY3XZZLiwBCLx+2cm 4GB1ILA80xn1xzjiM8nZNXRQ9CaHI+3LbtX3xOt26/4ZiAbzIApc9R2hQMby0N6z yn9aD5VmJlnKJjRshpl8jsFv5od/tdyK990XIMBppxNt3DT9MEK6/epn7ZR61EmL e4ldLv7RpYwPWuk5ACmFCIZPWfloHVeUZCu/NmLzMJP4qvx7tPoJ+hDGTZ9ILivC BYe7ZbXhBAbATX+EK+D49EQ0BO74Sp3oTK9oypbP6iIAl4HXritAsJmDxOi/uwDY 4whii+YIRKRgmOKlnDw1L5h+Be/OhNpFCby2d4j/g2AAS1dWY5pNoOfhoErgIeiR jxiYsO8BIJ8linyQ8orB05fRZbMdjo13827AMnIcJIEaggRBlaU8pVu9prJJryB/ jx9mRzWB2KZuhq83aWkVXb1ZLqPRcOr0tnASctc2wciOtitGuwcG5i3YMAaG9Cy3 yDr2+2FPWIw7Eq8AEQEAAbQgTWF0YW5vIExhYnMgPHN1cHBvcnRAbWF0YW5vLmRl dj6JAc4EEwEKADgWIQTG7ud4szRiEG9jmRAzdPG4GgGUEQUCYxyXfQIbAwULCQgH AgYVCgkICwIEFgIDAQIeAQIXgAAKCRAzdPG4GgGUEdleC/oDebqvwUjrJ+bc6BSb KHKi2rR3vMVkfBsqYsoq9+nogNYVHBzXFLqBoAiI5ztQWV4n1MrWcGgqoN9HyqnM zBXIuaME92br6UvHaWeHCcjs65VkFy6Jujk6MWjaFty1Kt8H0znTcD/UYBU05VnG wAptCGwB9GXQk3GR3SFZ/6mx9xxGFud6APZn0XTrLX0939S1BhT8dd7V+Yr6KsTe gYX1c3e3Qp0E0lpO8E8+UMqou7Nbe/+NU/J3/bO8ywrZ5a1CWasEQkQXsCKOCF2e 9G/tOoZ+B0ko3TlBxUtWNz+yfNSgskto3suVzp/bURqTDBqUvFVPn+seFzPJw87Y 3HQjMehnZLZQOQhg/JidJK0ZRBhLSmkr63vIHzzTdBdwzfTa4/ryql30y/BtogzT 6/LMr9SFIdgsbJRtu/ybdi/ER8CRz07b4l04GBUi7qKW+FDsUqXvAL0yJmK6JeEi B+JmFae6TVZGFH8ewMzl1jBpvTz2ubet5Ft9u2igoKNu7dK5AY0EYxyXfQEMANlS ZMeM2D8TN344oDfiSgdKMIRMccMzLlgNFpL9aVP0esy1iYOomhURuPMwrjh+5kRM d9jml33y9mtLgSJTKOGOX9mG/vWKUxm5s0OrTIVw2mdGHq6mskFbbT8dek4H8CBQ dJwf6mLcgJQ2H8ulcsvBEM0W8wME2tHFAcnc4+R7O9WLlbVhPvGWaLpe8oNsZMvv lNTDw7ZyRqv4wY9VHHorMmh93lB9813aRvhettyxYA45CFCFgBRBrnjctgpItJk8 Ha1TSRX6VoEDYufE/GMJ3z0qYqzKQVk6+LB/PxXnYeqdDkpoq+Xc6ocGpDwC0B+R 2Zy/VLqU5YisLGQOosnPNd0QucszvNkPhXilrbS+SEmzAzyW8sOo8xXhKIxsTbw8 mMP6+wIrldJpLn+OHu+q9yyOvKHvCw3MzpcjRWWZvfJdRvFIH5iRKuW6DF2oLLIH Zy9us7MX4IhVj+NDknDin/9cjhivJR23OPXnk9JFTCfoSigwMPr4FB0aHNBfEwAR AQABiQG2BBgBCgAgFiEExu7neLM0YhBvY5kQM3TxuBoBlBEFAmMcl30CGwwACgkQ M3TxuBoBlBE4NQwAgz1gh9eAS2PsxrZI6vty21V4aaAoRUW757ktOfs9ZtHqSEPR lLhlMnhYO0h00FdG4yVg65Vr93RGKPcIrWHAdZAMn+/GY4NqMBdAHOo0WM3FGIoO D50LcPE7OwjDOuI8a4bz0jZe29RvET2jmrl4zN8H0tbSzdEp7K+cT/HTjKXyRIGQ AnVfKFzj50x75+L6OvMU3tkSsVS7SFZUD0cWCekr0LRZKA4D5LAYaMZN57W/7cYj gWFSED0Re8bcWUSvdRlsEUYvRZ6JWhq4O9E+25fayDky4Xo7vZYZ3I3AYVRuzfrY yXo2Z1kj3sb/Nt/++NksoE3rxJYqEj3Lf6IiJq8ANHiR4TsbBsngIGIP648DXzwy wMzhDerSX5DKnkY6lcRoZjYurwEORl4X9N7fE7yoyMkDknRCHtIN49vTF5QcLcEI pFKd+2Dawz/X7kBWHL8J9murTfhuA0Sl7Zn7FC49gzondVJqZBngbW7qysfUx07z FXm9MedEAPNT2hc9 =BE9X --END PGP PUBLIC KEY BLOCK-- ``` </details>
Project: YDB (App Definition and Development / Database)
File: CONTRIBUTING.md

Hello! In order for us (YANDEX LLC) to accept patches and other contributions from you, you will have to adopt our Yandex Contributor License Agreement (the CLA). The current version of the CLA you may find here: 1) https://yandex.ru/legal/cla/?lang=en (in English) and 2) https://yandex.ru/legal/cla/?lang=ru (in Russian). By adopting the CLA, you state the following: You obviously wish and are willingly licensing your contributions to us for our open source projects under the terms of the CLA, You has read the terms and conditions of the CLA and agree with them in full, You are legally able to provide and license your contributions as stated, We may use your contributions for our open source projects and for any other our project too, We rely on your assurances concerning the rights of third parties in relation to your contributes. If you agree with these principles, please read and adopt our CLA. By providing us your contributions, you hereby declare that you has already read and adopt our CLA, and we may freely merge your contributions with our corresponding open source project and use it in further in accordance with terms and conditions of the CLA. If you have already adopted terms and conditions of the CLA, you are able to provide your contributes. When you submit your pull request, please add the following information into it: ``` I hereby agree to the terms of the CLA available at: [link]. ``` Replace the bracketed text as follows: [link] is the link at the current version of the CLA (you may add here a link https://yandex.ru/legal/cla/?lang=en (in English) or a link https://yandex.ru/legal/cla/?lang=ru (in Russian). It is enough to provide us such notification at once. If you have any questions, please mail us at opensource@yandex-team.ru.
Project: StarRocks (App Definition and Development / Database)
File: protobuf-guides.md

displayed_sidebar: "English" As the project involving, any fields may become optional. But if it is defined as required, it can not be removed. So `required` should not be used. To be back compatible, the ordinal of the field SHOULD NOT be changed. The names of messages are all lowercase, with underscores between words. Files should end in `.proto`. ``` my_message.proto // Good mymessage.proto // Bad my_message.pb // Bad ``` Message names start with a capital letter and have a capital letter for each new word, with no underscores, and with `PB` as postfix: MyMessagePB ```protobuf message MyMessagePB // Good message MyMessage // Bad message MyMessagePB // Bad message myMessagePB // Bad ``` The names of messages are all lowercase, with underscores between words. ``` optional int64 my_field = 3; // Good optional int64 myField = 3; // Bad ```
Project: StarRocks (App Definition and Development / Database)
File: url_encode.md

displayed_sidebar: "English" Translates a string into the format. This functions is supported from v3.2. ```haskell VARCHAR url_encode(VARCHAR str) ``` `str`: the string to encode. If `str` is not a string, this function will try implicit cast first. Returns an encoded string compliant with the format. ```plaintext mysql> select urlencode('https://docs.starrocks.io/docs/introduction/StarRocksintro/'); +-+ | urlencode('https://docs.starrocks.io/docs/introduction/StarRocksintro/') | +-+ | https%3A%2F%2Fdocs.starrocks.io%2Fdocs%2Fintroduction%2FStarRocks_intro%2F | +-+ ```
Project: StarRocks (App Definition and Development / Database)
File: concat.md

displayed_sidebar: "English" This function combines multiple strings. If any of the parameter value is NULL, it will return NULL. ```Haskell VARCHAR concat(VARCHAR,...) ``` ```Plain Text MySQL > select concat("a", "b"); ++ | concat('a', 'b') | ++ | ab | ++ MySQL > select concat("a", "b", "c"); +--+ | concat('a', 'b', 'c') | +--+ | abc | +--+ MySQL > select concat("a", null, "c"); ++ | concat('a', NULL, 'c') | ++ | NULL | ++ ``` CONCAT
Project: KICS (Provisioning / Security & Compliance)
File: ffb02aca-0d12-475e-b77c-a726f7aeff4b.md

title: Log Retention Is Not Set hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ffb02aca-0d12-475e-b77c-a726f7aeff4b Query name: Log Retention Is Not Set Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Make sure that for PostgreSQL Database, server parameter 'log_retention' is set to 'ON'<br> ```tf title="Positive test num. 1 - tf file" hl_lines="19 12 5" resource "azurermpostgresqlconfiguration" "positive1" { name = "log_retention" resourcegroupname = data.azurermresourcegroup.example.name servername = azurermpostgresql_server.example.name value = "off" } resource "azurermpostgresqlconfiguration" "positive2" { name = "log_retention" resourcegroupname = data.azurermresourcegroup.example.name servername = azurermpostgresql_server.example.name value = "Off" } resource "azurermpostgresqlconfiguration" "positive3" { name = "log_retention" resourcegroupname = data.azurermresourcegroup.example.name servername = azurermpostgresql_server.example.name value = "OFF" } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermpostgresqlconfiguration" "negative1" { name = "log_retention" resourcegroupname = data.azurermresourcegroup.example.name servername = azurermpostgresql_server.example.name value = "on" } resource "azurermpostgresqlconfiguration" "negative2" { name = "log_retention" resourcegroupname = data.azurermresourcegroup.example.name servername = azurermpostgresql_server.example.name value = "On" } resource "azurermpostgresqlconfiguration" "negative3" { name = "log_retention" resourcegroupname = data.azurermresourcegroup.example.name servername = azurermpostgresql_server.example.name value = "ON" } ```
Project: ArangoDB (App Definition and Development / Database)
File: success.md

+++ title = "`auto success(T &&, ...)`" description = "Returns appropriate type sugar for constructing a successful result or outcome." +++ Returns appropriate type sugar for constructing a successful result or outcome, usually {{% api "success_type<T>" %}} with a decayed `T`. Two default overloads are provided, one taking a single required parameter with optional spare storage value parameter returning `successtype<std::decayt<T>>` and perfectly forwarding the input. The other overload takes no parameters, and returns `successtype<void>`, which usually causes the construction of the receiving `basicresult` or `basic_outcome`'s with a default construction of their value type. Overridable: By Argument Dependent Lookup (ADL). Requires: Always available. Namespace: `BOOSTOUTCOMEV2_NAMESPACE` Header: `<boost/outcome/success_failure.hpp>`
Project: Druid (App Definition and Development / Database)
File: flaky_test.md

name: Flaky Test about: A template for Druid CI flaky test reports title: "Flaky Test: test name" labels: Flaky Test assignees: '' Please replace 'test name' in the title with the actual test name. Also include a stack trace as well as link to a failing test run, along with any investigation you might have done to triage the issue.
Project: YugabyteDB (App Definition and Development / Database)
File: connect-ycql.md

title: YCQL API connection issues linkTitle: YCQL API connection issues description: Cannot connect to YCQL API aliases: /troubleshoot/cluster/connect-cassandra/ menu: preview: parent: troubleshoot-cluster weight: 822 type: docs To troubleshoot YCQL API connection issues, you should perform a number of checks. You should ensure that the expected YugabyteDB processes are on the current node. At a minimum, the YB-TServer process needs to be running to be able to connect to this node with a YCQL client or application. Additionally, depending on the setup, you might expect a YB-Master process to also be running on this node. For detailed instructions, see . If the YB-TServer process is running, execute the following command to verify that the YCQL API is enabled and listening on the YCQL port (default `9042`): ```sh lsof -i :9042 ``` ```output COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME yb-tserve 81590 centos 131u IPv4 0xdeadbeef 0t0 TCP localhost:9042 (LISTEN) ``` You may need to install `lsof` first. When running a local cluster with `yb-ctl`, you should see all the nodes with different IP addresses, as per the following example: ```sh lsof -i :9042 ``` ```output COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME yb-tserve 81590 centos 131u IPv4 0xdeadbeef 0t0 TCP localhost:9042 (LISTEN) yb-tserve 81593 centos 131u IPv4 0xdeadbeef 0t0 TCP 127.0.0.2:9042 (LISTEN) yb-tserve 81596 centos 131u IPv4 0xdeadbeef 0t0 TCP 127.0.0.3:9042 (LISTEN) ``` If another process is using this port, you might need to stop that and restart the YB-TServer process. Otherwise, if no process is listening but the YB-TServer is running, check the value of the `--cqlproxybind_address` flag passed to the YB-TServer process. Once on the machine where YugabyteDB is running, use `ycqlsh` to connect to the local YugabyteDB instance, as follows: ```sh ycqlsh <yb-local-address> ``` Depending on your configuration, you may need to install `ycqlsh`; otherwise, it is available in the YugabyteDB `bin` directory. In the preceding command, `<yb-local-address>` is the address where the YugabyteDB YCQL server is listening (for example, as returned by `lsof`). For instance, it maps to `localhost` in the examples presented in this document (or, additionally, `127.0.0.2` and `127.0.0.3` for the `yb-ctl` case). If `ycqlsh` can connect, the issue is likely a network issue with the original client not being able to access the node where YugabyteDB is running. See also
Project: Cadence Workflow (Provisioning / Automation & Configuration)
File: flow.md

Below diagram demonstrates how a workflow is processed by Cadence workers and backend components. Note that this is a partial diagram that only highlights selected components and their interactions. There is more happening behind the scenes. ```mermaid flowchart TD User((Domain X Admin)) -->|"0. Deploy worker with config: domain, tasklist(s)"| Worker[[\nDomain X Worker\n\n]] ExternalInitiator(("Domain X\nAnother Service/CLI")) -->|"1. Start/Signal Workflow"| Frontend Worker -->|2. Poll tasks for domain: X, tasklist: tl1| Frontend[[\nCadence Frontend\n\n]] Frontend -->|3. Forward Poll request| Matching[[\nCadence Matching\n\n]] Matching -->|4. Poll| TaskListManager(Tasklist Manager for tl1) TaskListManager -->|5. Long Poll| WaitUntilTaskFound WaitUntilTaskFound --> |6. Return task to worker| Worker Worker -->|7. Generate decisions\n& respond| Frontend Frontend -->|8. Respond decisions| History[[\nCadence History\n\n]] History -->|9. Mutable state update| ExecutionsStore[(Executions Store)] History -->|10.a. Notify| HistoryQueue(History Queues - per shard) HistoryQueue -->|Periodic task fetch| ExecutionsStore HistoryQueue -->|11.b. Execute transfer task| TransferTaskExecutor(Transfer Task Executor) HistoryQueue -->|11.a. Execute timer task| TimerTaskExecutor(Timer Task Executor) HistoryQueue -->|Periodic per-shard offset save| ShardsStore[(Shards Store)] TransferTaskExecutor -->|12.b. Add task| Matching TimerTaskExecutor -->|12.a. Add task| Matching Matching -->|13. Add task| TaskListManager TaskListManager -->|14. Add task| SyncMatch{Check sync match} SyncMatch -->|15.b. Found poller - Do sync match| SyncMatched SyncMatch -->|15.a. No pollers - Save task| TasksStore[(Tasks Store)] TaskListManager -->|Periodic task fetch| TasksStore ``` In order to leverage , Cadence stores multiple types of records in the same `executions` table. () Shards Store: Shard records are stored in `executions` table with type=0. Executions Store: Execution records are stored in `executions` table with type=1 Tasks Store: Task records are stored in `executions` table with type={2,3,4,5}