cwielenb/CNCF-Dataset huggingface dataset:
Project: Kyverno (Provisioning / Security & Compliance)
File: kyverno_test.md

Run tests from a local filesystem or a remote git repository. Run tests from a local filesystem or a remote git repository. The test command provides a facility to test resources against policies by comparing expected results, declared ahead of time in a test manifest file, to actual results reported by Kyverno. Users provide the path to the folder containing a kyverno-test.yaml file where the location could be on a local filesystem or a remote git repository. For more information visit https://kyverno.io/docs/kyverno-cli/#test ``` kyverno test [local folder or git repository]... [flags] ``` ``` kyverno test https://github.com/kyverno/policies/pod-security --git-branch main kyverno test . kyverno test . --test-case-selector "policy=disallow-latest-tag, rule=require-image-tag, resource=test-require-image-tag-pass" ``` ``` --detailed-results If set to true, display detailed results --fail-only If set to true, display all the failing test only as output for the test command -f, --file-name string Test filename (default "kyverno-test.yaml") -b, --git-branch string Test github repository branch -h, --help help for test --registry If set to true, access the image registry using local docker credentials to populate external data --remove-color Remove any color from output -t, --test-case-selector string Filter test cases to run (default "policy=,rule=,resource=*") ``` ``` --adddirheader If true, adds the file directory to the header of the log messages --alsologtostderr log to standard error as well as files (no effect when -logtostderr=true) --logbacktraceat traceLocation when logging hits line file:N, emit a stack trace (default :0) --log_dir string If non-empty, write log files in this directory (no effect when -logtostderr=true) --log_file string If non-empty, use this log file (no effect when -logtostderr=true) --logfilemax_size uint Defines the maximum size a log file can grow to (no effect when -logtostderr=true). Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800) --logtostderr log to standard error instead of files (default true) --one_output If true, only write logs to their native severity level (vs also writing to each lower severity level; no effect when -logtostderr=true) --skip_headers If true, avoid header prefixes in the log messages --skiplogheaders If true, avoid headers when opening log files (no effect when -logtostderr=true) --stderrthreshold severity logs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or -alsologtostderr=true) (default 2) -v, --v Level number for the log level verbosity --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging ``` - Kubernetes Native Policy Management.
Project: Meshery (Provisioning / Automation & Configuration)
File: aws-cloudtrail-controller.md

layout: integration title: AWS CloudTrail subtitle: Collaborative and visual infrastructure as code for AWS CloudTrail image: /assets/img/integrations/aws-cloudtrail-controller/icons/color/aws-cloudtrail-controller-color.svg permalink: extensibility/integrations/aws-cloudtrail-controller docURL: https://docs.meshery.io/extensibility/integrations/aws-cloudtrail-controller description: integrations-category: Observability and Analysis integrations-subcategory: Logging registrant: GitHub components: name: field-export colorIcon: assets/img/integrations/aws-cloudtrail-controller/components/field-export/icons/color/field-export-color.svg whiteIcon: assets/img/integrations/aws-cloudtrail-controller/components/field-export/icons/white/field-export-white.svg description: name: adopted-resource colorIcon: assets/img/integrations/aws-cloudtrail-controller/components/adopted-resource/icons/color/adopted-resource-color.svg whiteIcon: assets/img/integrations/aws-cloudtrail-controller/components/adopted-resource/icons/white/adopted-resource-white.svg description: name: event-data-store colorIcon: assets/img/integrations/aws-cloudtrail-controller/components/event-data-store/icons/color/event-data-store-color.svg whiteIcon: assets/img/integrations/aws-cloudtrail-controller/components/event-data-store/icons/white/event-data-store-white.svg description: name: trail colorIcon: assets/img/integrations/aws-cloudtrail-controller/components/trail/icons/color/trail-color.svg whiteIcon: assets/img/integrations/aws-cloudtrail-controller/components/trail/icons/white/trail-white.svg description: featureList: [ "Data events that capture data plane actions within a resource, such as reading or writing an Amazon S3 object.", "Configuration items from AWS Config that capture resource configuration history and resource compliance history as evaluated by AWS Config rules.", "Audit evidence from AWS Audit Manager that contains the information needed to demonstrate compliance with the requirements as specified by Audit Manager controls." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: SPIFFE (Provisioning / Key Management)
File: ANDRES_VEGA.md

