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

Provides a command-line interface to JMESPath, enhanced with Kyverno specific custom functions. Provides a command-line interface to JMESPath, enhanced with Kyverno specific custom functions. For more information visit https://kyverno.io/docs/kyverno-cli/#jp ``` kyverno jp [flags] ``` ``` kyverno jp function kyverno jp query -i object.yaml 'request.object.metadata.name | truncate(@, `9`)' kyverno jp parse 'request.object.metadata.name | truncate(@, `9`)' ``` ``` -h, --help help for jp ``` ``` --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. - Provides function informations. - Parses jmespath expression and shows corresponding AST. - Provides a command-line interface to JMESPath, enhanced with Kyverno specific custom functions.
Project: ClickHouse (App Definition and Development / Database)
File: maxintersections.md

slug: /en/sql-reference/aggregate-functions/reference/maxintersections sidebar_position: 360 title: maxIntersections Aggregate function that calculates the maximum number of times that a group of intervals intersects each other (if all the intervals intersect at least once). The syntax is: ```sql maxIntersections(startcolumn, endcolumn) ``` Arguments `startcolumn` the numeric column that represents the start of each interval. If `startcolumn` is `NULL` or 0 then the interval will be skipped. `endcolumn` - the numeric column that represents the end of each interval. If `endcolumn` is `NULL` or 0 then the interval will be skipped. Returned value Returns the maximum number of intersected intervals. Example ```sql CREATE TABLE my_events ( start UInt32, end UInt32 ) Engine = MergeTree ORDER BY tuple(); INSERT INTO my_events VALUES (1, 3), (1, 6), (2, 5), (3, 7); ``` The intervals look like the following: ```response 1 - 3 1 - - - - 6 2 - - 5 3 - - - 7 ``` Three of these intervals have a common value (the value is `4`, but the value that is common is not important, we are measuring the count of the intersections). The intervals `(1,3)` and `(3,7)` share an endpoint but are not considered intersecting by the `maxIntersections` function. ```sql SELECT maxIntersections(start, end) FROM my_events; ``` Response: ```response 3 ``` If you have multiple occurrences of the maximum interval, you can use the to locate the number and location of those occurrences.
Project: Trivy-Operator (Provisioning / Security & Compliance)
File: upgrade.md

We recommend that you upgrade Trivy Operator often to stay up to date with the latest fixes and enhancements. However, at this stage we do not provide automated upgrades. Therefore, uninstall the previous version of the operator before you install the latest release. !!! warning Consult release notes and changelog to revisit and migrate configuration settings which may not be compatible between different versions.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.3-patch.4.md

