cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: 063234c0-91c0-4ab5-bbd0-47ddb5f23786.md

title: Ram Account Password Policy Not Required Numbers hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 063234c0-91c0-4ab5-bbd0-47ddb5f23786 Query name: Ram Account Password Policy Not Required Numbers Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Secret Management URL: Ram Account Password Policy should have 'require_numbers' set to true<br> ```tf title="Positive test num. 1 - tf file" hl_lines="5" resource "alicloudramaccountpasswordpolicy" "corporate" { minimumpasswordlength = 9 requirelowercasecharacters = false requireuppercasecharacters = false require_numbers = false require_symbols = false hard_expiry = true maxpasswordage = 12 passwordreuseprevention = 5 maxloginattempts = 3 } ``` ```tf title="Negative test num. 1 - tf file" resource "alicloudramaccountpasswordpolicy" "corporate" { minimumpasswordlength = 9 requirelowercasecharacters = false requireuppercasecharacters = false require_numbers = true require_symbols = false hard_expiry = true maxpasswordage = 12 passwordreuseprevention = 5 maxloginattempts = 3 } ``` ```tf title="Negative test num. 2 - tf file" resource "alicloudramaccountpasswordpolicy" "corporate" { minimumpasswordlength = 9 requirelowercasecharacters = false requireuppercasecharacters = false require_symbols = false hard_expiry = true maxpasswordage = 12 passwordreuseprevention = 5 maxloginattempts = 3 } ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: aliz.md

title: "Aliz" icon: /images/logos/powered-by/aliz.png hasLink: "https://aliz.ai/en/blog/dataflow-vs-spark-4-key-difference-to-consider/" <!-- Licensed 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. -->
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.11.27.md

RabbitMQ `3.11.27` is a maintenance release in the `3.11.x` . This release series . Please refer to the upgrade section from if upgrading from a version prior to 3.11.0. This release requires Erlang 25 and supports Erlang versions up to `25.3.x`. has more details on Erlang version requirements for RabbitMQ. As of 3.11.0, RabbitMQ requires Erlang 25. Nodes will fail to start on older Erlang releases. Erlang 25 as our new baseline means much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation available to all RabbitMQ 3.11 users. Release notes can be found on GitHub at . Avoids a rare exception that could stop TCP socket writes on a client connection. GitHub issues: , Definition files that are virtual host-specific cannot be imported on boot. Such files will now be detected early and the import process will terminate after logging a more informative message. Previous the import process would run into an obscure exception. GitHub issues: , Avoids two Shovels being started after an upgrade from `3.11.25` or older versions. Two Shovels running concurrently would still transfer messages but because they act as competing consumers (and publishers), this affected message ordering in the target queue. Contributed by @gomoripeti (CloudAMQP). GitHub issues: , `DELETE /api/policies/{vhost}/{policy}` returned a 500 response instead of a 404 one when target virtual host did not exist. GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.27.tar.xz` instead of the source tarball produced by GitHub.
Project: KubeZoo (Provisioning / Automation & Configuration)
File: debug-kubezoo-locally.md

