cwielenb/CNCF-Dataset huggingface dataset:
Project: Meshery (Provisioning / Automation & Configuration)
File: kubedb-catalog.md

layout: integration title: Kubedb Catalog subtitle: Collaborative and visual infrastructure as code for Kubedb Catalog image: /assets/img/integrations/kubedb-catalog/icons/color/kubedb-catalog-color.svg permalink: extensibility/integrations/kubedb-catalog docURL: https://docs.meshery.io/extensibility/integrations/kubedb-catalog description: integrations-category: App Definition and Development integrations-subcategory: Database registrant: Artifact Hub components: featureList: [ "KubeDB simplifies many of the difficult or tedious management tasks of running a production grade databases on private and public clouds. Maintain one stack for all your stateless and stateful applications and simplify the operational complexity.", "Standard Kubernetes is all you need. If you can run Kubernetes, you can provision and manage databases using KubeDB. Use standard Kubernetes CLI and API to provision and manage databases.", "KubeDB uses Persistent Volume Claims (PVC) to dynamically provision disks for database instances. Using appropriately defined StorageClasses, KubeDB provisioned database instances are designed to scale from small development workloads up to performance-intensive workloads on private and public cloud environments." ] 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: StarRocks (App Definition and Development / Database)
File: from_unixtime.md

displayed_sidebar: "English" Converts a UNIX timestamp into the required time format. The default format is `yyyy-MM-dd HH:mm:ss`. It also supports the formats in . Currently, `string_format` supports the following formats: ```plain text %Y: Year e.g.: 2014, 1900 %m: Month e.g.: 12, 09 %d: Day e.g.: 11, 01 %H: Hour e.g.: 23, 01, 12 %i: Minute e.g.: 05, 11 %s: Second e.g.: 59, 01 ``` Other formats are invalid and NULL will be returned. ```Haskell VARCHAR fromunixtime(BIGINT unixtimestamp[, VARCHAR string_format]) ``` `unix_timestamp`: the UNIX timestamp you want to convert. It must be of the BIGINT type. If the specified timestamp is less than 0 or larger than 253402243199, NULL will be returned. That is, the range for timestamp is `1970-01-01 00:00:00` to `9999-12-30 11:59:59`(varies because of timezone). `string_format`: the required time format. Returns a DATETIME or DATE value of the VARCHAR type. If `string_format` specifies the DATE format, a DATE value of the VARCHAR type is returned. If the timestamp exceeds the value range or if `string_format` is invalid, NULL will be returned. ```plain text MySQL > select from_unixtime(1196440219); ++ | from_unixtime(1196440219) | ++ | 2007-12-01 00:30:19 | ++ MySQL > select from_unixtime(1196440219, 'yyyy-MM-dd HH:mm:ss'); +--+ | from_unixtime(1196440219, 'yyyy-MM-dd HH:mm:ss') | +--+ | 2007-12-01 00:30:19 | +--+ MySQL > select from_unixtime(1196440219, '%Y-%m-%d'); +--+ | from_unixtime(1196440219, '%Y-%m-%d') | +--+ | 2007-12-01 | +--+ MySQL > select from_unixtime(1196440219, '%Y-%m-%d %H:%i:%s'); +--+ | from_unixtime(1196440219, '%Y-%m-%d %H:%i:%s') | +--+ | 2007-12-01 00:30:19 | +--+ ``` FROM_UNIXTIME,FROM,UNIXTIME
Project: StarRocks (App Definition and Development / Database)
File: get_json_int.md

