cwielenb/CNCF-Dataset huggingface dataset:
Project: ClickHouse (App Definition and Development / Database)
File: template-function.md

Short description. Syntax (without SELECT) ``` sql <function syntax> ``` Alias: `<alias name>`. (Optional) More text (Optional). Arguments (Optional) `x` Description. Optional (only for optional arguments). Possible values: <values list>. Default value: <value>. . `y` Description. Optional (only for optional arguments). Possible values: <values list>.Default value: <value>. . Parameters (Optional, only for parametric aggregate functions) `z` Description. Optional (only for optional parameters). Possible values: <values list>. Default value: <value>. . Returned value(s) Returned values list. Type: . Example The example must show usage and/or a use cases. The following text contains recommended parts of an example. Input table (Optional): ``` text ``` Query: ``` sql ``` Result: ``` text ``` See Also (Optional)
Project: Meshery (Provisioning / Automation & Configuration)
File: load-generators.md

layout: default title: "Extensibility: Load Generators" permalink: extensibility/load-generators type: Extensibility abstract: "Meshery offers support for more types of Kubernetes and cloud native infrastructure than any other project or product in the world. Meshery uses adapters for more deeply managing specific types of infrastructure." language: en list: include Users may prefer to use one load generator over the next given the difference of capabilities between load generators, so Meshery provides a `load generator interface` (a gRPC interface) behind which a load generator can be implemented. Meshery provides users with choice of which load generator they prefer to use for a given performance test. Users may configure their own preference for the load generator, different from the default load generator. Load generators will provide the capability to run load tests from Meshery. As of today the load generators are embedded as libraries in Meshery and Meshery invokes the load generators APIs with the right load test options to run the load test. At the moment, Meshery supports HTTP load generation. Support for gRPC and TCP load generation is on the roadmap. Meshery has functional integration with fortio, wrk2, and nighthawk. Different use cases and different opinions call for different approaches to statistical analysis of the performance results. For example, wrk2 accounts for a concept called Coordinated Omission. - Fortio load testing library, command line tool, advanced echo server and web UI in go (golang). Allows to specify a set query-per-second load and record latency histograms and other useful stats. - A constant throughput, correct latency recording variant of wrk. - Enables users to run distributed performance tests to better mimic real-world, distributed systems scenarios. See the Nighthawk project.
Project: Apache StreamPipes (App Definition and Development / Streaming & Messaging)
File: DEVELOPMENT.md

<!-- ~ Licensed to the Apache Software Foundation (ASF) under one or more ~ contributor license agreements. See the NOTICE file distributed with ~ this work for additional information regarding copyright ownership. ~ The ASF licenses this file to You under the Apache License, Version 2.0 ~ (the "License"); you may not use this file except in compliance with ~ the License. You may obtain a copy of the License at ~ ~ http://www.apache.org/licenses/LICENSE-2.0 ~ ~ Unless required by applicable law or agreed to in writing, software ~ distributed under the License is distributed on an "AS IS" BASIS, ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. ~ See the License for the specific language governing permissions and ~ limitations under the License. ~ --> This document describes how to easily set up your local dev environment to work on the StreamPipes Python client :snake:. <br> 1) Set up your Python environment Create a virtual Python environment with a tool of your choice. As a next step, install all required dependencies for the development, e.g., with `pip`: ``` pip install .[dev] # or alternatively: pip install .[all] to include dependencies for building the docs as well ``` In case you are on macOS and using `zsh` the following should work for you: ``` pip install ."[dev]" ``` <br> 2) Install pre-commit hook The pre-commit hook is run before every commit and takes care about code style, linting, type hints, import sorting, etc. It will stop your commit in case the changes do not apply the expected format. Always check to have the recent version of the pre-commit installed otherwise the CI build might fail: ``` pre-commit install ``` The definition of the pre-commit hook can be found in . <br> Below we list some conventions that we have agreed on for creating the StreamPipes Python client. Please comply to them when you plan to contribute to this project. If you have any other suggestions or would like to discuss them, we would be happy to hear from you on our mailing list . 1) Use `numpy` style for Python docstrings :pagefacingup: <br> Please stick to the `numpy` style when writing docstrings, as we require this for generating our documentation. 2) Provide tests :whitecheckmark: <br> We are aiming for broad test coverage for the Python client and have therefore set a requirement of at least 90% unit test coverage. Therefore, please remember to write (unit) tests already during development. If you have problems with writing tests, don't hesitate to ask us for help directly in the PR or even before that via our mailing list (see above). <! TODO: replace link to java file by link to documentation > 3) Build a similar API as the Java client provides :arrows_clockwise: <br> Whenever possible, please try to develop the API of the Python client the same as the . By doing so, we would like to provide a consistent developer experience and the basis for automated testing in the future.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.44.md