layout: release date: 2023-12-28 tag: v0.7.3-patch.4 [bug] Fix searching in MeshSync resources @theBeginner86 (#9737) [Server] Added filters in connections API @Yashsharma1911 (#9729) Fix nil pointer errors and updated the keys new URL path @Yashsharma1911 (#9731) [typo] Update sibling_matchlabels.rego @theBeginner86 (#9734) chore(deps): Bump golang.org/x/crypto from 0.14.0 to 0.17.0 in /scripts/component_updater @dependabot (#9669) : drop dead code @VihasMakwana (#9609) [MeshSync API]add API to delete resources by ID @MUzairS15 (#9728) update schemas and structs @MUzairS15 (#9723) fix meshkit error utiltiy @MUzairS15 (#9724) [Server] Handle database conflicts when persisting MeshSync data. @MUzairS15 (#9718) [bug/rego] Fixes Tag Set Relationship Evaluation @theBeginner86 (#9714) [Relationships] Add Environment Hierarchical Parent Relationship @theBeginner86 (#9677) Add Routing To Dashboard tabs @aabidsofi19 (#9687) [ci] Fix Eslint @theBeginner86 (#9742) Fix routing issue in settings page @senali-d (#9736) [UI] Feat: Assign Connection to Envs @theBeginner86 (#9637) fix name in expansion row @sudhanshutech (#9720) [Environments] - Dark mode support and RTK migration @senali-d (#9705) Fix cols and add resizeable support @sudhanshutech (#9713) Prevent expansion on chip @sudhanshutech (#9703) Added logic of HTML entity encoding in RJSF Text fields widget @Yashsharma1911 (#9702) Enhancements in RJSF select widget @Yashsharma1911 (#9699) [UI] fix kubernetes icon @aabidsofi19 (#9690) Add Routing To Dashboard tabs @aabidsofi19 (#9687) [Helm] chore: dependency upgrade to Ingress v1 @leecalcote (#9745) chore(deps): Bump golang.org/x/crypto from 0.15.0 to 0.17.0 @dependabot (#9668) chore(deps): Bump golang.org/x/crypto from 0.16.0 to 0.17.0 in /scripts/component_generation @dependabot (#9667) Update build-and-release-stable.yml @theBeginner86 (#9711) Bump meshkit to v0.7.1 @Yashsharma1911 (#9709) [snapshot] Update meshmap.yml @theBeginner86 (#9701) Update meshmap.yml @theBeginner86 (#9700) [snapshot] Update meshmap.yml @theBeginner86 (#9698) [CI] Update meshmap.yml to v0.1.3 @leecalcote (#9697) chore(deps): Bump github.com/containerd/containerd from 1.7.6 to 1.7.11 @dependabot (#9683) Add OpenAPI Schema Links to concepts on docs @LakshyaSatpal (#9708) Adding consistent color to list-structure @yash37158 (#9740) sidebar-list-restructure @vishalvivekm (#9710) [meshsync] GET MeshSync Resources Kinds @theBeginner86 (#9730) [UI] Feat: Assign Connection to Envs @theBeginner86 (#9637) [CI] feat: Dedicated URL for latest Meshery release tag @leecalcote (#9725) Feat: Workspaces @theBeginner86 (#9654) Sidebar Unordered Lists Restructure @yash37158 (#9611) [bug] Fix support for exporting designs @theBeginner86 (#9692) [Docs] Update for each page's abstract @leecalcote (#9685) Thank you to our contributors for making this release possible: @LakshyaSatpal, @MUzairS15, @VihasMakwana, @Yashsharma1911, @aabidsofi19, @dependabot, @leecalcote, @senali-d, @sudhanshutech, @theBeginner86, @vishalvivekm and @yash37158
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: rabbitmq-perftest-6566.md

RabbitMQ message latency & throughput across all PerfTest instances RabbitMQ is a RabbitMQ performance testing tool. Verified to work with PerfTest v2.2.0 - v2.9.0. Visualise the following metrics from all PerfTest instances: end-to-end message latency publish confirm latency messages published / s messages confirmed / s messages returned / s messages consumed / s messages rejected / s To get it working locally with RabbitMQ in 3 simple steps, follow this
Project: ArangoDB (App Definition and Development / Database)
File: two-phase-init.md

+++ title = "Two phase construction" description = "" weight = 10 +++ The first thing to do is to break your object's construction into two phases: Place the object into a state where it can be legally destructed without doing any initialisation which could throw an exception (i.e. everything done in phase 1 is `constexpr`). This phase usually involves initialising member variables to various default values, most often using default member initialisers. Most standard C++ library objects and containers have `constexpr` constructors, and thus can be initialised during phase 1. If you need to initialise a member variable without a `constexpr` constructor, {{% api "std::optional<T>" %}} is the usual workaround. Do the remainder of the construction, the parts which could fail. Because phase 1 placed the object into a legally destructible state, it is usually the case that one can bail out during phase 2 and the destructor will clean things up correctly. The phase 1 construction will be placed into a private `constexpr` constructor so nobody external can call it. The phase 2 construction will be placed into a static member initialisation function which returns a `result` with either the successfully constructed object, or the cause of any failure to construct the object. Finally, as a phase 3, some simple metaprogramming will implement a `make<T>{Args...}()` free function which will construct any object `T` by calling its static initialisation function with `Args...` and returning the `result` returned. This isn't as nice as calling `T(Args...)` directly, but it's not too bad in practice. And more importantly, it lets you write generic code which can construct any unknown object which fails via returning `result`, completely avoiding C++ exception throws.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: breaking-12634.en.md

Triple-quote string values in HOCON config files no longer support escape sequence. The detailed information can be found in . Here is a summary for the impact on EMQX users: EMQX 5.6 is the first version to generate triple-quote strings in `cluster.hocon`, meaning for generated configs, there is no compatibility issue. For user hand-crafted configs (such as `emqx.conf`) a thorough review is needed to inspect if escape sequences are used (such as `\n`, `\r`, `\t` and `\\`), if yes, such strings should be changed to regular quotes (one pair of `"`) instead of triple-quotes.
Project: LinuxKit (Provisioning / Automation & Configuration)
File: troubleshooting.md

This document contains a list of known issues related to using, building or testing linuxkit. Problem ``` Error: error building and pushing "linuxkit/mkimage-iso-efi-initrd:0e66171ffde9bb735b0e014f811f9626fc8b9bc9": PUT https://index.docker.io/v2/linuxkit/mkimage-iso-efi-initrd/manifests/0e66171ffde9bb735b0e014f811f9626fc8b9bc9: MANIFEST_INVALID: manifest invalid; if present, mediaType in image index should be 'application/vnd.oci.image.index.v1+json' not 'application/vnd.docker.distribution.manifest.list.v2+json' ``` The above message is caused by registries, notably docker hub, refusing to accept indexes with the docker media type of `application/vnd.docker.distribution.manifest.list.v2+json`, rather than the OCI one `application/vnd.oci.image.index.v1+json`. Linuxkit does use the OCI media type, however, if the image already exists in the registry, linuxkit will pull the index down, update it, and push it back up. The above error occurs because the index that exists in the hub, the one that is pulled down, has the older media type, from when the registry accepted it. Solution The solution is to force an entirely new build, which will generate the images and index with the correct media type. ``` linuxkit pkg build --force <path> linuxkit pkg push <path> ```
Project: YugabyteDB (App Definition and Development / Database)
File: add-extensions.md

title: Create YSQL extensions linkTitle: Create extensions description: Add extensions to a YugabyteDB Managed cluster. headcontent: Extend the functionality of your cluster using PostgreSQL extensions menu: preview_yugabyte-cloud: identifier: add-extensions parent: cloud-clusters weight: 400 type: docs YugabyteDB includes a number of , tested to work with YSQL, that you can use to extend the functionality of your database. {{< note title="Extensions must be pre-bundled" >}} YugabyteDB Managed only supports extensions that are pre-bundled in YugabyteDB. You cannot install new extensions in YugabyteDB Managed. Refer to for the list of pre-bundled extensions. {{< /note >}} Before using an extension, you must load it in the database using the command. For example: ```sql CREATE EXTENSION fuzzystrmatch; ``` In YugabyteDB Managed, extensions can only be loaded by users that are a member of the `ybextension` role. All `ybsuperuser` users, including the default database admin user, are members of `yb_extension`. Use the `GRANT` statement to assign the role to users. For example, to grant the `yb_extension` role to `user`, use the following command: ```sql yugabyte=# GRANT yb_extension TO user; ``` For more information on roles in YugabyteDB Managed, refer to .
Project: KICS (Provisioning / Security & Compliance)
File: dd667399-8d9d-4a8d-bbb4-e49ab53b2f52.md

title: DB Security Group Has Public Interface hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: dd667399-8d9d-4a8d-bbb4-e49ab53b2f52 Query name: DB Security Group Has Public Interface Platform: Crossplane Severity: <span style="color:#bb2124">High</span> Category: Insecure Configurations URL: The CIDR IP should not be a public interface<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="17 55" apiVersion: ec2.aws.crossplane.io/v1beta1 kind: SecurityGroup metadata: name: ec2-rule2 spec: forProvider: region: us-east-1 vpcIdSelector: matchControllerRef: true groupName: crossplane-getting-started description: Allow access to PostgreSQL ingress: fromPort: 5432 toPort: 5432 ipProtocol: tcp ipRanges: cidrIp: 0.0.0.0/0 description: Everywhere apiVersion: apiextensions.crossplane.io/v1 kind: Composition metadata: name: cluster-aws labels: provider: aws cluster: eks spec: compositeTypeRef: apiVersion: mydev.org/v1alpha1 kind: CompositeCluster writeConnectionSecretsToNamespace: crossplane-system patchSets: name: metadata patches: fromFieldPath: metadata.labels resources: name: sample-ec2 base: apiVersion: ec2.aws.crossplane.io/v1beta1 kind: SecurityGroup metadata: name: ec2-rule5 spec: forProvider: region: us-east-1 vpcIdSelector: matchControllerRef: true groupName: crossplane-getting-started description: Allow access to PostgreSQL ingress: fromPort: 5432 toPort: 5432 ipProtocol: tcp ipRanges: cidrIp: 0.0.0.0/0 description: Everywhere ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: ec2.aws.crossplane.io/v1beta1 kind: SecurityGroup metadata: name: ec2-rule1 spec: forProvider: region: us-east-1 vpcIdSelector: matchControllerRef: true groupName: crossplane-getting-started description: Allow access to PostgreSQL ingress: fromPort: 5432 toPort: 5432 ipProtocol: tcp ipRanges: cidrIp: 10.0.0.0/8 description: sample apiVersion: apiextensions.crossplane.io/v1 kind: Composition metadata: name: cluster-aws labels: provider: aws cluster: eks spec: compositeTypeRef: apiVersion: mydev.org/v1alpha1 kind: CompositeCluster writeConnectionSecretsToNamespace: crossplane-system patchSets: name: metadata patches: fromFieldPath: metadata.labels resources: name: sample-ec2 base: apiVersion: ec2.aws.crossplane.io/v1beta1 kind: SecurityGroup metadata: name: ec2-rule spec: forProvider: region: us-east-1 vpcIdSelector: matchControllerRef: true groupName: crossplane-getting-started description: Allow access to PostgreSQL ingress: fromPort: 5432 toPort: 5432 ipProtocol: tcp ipRanges: cidrIp: 10.0.0.0/8 description: sample ```
Project: Grafeas (Provisioning / Security & Compliance)
File: RELEASING.md

We're following approach to releases in Grafeas server. See document for the rationale of API, server, and client versioning. Modify the Grafeas version values for the containers in these locations: Assemble all the meaningful changes since the last release into the file. Make sure your fork of the repository is updated. Assuming `git remote` shows the `origin` (the fork) and `upstream` (the main repository), do: ```shell git pull origin master git pull upstream master git tag -am "grafeas-vX.Y.Z release" vX.Y.Z git push upstream --tags ``` NOTE: the last command will not work if you set `git remote set-url --push upstream no_push` as described in . You will need to re-enable the `push` for this to work, so proceed with caution. You can find the releases in GitHub, e.g. . Ensure you have the right access to push images. Set up the `gcloud` project: ```shell PROJECT=grafeas gcloud config set project $PROJECT gcloud auth configure-docker ... gcloud credential helpers already registered correctly. ``` Now, build the Grafeas server image inside the fork, `go/src/github.com/grafeas/grafeas`: ```shell docker build --tag=grafeas . docker tag grafeas us.gcr.io/grafeas/grafeas-server:vX.Y.Z docker push us.gcr.io/grafeas/grafeas-server:vX.Y.Z ``` You'll need a service account key for `grafeas-helm-manual-release`. Ask the maintainers team for the key, or to execute the following commands on your behalf: ```shell export GOOGLEAPPLICATIONCREDENTIALS="/path/to/json-key.json" ``` Inside the fork, `go/src/github.com/grafeas/grafeas`, run the commands below: ```shell cd grafeas-charts helm plugin install https://github.com/hayorov/helm-gcs helm repo add grafeas-charts-repository gs://grafeas-charts/repository helm package . helm gcs push grafeas-charts-*.tgz grafeas-charts-repository ``` . Navigate to the `grafeas` GCP project and confirm the new image has been uploaded to the registry, and the new Helm chart is on the list of items in Cloud Storage.
Project: KICS (Provisioning / Security & Compliance)
File: 3f23c96c-f9f5-488d-9b17-605b8da5842f.md

title: Unrestricted SQL Server Access hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 3f23c96c-f9f5-488d-9b17-605b8da5842f Query name: Unrestricted SQL Server Access Platform: Ansible Severity: <span style="color:#ff0000">Critical</span> Category: Networking and Firewall URL: Azure SQL Server Accessibility should be set to a minimal address range to grant the principle of least privileges, which means the difference between the values of the 'endipaddress' and 'startipaddress' should be less than 256. Additionally, both ips should be different from '0.0.0.0'<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="10 3" name: Create (or update) Firewall Rule1 azurermsqlfirewallrule: resource_group: myResourceGroup1 server_name: firewallrulecrudtest-6285 name: firewallrulecrudtest-5370 startipaddress: 0.0.0.0 endipaddress: 172.28.11.138 name: Create (or update) Firewall Rule2 azurermsqlfirewallrule: resource_group: myResourceGroup2 server_name: firewallrulecrudtest-6285 name: firewallrulecrudtest-5370 startipaddress: 172.28.10.136 endipaddress: 172.28.11.138 ``` ```yaml title="Negative test num. 1 - yaml file" name: Create (or update) Firewall Rule azurermsqlfirewallrule: resource_group: myResourceGroup server_name: firewallrulecrudtest-6285 name: firewallrulecrudtest-5370 startipaddress: 172.28.10.136 endipaddress: 172.28.10.138 ```
Project: KICS (Provisioning / Security & Compliance)
File: ade36cf4-329f-4830-a83d-9db72c800507.md

title: MSSQL Server Public Network Access Enabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ade36cf4-329f-4830-a83d-9db72c800507 Query name: MSSQL Server Public Network Access Enabled Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Networking and Firewall URL: MSSQL Server public network access should be disabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "azurermmssqlserver" "positive1" { name = "mssqlserver" resourcegroupname = azurermresourcegroup.example.name location = azurermresourcegroup.example.location version = "12.0" administrator_login = "mradministrator" administratorloginpassword = "thisIsDog11" extendedauditingpolicy { storageendpoint = azurermstorageaccount.example.primaryblob_endpoint storageaccountaccesskey = azurermstorageaccount.example.primaryaccess_key storageaccountaccesskeyis_secondary = true retentionindays = 90 } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="16" resource "azurermmssqlserver" "positive2" { name = "mssqlserver" resourcegroupname = azurermresourcegroup.example.name location = azurermresourcegroup.example.location version = "12.0" administrator_login = "mradministrator" administratorloginpassword = "thisIsDog11" extendedauditingpolicy { storageendpoint = azurermstorageaccount.example.primaryblob_endpoint storageaccountaccesskey = azurermstorageaccount.example.primaryaccess_key storageaccountaccesskeyis_secondary = true retentionindays = 90 } publicnetworkaccess_enabled = true } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermmssqlserver" "negative1" { name = "mssqlserver" resourcegroupname = azurermresourcegroup.example.name location = azurermresourcegroup.example.location version = "12.0" administrator_login = "mradministrator" administratorloginpassword = "thisIsDog11" extendedauditingpolicy { storageendpoint = azurermstorageaccount.example.primaryblob_endpoint storageaccountaccesskey = azurermstorageaccount.example.primaryaccess_key storageaccountaccesskeyis_secondary = true retentionindays = 90 } publicnetworkaccess_enabled = false } ```
Project: ClickHouse (App Definition and Development / Database)
File: grouparraylast.md

slug: /en/sql-reference/aggregate-functions/reference/grouparraylast sidebar_position: 110 Syntax: `groupArrayLast(max_size)(x)` Creates an array of last argument values. For example, `groupArrayLast(1)(x)` is equivalent to `[anyLast (x)]`. In some cases, you can still rely on the order of execution. This applies to cases when `SELECT` comes from a subquery that uses `ORDER BY` if the subquery result is small enough. Example Query: ```sql select groupArrayLast(2)(number+1) numbers from numbers(10) ``` Result: ```text numbers [9,10] ``` In compare to `groupArray`: ```sql select groupArray(2)(number+1) numbers from numbers(10) ``` ```text numbers [1,2] ```