cwielenb/CNCF-Dataset huggingface dataset:
Project: StarRocks (App Definition and Development / Database)
File: tables.md

displayed_sidebar: "English" `tables` provides information about tables. The following fields are provided in `tables`: | Field | Description | | | | | TABLE_CATALOG | Name of the catalog that stores the table. | | TABLE_SCHEMA | Name of the database that stores the table. | | TABLE_NAME | Name of the table. | | TABLE_TYPE | Type of the table. Valid values: `BASE TABLE` or `VIEW`. | | ENGINE | Engine type of the table. Valid values: `StarRocks`, `MySQL`, `MEMORY` or an empty string. | | VERSION | Applies to a feature not available in StarRocks. | | ROW_FORMAT | Applies to a feature not available in StarRocks. | | TABLE_ROWS | Row count of the table. | | AVGROWLENGTH | Average row length (size) of the table. It is equivalent to `DATALENGTH`/`TABLEROWS`. Unit: Byte. | | DATA_LENGTH | Data length (size) of the table. Unit: Byte. | | MAXDATALENGTH | Applies to a feature not available in StarRocks. | | INDEX_LENGTH | Applies to a feature not available in StarRocks. | | DATA_FREE | Applies to a feature not available in StarRocks. | | AUTO_INCREMENT | Applies to a feature not available in StarRocks. | | CREATE_TIME | The time when the table was created. | | UPDATE_TIME | The last time when the table was updated. | | CHECK_TIME | The last time when a consistency check was performed on the table. | | TABLE_COLLATION | The default collation of the table. | | CHECKSUM | Applies to a feature not available in StarRocks. | | CREATE_OPTIONS | Applies to a feature not available in StarRocks. | | TABLE_COMMENT | Comment on the table. |
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: cpu-rt-runtime.md

Limit the CPU real-time runtime in microseconds. Limit the containers Real Time CPU usage. This option tells the kernel to limit the amount of time in a given CPU period Real Time tasks may consume. Ex: Period of 1,000,000us and Runtime of 950,000us means that this container can consume 95% of available CPU and leave the remaining 5% to normal priority tasks. The sum of all runtimes across containers cannot exceed the amount allotted to the parent cgroup. This option is only supported on cgroups V1 rootful systems.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: feature-and-limit-list-pg.md

