cwielenb/CNCF-Dataset huggingface dataset:
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-qry-select-inline-table.md

layout: global title: Inline Table displayTitle: Inline Table license: | 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. An inline table is a temporary table created using a VALUES clause. ```sql VALUES ( expression [ , ... ] ) [ table_alias ] ``` expression* Specifies a combination of one or more values, operators and SQL functions that results in a value. table_alias* Specifies a temporary name with an optional column name list. Syntax: `[ AS ] tablename [ ( columnname [ , ... ] ) ]` ```sql -- single row, without a table alias SELECT * FROM VALUES ("one", 1); +-+-+ |col1|col2| +-+-+ | one| 1| +-+-+ -- three rows with a table alias SELECT * FROM VALUES ("one", 1), ("two", 2), ("three", null) AS data(a, b); +--+-+ | a| b| +--+-+ | one| 1| | two| 2| |three|null| +--+-+ -- complex types with a table alias SELECT * FROM VALUES ("one", array(0, 1)), ("two", array(2, 3)) AS data(a, b); +++ | a| b| +++ |one|[0, 1]| |two|[2, 3]| +++ ```
Project: LinuxKit (Provisioning / Automation & Configuration)
File: MIGRATION_GUIDE.md

Starting from , the import path will be: "github.com/golang-jwt/jwt/v4" The `/v4` version will be backwards compatible with existing `v3.x.y` tags in this repo, as well as `github.com/dgrijalva/jwt-go`. For most users this should be a drop-in replacement, if you're having troubles migrating, please open an issue. You can replace all occurrences of `github.com/dgrijalva/jwt-go` or `github.com/golang-jwt/jwt` with `github.com/golang-jwt/jwt/v4`, either manually or by using tools such as `sed` or `gofmt`. And then you'd typically run: ``` go get github.com/golang-jwt/jwt/v4 go mod tidy ``` The original migration guide for older releases can be found at https://github.com/dgrijalva/jwt-go/blob/master/MIGRATION_GUIDE.md.
Project: YDB (App Definition and Development / Database)
File: in.md

Checking whether a value is inside of a set of values. It's logically equivalent to a chain of equality comparisons using `OR` but implemented more efficiently. {% note warning "Warning" %} Unlike a similar keyword in Python, in YQL `IN ` DOES NOT searches for a substring inside a string. To search for a substring, use the function or mentioned above. {% endnote %} Immediately after `IN`, you can specify the `COMPACT` modifier. If `COMPACT` is not specified, then `IN` with a subquery is executed as a relevant `JOIN` (`LEFT SEMI` for `IN` and `LEFT ONLY` for `NOT IN`), if possible. Using the `COMPACT` modifier forces the in-memory execution strategy: a hash table is immediately built from the contents of the right `IN` part in-memory, and then the left part is filtered. The `COMPACT` modifier must be used with care. Since the hash table is built in-memory, the query may fail if the right part of `IN` contains many large or different elements. {% if feature_mapreduce %} Since YQL imposes a limit on the query size in bytes (it's about 1Mb), add large lists of values to your query by URLs and use the function. {% endif %} Examples ```yql SELECT column IN (1, 2, 3) FROM my_table; ``` ```yql SELECT * FROM my_table WHERE string_column IN ("a", "b", "c"); ``` ```yql $foo = AsList(1, 2, 3); SELECT 1 IN $foo; ``` ```yql $values = (SELECT column + 1 FROM table); SELECT * FROM my_table WHERE -- filtering by an in-memory hash table for one_table column1 IN COMPACT $values AND -- followed by LEFT ONLY JOIN with other_table column2 NOT IN (SELECT othercolumn FROM othertable); ```
Project: Cyclops (App Definition and Development / Application Definition & Image Build)
File: edit_module.md

Let's edit the values of our module and see what happens! The first step is to click on the Edit button. Try changing the number of replicas or the version of the image (`1.14.2` -> `1.14.1`) to see how the pods are changing. In the image above, we can see that we have some pods running on version `1.14.2` that are waiting to be replaced by pods of version `1.14.1`. In the end, only the `1.14.1` pods will be up and running. When toggling off a module's service, the service won't be automatically deleted. Instead, there will be a warning sign that indicates that the template no longer supports the service, and you can delete it manually if necessary. Now, you can delete the service by clicking the Delete button. If an error pops up referencing [the Kubernetes naming convention](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/), try conforming to the following rules: [x] contain no more than 63 characters [x] contain only lowercase alphanumeric characters or '-' [x] start with an alphanumeric character [x] end with an alphanumeric character
Project: KICS (Provisioning / Security & Compliance)
File: 5b4d4aee-ac94-4810-9611-833636e5916d.md