I am honored to nominate Andres Vega for the SPIFFE Steering Committee. Andres is a SPIFFE/SPIRE champion who has helped the project and community extensively grow. In addition to being a long time friend to the SPIFFE project and author of the SPIFFE Turtle Book, Andres has spent countless hours helping many organizations adopt, plan, and deploy SPIFFE environments. Most importantly, Andres has always taken a community first approach which is vital for the continued success of SPIFFE. Andres answered the following questions in support of his nomination. What makes you a good fit for the SPIFFE Steering Committee? I have a been a contributor to the spiffe community for a number of yearsd. Some of my contributions to the project and its community include: Led the certification of the project to attain a Core Infrastructure Initiative Best Practices badge. Authored and led the CNCF SIG-Security assessment. Drove and represented the project moving from CNCF sandbox level into the incubation stage. Delivered a number of SPIFFE/SPIRE webinars and trainings. Coauthored "Solving the Bottom Turtle" What aspects of SSC participation are you most excited about? What excites me the most of SSC participation is voicing the needs of the end users in order to ease adoption and consumption of spiffe in production systems. My other side hustle is security advisory to the CNCF ecosystem. As such I'm hopeful to help crosspolinate spiffe integrations with other technologies in the ecosystem. Is there anything else you'd like to say as part of your nomination? Two other growth areas I'm passionate about about is democratizing the use of spire by setting it into a direction that is set and forget it. So easy that someone that does not possess domain expertise can consume it. And then, integrations, integrations, integrations. What I mean by that is I'd like to see a future of a more secure cloud native ecosystem where the top 50 OSS projects support SPIFFE authentication natively. GitHub Handle: anvega Email address: Av@monkey.org Linkedin Profile: https://www.linkedin.com/in/avegaarias/ Current Affiliation: VMware
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: MAINTAINERS.md

This page lists all active maintainers of this repository. If you were a maintainer and would like to add your name to the Emeritus list, please send us a PR. See for governance guidelines and how to become a maintainer. See for general contribution guidelines. , Datadog, Inc. , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC
Project: ClickHouse (App Definition and Development / Database)
File: fuzzJSON.md