title: Full feature and limit list description: The full feature and limit list of KubeBlocks migration function for PostgreSQL keywords: [postgresql, migration, migrate data in PostgreSQL to KubeBlocks, full feature, limit] sidebar_position: 1 sidebar_label: Full feature and limit list Precheck Database connection Database version Whether the incremental migration is supported by a database The existence of the table structure Whether the table structure of the source database is supported Structure initialization PostgreSQL Table Struct Table Constraint Table Index Comment Table Sequence Data initialization Supports all major data types Incremental data migration Supports all major data types Support the resumable upload capability of eventual consistency Overall limits If the incremental data migration is used, the source database should enable CDC (Change Data Capture) related configurations (both are checked and blocked in precheck). A table without a primary key is not supported. And a table with a foreign key is not supported (both are checked and blocked in precheck). Except for the incremental data migration module, other modules do not support resumable upload, i.e. if an exception occurs in this module, such as pod failure caused by downtime and network disconnection, a re-migration is required. During the data transmission task, DDL on the migration objects in the source database is not supported. The table name and field name cannot contain Chinese characters and special characters like a single quotation mark (') and a comma (,). During the migration process, the switchover of primary and secondary nodes in the source library is not supported, which may cause the connection string specified in the task configuration to change. This further leads to migration link failure. Precheck module: None Structure initialization module The Array data type is not supported, such as text, integer[]. The user-defined type is not supported. The database character set other than UTF-8 is not supported. Data initialization module Character sets of the source and sink databases should be the same. Data incremental migration module Character sets of the source and sink databases should be the same.
Project: GreptimeDB (App Definition and Development / Database)
File: README.md

This crate provides an easy approach to dump memory profiling info. ```bash brew install jemalloc sudo apt install libjemalloc-dev ``` ```bash curl https://raw.githubusercontent.com/brendangregg/FlameGraph/master/flamegraph.pl > ./flamegraph.pl ``` ```bash cargo build --features=mem-prof ``` Start GreptimeDB instance with environment variables: ```bash MALLOCCONF=prof:true,lgprof_interval:28 ./target/debug/greptime standalone start ``` Dump memory profiling data through HTTP API: ```bash curl localhost:4000/v1/prof/mem > greptime.hprof ``` You can periodically dump profiling data and compare them to find the delta memory usage. To create flamegraph according to dumped profiling data: ```bash jeprof --svg <pathtogreptimedbbinary> --base=<baselineprof> <profile_data> > output.svg ``` ill use `conf/kafka-cluster.yml` to start a Kafka cluster. This requires `docker` and `docker-compose` commands in your environment. Otherwise, you can additionally pass the your existing kafka environment to sqlness with `-k` option. E.g.: ```shell cargo sqlness -w kafka -k localhost:9092 ``` In this case, sqlness will not start its own kafka cluster and the one you provided instead. Unlike other tests, this harness is in a binary target form. You can run it with: ```shell cargo sqlness ``` It automatically finishes the following procedures: compile `GreptimeDB`, start it, grab tests and feed it to the server, then collect and compare the results. You only need to check if the `.result` files are changed. If not, congratulations, the test is passed !
Project: Teleport (Provisioning / Security & Compliance)
File: 0024-dynamo-event-overflow.md

authors: Joel Wejdenstal (jwejdenstal@goteleport.com) state: implemented This RFD was sparked from a discussion about event storage, scaling and DynamoDB between me, Russell and Sasha. Rework the existing read-only global secondary index view to partition on the day of the event instead of the hard coded string `default`. DynamoDB has a limit of 10 GB on partitions which are it's internal storage unit for key and index setups similar to ours. Our primary table index partitions on the session ID which is ideal to spread events across partitions so that 10 GB limit is never reached. We also happen to maintain a DynamoDB Global Secondary Index which acts as a read only materialized view of table. This index does not partition on the session ID but on the namespace field which is the hardcoded string `default`. This means that the Global Secondary Index has a singular partition which is approaching 10 GB on production deployments. When the 10 GB limit is reached, the index will stop synchronizing data from the main table and no new events can be read. Another concern is that allowing a single partition to contain too many events may impact search times due to the internal B-Tree index growing very deep. Currently we do not store a suitable field on audit event entries in Dynamo to partition on. This means that we need to add a new field storing the date of the event in the string format `yyyy-mm-dd`. I propose to create a new Global Secondary index that is identical to existing one except it shall partition on the date key instead of the namespace key. A scheme like this will prevent size blowup on a single partition and instead spread long term data over multiple partitions. Searching over this new Global Secondary Index is trivial since the partition keys are simply a set of dates which can be generated easily from the start and end timestamps provided internally. We generate a set of partition keys to search over and include it in the query. Since the new date field will not exist on all past events on existing deployments by default, the Teleport auth server will need to go back and retroactively calculate and add this field to all past events. This will be done as a once-off background task created when the DynamoDB backend is created. The consequence of this is that past events will not be visible or searchable until this field as been added but due to the background process they will appear quickly again. The last thing that will be done is removing the old Global Secondary Index. After this step, the transition is complete.
Project: KICS (Provisioning / Security & Compliance)
File: fa00ce45-386d-4718-8392-fb485e1f3c5b.md

title: Secrets Manager With Vulnerable Policy hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: fa00ce45-386d-4718-8392-fb485e1f3c5b Query name: Secrets Manager With Vulnerable Policy Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: Secrets Manager policy should avoid wildcard in 'Principal' and 'Action'<br> ```tf title="Positive test num. 1 - tf file" hl_lines="12" provider "aws" { region = "us-east-1" } resource "awssecretsmanagersecret" "notsecurepolicy" { name = "notsecuresecret" } resource "awssecretsmanagersecret_policy" "example" { secretarn = awssecretsmanagersecret.notsecure_policy.arn policy = <<POLICY { "Version": "2012-10-17", "Statement": [ { "Sid": "EnableAllPermissions", "Effect": "Allow", "Principal": { "AWS": "*" }, "Action": "secretsmanager:*", "Resource": "*" } ] } POLICY } ``` ```tf title="Negative test num. 1 - tf file" resource "awssecretsmanagersecret" "example2" { name = "example" } resource "awssecretsmanagersecret_policy" "example2" { secretarn = awssecretsmanager_secret.example2.arn policy = <<POLICY { "Version": "2012-10-17", "Statement": [ { "Sid": "EnableAllPermissions", "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam::var.accountid:saml-provider/var.providername" }, "Action": "secretsmanager:GetSecretValue", "Resource": "*" } ] } POLICY } ```
Project: ClickHouse (App Definition and Development / Database)
File: quantileexactweighted.md

slug: /en/sql-reference/aggregate-functions/reference/quantileexactweighted sidebar_position: 203 Exactly computes the of a numeric data sequence, taking into account the weight of each element. To get exact value, all the passed values are combined into an array, which is then partially sorted. Each value is counted with its weight, as if it is present `weight` times. A hash table is used in the algorithm. Because of this, if the passed values are frequently repeated, the function consumes less RAM than . You can use this function instead of `quantileExact` and specify the weight 1. When using multiple `quantile*` functions with different levels in a query, the internal states are not combined (that is, the query works less efficiently than it could). In this case, use the function. Syntax ``` sql quantileExactWeighted(level)(expr, weight) ``` Alias: `medianExactWeighted`. Arguments `level` Level of quantile. Optional parameter. Constant floating-point number from 0 to 1. We recommend using a `level` value in the range of `. `expr` Expression over the column values resulting in numeric , or . `weight` Column with weights of sequence members. Weight is a number of value occurrences. Returned value Quantile of the specified level. Type: for numeric data type input. if input values have the `Date` type. if input values have the `DateTime` type. Example Input table: ``` text nval 0 3 1 2 2 1 5 4 ``` Query: ``` sql SELECT quantileExactWeighted(n, val) FROM t ``` Result: ``` text quantileExactWeighted(n, val) 1 ``` See Also
Project: YugabyteDB (App Definition and Development / Database)
File: 02-order-by.md

title: "ORDER BY" In this exercise we sort employees by first\name_ in ascending order. ``` SELECT first_name, last_name, title, address, city FROM employees ORDER BY first_name ASC; ``` The query should return 9 rows. In this exercise we sort employees by first\name_ in descending order. ``` SELECT first_name, last_name, title, address, city FROM employees ORDER BY first_name DESC; ``` The query should return 9 rows. In this exercise we sort employees by first\name_ in ascending order and then by last name in descending order. ``` SELECT first_name, last_name FROM employees ORDER BY first_name ASC, last_name DESC; ``` The query should return 9 rows
Project: StarRocks (App Definition and Development / Database)
File: hll_hash.md

displayed_sidebar: "English" Converts a value to an hll type. Typically used in imports to map a value in the source data to an HLL column type in the StarRocks table. ```Haskell HLLHASH(columnname) ``` `column_name`: The name of the generated HLL column. Returns a value of the HLL type. ```plain text mysql> select hllcardinality(hllhash("a")); +--+ | hllcardinality(hllhash('a')) | +--+ | 1 | +--+ ```
Project: Checkov (Provisioning / Security & Compliance)
File: Feature Descriptions.md

layout: default published: true title: Feature Descriptions nav_order: 4 With Checkov you can: Run a variety of scan types Enable Checkov to run as part of your CI/CD workflow Create and contribute custom Checkov policies With Checkov you can scan a repository, branch, folder, or a single file with attribute-based misconfigurations or connection state errors. See . When running Checkov, you can also: In addition to integrating with your code repository, Checkov can also integrate with your automated build pipeline via CI/CD providers. When your build tests run, Checkov will scan your infrastructure as code files for misconfigurations and you can review the output directly in your CI pipeline.
Project: KICS (Provisioning / Security & Compliance)
File: 25db74bf-fa3b-44da-934e-8c3e005c0453.md

title: Route53 Record Undefined hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 25db74bf-fa3b-44da-934e-8c3e005c0453 Query name: Route53 Record Undefined Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Networking and Firewall URL: Check if Record is set<br> ```tf title="Positive test num. 1 - tf file" hl_lines="8" resource "awsroute53record" "example" { allow_overwrite = true name = "test.example.com" ttl = 30 type = "NS" zoneid = awsroute53zone.example.zoneid records = [ ] } ``` ```tf title="Negative test num. 1 - tf file" resource "awsroute53record" "example" { allow_overwrite = true name = "test.example.com" ttl = 30 type = "NS" zoneid = awsroute53zone.example.zoneid records = [ awsroute53zone.example.name_servers[0], awsroute53zone.example.name_servers[1], awsroute53zone.example.name_servers[2], awsroute53zone.example.name_servers[3], ] } ```
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: querying-graphql.md

Youll need an app for sending and receiving GraphQL queries. We recommend GraphiQL. If youre using Homebrew, you can install it with `brew install --cask graphiql`. We need to tell Lagoon Core about the Kubernetes cluster. The GraphQL endpoint is: `https://<YOUR-API-URL>/graphql` Go to Edit HTTP Headers, and Add Header. Header Name: `Authorization` Value: `Bearer YOUR-TOKEN-HERE` In your home directory, the Lagoon CLI has created a `.lagoon.yml` file. Copy the token from that file and use it for the value here. Save. Now youre ready to run some queries. Run the following test query to ensure everything is working correctly: ```graph title="Get all projects" query allProjects {allProjects {name } } ``` This should give you the following response: ```graph title="API Response" { "data": { "allProjects": [] } } ``` Once you get the correct response, we need to add a mutation. Run the following query: ```graphql title="Add mutation" mutation addKubernetes { addKubernetes(input: { name: "<TARGET-NAME-FROM-REMOTE-VALUES.yml>", consoleUrl: "<URL-OF-K8S-CLUSTER>", token: "xxxxxx routerPattern: "${environment}.${project}.lagoon.example.com" }){id} } ``` `name`: get from `lagoon-remote-values.yml` `consoleUrl`: API Endpoint of Kubernetes cluster. Get from `values.yml` `token`: get a token for the `ssh-core` service account ```bash title="Get token" kubectl -n lagoon get secret/lagoon-remote-ssh-core-token -o json | jq -r '.data.token | @base64d' ``` !!! Info Authorization tokens for GraphQL are very short term so you may need to generate a new one. Run `lagoon login` and then cat the `.lagoon.yml` file to get the new token, and replace the old token in the HTTP header with the new one.
Project: YDB (App Definition and Development / Database)
File: topic-alter.md

You can use the `topic alter` subcommand to update a topic. General format of the command: ```bash {{ ydb-cli }} [global options...] topic alter [options...] <topic-path> ``` `global options`: . `options`: . `topic-path`: Topic path. View the description of the update topic command: ```bash {{ ydb-cli }} topic alter --help ``` The command changes the values of parameters specified in the command line. The other parameter values remain unchanged. | Name | Description | | | `--partitions-count` | The number of topic . You can only increase the number of partitions. | | `--retention-period-hours` | The retention period for topic data, in hours. | | `--partition-write-speed-kbps` | The maximum write speed to a , specified in KB/s.<br>The default value is `1024`. | | `--retention-storage-mb` | The maximum storage size, specified in MB. When the limit is reached, the oldest data will be deleted.<br>The default value is `0` (no limit). | | `--supported-codecs` | Supported data compression methods.<br>Possible values:<ul><li>`RAW`: No compression.</li><li>`ZSTD`: compression.</li><li>`GZIP`: compression.</li><li>`LZOP`: compression.</li></ul> | | `--metering-mode` | The topic pricing method for a serverless database.<br>Possible values:<ul><li>`request-units`: Based on actual usage.</li><li>`reserved-capacity`: Based on dedicated resources.</li></ul> | {% include %} Add a partition and the `lzop` compression method to the topic: ```bash {{ ydb-cli }} -p quickstart topic alter \ --partitions-count 3 \ --supported-codecs raw,gzip,lzop \ my-topic ``` Make sure that the topic parameters have been updated: ```bash {{ ydb-cli }} -p quickstart scheme describe my-topic ``` Result: ```text RetentionPeriod: 2 hours PartitionsCount: 3 SupportedCodecs: RAW, GZIP, LZOP ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.62.md

layout: release date: 2023-03-07 tag: v0.6.62 language: en Add search by display name in greedy meshmodel search @Revolyssup (#7302) fix meshmodel duplicates @Revolyssup (#7299) Added Antonette Cardwell to maintainers @Shivam-AfA (#6948) Do not registered unpublished components and fix modelDisplayName @Revolyssup (#7288) Add meshmodel-categories svgs @Abhishek-kumar09 (#7300) [UI] Fixed User Preferences Tabs @soham4abc (#7285) Troubleshoot Guide Dark Mode @hs05june (#7289) This PR fixes #7265 @parmishh (#7267) Search Filter remains on Pagination @hs05june (#7281) Fixed RJSF input tooltip disappearing on hover @asubedy (#7268) Release table text alignment fix @gurpreet-legend (#7270) Platform compatibility matrix alignment fix @gurpreet-legend (#7272) [Docs]: Added create new file feature @soham4abc (#7260) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Chadha93, @Revolyssup, @Shivam-AfA, @asubedy, @gurpreet-legend, @hs05june, @l5io, @leecalcote, @parmishh, @soham4abc, Gurpreet Singh and l5io
Project: Cyclops (App Definition and Development / Application Definition & Image Build)
File: SECURITY.md

If you discover a security vulnerability in this project, please follow these steps to report it to us: DO NOT open a public GitHub issue. Security issues must be reported privately via email. Email us at with a detailed description of the vulnerability. Include information about how the vulnerability can be reproduced or exploited. Provide any relevant documentation, code snippets, or steps to help us understand and reproduce the issue. Our team will acknowledge your email within [time frame] and will work with you to address the issue. We appreciate your responsible disclosure and will keep you informed about the progress of fixing the vulnerability. Since we currently don't have any official releases, we do not have specific versioning to provide support for. However, security issues reported will be addressed in the latest development code. While we are actively working on developing our project, we are committed to maintaining security best practices: Regular code reviews by our development team. Integration of automated testing to catch common vulnerabilities. Continuous monitoring of dependencies for security updates. As we start releasing official versions, we will include security updates and advisories in our release notes. Until then, any security-related updates will be communicated directly to anyone who has reported a security issue. We appreciate your understanding as we work to improve the security of our project. Thank you for your support and cooperation in helping to make our project secure.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: cpus.container.md

Number of CPUs. The default is 0.0 which means no limit. This is shorthand for --cpu-period and --cpu-quota, therefore the option cannot be specified with --cpu-period or --cpu-quota. On some systems, changing the CPU limits may not be allowed for non-root users. For more details, see https://github.com/containers/podman/blob/main/troubleshooting.md#26-running-containers-with-resource-limits-fails-with-a-permissions-error This option is not supported on cgroups V1 rootless systems.
Project: Veinmind Tools (Provisioning / Security & Compliance)
File: veinmind-runner_scan_container.md

Scan container Scan container from multi source, include dockerd/containerd ``` veinmind-runner scan container [flags] target ``` ``` scan dockerd container (all) veinmind-runner scan container dockerd:* scan dockerd container d29e2ca5b3a8 (container id) veinmind-runner scan container dockerd:d29e2ca5b3a8 scan containerd container webapp (container name) veinmind-runner scan container containerd:webapp use openai analyze result veinmind-runner scan container --enable-analyze --openai-token <youropenaitoken> containerd:webapp use openai analyze result with yourself questions veinmind-runner scan container --enable-analyze --openai-token <youropenaitoken> -p "explain what happened at this json" containerd:webapp ``` ``` -h, --help help for container ``` ``` --enable-analyze auto use openai analyze result -e, --exit-code int exit-code when veinmind-runner find security issues --format string output format: html/json/cli (default "cli") -g, --glob string specifies the pattern of plugin file to find --insecure-skip skip tls config --openai-token string auto openai analyze openai_key -o, --output string output filepath of report -p, --prefix string training openai limit sentence --threads int threads for scan action (default 5) -v, --verbose output verbose detail ``` - Scan cloud native objects security, include image/container/iac
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.4.27.md

layout: release date: 2020-12-11 tag: v0.4.27 Bump ini from 1.3.5 to 1.3.7 in /provider-ui @dependabot (#2077) Made first row selectable in the Results section @dhruv0000 (#2074) feat: add channel switch in mesheryctl @kushthedude (#1990) [Security] Bump ini from 1.3.5 to 1.3.7 in /provider-ui @dependabot-preview (#2075) [Security] Bump ini from 1.3.5 to 1.3.7 in /ui @dependabot-preview (#2076)