title: Role With Privilege Escalation By Actions 'iam:CreateAccessKey' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 5b4d4aee-ac94-4810-9611-833636e5916d Query name: Role With Privilege Escalation By Actions 'iam:CreateAccessKey' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Role with privilege escalation by actions 'iam:CreateAccessKey' and Resource set to '*'. For more information see https://rhinosecuritylabs.com/aws/aws-privilege-escalation-methods-mitigation/.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsiamrole" "cosmic" { name = "cosmic" } resource "awsiamrolepolicy" "testinline_policy" { name = "testinlinepolicy" role = awsiamrole.cosmic.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "iam:CreateAccessKey", ] Effect = "Allow" Resource = "*" }, ] }) } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamuser" "cosmic2" { name = "cosmic2" } resource "awsiamuserpolicy" "inlinepolicyruninstances2" { name = "inlinepolicyrun_instances" user = awsiamuser.cosmic2.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "ec2:Describe*", ] Effect = "Allow" Resource = "*" }, ] }) } ```
Project: Checkov (Provisioning / Security & Compliance)
File: languages_issue.md

name: Languages Issue about: Create an issue regarding the frameworks and languages supported by checkov title: '' labels: 'languages' assignees: '' Describe the issue Describe the framework / feature that is missing in a supported framework that you would like to add and explain what the use case is. Example Value Please share an example check / use case that this issue will allow checkov to support.
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: getting-started.md

Download and install the latest version from GitHub below the `.dmg` file. the `.exe` file. the `.appImage`/`.deb`/`.rpm` file for your platform. See on how to run Monokle Desktop from its source-code. Monokle Desktop uses Helm, Kubectl and Kustomize for corresponding preview functionality, and Git for version control. - required for functionality or - required for and functionality - required for Version Control Check out one of our tutorials to get started: to get you started with basic concepts. to help you interact with your cluster(s). to see how you can set up Monokle Desktop to your needs. to give you an idea of how Monokle Desktop can be used for resource validation and correction. to see how the Form editor for ConfigMaps helps you edit resources without having to write any YAML. Have problems? Suggestions? Feature requests? Please join our and let us know - or open an issue on .
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.2.md