This tutorial introduces how to debug KubeZoo locally, with a `kind` cluster as the upstream cluster. Please install the latest version of , , , and ```console kind create cluster kubectl config use-context kind-kind ``` We need two sets of certificates/keys to run KubeZoo: certificates/keys used to secure the communication between tenant clients and KubeZoo, which will be generated locally and store in the subdirectory `_output/kubezoo` under KubeZoo root directory; certificates/keys used to secure the communication between KubeZoo and the upstream cluster, which will need to be fetched from the upstream cluster and store in the secret `_output/kubezoo` under KubeZoo root directory ```console $ bash $KUBEZOOPATH/hack/lib/genpki.sh genpkisetupctxprint_parameters ``` Upon success, the parameters to run KubeZoo are printed ```console --allow-privileged=true --apiserver-count=1 --cors-allowed-origins=.* --delete-collection-workers=1 --etcd-prefix=/zoo ... ``` This script will also setup a `kubectl` context for accessing `KubeZoo` ```console $ kubectl config get-contexts CURRENT NAME CLUSTER AUTHINFO NAMESPACE kind-kind kind-kind kind-kind zoo zoo zoo-admin ``` ```console $ etcd {"level":"info","ts":"2021-09-17T09:19:32.783-0400","caller":"etcdmain/etcd.go:72","msg":... } ``` ```console kubezoo --allow-privileged=true --apiserver-count=1 --cors-allowed-origins=.* --delete-collection-workers=1 --etcd-prefix=/zoo ... ``` ```console $ kubectl api-resources --context zoo NAME SHORTNAMES APIVERSION NAMESPACED KIND ... tenants tenant.kubezoo.io/v1alpha1 false Tenant ``` ```console $ kubectl apply -f config/setup/sample_tenant.yaml --context zoo tenant.tenant.kubezoo.io/111111 created ``` The tenant name must be a valid 6-character DNS label prefix (`{5}`). ```console $ kubectl get tenant 111111 --context zoo -o jsonpath='{.metadata.annotations.kubezoo\.io\/tenant\.kubeconfig\.base64}' | base64 --decode > 111111.kubeconfig ``` ```console $ kubectl apply --kubeconfig 111111.kubeconfig -f- <<EOF apiVersion: v1 kind: Pod metadata: name: test spec: containers: name: test image: busybox command: tail args: -f /dev/null EOF pod/test created ``` Get the pod as the tenant ```console $ kubectl get po --kubeconfig 111111.kubeconfig NAME READY STATUS RESTARTS AGE test 1/1 Running 0 44s ``` Get the pod as the cluster administrator ```console $ kubectl get po -A NAMESPACE NAME READY STATUS RESTARTS AGE 111111-default test 1/1 Running 0 2m28s ... ```
Project: KubeEdge (Provisioning / Automation & Configuration)
File: failing-test.md

name: Failing Test about: Report test failures in KubeEdge CI jobs labels: kind/failing-test <!-- Please only use this template for submitting reports about failing tests in KubeEdge CI jobs --> Which jobs are failing: Which test(s) are failing: Since when has it been failing: Reason for failure: Anything else we need to know:
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.42.md

