cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: 03aabc8c-35d6-481e-9c85-20139cf72d23.md

title: CNI Plugin Does Not Support Network Policies hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 03aabc8c-35d6-481e-9c85-20139cf72d23 Query name: CNI Plugin Does Not Support Network Policies Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: Ensure the use of CNI Plugin that support Network Policies. If the CNI Plugin in use does not support Network Policies it may not be possible to effectively restrict traffic in the cluster<br> ```json title="Positive test num. 1 - json file" hl_lines="6" { "name": "k8s-pod-network", "cniVersion": "0.3.0", "plugins": [ { "type": "flannel", "log_level": "info", "datastore_type": "kubernetes", "nodename": "127.0.0.1", "ipam": { "type": "host-local", "subnet": "usePodCidr" }, "policy": { "type": "k8s" }, "kubernetes": { "kubeconfig": "/etc/cni/net.d/flannel-kubeconfig" } }, { "type": "portmap", "capabilities": {"portMappings": true} } ] } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="10" kind: ConfigMap apiVersion: v1 metadata: name: kube-flannel-cfg namespace: kube-system labels: tier: node app: flannel data: cni-conf.json: | { "name": "cbr0", "plugins": [ { "type": "flannel", "delegate": { "hairpinMode": true, "isDefaultGateway": true } }, { "type": "portmap", "capabilities": { "portMappings": true } } ] } net-conf.json: | { "Network": "10.244.0.0/16", "Backend": { "Type": "vxlan" } } ``` ```json title="Negative test num. 1 - json file" { "name": "k8s-pod-network", "cniVersion": "0.3.0", "plugins": [ { "type": "calico", "log_level": "info", "datastore_type": "kubernetes", "nodename": "127.0.0.1", "ipam": { "type": "host-local", "subnet": "usePodCidr" }, "policy": { "type": "k8s" }, "kubernetes": { "kubeconfig": "/etc/cni/net.d/calico-kubeconfig" } }, { "type": "portmap", "capabilities": {"portMappings": true} } ] } ``` ```yaml title="Negative test num. 2 - yaml file" kind: ConfigMap apiVersion: v1 metadata: name: kube-flannel-cfg namespace: kube-system labels: tier: node app: calico data: cni-conf.json: | { "name": "cbr0", "plugins": [ { "type": "calico", "delegate": { "hairpinMode": true, "isDefaultGateway": true } }, { "type": "portmap", "capabilities": { "portMappings": true } } ] } net-conf.json: | { "Network": "10.244.0.0/16", "Backend": { "Type": "vxlan" } } ```
Project: YugabyteDB (App Definition and Development / Database)
File: alert.md

title: Alerts in YugabyteDB Anywhere headerTitle: Alerts linkTitle: Alerts description: Use alerts menu: v2.18_yugabyte-platform: identifier: alert parent: alerts-monitoring weight: 10 type: docs YugabyteDB Anywhere allows you to view a list of generated alerts and manage these alerts by navigating to Alerts, as per the following illustration: By default, the list is sorted in reverse chronological order by the alert issue time. You can reorder the list by clicking column headers. {{< tip title="Configure alerts" >}} For information on configuring your alerts, both for universe and YugabyteDB Anywhere metrics, refer to . {{< /tip >}} You can access detailed information about a specific alert by clicking on its name to open the Alert Details dialog shown in the following illustration: The alert status and timeframe provide information on when the threshold was exceeded during the most recent alert check. For example, suppose there is an alert rule that checks if the average CPU utilization is higher than 75% for 15 minutes. In this case, the alert is triggered for as long as the CPU usage is higher than 75%. To avoid receiving continuous alerts, you can either acknowledge the active alert therefore preventing YugabyteDB Anywhere from sending additional notifications to the alert's destination, or you can resolve the alert by addressing the condition that triggered it. To summarize, the alert status can be active, acknowledged, or resolved. You change the status by taking an appropriate action, such as, for example, Acknowledge for an active alert. Note that if you are using a read-only account for YugabyteDB Anywhere, you cannot perform actions. For additional information, see the following:
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.81.md