slug: /en/sql-reference/table-functions/fuzzJSON sidebar_position: 75 sidebar_label: fuzzJSON Perturbs a JSON string with random variations. ``` sql fuzzJSON({ namedcollection [, option=value [,..]] | jsonstr[, random_seed] }) ``` Arguments `named_collection`- A . `option=value` - Named collection optional parameters and their values. `json_str` (String) - The source string representing structured data in JSON format. `random_seed` (UInt64) - Manual random seed for producing stable results. `reuse_output` (boolean) - Reuse the output from a fuzzing process as input for the next fuzzer. `malform_output` (boolean) - Generate a string that cannot be parsed as a JSON object. `maxoutputlength` (UInt64) - Maximum allowable length of the generated or perturbed JSON string. `probability` (Float64) - The probability to fuzz a JSON field (a key-value pair). Must be within [0, 1] range. `maxnestinglevel` (UInt64) - The maximum allowed depth of nested structures within the JSON data. `maxarraysize` (UInt64) - The maximum allowed size of a JSON array. `maxobjectsize` (UInt64) - The maximum allowed number of fields on a single level of a JSON object. `maxstringvalue_length` (UInt64) - The maximum length of a String value. `minkeylength` (UInt64) - The minimum key length. Should be at least 1. `maxkeylength` (UInt64) - The maximum key length. Should be greater or equal than the `minkeylength`, if specified. Returned Value A table object with a a single column containing perturbed JSON strings. ``` sql CREATE NAMED COLLECTION jsonfuzzer AS jsonstr='{}'; SELECT * FROM fuzzJSON(json_fuzzer) LIMIT 3; ``` ``` text {"52Xz2Zd4vKNcuP2":true} {"UPbOhOQAdPKIg91":3405264103600403024} {"X0QUWu8yT":[]} ``` ``` sql SELECT * FROM fuzzJSON(jsonfuzzer, jsonstr='{"name" : "value"}', random_seed=1234) LIMIT 3; ``` ``` text {"key":"value", "mxPG0h1R5":"L-YQLv@9hcZbOIGrAn10%GA"} {"BRE3":true} {"key":"value", "SWzJdEJZ04nrpSfy":[{"3Q23y":[]}]} ``` ``` sql SELECT * FROM fuzzJSON(jsonfuzzer, jsonstr='{"students" : ["Alice", "Bob"]}', reuse_output=true) LIMIT 3; ``` ``` text {"students":["Alice", "Bob"], "nwALnRMc4pyKD9Krv":[]} {"students":["1rNY5ZNs0wU&82t_P", "Bob"], "wLNRGzwDiMKdw":[{}]} {"xeEk":["1rNY5ZNs0wU&82t_P", "Bob"], "wLNRGzwDiMKdw":[{}, {}]} ``` ``` sql SELECT * FROM fuzzJSON(jsonfuzzer, jsonstr='{"students" : ["Alice", "Bob"]}', maxoutputlength=512) LIMIT 3; ``` ``` text {"students":["Alice", "Bob"], "BREhhXj5":true} {"NyEsSWzJdeJZ04s":["Alice", 5737924650575683711, 5346334167565345826], "BjVO2X9L":true} {"NyEsSWzJdeJZ04s":["Alice", 5737924650575683711, 5346334167565345826], "BjVO2X9L":true, "k1SXzbSIz":[{}]} ``` ``` sql SELECT * FROM fuzzJSON('{"id":1}', 1234) LIMIT 3; ``` ``` text {"id":1, "mxPG0h1R5":"L-YQLv@9hcZbOIGrAn10%GA"} {"BRjE":16137826149911306846} {"XjKE":15076727133550123563} ``` ``` sql SELECT * FROM fuzzJSON(jsonnc, jsonstr='{"name" : "FuzzJSON"}', randomseed=1337, malformoutput=true) LIMIT 3; ``` ``` text U"name":"FuzzJSON*"SpByjZKtr2VAyHCO"falseh {"name"keFuzzJSON, "g6vVO7TCIk":jTt^ {"DBhz":YFuzzJSON5} ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.1.md

layout: release date: 2021-04-03 tag: v0.5.1 Add support for patternfiles for default/none provider @utkarsh-pro (#2649) [meshery] Extend meshops.proto to provide adapter version, and other info @mgfeller (#2454) changes for the extensions flow @kumarabd (#2618) [MesheryAdapterPlayComponent] - Updated UI Card Margins On Management Page @adithyaakrishna (#2615) [WIP] K8s Pre-req check @metonymic-smokey (#2606) fix mesheryctl issue template @navendu-pottekkat (#2609) [WIP] Update Meshery results to follow SMP @navendu-pottekkat (#2605) bug fix for mesheryctl auto redireect @kumarabd (#2602) [Mesheryctl] Add "--yes" global flag to system commands @hexxdump (#2604) [Docs] Footer: Update copyright year to 2021 @onwuvic (#2597) Move from Bitcask to Sqlite @utkarsh-pro (#2599) Added version check for config.yaml @metonymic-smokey (#2583) [mesheryctl] platform: kubernetes support for `mesheryctl system logs` command @piyushsingariya (#2592) [docs] fix partially resolved merge conflict @DelusionalOptimist (#2594) Redesign mesheryctl commands on docs site @alphaX86 (#2546) Bump cypress from 6.4.0 to 6.8.0 in /ui @dependabot (#2635) Bump @cypress/code-coverage from 3.9.2 to 3.9.4 in /provider-ui @dependabot (#2630) Bump @cypress/code-coverage from 3.9.2 to 3.9.4 in /ui @dependabot (#2632) Bump eslint-plugin-react from 7.22.0 to 7.23.1 in /provider-ui @dependabot (#2636) Bump cypress from 6.5.0 to 6.8.0 in /provider-ui @dependabot (#2634) Bump start-server-and-test from 1.12.0 to 1.12.1 in /provider-ui @dependabot (#2628) Bump mui-datatables from 3.7.3 to 3.7.6 in /ui @dependabot (#2627) Bump babel-plugin-relay from 11.0.0 to 11.0.1 in /ui @dependabot (#2631) Bump react and react-dom in /provider-ui @dependabot (#2633) Bump next from 10.0.7 to 10.1.2 in /provider-ui @dependabot (#2626) Bump react-jss from 10.5.1 to 10.6.0 in /ui @dependabot (#2637) Bump lint-staged from 10.5.3 to 10.5.4 in /ui @dependabot (#2640) Bump eslint from 7.21.0 to 7.23.0 in /ui @dependabot (#2641) Bump react-redux from 7.2.2 to 7.2.3 in /ui @dependabot (#2629) Bump eslint from 7.21.0 to 7.23.0 in /provider-ui @dependabot (#2638) Bump @fortawesome/free-brands-svg-icons from 5.15.2 to 5.15.3 in /ui @dependabot (#2639) Bump @fortawesome/free-solid-svg-icons from 5.15.2 to 5.15.3 in /ui @dependabot (#2642) Bump y18n from 4.0.0 to 4.0.1 in /ui @dependabot (#2625) Add Kubernetes instructions - part 2 @metonymic-smokey (#2613) [Docs] Add performance profiles section @utkarsh-pro (#2616)
Project: kube-bench (Provisioning / Security & Compliance)
File: architecture.md

The tests (or "controls") are maintained in YAML documents. There are different versions of these test YAML files reflecting different . You will find more information about the test file YAML definitions in our . The test files for the various versions of Benchmarks can be found in directories with same name as the Benchmark versions under the `cfg` directory next to the kube-bench executable, for example `./cfg/cis-1.5` will contain all test files for which are: master.yaml, controlplane.yaml, node.yaml, etcd.yaml, policies.yaml and config.yaml Check the contents of the benchmark directory under `cfg` to see which targets are available for that benchmark. Each file except `config.yaml` represents a target (also known as a `control` in other parts of this documentation). The following table shows the valid targets based on the CIS Benchmark version. | CIS Benchmark | Targets | |-|| | cis-1.5 | master, controlplane, node, etcd, policies | | cis-1.6 | master, controlplane, node, etcd, policies | | cis-1.20 | master, controlplane, node, etcd, policies | | cis-1.23 | master, controlplane, node, etcd, policies | | cis-1.24 | master, controlplane, node, etcd, policies | | cis-1.7 | master, controlplane, node, etcd, policies | | cis-1.8 | master, controlplane, node, etcd, policies | | gke-1.0 | master, controlplane, node, etcd, policies, managedservices | | gke-1.2.0 | controlplane, node, policies, managedservices | | eks-1.0.1 | controlplane, node, policies, managedservices | | eks-1.1.0 | controlplane, node, policies, managedservices | | eks-1.2.0 | controlplane, node, policies, managedservices | | ack-1.0 | master, controlplane, node, etcd, policies, managedservices | | aks-1.0 | controlplane, node, policies, managedservices | | rh-0.7 | master,node| | rh-1.0 | master, controlplane, node, etcd, policies | | cis-1.6-k3s | master, controlplane, node, etcd, policies | | cis-1.24-microk8s | master, controlplane, node, etcd, policies | The following table shows the valid DISA STIG versions | STIG | Targets | |-|| | eks-stig-kubernetes-v1r6 | master, controlplane, node, policies, managedservices |
Project: OceanBase (App Definition and Development / Database)
File: CONTRIBUTING.md

The development guide is located under the folder. Welcome to [oceanbase]! We're thrilled that you'd like to contribute. Your help is essential for making it better. Before you start contributing, please make sure you have read and understood our . First, fork the to your own GitHub account. This will create a copy of the project under your account. ```bash git clone https://github.com/`your-github-name`/oceanbase ``` ```bash cd oceanbase ``` Create a new branch for your feature or bug fix: ```bash git checkout -b feature-branch ``` feature-branch is the name of the branch where you will be making your changes. You can name this whatever you want. Make your changes and commit them: ```bash git add . git commit -m "Description of your changes" ``` Push your changes to your fork: ```bash git push origin feature-branch ``` Finally Click on `Compare & Pull request` to contribute on this repository. After you create the pull request, a member of the Oceanbase team will review your changes and provide feedback. Once satisfied, they will merge your pull request. And there are some CI checks to pass before your pull request can be merged. Currently, there are two types of CI checks: Compile: This check will compile the code on CentOS and Ubuntu. Farm: This check will run the unit tests and some mysql test cases. Note: If the farm failed and you think it is not related to your changes, you can ask the reviewer to re-run the farm or the reviewer will re-run the farm. In default, the pull request is merged into develop branch which is the default branch of . We will merge develop into master branch periodically. So if you want to get the latest code, you can pull the master branch. If you want to develop a new feature, you should create a first. If your idea is accepted, you can create a new issue and start to develop your feature and we will create a feature branch for you. After you finish your feature, you can create a pull request to merge your feature branch into oceanbase feature branch. The flow like below. Create a Create a new issue Create a new feature branch on for your feature Make your changes and commit them Push your changes to your fork Create a pull request to merge your code into feature branch After your pull request is merged, we will merge your feature branch into master
Project: YDB (App Definition and Development / Database)
File: as.md