displayed_sidebar: "English" This function analyzes and gets the integer value from a specified path in json string. json_path must start with `$` and use `.` as the path separator. If the path includes `.`, it could be circled by `"` and `"`. `[ ]` is used as the array subscripts which start from 0. Content in the path should not contain `"` , `[` and `]`. If the format of jsonstring or jsonpath is wrong, this function will return NULL. ```Haskell BIGINT getjsonint(VARCHAR jsonstr, VARCHAR jsonpath) ``` Get the value whose key is "k1" ```Plain Text MySQL > SELECT getjsonint('{"k1":1, "k2":"2"}', "$.k1"); +--+ | getjsonint('{"k1":1, "k2":"2"}', '$.k1') | +--+ | 1 | +--+ ``` Get the second element in the array whose key is "my.key" ```Plain Text MySQL > SELECT getjsonint('{"k1":"v1", "my.key":[1, 2, 3]}', '$."my.key"[1]'); ++ | getjsonint('{"k1":"v1", "my.key":[1, 2, 3]}', '$."my.key"[1]') | ++ | 2 | ++ ``` Get the first element in the array whose path is k1.key -> k2. ```Plain Text MySQL > SELECT getjsonint('{"k1.key":{"k2":[1, 2]}}', '$."k1.key".k2[0]'); +--+ | getjsonint('{"k1.key":{"k2":[1, 2]}}', '$."k1.key".k2[0]') | +--+ | 1 | +--+ ``` GETJSONINT,GET,JSON,INT
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: regocpp.md

title: regocpp software: regopy regorust inventors: microsoft tutorials: https://microsoft.github.io/rego-cpp/ code: https://github.com/microsoft/rego-cpp The rego-cpp project is a Rego compiler and runtime implemented in C++. As such, it provides the ability to integrate Rego natively into a wider range of languages. We currrently support C, C++, Rust, and Python, and are largely compatible with v0.55.0 of the language.
Project: StarRocks (App Definition and Development / Database)
File: round.md

displayed_sidebar: "English" Rounds a number to a specified number of digits. If `n` is not specified, `x` is rounded to the nearest integer. If `n` is specified, `x` is rounded to `n` decimal places. If `n` is negative, `x` is rounded to the left of the decimal point. If overflow occurs, an error is returned. ```Haskell ROUND(x [,n]); ``` `x`: the number to be rounded. It supports the DOUBLE and DECIMAL128 data types. `n`: the number of decimal places to round the number to. It supports the INT data type. This parameter is optional. If only `x` is specified, the return value is of the following data type: ["DECIMAL128"] -> "DECIMAL128" ["DOUBLE"] -> "BIGINT" If both `x` and `n` are specified, the return value is of the following data type: ["DECIMAL128", "INT"] -> "DECIMAL128" ["DOUBLE", "INT"] -> "DOUBLE" ```Plain mysql> select round(3.14); +-+ | round(3.14) | +-+ | 3 | +-+ mysql> select round(3.14,1); +-+ | round(3.14, 1) | +-+ | 3.1 | +-+ mysql> select round(13.14,-1); ++ | round(13.14, -1) | ++ | 10 | ++ mysql> select round(122.14,-1); +-+ | round(122.14, -1) | +-+ | 120 | +-+ mysql> select round(122.14,-2); +-+ | round(122.14, -2) | +-+ | 100 | +-+ mysql> select round(122.14,-3); +-+ | round(122.14, -3) | +-+ | 0 | +-+ ```
Project: ArangoDB (App Definition and Development / Database)
File: assume_error_lvalue_const.md

+++ title = "`const errortype &assumeerror() const & noexcept`" description = "Narrow contract const lvalue reference observer of the stored error. Constexpr propagating, never throws." categories = ["observers"] weight = 710 +++ Narrow contract const lvalue reference observer of the stored error. `NoValuePolicy::narrowerrorcheck()` is first invoked, then the reference to the error is returned. As a valid default constructed error is always present, no undefined behaviour occurs unless `NoValuePolicy::narrowerrorcheck()` does that. Note that if `error_type` is `void`, only a `const` overload returning `void` is present. Requires: Always available. Complexity: Depends on `NoValuePolicy::narrowerrorcheck()`. Guarantees: An exception is never thrown.
Project: KICS (Provisioning / Security & Compliance)
File: documentation.md