layout: release date: 2023-04-14 tag: v0.6.81 Remove non-core K8s Meshmodel components @Revolyssup (#7549) Cleanup prettification code @Revolyssup (#7547) Revert "[update] Meshmodel categories icons updated" @ritiksaxena124 (#7550) Crawl oneOf, allOf and anyOf in schema validation process @Abhishek-kumar09 (#7552) Enhances snackbar @MdSahil-oss (#7517) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @MdSahil-oss, @Revolyssup, @leecalcote and @ritiksaxena124
Project: ClickHouse (App Definition and Development / Database)
File: log.md

slug: /en/engines/table-engines/log-family/log toc_priority: 33 toc_title: Log The engine belongs to the family of `Log` engines. See the common properties of `Log` engines and their differences in the article. `Log` differs from in that a small file of "marks" resides with the column files. These marks are written on every data block and contain offsets that indicate where to start reading the file in order to skip the specified number of rows. This makes it possible to read table data in multiple threads. For concurrent data access, the read operations can be performed simultaneously, while write operations block reads and each other. The `Log` engine does not support indexes. Similarly, if writing to a table failed, the table is broken, and reading from it returns an error. The `Log` engine is appropriate for temporary data, write-once tables, and for testing or demonstration purposes.
Project: YugabyteDB (App Definition and Development / Database)
File: yba_completion.md

Generate the autocompletion script for the specified shell Generate the autocompletion script for yba for the specified shell. See each sub-command's help for details on how to use the generated script. ``` -h, --help help for completion ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - yba - Command line tools to manage your YugabyteDB Anywhere (Self-managed Database-as-a-Service) resources. - Generate the autocompletion script for bash - Generate the autocompletion script for fish - Generate the autocompletion script for powershell - Generate the autocompletion script for zsh
Project: ShardingSphere (App Definition and Development / Database)
File: drop-sharding-table-rule.en.md

+++ title = "DROP SHARDING TABLE RULE" weight = 3 +++ The `DROP SHARDING TABLE RULE` syntax is used to drop sharding table rule for specified database. {{< tabs >}} {{% tab name="Grammar" %}} ```sql DropShardingTableRule ::= 'DROP' 'SHARDING' 'TABLE' 'RULE' ifExists? ruleName (',' ruleName)* ('FROM' databaseName)? ifExists ::= 'IF' 'EXISTS' ruleName ::= identifier databaseName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} When `databaseName` is not specified, the default is the currently used `DATABASE`. If `DATABASE` is not used, `No database selected` will be prompted; `ifExists` clause is used to avoid `Sharding rule not exists` error. Drop mutiple sharding table rules for specified database ```sql DROP SHARDING TABLE RULE torder, torderitem FROM shardingdb; ``` Drop a sharding table rule for current database ```sql DROP SHARDING TABLE RULE t_order; ``` Drop sharding table rule with `ifExists` clause ```sql DROP SHARDING TABLE RULE IF EXISTS t_order; ``` `DROP`, `SHARDING`, `TABLE`, `RULE`, `FROM`
Project: TiKV (App Definition and Development / Database)
File: pull_request_template.md

<!-- Thank you for contributing to TiKV! If you haven't already, please read TiKV's document. If you're unsure about anything, just ask; somebody should be along to answer within a day or two. PR Title Format: module [, module2, module3]: what's changed *: what's changed --> <!-- Please create an issue first to describe the problem. There MUST be one line starting with "Issue Number: " and linking the relevant issues via the "close" or "ref". For more info, check https://github.com/tikv/tikv/blob/master/CONTRIBUTING.md#linking-issues. --> Issue Number: Close #xxx <!-- You could use "commit message" code block to add more description to the final commit message. For more info, check https://github.com/tikv/tikv/blob/master/CONTRIBUTING.md#format-of-the-commit-message. --> What's Changed: ```commit-message ``` [ ] PR to update `pingcap/docs`/`pingcap/docs-cn`: [ ] Need to cherry-pick to the release branch Tests <!-- At least one of them must be included. --> [ ] Unit test [ ] Integration test [ ] Manual test (add detailed scripts or steps below) [ ] No code Side effects [ ] Performance regression: Consumes more CPU [ ] Performance regression: Consumes more Memory [ ] Breaking backward compatibility <!-- Compatibility change, improvement, bugfix, and new feature need a release note. Please refer to to write a quality release note. If you don't think this PR needs a release note then fill it with None. If this PR will be picked to release branch, then a release note is probably required. --> ```release-note ```
Project: KICS (Provisioning / Security & Compliance)
File: 86b0efa7-4901-4edd-a37a-c034bec6645a.md

title: SQS Queue Exposed hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 86b0efa7-4901-4edd-a37a-c034bec6645a Query name: SQS Queue Exposed Platform: Ansible Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: Checks if the SQS Queue is exposed<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="10 31" name: example community.aws.sqs_queue: name: my-queue region: ap-southeast-2 defaultvisibilitytimeout: 120 messageretentionperiod: 86400 maximummessagesize: 1024 delivery_delay: 30 receivemessagewait_time: 20 policy: Version: '2012-10-17' Id: sqspolicy Statement: Sid: First Effect: Allow Principal: '*' Action: sqs:SendMessage Resource: ${awssqsqueue.q.arn} Condition: ArnEquals: aws:SourceArn: ${awssnstopic.example.arn} name: example with list community.aws.sqs_queue: name: my-queue12 region: ap-southeast-1 defaultvisibilitytimeout: 120 messageretentionperiod: 86400 maximummessagesize: 1024 delivery_delay: 30 receivemessagewait_time: 20 policy: Version: "2012-10-17" Statement: Effect: "Allow" Action: "sqs:*" Resource: "*" Principal: "*" make_default: false state: present ``` ```yaml title="Negative test num. 1 - yaml file" name: example community.aws.sqs_queue: name: my-queue region: ap-southeast-2 defaultvisibilitytimeout: 120 messageretentionperiod: 86400 maximummessagesize: 1024 delivery_delay: 30 receivemessagewait_time: 20 policy: Version: '2012-10-17' Id: sqspolicy Statement: Sid: First Effect: Allow Action: sqs:SendMessage Resource: ${awssqsqueue.q.arn} Condition: ArnEquals: aws:SourceArn: ${awssnstopic.example.arn} ```
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_alter_foreign_table.md

title: ALTER FOREIGN TABLE statement [YSQL] headerTitle: ALTER FOREIGN TABLE linkTitle: ALTER FOREIGN TABLE description: Use the ALTER FOREIGN TABLE statement to alter a foreign table. menu: v2.18: identifier: ddlalterforeign_table parent: statements type: docs Use the `ALTER FOREIGN TABLE` command to alter a foreign table. {{%ebnf%}} alterforeigntable {{%/ebnf%}} Alter the foreign table named table_name. The `ADD COLUMN` clause can be used to add a new column to the foreign table. There's no effect on the underlying storage: the `ADD COLUMN` action just indicates that the newly added column can be accessed through the foreign table. The `DROP COLUMN` clause can be used to drop a column from the foreign table. `CASCADE` or `RESTRICT` can be specified. The `OWNER TO` clause can be used to specify the new_owner. The `OPTIONS` clause can be used to specify the new options of the foreign table. `ADD`, `SET`, and `DROP` specify the action to be performed. `ADD` is assumed if no operation is explicitly specified. The `RENAME TO` clause can be used to rename the foreign table to table_name. Adding a new column. ```plpgsql yugabyte=# ALTER FOREIGN TABLE mytable ADD COLUMN newcol int; ``` Change the options. ```plpgsql yugabyte=# ALTER FOREIGN TABLE my_table OPTIONS (ADD newopt1 'value1', DROP oldopt1 'value2', SET oldopt2 'value3'); ```
Project: KICS (Provisioning / Security & Compliance)
File: 04c686f1-e0cd-4812-88e1-4e038410074c.md

title: Group With Privilege Escalation By Actions 'iam:CreateLoginProfile' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 04c686f1-e0cd-4812-88e1-4e038410074c Query name: Group With Privilege Escalation By Actions 'iam:CreateLoginProfile' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Group with privilege escalation by actions 'iam:CreateLoginProfile' and Resource set to '*'. For more information see https://rhinosecuritylabs.com/aws/aws-privilege-escalation-methods-mitigation/.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsiamgroup" "cosmic" { name = "cosmic" } resource "awsiamgrouppolicy" "testinline_policy" { name = "testinlinepolicy" group = awsiamgroup.cosmic.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "iam:CreateLoginProfile", ] Effect = "Allow" Resource = "*" }, ] }) } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamuser" "cosmic2" { name = "cosmic2" } resource "awsiamuserpolicy" "inlinepolicyruninstances2" { name = "inlinepolicyrun_instances" user = awsiamuser.cosmic2.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "ec2:Describe*", ] Effect = "Allow" Resource = "*" }, ] }) } ```
Project: YugabyteDB (App Definition and Development / Database)
File: drop_sequence.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="593" height="70" viewbox="0 0 593 70"><path class="connector" d="M0 22h15m53 0h10m87 0h30m32 0h10m64 0h20m-141 0q5 0 5 5v8q0 5 5 5h116q5 0 5-5v-8q0-5 5-5m5 0h10m118 0h30m77 0h22m-109 25q0 5 5 5h5m79 0h5q5 0 5-5m-104-25q5 0 5 5v33q0 5 5 5h89q5 0 5-5v-33q0-5 5-5m5 0h15"/><polygon points="0,29 5,22 0,15" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="5" width="53" height="25" rx="7"/><text class="text" x="25" y="22">DROP</text><rect class="literal" x="78" y="5" width="87" height="25" rx="7"/><text class="text" x="88" y="22">SEQUENCE</text><rect class="literal" x="195" y="5" width="32" height="25" rx="7"/><text class="text" x="205" y="22">IF</text><rect class="literal" x="237" y="5" width="64" height="25" rx="7"/><text class="text" x="247" y="22">EXISTS</text><a xlink:href="../../../syntaxresources/grammardiagrams#sequence-name"><rect class="rule" x="331" y="5" width="118" height="25"/><text class="text" x="341" y="22">sequence_name</text></a><rect class="literal" x="479" y="5" width="77" height="25" rx="7"/><text class="text" x="489" y="22">CASCADE</text><rect class="literal" x="479" y="35" width="79" height="25" rx="7"/><text class="text" x="489" y="52">RESTRICT</text><polygon points="589,29 593,29 593,15 589,15" style="fill:black;stroke-width:0"/></svg>
Project: KICS (Provisioning / Security & Compliance)
File: ca02f4e8-d3ae-4832-b7db-bb037516d9e7.md

title: Request Body JSON Reference Does Not Exists hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ca02f4e8-d3ae-4832-b7db-bb037516d9e7 Query name: Request Body JSON Reference Does Not Exists Platform: OpenAPI Severity: <span style="color:#5bc0de">Info</span> Category: Structure and Semantics URL: Request Body reference should exists on components field<br> ```json title="Positive test num. 1 - json file" hl_lines="18" { "openapi": "3.0.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "$ref": "#/components/schemas/MyObject" } }, "requestBody": { "$ref": "#/components/requestBodies/MyWrongObjectBody" } } } }, "components": { "schemas": { "MyObject": { "type": "object", "properties": { "id": { "type": "string" }, "name": { "type": "string" } } } }, "requestBodies": { "MyObjectBody": { "description": "A JSON object containing my object information", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/MyObject" } } } } } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="14" openapi: 3.0.0 info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '200': "$ref": "#/components/schemas/MyObject" requestBody: "$ref": "#/components/requestBodies/MyWrongObjectBody" components: schemas: MyObject: type: object properties: id: type: string name: type: string requestBodies: MyObjectBody: description: A JSON object containing my object information content: application/json: schema: "$ref": "#/components/schemas/MyObject" ``` ```json title="Negative test num. 1 - json file" { "openapi": "3.0.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "$ref": "#/components/schemas/MyObject" } }, "requestBody": { "$ref": "#/components/requestBodies/MyObjectBody" } } } }, "components": { "schemas": { "MyObject": { "type": "object", "properties": { "id": { "type": "string" }, "name": { "type": "string" } } } }, "requestBodies": { "MyObjectBody": { "description": "A JSON object containing my object information", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/MyObject" } } } } } } } ``` ```yaml title="Negative test num. 2 - yaml file" openapi: 3.0.0 info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '200': "$ref": "#/components/schemas/MyObject" requestBody: "$ref": "#/components/requestBodies/MyObjectBody" components: schemas: MyObject: type: object properties: id: type: string name: type: string requestBodies: MyObjectBody: description: A JSON object containing my object information content: application/json: schema: "$ref": "#/components/schemas/MyObject" ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.10.19.md

RabbitMQ `3.10.19` is a maintenance release in the `3.10.x` . This series . Please refer to the upgrade section from if upgrading from a version prior to 3.10.0. This release requires Erlang 24.3 and supports Erlang 25. has more details on Erlang version requirements for RabbitMQ. Erlang 23 and 24 versions older than 24.3 have reached . This release of RabbitMQ or later versions. Nodes will fail to start on older Erlang releases. Erlang 25.3 is recommended: it offers much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation. Release notes can be found on GitHub at . Individual virtual host page failed to render. GitHub issue: Individual exchange page failed to render. GitHub issue: Support for Identity Provider-initiated Login (IDP). GitHub issues: , , , The `authoauth2.preferredusername_claims` key in `rabbitmq.conf` now accepts a list of values. GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.10.19.tar.xz` instead of the source tarball produced by GitHub.
Project: Artifact Hub (App Definition and Development / Application Definition & Image Build)
File: kcl_modules_repositories.md

KCL modules repositories are expected to be hosted in GitHub, GitLab or Bitbucket repos. When adding your repository to Artifact Hub, the url used must follow the following format: `https://github.com/user/repo[/path/to/packages]` `https://gitlab.com/user/repo[/path/to/packages]` `https://bitbucket.org/user/repo[/path/to/packages]` By default the `master` branch is used, but it's possible to specify a different one from the UI. Please NOTE that the repository URL used when adding the repository to Artifact Hub must NOT contain the git hosting platform specific parts, like tree/branch, just the path to your packages like it would show in the filesystem. The path/to/packages provided can contain metadata for one or more packages. Each package version must be on a separate folder, and it's up to you to decide if you want to publish one or multiple versions of your package. The structure of a repository with multiple modules packages and versions could look something like this: ```sh $ tree path/to/packages path/to/packages artifacthub-repo.yml package1 1.0.0 README.md artifacthub-pkg.yml 2.0.0 README.md artifacthub-pkg.yml package2 1.0.0 README.md artifacthub-pkg.yml ``` This structure is flexible, and in some cases where you only have a package and a version it can be greatly simplified. In the case of a single package with a single version available at a time (the publisher doesn't want to make previous ones available, for example), the structure could look like this: ```sh $ tree path/to/packages path/to/packages artifacthub-repo.yml package1 README.md artifacthub-pkg.yml ``` In the previous case, even the `package1` directory could be omitted. The reason is that both packages names and versions are read from the `artifacthub-pkg.yml` metadata file, so directories names are not used at all. Each package version needs an `artifacthub-pkg.yml` metadata file. Please see the file for more details. The repository metadata file shown above can be used to setup features like or . This file must be located at `/path/to/packages`. Once you have added your repository, you are all set up. As you add new versions of your modules packages or new packages to your git repository, they'll be automatically indexed and listed in Artifact Hub.