Can be used in the following scenarios: Adding a short name (alias) for columns or tables within the query. Using named arguments in function calls. To specify the target type in the case of explicit type casting, see . {% if select_command != "SELECT STREAM" %} Examples: ```yql SELECT key AS k FROM my_table; ``` ```yql SELECT t.key FROM my_table AS t; ``` ```yql SELECT MyFunction(key, 123 AS myoptionalarg) FROM my_table; ``` {% else %} Examples: ```yql SELECT STREAM key AS k FROM my_stream; ``` ```yql SELECT STREAM s.key FROM my_stream AS s; ``` ```yql SELECT STREAM MyFunction(key, 123 AS myoptionalarg) FROM my_stream; ``` {% endif %}
Project: KICS (Provisioning / Security & Compliance)
File: 829f1c60-2bab-44c6-8a21-5cd9d39a2c82.md

title: Compute Instance Is Publicly Accessible hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 829f1c60-2bab-44c6-8a21-5cd9d39a2c82 Query name: Compute Instance Is Publicly Accessible Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: Compute instances shouldn't be accessible from the Internet.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="6" name: create a instance google.cloud.gcpcomputeinstance: name: test_object network_interfaces: network: "{{ network }}" access_configs: name: External NAT nat_ip: "{{ address }}" type: ONETOONE_NAT zone: us-central1-a project: test_project auth_kind: serviceaccount state: present ``` ```yaml title="Negative test num. 1 - yaml file" name: create a instance google.cloud.gcpcomputeinstance: name: test_object network_interfaces: network: '{{ network }}' zone: us-central1-a project: test_project auth_kind: serviceaccount state: present ```
Project: StarRocks (App Definition and Development / Database)
File: months_add.md