layout: release date: 2021-04-08 tag: v0.5.2 General Fixes 404 for invalid id and gostatic lint suggestions @aneeshnema Updates Lint @ramrodo Organizing the start of user guides @leecalcote (#2653) Moved support for pattern command directly under mesheryctl @piyushsingariya (#2654) Fix Relese Drafter @ramrodo (#2655) Replace the install steps to follow the style of Atifact Hub @Aisuko (#2659) Removed usage/help when platform not available @metonymic-smokey (#2660) Fix Pattern Search For Remote Provider @utkarsh-pro (#2663) [mesheryctl] system restart command deletes the pods on meshery namespace and leave the services running @piyushsingariya (#2666) [mesheryctl] Removed context command from experimental @piyushsingariya (#2667) Updated Font Size of Meshery Welcome Screen @adithyaakrishna (#2670) [CI] mesheryctl: ignore publishing of ARM6 + Windows combo @leecalcote (#2673) Minor changes for system restart in logs @piyushsingariya (#2676) [meshery] return 404 when api/experimental/patternfile/id fetched with invalid id @aneeshnema (#2679)
Project: Sonobuoy (Provisioning / Security & Compliance)
File: sonobuoy-query.md

`sonobuoy query` command runs queries against your cluster and helps in debugging by providing useful information about the cluster which helps us to find bugs and fix them before they can cause any severe harm to the cluster. These queries were run from the aggregator pod (made through `sonobuoy run`) in the past. Now you can run them locally without running Sonobuoy or launching pods. Just run sonobuoy query which is much faster and convenient. The logs are generated via logrus (https://github.com/sirupsen/logrus), which contains three parts `time, level, msg`. `msg` provides information about the cluster which helps us to find bugs in our clusters and tackle them. `level` specifies log level. We can specify it via the level flag and valid values are `{panic, fatal, error, warn, info, debug, trace}` and the default is `info`. By default, Sonobuoy uses creates a temporary directory in the current directory to store the query information. You can capture this directory for scripting (its the only value output to stdout) or you can specify your own directory via the `--output` flag. While logging we can also specify sonobuoy config file in order to specify query configuration values. This allows you to tweak things like which namespaces to get pod logs for or what API resources to query. In most cases, the default is appropriate (gets logs for kube-system and queries all non-secret resources).
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.1.5-patch.1.en.md

This change allows to set the minReadySeconds for the StatefulSet. This allows to add a gap between the restarts of each pod by upgrade or restart command. Add `node.brokerpoolsize`, `node.genericpoolsize`, `node.channelcleanupbatch_size` options to EMQX configuration. Tuning these options can significantly improve performance if cluster interconnect network latency is high. Improved retained message publishing latency by consolidating multiple index update operations into a single mnesia activity, leveraging the new APIs introduced in mria 0.6.0. Improve the error reason of the `datetounix_ts` to make more sense. Increase `emqxroutersup` restart intensity. The goal is to tolerate occasional crashes that can happen under relatively normal conditions and don't seem critical to shutdown the whole app (emqx). For example, mria write/delete call delegated from a replicant to a core node by `emqxrouterhelper` may fail, if the core node is being stopped / restarted / not ready. Reintroduce `cacerts` TLS client option as a deprecated option. This fixes issues found when trying to upgrade from 5.1.3 where that option is set in the configuration files or persisted in EMQX Operator settings.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: feat-11935.en.md

Switch to the new `v2` routing store schema by default. New schema improves both subscription and routing performance, especially so for scenarios with concurrent subscriptions to topic filters sharing common wildcard prefixes, at the cost of slightly increased memory usage. This schema also eliminates the need for a separate index, thus inconsistencies in the routing state rarely encountered in previous versions should no longer be possible. If a cluster is rolling upgraded from older version, the cluster will continue to use `v1` store until a full cluster (non-rolling) restart happens. The former schema can still be forced by setting `broker.routing.storage_schema` configuration option to `v1` and conducting full non-rolling cluster restart as well.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_cluster_expose.md

title: kbcli cluster expose Expose a cluster with a new endpoint, the new endpoint can be found by executing 'kbcli cluster describe NAME'. ``` kbcli cluster expose NAME --enable=[true|false] --type=[vpc|internet] [flags] ``` ``` kbcli cluster expose mycluster --type vpc --enable=true kbcli cluster expose mycluster --type internet --enable=true kbcli cluster expose mycluster --type vpc --enable=false ``` ``` --auto-approve Skip interactive approval before exposing the cluster --components strings Component names to this operations --dry-run string[="unchanged"] Must be "client", or "server". If with client strategy, only print the object that would be sent, and no data is actually sent. If with server strategy, submit the server-side request, but no data is persistent. (default "none") --enable string Enable or disable the expose, values can be true or false -h, --help help for expose --name string OpsRequest name. if not specified, it will be randomly generated -o, --output format Prints the output in the specified format. Allowed values: JSON and YAML (default yaml) --ttlSecondsAfterSucceed int Time to live after the OpsRequest succeed --type string Expose type, currently supported types are 'vpc', 'internet' ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - Cluster command.
Project: Couler (Provisioning / Automation & Configuration)
File: couler-step-zoo.md

This document introduces the Couler Step Zoo, which consists of a collection of pre-defined and reusable steps that can be used directly as part of a workflow defined using Couler. Currently, Couler Step Zoo consists of the following pre-defined steps: | Name | Description | API | | - | -- | | | MPI | Submit MPI-based distributed jobs via Kubeflow MPI Operator | `couler.steps.mpi.train()` | | TensorFlow | Submit TensorFlow distributed training jobs via Kubeflow TF Operator | `couler.steps.tensorflow.train()` | | PyTorch | Submit PyTorch distributed training jobs via Kubeflow PyTorch Operator | `couler.steps.pytorch.train()` | | Katib | Submit AutoML experiments (e.g. hyperparameter tuning and neural architecture search) via Kubeflow Katib | `couler.steps.katib.run()` | If you'd like to add a new pre-defined steps to the Couler Step Zoo, please see the following sections for the specific requirements and instructions. In order to provide a consistent and friendly experience to our users, below are the requirements for a new pre-defined step to be eligible for inclusion in Couler Step Zoo: It should be completely implemented using the core . It should expose backend specific configurations instead of hard-coding them. It should have a clear set of dependencies that can be easily installed with sufficient instructions. When possible, proving a minimal set of unit tests and integration tests to make sure the step functions correctly. To add a pre-defined step to the Couler Step Zoo, please follow the instructions below. Make sure the step meets the list of requirements in the above section. Add the step implementation to . The interface would look like the following: ```python def random_code(): import random res = "heads" if random.randint(0, 1) == 0 else "tails" print(res) def run_heads( image="alpine:3.6", command=["sh", "-c", 'echo "it was heads"'], ): result = random_code() couler.when( couler.equal(result, "heads"), lambda: couler.run_step( command=command, image=image, )) ``` Here we implemented a pre-defined step `run_heads()` that could run a specified command such as `["sh", "-c", 'echo "it was heads"']` if `random_code()` returns `"heads"`. Note that the step should be completely implemented using the core in order to work well with different Couler backends. You can find reference step implementations . Provide minimal set of and when possible. Provide necessary user-facing documentation in the API docstring, including documentation on each arguments in the step signature and the system dependencies. Some workflow engines or frameworks provide their own library for distributing the set of reusable steps/tasks/components, for example: Even though it's relatively easier to provide wrappers around the existing reusable libraries, there are some issues with that approach: It's hard to maintain and keep the wrappers up-to-date. It's non-trivial to provide a consistent interface that would work across different backends. This would introduce bad user experience due to feature parity across those reusable libraries implemented for different backends.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.11.4.md

RabbitMQ `3.11.4` is a maintenance release in the `3.11.x` . Please refer to the upgrade section from if upgrading from a version prior to 3.11.0. This release requires Erlang 25. 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 . Import of definition files with many streams is now more efficient. GitHub issue: Lower CPU throughput in clusters with many mostly idle streams. GitHub issue: Streams with `max_age` retention now attempt to reclaim disk space every hour. This is relevant in environments with a lot of mostly inactive streams that set `max_age`. GitHub issue: Quorum queues are now more resilient to WAL log growth with workloads that involve clients that register a consumer and then close the channel or connection without ever consuming any deliveries or cancelling the consumer. GitHub issue: Dead-lettering of a large number of messages to a classic mirrored queues now has lower peak memory footprint. GitHub issue: When a node encouters an invalid `definitions.local.file` on boot, it will refuse to start instead of ignoring the file. GitHub issue: Fixed a type analyzer definition. Contributed by @illotum (AWS). GitHub issue: `rabbitmq-diagnostics checkifnodeisquorum_critical` and `rabbitmq-upgrade awaitonlinequorumplusone` now consider stream (not just quorum queues) replica placement when determining if target node is quorum-critical. GitHub issue: Queue info keys now support more inclusive property names related to (deprecated) classic mirrored queues. For example, `mirror_pids` can now be used instead of `slave_pids`. Contributed by @illotum (AWS). GitHub issue: `rabbitmq-diagnostics memory_breakdown` now executes significantly faster in environments with a large number (say, tens or hundreds of thousands) of quorum queues. Two orders of magnitude faster, in fact. GitHub issue: Definition export in JSON failed on nodes that used `definitions.skipifunchanged`. GitHub issue: Using quorum queue-specific commands on streams now results in clearer error messages. Contributed by @gomoripeti (CloudAMQP). GitHub issue: LDAP server password could end up in the logs in certain types of exceptions. Contributed by @SimonUnge (AWS). GitHub issue: `x-max-age` now can be set by STOMP clients via a header. GitHub issue: `osiris` was upgraded To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.4.tar.xz` instead of the source tarball produced by GitHub.
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: CHANGELOG-v2020.10.27-rc.2.md

title: Changelog | KubeDB description: Changelog menu: docs_{{.version}}: identifier: changelog-kubedb-v2020.10.27-rc.2 name: Changelog-v2020.10.27-rc.2 parent: welcome weight: 20201027 product_name: kubedb menuname: docs{{.version}} sectionmenuid: welcome url: /docs/{{.version}}/welcome/changelog-v2020.10.27-rc.2/ aliases: /docs/{{.version}}/CHANGELOG-v2020.10.27-rc.2/ Prepare for release v0.1.0-rc.2 (#84) Add dnsConfig and dnsPolicy to podTemplate (#636) Prepare for release v0.14.0-rc.2 (#533) Prepare for release v0.14.0-rc.2 (#396) Prepare for release v0.14.0-rc.2 (#176) Prepare for release v0.7.0-rc.2 (#228) Prepare for release v0.7.0-rc.2 (#298) Prepare for release v0.7.0-rc.2 (#288) Prepare for release v0.1.0-rc.2 (#76) Prepare for release v0.14.0-rc.2 (#336) Prepare for release v0.1.0-rc.2 (#120) Prepare for release v0.1.0-rc.2 (#93) Prepare for release v0.14.0-rc.2 (#406) Prepare for release v0.1.0-rc.2 (#102) Prepare for release v0.7.0-rc.2 (#247)
Project: Apollo (Provisioning / Automation & Configuration)
File: golang-sdks-user-guide.md

Project address: Thanks for providing support for the Go Apollo client Project address: Thanks for providing support for the Go Apollo client Project address: Thanks for providing support for the Go Apollo client Project address: Thanks for providing support for the Go Apollo client Project address: Thanks for providing support for the Go Apollo client Project address: Thanks for providing support for the Go Apollo client Project address: Thanks and for providing support for the Go Apollo client Project address: Thanks for providing support for the Go Apollo client Project address: Thanks for providing support for the Go Apollo client