cwielenb/CNCF-Dataset huggingface dataset:
Project: YugabyteDB (App Definition and Development / Database)
File: create_user_mapping.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="1049" height="50" viewbox="0 0 1049 50"><path class="connector" d="M0 22h15m67 0h10m53 0h10m75 0h30m32 0h10m45 0h10m64 0h20m-196 0q5 0 5 5v8q0 5 5 5h171q5 0 5-5v-8q0-5 5-5m5 0h10m44 0h10m46 0h10m68 0h10m99 0h30m74 0h10m25 0h10m92 0h10m25 0h20m-281 0q5 0 5 5v8q0 5 5 5h256q5 0 5-5v-8q0-5 5-5m5 0h15"/><polygon points="0,29 5,22 0,15" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="5" width="67" height="25" rx="7"/><text class="text" x="25" y="22">CREATE</text><rect class="literal" x="92" y="5" width="53" height="25" rx="7"/><text class="text" x="102" y="22">USER</text><rect class="literal" x="155" y="5" width="75" height="25" rx="7"/><text class="text" x="165" y="22">MAPPING</text><rect class="literal" x="260" y="5" width="32" height="25" rx="7"/><text class="text" x="270" y="22">IF</text><rect class="literal" x="302" y="5" width="45" height="25" rx="7"/><text class="text" x="312" y="22">NOT</text><rect class="literal" x="357" y="5" width="64" height="25" rx="7"/><text class="text" x="367" y="22">EXISTS</text><rect class="literal" x="451" y="5" width="44" height="25" rx="7"/><text class="text" x="461" y="22">FOR</text><a xlink:href="../../../syntaxresources/grammardiagrams#user"><rect class="rule" x="505" y="5" width="46" height="25"/><text class="text" x="515" y="22">user</text></a><rect class="literal" x="561" y="5" width="68" height="25" rx="7"/><text class="text" x="571" y="22">SERVER</text><a xlink:href="../../../syntaxresources/grammardiagrams#server-name"><rect class="rule" x="639" y="5" width="99" height="25"/><text class="text" x="649" y="22">servername</text></a><rect class="literal" x="768" y="5" width="74" height="25" rx="7"/><text class="text" x="778" y="22">OPTIONS</text><rect class="literal" x="852" y="5" width="25" height="25" rx="7"/><text class="text" x="862" y="22">(</text><a xlink:href="../../../syntaxresources/grammardiagrams#fdw-options"><rect class="rule" x="887" y="5" width="92" height="25"/><text class="text" x="897" y="22">fdwoptions</text></a><rect class="literal" x="989" y="5" width="25" height="25" rx="7"/><text class="text" x="999" y="22">)</text><polygon points="1045,29 1049,29 1049,15 1045,15" style="fill:black;stroke-width:0"/></svg>
Project: Tremor (App Definition and Development / Streaming & Messaging)
File: toplevelexpr.md