displayed_sidebar: "English" Adds a specified number of months to the date, accurate to the month. The function provides similar functionalities. ```Haskell DATETIME months_add(DATETIME expr1, INT expr2); ``` `expr1`: the start time. It must be of the DATETIME or DATE type. `expr2`: the months to add. It must be of the INT type. It can be greater, equal, or less than zero. A negative value subtracts months from `date`. Returns a DATETIME value. ```Plain select months_add('2019-08-01 13:21:03', 8); +--+ | months_add('2019-08-01 13:21:03', 8) | +--+ | 2020-04-01 13:21:03 | +--+ select months_add('2019-08-01', 8); +--+ | months_add('2019-08-01', 8) | +--+ | 2020-04-01 00:00:00 | +--+ select months_add('2019-08-01 13:21:03', -8); ++ | months_add('2019-08-01 13:21:03', -8) | ++ | 2018-12-01 13:21:03 | ++ select months_add('2019-02-28 13:21:03', 1); +--+ | months_add('2019-02-28 13:21:03', 1) | +--+ | 2019-03-28 13:21:03 | +--+ select months_add('2019-01-30 13:21:03', 1); +--+ | months_add('2019-01-30 13:21:03', 1) | +--+ | 2019-02-28 13:21:03 | +--+ ```
Project: YugabyteDB (App Definition and Development / Database)
File: delphix.md

title: Delphix linkTitle: Delphix description: Use Delphix to virtualize your YugabyteDB database. menu: preview_integrations: identifier: Delphix parent: integrations-platforms weight: 571 type: docs Delphix is a data operations company that enables organizations to modernize their data infrastructure by providing software solutions for data management and delivery. Some of its key features include data virtualization, data masking, data replication, and data management across on-premises, cloud, and hybrid environments. Delphix offers the following key capabilities as part of its integration with YugabyteDB: Select Connector for continuous data (Data Virtualization): Delphix can virtualize YugabyteDB databases by ingesting data to the Delphix platform, and create lightweight copies of YugabyteDB that can be provisioned quickly. Select Connector for continuous compliance (Data Masking): Delphix provides data masking capabilities for YugabyteDB to protect sensitive information in the database, and also comply with data privacy regulations. The resulting virtual copies can then be used for different use cases such as development, testing, analytics, reporting, and so on. For more information, refer to in the Delphix documentation.
Project: ClickHouse (App Definition and Development / Database)
File: set.md

slug: /en/sql-reference/statements/set sidebar_position: 50 sidebar_label: SET ``` sql SET param = value ``` Assigns `value` to the `param` for the current session. You cannot change this way. You can also set all the values from the specified settings profile in a single query. ``` sql SET profile = 'profile-name-from-the-settings-file' ``` For more information, see .