There are multiple ways to get KICS up and running: KICS is available as a <a href="https://hub.docker.com/r/checkmarx/kics" target="_blank">Docker image</a> and can be used as follows: To scan a directory/file on your host you have to mount it as a volume to the container and specify the path on the container filesystem with the -p KICS parameter (see Scan Command Options section below) ```shell docker pull checkmarx/kics:latest docker run -t -v "{pathtohostfolderto_scan}":/path checkmarx/kics scan -p /path -o "/path/" ``` You can see the list of available tags in UBI Based Images When using based image, the KICS process will run under the `kics` user and `kics` group with default UID=1000 and GID=1000, when using bind mount to share host files with the container, the UID and GID can be overriden to match current user with the `-u` flag that overrides the username:group or UID:GID. e.g: ```sh docker run -it -u $UID:$GID -v $PWD:/path checkmarx/kics:ubi8 scan -p /path/assets/queries/dockerfile -o /path -v ``` Another option is providing build arguments e.g: `--build-arg UID=999 --build-arg GID=999 --build-arg KUSER=myuser --build-arg KUSER=mygroup` Download and install Go 1.16 or higher from <a href="https://golang.org/dl/" target="_blank">https://golang.org/dl/</a>. Clone the repository: ```sh git clone https://github.com/Checkmarx/kics.git ``` Build the binaries: ```sh cd kics go mod vendor make build ``` or ```sh cd kics go mod vendor LINUX/MAC: go build -o ./bin/kics cmd/console/main.go WINDOWS: go build -o ./bin/kics.exe cmd/console/main.go (make sure to create the bin folder) ``` Kick a scan! ```sh ./bin/kics scan -p '<path-of-your-project-to-scan>' --report-formats json -o ./results ``` KICS is available on Checkmarx only for versions until 1.5.1. It can be used as follows: ``` brew install Checkmarx/tap/kics ``` To use KICS default queries add the KICSQUERIESPATH environmental variable to your shell profile, e.g: ``` echo 'export KICSQUERIESPATH=/usr/local/opt/kics/share/kics/assets/queries' >> ~/.zshrc ``` You can provide your own path to the queries directory with `-q` CLI option (see CLI Options section below), otherwise the default directory will be used The default ./assets/queries is built-in in the image. You can use this to provide a path to your own custom queries. Check to learn how to define your own queries. Since the Password and Secrets mechanism uses generic regexes, we advise you to tweak the rules of the secret to your context. Please, see the to know how you can use your own rules. Note: KICS does not execute scan by default as of . Note: KICS deprecated the availability of binaries in the GitHub releases assets as of , it is advised to update all systems (pipelines, integrations, etc.) to use the . so you can have a better KICS experience. to see what you can do with KICS. to see which files you can scan with KICS. for better understanding how KICS works. to learn how to create your own custom queries. and quickly fix the issues detected. if you want to go the extra mile.
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_enter.md