layout: release date: 2024-04-04 tag: v0.7.44 Revert "upgrade alpine from 3.15.3 to 3.18.5 to solve vulnerabilities " @MUzairS15 (#10673) Thank you to our contributors for making this release possible: @MUzairS15
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-system-connection-default.1.md

% podman-system-connection-default 1 podman\-system\-connection\-default - Set named destination as default for the Podman service podman system connection default name Set named ssh destination as default destination for the Podman service. Set the specified connection as default: ``` $ podman system connection default production ``` , , July 2020, Originally compiled by Jhon Honce (jhonce at redhat dot com)
Project: KICS (Provisioning / Security & Compliance)
File: f5f38943-664b-4acc-ab11-f292fa10ed0b.md

title: API Gateway without WAF hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: f5f38943-664b-4acc-ab11-f292fa10ed0b Query name: API Gateway without WAF Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: API Gateway should have WAF (Web Application Firewall) enabled<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="8" name: add test alb to waf string032 community.aws.wafv2_resources: name: string03 scope: REGIONAL state: present arn: "arn:aws:apigateway:region::/restapis/api-id/stages/prod" name: Setup AWS API Gateway setup on AWS and deploy API definition2 community.aws.awsapigateway: swaggerfile: myapi.yml stage: production cache_enabled: true cache_size: '1.6' tracing_enabled: true endpoint_type: EDGE state: present ``` ```yaml title="Negative test num. 1 - yaml file" name: add test alb to waf string03 community.aws.wafv2_resources: name: string03 scope: REGIONAL state: present arn: "arn:aws:apigateway:region::/restapis/api-id/stages/produ" name: Setup AWS API Gateway setup on AWS and deploy API definition community.aws.awsapigateway: swaggerfile: myapi.yml stage: produ cache_enabled: true cache_size: '1.6' tracing_enabled: true endpoint_type: EDGE state: present ```
Project: YDB (App Definition and Development / Database)
File: load-actors-kqp.md

Runs general performance testing for the {{ ydb-short-name }} cluster by loading all components via the Query Processor layer. The load is similar to that from the {{ ydb-short-name }} CLI subcommand, but it is generated from within the cluster. You can run two types of load: Stock*: Simulates a warehouse of an online store: creates multi-product orders, gets a list of orders per customer. Key-value*: Uses the DB as a key-value store. Before this test, the necessary tables are created. After it's completed, they are deleted. {% include %} | Parameter | Description | | | `DurationSeconds` | Load duration in seconds. | | `WindowDuration` | Statistics aggregation window duration. | | `WorkingDir` | Path to the directory to create test tables in. | | `NumOfSessions` | The number of parallel threads creating the load. Each thread writes data to its own session. | | `DeleteTableOnFinish` | Set it to `False` if you do not want the created tables deleted after the load stops. This might be helpful when a large table is created upon the actor's first run, and then queries are made to that table. | | `UniformPartitionsCount` | The number of partitions created in test tables. | | `WorkloadType` | Type of load.<br>For Stock:<ul><li>`0`: InsertRandomOrder.</li><li>`1`: SubmitRandomOrder.</li><li>`2`: SubmitSameOrder.</li><li>`3`: GetRandomCustomerHistory.</li><li>`4`: GetCustomerHistory.</li></ul>For Key-Value:<ul><li>`0`: UpsertRandom.</li><li>`1`: InsertRandom.</li><li>`2`: SelectRandom.</li></ul> | | `Workload` | Kind of load.<br>`Stock`:<ul><li>`ProductCount`: Number of products.</li><li>`Quantity`: Quantity of each product in stock.</li><li>`OrderCount`: Initial number of orders in the database.</li><li>`Limit`: Minimum number of shards for tables.</li></ul>`Kv`:<ul><li>`InitRowCount`: Before load is generated, the load actor writes the specified number of rows to the table.</li><li>`StringLen`: Length of the `value` string.</li><li>`ColumnsCnt`: Number of columns to use in the table.</li><li>`RowsCnt`: Number of rows to insert or read per SQL query.</li></ul> | The following actor runs a stock load on the `/slice/db` database by making simple UPSERT queries of `64` threads during `30` seconds. ```proto KqpLoad: { DurationSeconds: 30 WindowDuration: 1 WorkingDir: "/slice/db" NumOfSessions: 64 UniformPartitionsCount: 1000 DeleteTableOnFinish: 1 WorkloadType: 0 Stock: { ProductCount: 100 Quantity: 1000 OrderCount: 100 Limit: 10 } } ``` As a result of the test, the number of successful transactions per second, the number of transaction execution retries, and the number of errors are output.
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: LICENSE.md

Copyright (C) 2014 by Oleku Konko Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Project: Meshery (Provisioning / Automation & Configuration)
File: 05-21-2023-14-25-05_f6f29ec3.md

timestamp: "2023-05-21 14:25:20 UTC Sun" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "*name" k8s-distro: minikube k8s-version: "v1.23.9" service-mesh: Consul service-mesh-version: "v1.0.7" tests: consul-client: null consul-server: null overall-status: "failing"
Project: Chef InSpec (Provisioning / Security & Compliance)
File: azurerm_monitor_log_profile.md

+++ title = "azurermmonitorlog_profile resource" draft = false gh_repo = "inspec" platform = "azure" [menu] [menu.inspec] title = "azurermmonitorlog_profile" identifier = "inspec/resources/azure/azurermmonitorlogprofile.md azurermmonitorlogprofile resource" parent = "inspec/resources/azure" +++ {{< inspec/azurermdeprecated resource="azuremonitorlogprofile" >}} Use the `azurermmonitorlog_profile` InSpec audit resource to test properties of an Azure Monitor Log Profile. This resource interacts with version `2016-03-01` of the Azure Management API. For more information see the . At the moment, there doesn't appear to be a way to select the version of the Azure API docs. If you notice a newer version being referenced in the official documentation please open an issue or submit a pull request using the updated version. This resource is available in the `inspec-azure` [resource pack](/inspec/glossary/#resource-pack). To use it, add the following to your `inspec.yml` in your top-level profile: depends: name: inspec-azure git: https://github.com/inspec/inspec-azure.git You'll also need to setup your Azure credentials; see the resource pack . An `azurermmonitorlog_profile` resource block identifies a Log Profile by name. describe azurermmonitorlog_profile(name: 'default') do ... end describe azurermmonitorlog_profile(name: 'default') do it { should exist } end describe azurermmonitorlog_profile(name: 'default') do its('retention_enabled') { should be true } end `name` The name of the Log Profile. describe azurermmonitorlog_profile(name: 'default') do it { should exist } end `retention_enabled` `retention_days` Determine if retention is enabled its('retention_enabled') { should be true } Determine number of days retention is enabled for its('retention_days') { should eq(365) } There are additional attributes that may be accessed that we have not documented. Please take a look at the . Any attribute in the response may be accessed with the key names separated by dots (`.`). The API may not always return keys that do not have any associated data. There may be cases where the deeply nested property may not have the desired attribute along your call chain. If you find yourself writing tests against properties that may be nil, fork this resource pack and add an accessor to the resource. Within that accessor you'll be able to guard against nil keys. Pull requests are always welcome. {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The control will pass if the resource returns a result. Use `should_not` if you expect zero matches. describe azurermmonitorlog_profile(name: 'default') do it { should exist } end describe azurermmonitorlog_profile(name: 'default') do it { should_not exist } end Your [Service Principal](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal) must be setup with a `contributor` role on the subscription you wish to test.
Project: Strimzi (App Definition and Development / Streaming & Messaging)
File: README.md

This document gives a detailed breakdown of the testing processes using testing farm service. Python >=3.9 TMT command line tool (optional) - for lint and check tmt formatted test plans and tests `pip install tmt[all]` Testing farm command line tool - for trigger your test plan in testing-farm `pip install tft-cli` Plans are stored in folder, there is a file called `main.fmf` which contains test plan definition. This definition is composed of hw requirements, prepare steps for created VM executor and specific plans. Specific plan defines selectors for which should be executed. smoke upgrade regression-operators regression-components kraft-operators kraft-components Get API token for testing farm Store token into env var ```export TESTINGFARMAPITOKEN="yourtoken"``` Run all plans ```commandline testing-farm request --compose Fedora-38 --git-url https://github.com/strimzi/strimzi-kafka-operator.git ``` Select specific plan and git branch ```commandline testing-farm request --compose Fedora-38 \ --git-url https://github.com/strimzi/strimzi-kafka-operator.git \ --git-ref some-branch \ --plan smoke ``` Run multi-arch build ```commandline testing-farm request --compose Fedora-Rawhide \ --git-url https://github.com/strimzi/strimzi-kafka-operator.git \ --git-ref some-branch \ --plan smoke \ --arch aarch64,x86_64 ``` is a github application for running testing-farm jobs from PR requested by command. Definition of the jobs is stored in . Packit can be triggered from the PR by comment, but only members of strimzi organization are able to run tests. Run all jobs for PR ``` /packit test ``` Run selected jobs by label ``` /packit test --labels upgrade,kraft-operators ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: detach-keys.md

Specify the key sequence for detaching a container. Format is a single character `[a-Z]` or one or more `ctrl-<value>` characters where `<value>` is one of: `a-z`, `@`, `^`, `[`, `,` or `_`. Specifying "" disables this feature. The default is ctrl-p,ctrl-q. This option can also be set in containers.conf(5) file.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_migration.md

title: kbcli migration Data migration between two data sources. ``` -h, --help help for migration ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - Create a migration task. - Show details of a specific migration task. - List migration tasks. - Access migration task log file. - List migration templates. - Delete migration task.
Project: Sonobuoy (Provisioning / Security & Compliance)
File: pullsecrets.md

This document describes how to use the ImagePullSecrets option in order to run Sonobuoy using a private Sonobuoy image. The name of the secret to use when pulling the image can be set easily in the configuration file passed to `sonobuoy run` or `sonobuoy gen`: ``` echo '{"ImagePullSecrets":"mysecret"}' > secretconfig.json sonobuoy gen --config secretconfig.json ``` Doing this properly passes the value and places it into the YAML for the Sonobuoy aggregator pod and all the pods for each plugin. The main complication for this flow is that secrets can only be referenced from within their own namespace. As a result we need to create the secret at the same time we create the initial resources. Sonobuoy does not have built in support for this, but it can be manually achieved via the following process: Manually create the YAML for the secret Insert the YAML into the output from `sonobuoy gen --config secretconfig.json` Run with `sonobuoy run -f ...` As an example of how to create the secret you can follow the instructions in order to create a secret in the default namespace. Then get a copy of its YAML via: ``` kubectl get secret <secret name> -o yaml > secret.yaml ``` Manually edit the file and remove/adjust the metadata as appropriate. The namespace should be adjusted to your desired Sonobuoy namespace (default: sonobuoy) and the following fields can be removed: annotations creationTimestamp resourceVersion selfLink uid Then just insert that YAML into the output from `sonobuoy gen` and run with `sonobuoy run -f ...`
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.130.md

layout: release date: 2023-08-22 tag: v0.6.131 change the location where binded node info is captured @MUzairS15 (#8562) [CI] Swagger docs build failing @suhail34 (#8551) [Lifecycle] mesheryctl: slim profile with no adapters by default @leecalcote (#8566) [UI] Fix issue with button alignment @abhinandanudupa (#8539) [connections] Migrate K8sCtx to Connections @theBeginner86 (#8321) Bump eslint from 8.46.0 to 8.47.0 in /provider-ui @dependabot (#8525) Refactor drawer links @aabidsofi19 (#8558) Bump cypress from 12.17.1 to 12.17.4 in /provider-ui @dependabot (#8529) Bump eslint-plugin-cypress from 2.13.3 to 2.14.0 in /provider-ui @dependabot (#8523) Meshmodel Browser @UsmanDev09 (#8466) Fixed height consistency in design cards @EraKin575 (#8492) [Notification Center] Refactor EVENT_TYPES and Icons @aabidsofi19 (#8546) [Notification Center] Refactor EVENT_TYPES and Icons @aabidsofi19 (#8546) Bump eslint from 8.46.0 to 8.47.0 in /provider-ui @dependabot (#8525) Bump cypress from 12.17.1 to 12.17.4 in /provider-ui @dependabot (#8529) Bump eslint-plugin-cypress from 2.13.3 to 2.14.0 in /provider-ui @dependabot (#8523) Fixed email-on-failure job in stable release @VaibhavMalik4187 (#8554) Scrolling error in meshery docs for small screen fixed @Aayush987 (#8550) Fixing Documentation issues @thisiskaransgit (#8128) Thank you to our contributors for making this release possible: @Aayush987, @Aisuko, @Chadha93, @EraKin575, @MUzairS15, @UsmanDev09, @VaibhavMalik4187, @aabidsofi19, @abhinandanudupa, @alphaX86, @dependabot, @dependabot[bot], @l5io, @leecalcote, @suhail34, @theBeginner86, @thisiskaransgit and l5io