layout: release date: 2023-01-12 tag: v0.6.42 language: en Refactor pattern engine logic to avoid invalid components @Revolyssup (#6872) Bump json5 from 1.0.1 to 1.0.2 in /install/docker-extension/ui @dependabot (#6836) fix panic @Revolyssup (#6866) updated the link Meshery Contributors Welcome Guide @VedRatan (#6855) fix applications update not reflected @MUzairS15 (#6854) Fix component updater workflow logic @Revolyssup (#6853) improve `meshery pattern list` cmd error message @ayushthe1 (#6852) Bump cypress from 11.2.0 to 12.2.0 in /provider-ui @dependabot (#6820) remove deprecated targets from meshery makefile @ayushthe1 (#6810) [CI] Fix: codecov update failure @Abhishek-kumar09 (#6869) [UI] Fixed the applications page modal bug @partik03 (#6804) [UI] Fixed the code mirror bug of filters page @partik03 (#6843) Bump cypress from 11.2.0 to 12.2.0 in /provider-ui @dependabot (#6820) git auto commit action used to push changes to repo in discussions-data-files-update workflow @deepakdinesh1123 (#6845) remove deprecated targets from meshery makefile @ayushthe1 (#6810) [CI] Fix: codecov update failure @Abhishek-kumar09 (#6869) Migrate older MeshModel endpoints to proposed MeshModel endpoints @Revolyssup (#6849) [Doc] - Meshery installation documentation update @gurpreet-legend (#6857) remove deprecated targets from meshery makefile @ayushthe1 (#6810) [Docs] - make command update in docs @gurpreet-legend (#6858) Fixing contributing.md @VedRatan (#6863) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Chadha93, @MUzairS15, @MarioArriaga92, @Nikhil-Ladha, @Revolyssup, @UtkarshMishra12, @VedRatan, @ayushthe1, @deepakdinesh1123, @dependabot, @gurpreet-legend, @leecalcote, @partik03 and Discussions Bot
Project: StarRocks (App Definition and Development / Database)
File: money_format.md

displayed_sidebar: "English" This function returns a string formatted as a currency string. The integer part is separated by comma every three bits and the decimal part is reserved for two bits. ```Haskell VARCHAR money_format(Number) ``` ```Plain Text MySQL > select money_format(17014116); ++ | money_format(17014116) | ++ | 17,014,116.00 | ++ MySQL > select money_format(1123.456); ++ | money_format(1123.456) | ++ | 1,123.46 | ++ MySQL > select money_format(1123.4); +-+ | money_format(1123.4) | +-+ | 1,123.40 | +-+ ``` MONEY_FORMAT,MONEY,FORMAT
Project: YugabyteDB (App Definition and Development / Database)
File: window_definition.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="335" height="260" viewbox="0 0 335 260"><path class="connector" d="M0 22h15m25 0h30m54 0h20m-89 0q5 0 5 5v8q0 5 5 5h64q5 0 5-5v-8q0-5 5-5m5 0h7m2 0h2m2 0h2m-159 80h2m2 0h2m2 0h27m85 0h10m35 0h30m-5 0q-5 0-5-5v-20q0-5 5-5h35m24 0h36q5 0 5 5v20q0 5-5 5m-5 0h40m-300 0q5 0 5 5v8q0 5 5 5h275q5 0 5-5v-8q0-5 5-5m5 0h7m2 0h2m2 0h2m-335 80h2m2 0h2m2 0h27m62 0h10m35 0h30m-5 0q-5 0-5-5v-20q0-5 5-5h35m24 0h36q5 0 5 5v20q0 5-5 5m-5 0h40m-277 0q5 0 5 5v8q0 5 5 5h252q5 0 5-5v-8q0-5 5-5m5 0h7m2 0h2m2 0h2m-312 50h2m2 0h2m2 0h27m100 0h20m-135 0q5 0 5 5v8q0 5 5 5h110q5 0 5-5v-8q0-5 5-5m5 0h10m25 0h15"/><polygon points="0,29 5,22 0,15" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="5" width="25" height="25" rx="7"/><text class="text" x="25" y="22">(</text><a xlink:href="../../../syntaxresources/grammardiagrams#name"><rect class="rule" x="70" y="5" width="54" height="25"/><text class="text" x="80" y="22">name</text></a><rect class="literal" x="35" y="85" width="85" height="25" rx="7"/><text class="text" x="45" y="102">PARTITION</text><rect class="literal" x="130" y="85" width="35" height="25" rx="7"/><text class="text" x="140" y="102">BY</text><rect class="literal" x="225" y="55" width="24" height="25" rx="7"/><text class="text" x="235" y="72">,</text><a xlink:href="../../../syntaxresources/grammardiagrams#order-expr"><rect class="rule" x="195" y="85" width="85" height="25"/><text class="text" x="205" y="102">orderexpr</text></a><rect class="literal" x="35" y="165" width="62" height="25" rx="7"/><text class="text" x="45" y="182">ORDER</text><rect class="literal" x="107" y="165" width="35" height="25" rx="7"/><text class="text" x="117" y="182">BY</text><rect class="literal" x="202" y="135" width="24" height="25" rx="7"/><text class="text" x="212" y="152">,</text><a xlink:href="../../../syntaxresources/grammardiagrams#order-expr"><rect class="rule" x="172" y="165" width="85" height="25"/><text class="text" x="182" y="182">orderexpr</text></a><a xlink:href="../../../syntaxresources/grammardiagrams#frame-clause"><rect class="rule" x="35" y="215" width="100" height="25"/><text class="text" x="45" y="232">frame_clause</text></a><rect class="literal" x="165" y="215" width="25" height="25" rx="7"/><text class="text" x="175" y="232">)</text><polygon points="201,239 205,239 205,225 201,225" style="fill:black;stroke-width:0"/></svg>
Project: Presto (App Definition and Development / Database)
File: khll.md

This implementation meets the specifications detailed in . Unless otherwise noted, all values are little-endian. KHyperLogLog maintains a k-sized MinHash structure whose entries map a long key to a HyperLogLog sketch. HyperLogLog (HLL) sketches are serialized according to . format: byte value which represents the format used for serialization (currently just one format exists, `0`) K: the maximum amount of entries that can be stored in the MinHash struct HLL buckets: the amount of buckets the HLL sketches are composed of \# of entries: the number of entries currently in the MinHash struct (can be at most K) total HLL size: the sum of all the serialized HLL sketches' size, in bytes HLL sizes: sequence of ints specifying the size, in bytes, of each serialized HLL sketch keys: sequence of entries present in the MinHash struct, in ascending order HLLs: sequence of serialized HLL sketches corresponding to each key, in the same order the keys are serialized
Project: YDB (App Definition and Development / Database)
File: metadata.md

When you run YQL operations via the web interface or HTTP API, you get access to the following data: `CurrentOperationId()`: The private ID of the operation. `CurrentOperationSharedId()`: The public ID of the operation. `CurrentAuthenticatedUser()`: The username of the current user. No arguments. If this data is missing, for example, when you run operations in the embedded mode, the functions return an empty string. Examples ```yql SELECT CurrentOperationId(), CurrentOperationSharedId(), CurrentAuthenticatedUser(); ```
Project: Kapitan (Provisioning / Automation & Configuration)
File: kap_7_remote_inventory.md

This feature would add the ability to Kapitan to fetch parts of the inventory from remote locations (https/git). This would allow users to combine different inventories from different sources and build modular infrastructure reusable across various repos. Author: @alpharoy14 The configuration and declaration of remote inventories would be done in the inventory files. The file specifications are as follows: ```yaml parameters: kapitan: inventory: type: <inventory_type> #git\https source: <sourceofinventory> outputpath: <relativeoutput_path> ``` On executing the ```$ kapitan compile --fetch``` command, first the remote inventories will be fetched followed by fetching of external dependencies and finally merge the inventory to compile. The output path is the path to save the inventory items into. The path is relative to the `inventory/` directory. For example, it could be `/classes/`. The contents of the fetched inventory will be recursively copied. The fetched inventory files will be cached in the `.dependency_cache` directory if `--cache` is set. eg. `$ kapitan compile --fetch --cache` While fetching, the output path will be recursively checked to see if it contains any file with the same name. If so, kapitan will skip fetching it. To overwrite the files with the newly downloaded inventory items, we can add the `--force-fetch` flag to the compile command, as shown below. `$ kapitan compile --force-fetch` The URL type can be either git or http(s). Depending on the URL type, the configuration file may have additional arguments. E.g Git type may also include aditional `ref` parameter as illustrated below: ```yaml inventory: type: git #git\https source: <sourceofinventory> outputpath: <outputpath> ref: <commit_hash/branch/tag> ``` TODO module (and git executable) for git type requests module for http[s]
Project: ClickHouse (App Definition and Development / Database)
File: PULL_REQUEST_TEMPLATE.md

<! A technical comment, you are free to remove or leave it as it is when PR is created The following categories are used in the next scripts, update them accordingly utils/changelog/changelog.py tests/ci/cancelandrerunworkflowlambda/app.py --> New Feature Improvement Performance Improvement Backward Incompatible Change Build/Testing/Packaging Improvement Documentation (changelog entry is not required) Bug Fix (user-visible misbehavior in an official stable release) CI Fix or Improvement (changelog entry is not required) Not for changelog (changelog entry is not required) ... [ ] Documentation is written (mandatory for new features) <! Directly edit documentation source files in the "docs" folder with the same pull-request as code changes or Add a user-readable short description of the changes that should be added to docs.clickhouse.com below. At a minimum, the following information should be added (but add more as needed). Motivation: Why is this function, table engine, etc. useful to ClickHouse users? Parameters: If the feature being added takes arguments, options or is influenced by settings, please list them below with a brief explanation. Example use: A query or command. --> Information about CI checks: https://clickhouse.com/docs/en/development/continuous-integration/ <details> <summary>Modify your CI run</summary> NOTE: If your merge the PR with modified CI you MUST KNOW what you are doing NOTE: Checked options will be applied if set before CI RunConfig/PrepareRunConfig step [ ] <!ciincludefast--> Fast test [ ] <!ciincludeintegration--> Integration Tests [ ] <!ciincludestateless--> Stateless tests [ ] <!ciincludestateful--> Stateful tests [ ] <!ciincludeunit--> Unit tests [ ] <!ciincludeperformance--> Performance tests [ ] <!ciincludeasan--> All with ASAN [ ] <!ciincludetsan--> All with TSAN [ ] <!ciincludeanalyzer--> All with Analyzer [ ] <!ciincludeazure --> All with Azure [ ] <!ciincludeKEYWORD--> Add your option here [ ] <!ciexcludefast--> Fast test [ ] <!ciexcludeintegration--> Integration Tests [ ] <!ciexcludestateless--> Stateless tests [ ] <!ciexcludestateful--> Stateful tests [ ] <!ciexcludeperformance--> Performance tests [ ] <!ciexcludeasan--> All with ASAN [ ] <!ciexcludetsan--> All with TSAN [ ] <!ciexcludemsan--> All with MSAN [ ] <!ciexcludeubsan--> All with UBSAN [ ] <!ciexcludecoverage--> All with Coverage [ ] <!ciexcludeaarch64--> All with Aarch64 [ ] <!ciexcludeKEYWORD--> Add your option here [ ] <!donottest--> do not test (only style check) [ ] <!nomergecommit--> disable merge-commit (no merge from master before tests) [ ] <!nocicache--> disable CI cache (job reuse) [ ] <!batch_0--> 1 [ ] <!batch_1--> 2 [ ] <!batch_2--> 3 [ ] <!batch_3--> 4 </details>
Project: BigchainDB (App Definition and Development / Database)
File: ISSUE_TEMPLATE.md

make a bug report? Then read below about what should go in a bug report. make a feature request or proposal? Then read . ask a question about BigchainDB? Then (our chat room) and ask it there. share your neat idea or realization? Then (our chat room) and share it there. What computer are you on (hardware)? What operating system are you using, including version. e.g. Ubuntu 14.04? Fedora 23? What version of BigchainDB software were you using? Is that the latest version? What, exactly, did you do to get to the point where you got stuck? Describe all the steps so we can get there too. Show screenshots or copy-and-paste text to GitHub. Show what actually happened. Say what you tried to do to resolve the problem. Provide details to convince us that it matters to you. Is it for a school project, a job, a contract with a deadline, a child who needs it for Christmas? We will do our best but please understand that we don't have time to help everyone, especially people who don't care to help us help them. "It doesn't work." is not going to get any reaction from us. We need details. Tip: Use Github code block formatting to make code render pretty in GitHub. To do that, put three backticks followed by a string to set the type of code (e.g. `Python`), then the code, and then end with three backticks. There's more information about in the GitHub help pages.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-version.1.md

% podman-version 1 podman\-version - Display the Podman version information podman version [options] Shows the following information: Remote API Version, Version, Go Version, Git Commit, Build Time, OS, and Architecture. Change output format to "json" or a Go template. | Placeholder | Description | | - | | | .Client ... | Version of local podman | | .Server ... | Version of remote podman | Each of the above fields branch deeper into further subfields such as .Version, .APIVersion, .GoVersion, and more. A sample output of the `version` command: ``` $ podman version Version: 2.0.0 API Version: 1 Go Version: go1.14.2 Git Commit: 4520664f63c3a7f9a80227715359e20069d95542 Built: Tue May 19 10:48:59 2020 OS/Arch: linux/amd64 ``` Filtering out only the version: ``` $ podman version --format '{{.Client.Version}}' 2.0.0 ``` Print usage statement November 2018, Added --format flag by Tomas Tomecek <ttomecek@redhat.com> July 2017, Originally compiled by Urvashi Mohnani <umohnani@redhat.com>
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: erlang-distribution-11352.md

Erlang Distribution links, inet socket, port driver, dist process + tlsconnection & tlssender RabbitMQ Understand the behaviour of Erlang clustering via Erlang Distribution links, inet socket, port driver & dist process. If the Erlang Distribution is using TLS, the state of tlsconnection & tlssender processes will be shown as well. Metrics displayed: Distribution link State: established / connecting / waiting Data buffered Data sent to peer node / s Data received from peer node / s Messages sent to peer node / s Messages received from peer node / s Average inet packet size sent to peer node Average inet packet size received from peer node Port driver Memory used Data buffered Dist process State: waiting / running / garbage_collecting / runnable / suspended / exiting Queued messages Memory used Process reductions / s The last set of metrics are repeated for the `tlsconnection` and `tlssender` processes if the Erlang Distribution is using TLS. Filter by: RabbitMQ Cluster Process type Depends on `rabbitmq-prometheus` plugin, built-in since Learn more about To get it working locally with RabbitMQ in 3 simple steps, follow this