title: "Command - devspace enter" sidebar_label: devspace enter Open a shell to a container ``` devspace enter [flags] ``` ``` Execute a command or start a new terminal in your devspace: devspace enter devspace enter --pick # Select pod to enter devspace enter bash devspace enter -c my-container devspace enter bash -n my-namespace devspace enter bash -l release=test devspace enter bash --image-selector nginx:latest devspace enter bash --image-selector "${runtime.images.app.image}:${runtime.images.app.tag}" ``` ``` -c, --container string Container name within pod where to execute command -h, --help help for enter --image string Image is the config name of an image to select in the devspace config (e.g. 'default'), it is NOT a docker image like myuser/myimage --image-selector string The image to search a pod for (e.g. nginx, nginx:latest, ${runtime.images.app}, nginx:${runtime.images.app.tag}) -l, --label-selector string Comma separated key=value selector list (e.g. release=test) --pick Select a pod / container if multiple are found (default true) --pod string Pod to open a shell to --reconnect Will reconnect the terminal if an unexpected return code is encountered --wait Wait for the pod(s) to start if they are not running --workdir string The working directory where to open the terminal or execute the command ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --disable-profile-activation If true will ignore all profile activations --inactivity-timeout int Minutes the current user is inactive (no mouse or keyboard interaction) until DevSpace will exit automatically. 0 to disable. Only supported on windows and mac operating systems (default 180) --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile strings The DevSpace profiles to apply. Multiple profiles are applied in the order they are specified --profile-parent strings One or more profiles that should be applied before the specified profile (e.g. devspace dev --profile-parent=base1 --profile-parent=base2 --profile=my-profile) --profile-refresh If true will pull and re-download profile parent sources --restore-vars If true will restore the variables from kubernetes before loading the config --save-vars If true will save the variables to kubernetes after loading the config --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context DEPRECATED: Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) --vars-secret string The secret to restore/save the variables from/to, if --restore-vars or --save-vars is enabled (default "devspace-vars") ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.10.20.md

RabbitMQ `3.10.20` is a maintenance release in the `3.10.x` . This series . Please refer to the upgrade section from if upgrading from a version prior to 3.10.0. This release requires Erlang 24.3 and supports Erlang 25. has more details on Erlang version requirements for RabbitMQ. Erlang 23 and 24 versions older than 24.3 have reached . This release of RabbitMQ or later versions. Nodes will fail to start on older Erlang releases. Erlang 25.3 is recommended: it offers much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation. Release notes can be found on GitHub at . Boot time import of definitions from a `conf.d`-style directory failed unless `definitions.skipifunchanged` was set to `true`, for example, like in this `rabbitmq.conf`: ``` ini definitions.skipifunchanged = false definitions.importbackend = localfilesystem definitions.local.path = /path/to/RabbitMQ/definitions/conf.d/ ``` GitHub issue: Improved resiliency of dead-lettering. GitHib issue: `rabbitmq-streams help [command]` now looks up stream commands correctly. Contributed by @markus812498 (CloudAMQP). GitHub issue: HTTP API will now respond with a `405 Method Not Allowed` instead of a 500 when an unsupported method is used by the client. Contributed by @gomoripeti (CloudAMQP). GitHub issue: Node key TTL setting was unintentionally ignored. GitHub issues: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.10.20.tar.xz` instead of the source tarball produced by GitHub.
Project: ShardingSphere (App Definition and Development / Database)
File: check-migration.en.md