The `TopLevelExpr` rule specifies the expression forms that are legal at the outer most scope of a tremor script definition. The legal forms are: Use declarations - these allow external modules to be referenced. Constant expressions - these are immutable compile time constants. Function definitions - these are user defined functions. Intrinsic function definitions - these are builtin funtions provided by the runtime.
Project: Salt Project (Provisioning / Automation & Configuration)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: "[BUG]" labels: Bug, needs-triage assignees: '' Description A clear and concise description of what the bug is. Setup (Please provide relevant configs and/or SLS files (be sure to remove sensitive info. There is no general set-up of Salt.) Please be as specific as possible and give set-up details. [ ] on-prem machine [ ] VM (Virtualbox, KVM, etc. please specify) [ ] VM running on a cloud service, please be explicit and add details [ ] container (Kubernetes, Docker, containerd, etc. please specify) [ ] or a combination, please be explicit [ ] jails if it is FreeBSD [ ] classic packaging [ ] onedir packaging [ ] used bootstrap to install Steps to Reproduce the behavior (Include debug logs if possible and relevant) Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Versions Report <details><summary>salt --versions-report</summary> (Provided by running salt --versions-report. Please also mention any differences in master/minion versions.) ```yaml PASTE HERE ``` </details> Additional context Add any other context about the problem here.
Project: Kyverno (Provisioning / Security & Compliance)
File: kyverno_fix_test.md

Fix inconsistencies and deprecated usage in Kyverno test files. Fix inconsistencies and deprecated usage in Kyverno test files. NOTE: This is an experimental command, use `KYVERNO_EXPERIMENTAL=true` to enable it. ``` kyverno fix test [dir]... [flags] ``` ``` KYVERNO_EXPERIMENTAL=true kyverno fix test . KYVERNO_EXPERIMENTAL=true kyverno fix test . --save KYVERNO_EXPERIMENTAL=true kyverno fix test . --file-name test.yaml --save ``` ``` --compress Compress test results -f, --file-name string Test filename (default "kyverno-test.yaml") --force Force save file -h, --help help for test --save Save fixed file ``` ``` --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 ``` - Fix inconsistencies and deprecated usage of Kyverno resources.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_zone.md

+++ title = "googlecomputezone resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputezone" identifier = "inspec/resources/gcp/googlecomputezone.md googlecomputezone resource" parent = "inspec/resources/gcp" +++ A `googlecomputezone` is used to test a Google Zone resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputezone(project: 'chef-gcp-inspec', name: "us-central1-a") do it { should exist } it { should be_up } end ``` describe googlecomputezone(project: 'chef-inspec-gcp', zone: 'us-east1-b') do it { should exist } end describe googlecomputezone(project: 'chef-inspec-gcp', zone: 'us-east1-b') do its('status') { should eq 'UP' } it { should be_up } end describe googlecomputezone(project: 'chef-inspec-gcp', zone: 'us-east1-b') do its('availablecpuplatforms') { should include "Intel Skylake" } end Properties that can be accessed from the `googlecomputezone` resource: `creation_timestamp` : Creation timestamp in RFC3339 text format. `deprecated` : The deprecation status associated with this machine type. `deleted` : An optional RFC3339 timestamp on or after which the state of this resource is intended to change to DELETED. This is only informational and the status will not change unless the client explicitly changes it. `deprecated` : An optional RFC3339 timestamp on or after which the state of this resource is intended to change to DEPRECATED. This is only informational and the status will not change unless the client explicitly changes it. `obsolete` : An optional RFC3339 timestamp on or after which the state of this resource is intended to change to OBSOLETE. This is only informational and the status will not change unless the client explicitly changes it. `replacement` : The URL of the suggested replacement for a deprecated resource. The suggested replacement resource must be the same kind of resource as the deprecated resource. `state` : The deprecation state of this resource. This can be DEPRECATED, OBSOLETE, or DELETED. Operations which create a new resource using a DEPRECATED resource will return successfully, but with a warning indicating the deprecated resource and recommending its replacement. Operations which use OBSOLETE or DELETED resources will be rejected and result in an error. Possible values: DEPRECATED OBSOLETE DELETED `description` : An optional textual description of the resource. `id` : The unique identifier for the resource. `name` : Name of the resource. `region` : The region where the zone is located. `status` : The status of the zone. Possible values: UP DOWN `availablecpuplatforms` : The available CPU platforms in this zone Ensure the is enabled for the current project.
Project: Meshery (Provisioning / Automation & Configuration)
File: aws-api-gateway-operator.md

layout: integration title: AWS API Gateway Operator subtitle: Collaborative and visual infrastructure as code for AWS API Gateway Operator image: /assets/img/integrations/aws-api-gateway-operator/icons/color/aws-api-gateway-operator-color.svg permalink: extensibility/integrations/aws-api-gateway-operator docURL: https://docs.meshery.io/extensibility/integrations/aws-api-gateway-operator description: integrations-category: Cloud Native Network integrations-subcategory: Service Proxy registrant: Artifact Hub components: name: awsapi-gateway colorIcon: assets/img/integrations/aws-api-gateway-operator/components/awsapi-gateway/icons/color/awsapi-gateway-color.svg whiteIcon: assets/img/integrations/aws-api-gateway-operator/components/awsapi-gateway/icons/white/awsapi-gateway-white.svg description: featureList: [ "Create, publish, maintain, monitor, and secure REST, HTTP, and WebSocket APIs at any scale.", "Create APIs that access AWS or other web services, as well as data stored in the AWS Cloud.", "API Gateway creates RESTful APIs that enable stateless client-server communication." ] 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: ClickHouse (App Definition and Development / Database)
File: kurtpop.md

slug: /en/sql-reference/aggregate-functions/reference/kurtpop sidebar_position: 153 Computes the of a sequence. ``` sql kurtPop(expr) ``` Arguments `expr` returning a number. Returned value The kurtosis of the given distribution. Type Example ``` sql SELECT kurtPop(value) FROM serieswithvalue_column; ```
Project: Apache Heron (App Definition and Development / Streaming & Messaging)
File: cluster-config-system-level.md

id: version-0.20.0-incubating-cluster-config-system-level title: System Level Configuration sidebar_label: System Level Configuration original_id: cluster-config-system-level <!-- 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. --> The parameters in the sections below are set at the system level and thus do not apply to any specific component. Config | Meaning | Default :-- |:- |:- `heron.check.tmanager.location.interval.sec` | The interval, in seconds, after which to check if the topology manager location has been fetched or not | 120 `heron.metrics.export.interval` | The interval, in seconds, at which components export metrics to the topology's Metrics Manager Config | Meaning | Default :-- |:- |:- `heron.logging.directory` | The relative path to the logging directory | `log-files` `heron.logging.maximum.size.mb` | The maximum log file size (in megabytes) | 100 `heron.logging.maximum.files` | The maximum number of log files | 5 `heron.logging.prune.interval.sec` | The time interval, in seconds, at which Heron prunes log files | 300 `heron.logging.flush.interval.sec` | The time interval, in seconds, at which Heron flushes log files | 10 `heron.logging.err.threshold` | The threshold level to log error | 3
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.9.26.md

RabbitMQ `3.9.26` is a maintenance release in the `3.9.x` release series. Please refer to the Upgrading to 3.9 section from if upgrading from a version prior to 3.9.0. This release requires at least Erlang 24.2, and supports Erlang 25. has more details on Erlang version requirements for RabbitMQ. Erlang 23 support has reached its . Starting with this release, RabbitMQ requires Erlang 24.2 or later versions. Nodes will fail to start on older Erlang releases. Release notes can be found on GitHub at . Fixed a type analyzer definition. Contributed by @illotum (AWS). GitHub issue: LDAP server password could end up in the logs in certain types of exceptions. Contributed by @SimonUnge (AWS). GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.9.26.tar.xz` instead of the source tarball produced by GitHub.
Project: Flink (App Definition and Development / Streaming & Messaging)
File: experimental.md

title: "Experimental Features" weight: 101 type: docs aliases: /dev/stream/experimental.html <!-- 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 section describes experimental features in the DataStream API. Experimental features are still evolving and can be either unstable, incomplete, or subject to heavy change in future versions. Reinterpreting a pre-partitioned data stream as keyed stream We can re-interpret a pre-partitioned data stream as a keyed stream to avoid shuffling. {{< hint danger >}} WARNING: The re-interpreted data stream MUST already be pre-partitioned in EXACTLY the same way Flink's keyBy would partition the data in a shuffle w.r.t. key-group assignment. {{< /hint >}} One use-case for this could be a materialized shuffle between two jobs: the first job performs a keyBy shuffle and materializes each output into a partition. A second job has sources that, for each parallel instance, reads from the corresponding partitions created by the first job. Those sources can now be re-interpreted as keyed streams, e.g. to apply windowing. Notice that this trick makes the second job embarrassingly parallel, which can be helpful for a fine-grained recovery scheme. This re-interpretation functionality is exposed through `DataStreamUtils`: ```java static <T, K> KeyedStream<T, K> reinterpretAsKeyedStream( DataStream<T> stream, KeySelector<T, K> keySelector, TypeInformation<K> typeInfo) ``` Given a base stream, a key selector, and type information, the method creates a keyed stream from the base stream. Code example: {{< tabs "01a03be7-da80-4a50-b45f-97a28fbcd670" >}} {{< tab "Java" >}} ```java StreamExecutionEnvironment env = StreamExecutionEnvironment.getExecutionEnvironment(); DataStreamSource<Integer> source = ...; DataStreamUtils.reinterpretAsKeyedStream(source, (in) -> in, TypeInformation.of(Integer.class)) .window(TumblingEventTimeWindows.of(Time.seconds(1))) .reduce((a, b) -> a + b) .addSink(new DiscardingSink<>()); env.execute(); ``` {{< /tab >}} {{< tab "Scala" >}} ```scala val env = StreamExecutionEnvironment.getExecutionEnvironment env.setParallelism(1) val source = ... new DataStreamUtils(source).reinterpretAsKeyedStream((in) => in) .window(TumblingEventTimeWindows.of(Time.seconds(1))) .reduce((a, b) => a + b) .addSink(new DiscardingSink[Int]) env.execute() ``` {{< /tab >}} {{< /tabs >}} {{< top >}}
Project: Redpanda (App Definition and Development / Streaming & Messaging)
File: 05_rpunit_failure.md

name: Create ci-failure issue (rpunit) about: An unit/fixure test is failing in CI title: CI Failure (key symptom) in `_rpunit` labels: kind/bug, rpunit assignees: '' <!-- Before creating an issue look through existing rpunit to avoid duplicates https://github.com/redpanda-data/redpanda/issues?q=is%3Aissue+is%3Aopen+label%3Arpunit --> https://link.to/failing/build <!-- Copy the stacktrace and/or failing assertion --> ``` /redpanda/src/v/foo/tests/foo_test.cc:42: Failure Value of: returned Expected: contains 1 values, where each value and its corresponding value in {} same record eq Actual: { {}, {} }, which contains 2 values ```
Project: Infinispan (App Definition and Development / Database)
File: README-Build.md

You can read more about how to build Infinispan in the documentation: link:https://infinispan.org/docs/dev/titles/contributing/contributing.html[Infinispan Contributor's Guide] Provided you already have the correct versions of Java and Maven installed, you can get started right away. For convenience you can use the provided maven-settings.xml file which enables all additional repositories required for building Infinispan: ./mvnw -s maven-settings.xml clean install -DskipTests Available profiles ================== distribution* Builds the full distribution java-alt-test* Runs tests using an older JDK compared to the one required to build. Requires setting the `JAVAALTHOME` environment variable.
Project: ClickHouse (App Definition and Development / Database)
File: move.md

slug: /en/sql-reference/statements/move sidebar_position: 54 sidebar_label: MOVE This statement allows to move an access entity from one access storage to another. Syntax: ```sql MOVE {USER, ROLE, QUOTA, SETTINGS PROFILE, ROW POLICY} name1 [, name2, ...] TO accessstoragetype ``` Currently, there are five access storages in ClickHouse: `local_directory` `memory` `replicated` `users_xml` (ro) `ldap` (ro) Examples: ```sql MOVE USER test TO local_directory ``` ```sql MOVE ROLE test TO memory ```
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: COMPATIBILITY.md

Supported Capabilities ====================== Here is a non-comprehensive table of git commands and features whose equivalent is supported by go-git. | Feature | Status | Notes | ||--|-| | config | | config | | Reading and modifying per-repository configuration (`.git/config`) is supported. Global configuration (`$HOME/.gitconfig`) is not. | | getting and creating repositories | | init | | Plain init and `--bare` are supported. Flags `--template`, `--separate-git-dir` and `--shared` are not. | | clone | | Plain clone and equivalents to `--progress`, `--single-branch`, `--depth`, `--origin`, `--recurse-submodules` are supported. Others are not. | | basic snapshotting | | add | | Plain add is supported. Any other flag aren't supported | | status | | | commit | | | reset | | | rm | | | mv | | | branching and merging | | branch | | | checkout | | Basic usages of checkout are supported. | | merge | | | mergetool | | | stash | | | tag | | | sharing and updating projects | | fetch | | | pull | | Only supports merges where the merge can be resolved as a fast-forward. | | push | | | remote | | | submodule | | | inspection and comparison | | show | | | log | | | shortlog | (see log) | | describe | | | patching | | apply | | | cherry-pick | | | diff | | Patch object with UnifiedDiff output representation | | rebase | | | revert | | | debugging | | bisect | | | blame | | | grep | | | email || | am | | | apply | | | format-patch | | | send-email | | | request-pull | | | external systems | | svn | | | fast-import | | | administration | | clean | | | gc | | | fsck | | | reflog | | | filter-branch | | | instaweb | | | archive | | | bundle | | | prune | | | repack | | | server admin | | daemon | | | update-server-info | | | advanced | | notes | | | replace | | | worktree | | | annotate | (see blame) | | gpg | | git-verify-commit | | | git-verify-tag | | | plumbing commands | | cat-file | | | check-ignore | | | commit-tree | | | count-objects | | | diff-index | | | for-each-ref | | | hash-object | | | ls-files | | | merge-base | | Calculates the merge-base only between two commits, and supports `--independent` and `--is-ancestor` modifiers; Does not support `--fork-point` nor `--octopus` modifiers. | | read-tree | | | rev-list | | | rev-parse | | | show-ref | | | symbolic-ref | | | update-index | | | update-ref | | | verify-pack | | | write-tree | | | protocols | | http(s):// (dumb) | | | http(s):// (smart) | | | git:// | | | ssh:// | | | file:// | | | custom | | | other features | | gitignore | | | gitattributes | | | index version | | | packfile version | | | push-certs | |
Project: KICS (Provisioning / Security & Compliance)
File: 8ada6e80-0ade-439e-b176-0b28f6bce35a.md

title: Run Using Sudo hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 8ada6e80-0ade-439e-b176-0b28f6bce35a Query name: Run Using Sudo Platform: Dockerfile Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Avoid RUN with sudo command as it leads to unpredictable behavior<br> ```dockerfile title="Positive test num. 1 - dockerfile file" hl_lines="3" FROM alpine:3.5 RUN apk add --update py2-pip RUN sudo pip install --upgrade pip COPY requirements.txt /usr/src/app/ RUN pip install --no-cache-dir -r /usr/src/app/requirements.txt COPY app.py /usr/src/app/ COPY templates/index.html /usr/src/app/templates/ EXPOSE 5000 CMD ["python", "/usr/src/app/app.py"] ``` ```dockerfile title="Negative test num. 1 - dockerfile file" FROM alpine:3.5 RUN apk add --update py2-pip RUN pip install --upgrade pip RUN apt-get install sudo COPY requirements.txt /usr/src/app/ RUN pip install --no-cache-dir -r /usr/src/app/requirements.txt COPY app.py /usr/src/app/ COPY templates/index.html /usr/src/app/templates/ EXPOSE 5000 CMD ["python", "/usr/src/app/app.py"] ```
Project: Clair (Provisioning / Security & Compliance)
File: ROADMAP.md

This document defines a high level roadmap for Clair development. The dates below should not be considered authoritative, but rather indicative of the projected timeline of the project. The represent the most up-to-date and issue-for-issue plans. The roadmap below outlines new features that will be added to Clair, and while subject to change, define what future stable will look like. Support multiple namespaces per image This enables language-level package managers (e.g. npm, pip) in the future Take advantage of OCI/Docker content-addressiblity to avoid duplicated work This simplifies the amount of work required for an offline clair in the future Support mappings between source packages and binary packages Versioned detectors that are present in API results This will enable clients to determine when images need to be reindexed gRPC API that works on sets of layers rather than individual layers Structured logging in JSON Improve coverage and readability of documentation