+++ title = "CHECK MIGRATION " weight = 10 +++ The `CHECK MIGRATION LIST` syntax is used to check data consistancy in migration job. {{< tabs >}} {{% tab name="Grammar" %}} ```sql ShowMigrationList ::= 'CHECK' 'MIGRATION' migrationJobId 'BY' 'TYPE' '(' 'NAME' '=' migrationCheckAlgorithmType ')' migrationJobId ::= string migrationCheckAlgorithmType ::= string ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} `migrationJobId` needs to be obtained through syntax query `migrationCheckAlgorithmType` needs to be obtained through syntax query check data consistancy in migration job ```sql CHECK MIGRATION 'j01016e501b498ed1bdb2c373a2e85e2529a6' BY TYPE (NAME='CRC32_MATCH'); ``` `CHECK`, `MIGRATION`, `BY`, `TYPE`
Project: Kyverno (Provisioning / Security & Compliance)
File: kyverno_jp_parse.md

Parses jmespath expression and shows corresponding AST. Parses jmespath expression and shows corresponding AST. For more information visit https://kyverno.io/docs/kyverno-cli/#jp ``` kyverno jp parse [-f file|expression]... [flags] ``` ``` kyverno jp parse 'request.object.metadata.name | truncate(@, `9`)' kyverno jp parse -f my-file kyverno jp parse kyverno jp parse -f my-file1 -f my-file-2 'request.object.metadata.name | truncate(@, `9`)' cat my-file | kyverno jp parse ``` ``` -f, --file strings Read input from a JSON or YAML file instead of stdin -h, --help help for parse ``` ``` --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 ``` - Provides a command-line interface to JMESPath, enhanced with Kyverno specific custom functions.
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_list_providers.md

title: "Command - devspace list providers" sidebar_label: devspace list providers Lists all providers ``` devspace list providers [flags] ``` ``` Lists the providers that exist ``` ``` -h, --help help for providers ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile string The devspace profile to use (if there is any) --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) ```
Project: FOSSA (Provisioning / Security & Compliance)
File: telemetry.md

FOSSA CLI collects anonymous feature usage information, observed errors and warnings, and performance diagnostic information to help improve the experience for everyone. Getting a better understanding of usage patterns, the impact of exceptions, and crash reports, helps our team to better prioritize work and ultimately deliver a better user experience. CLI telemetry collects the following data: Fatal and non-fatal errors and warnings Configurations, and command-line arguments used Anonymous system information (operating system, and architecture) Feature usage data CLI telemetry does not collect personally identifiable information or metadata about source code. CLI telemetry data is collected at the provided endpoint in configuration (with --endpoint). CLI telemetry data is validated and processed for our logging system. You can view collected CLI telemetry data by running cli with environment variable `FOSSATELEMETRYDEBUG=1`, with scope of `FOSSATELEMETRYSCOPE=full`. This will generate `fossa.telemetry.json` file in your current working directory, and will not send any telemetry data to server. ```bash FOSSATELEMETRYDEBUG=1 FOSSATELEMETRYSCOPE=full fossa analyze sandbox ``` You can disable telemetry with any of the following options, (1) Setting environment variable ``` $ FOSSATELEMETRYSCOPE=off fossa analyze ``` (2) Using command line flag ``` $ fossa analyze --with-telemetry-scope=off ``` (3) Using the configuration file: ``` version: 3 telemetry: scope: off ``` Also, we do not collect telemetry when `--output` is used with analyze command. CLI sends telemetry data to the endpoint specified in the FOSSA CLI command. We never receive telemetry data collected from your endpoint. You can inspect collected telemetry data on your endpoint from your on-prem FOSSA database instance.
Project: YugabyteDB (App Definition and Development / Database)
File: download-date-time-utilities.md

title: Download date-time-utilities.zip [YSQL] headerTitle: Download and install the date-time utilities code linkTitle: Download & install the date-time utilities description: Explains how to download and install the code corpus on which many of the code-examples in the dare-time major section depend. [YSQL] menu: v2.18: identifier: download-date-time-utilities parent: api-ysql-datatypes-datetime weight: 140 type: docs {{< tip title="Download the '.zip' file and install the reusable code that the 'date-time' major section describes and uses." >}} Each of these five sections describes reusable code that you might find useful: Moreover, some of the code examples depend on some of this code. Yugabyte recommends therefore that you download and install the entire kit into the database that you use to support your study of the date-time data types. With this code installed, all the code examples on every page listed in the will run without error provided only that, in the general case, you run them in the order in which a particular page presents them. to any convenient directory and unzip it. It creates a small directory hierarchy. You'll find README.pdf at the top level. It describes the rest of the content and tells you simply to start the master script 0.sql at the ysqlsh prompt (or at the psql prompt). You can run it time and again. It will always finish silently. {{< /tip >}}
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: CONTRIBUTING.md

Welcome to Kubernetes. We are excited about the prospect of you joining our ! The Kubernetes community abides by the CNCF . Here is an excerpt: As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities. We have full documentation on how to get started contributing here: <! If your repo has certain guidelines for contribution, put them here ahead of the general k8s resources --> Kubernetes projects require that you sign a Contributor License Agreement (CLA) before we can accept your pull requests - Main contributor documentation, or you can just jump directly to the - Common resources for existing developers - We have a diverse set of mentorship programs available that are always looking for volunteers! <! Custom Information - if you're copying this template for the first time you can add custom content here, for example: - Replace `kubernetes-users` with your slack channel string, this will send users directly to your channel. -->