cwielenb/CNCF-Dataset huggingface dataset:
Project: BigchainDB (App Definition and Development / Database)
File: all-in-one-bigchaindb.md

<! Copyright 2020 Interplanetary Database Association e.V., BigchainDB and IPDB software contributors. SPDX-License-Identifier: (Apache-2.0 AND CC-BY-4.0) Code is Apache-2.0 and docs are CC-BY-4.0 > For those who like using Docker and wish to experiment with BigchainDB in non-production environments, we currently maintain a BigchainDB all-in-one Docker image and a `Dockerfile-all-in-one` that can be used to build an image for `bigchaindb`. This image contains all the services required for a BigchainDB node i.e. BigchainDB Server MongoDB Tendermint Note: NOT for Production Use: This is an single node opinionated image not well suited for a network deployment. This image is to help quick deployment for early adopters, for a more standard approach please refer to one of our deployment guides: . . With Docker installed, you can proceed as follows. In a terminal shell, pull the latest version of the BigchainDB all-in-one Docker image using: ```text $ docker pull bigchaindb/bigchaindb:all-in-one $ docker run \ --detach \ --name bigchaindb \ --publish 9984:9984 \ --publish 9985:9985 \ --publish 27017:27017 \ --publish 26657:26657 \ --volume $HOME/bigchaindb_docker/mongodb/data/db:/data/db \ --volume $HOME/bigchaindb_docker/mongodb/data/configdb:/data/configdb \ --volume $HOME/bigchaindb_docker/tendermint:/tendermint \ bigchaindb/bigchaindb:all-in-one ``` Let's analyze that command: `docker run` tells Docker to run some image `--detach` run the container in the background `publish 9984:9984` map the host port `9984` to the container port `9984` (the BigchainDB API server) `9985` BigchainDB Websocket server `27017` Default port for MongoDB `26657` Tendermint RPC server `--volume "$HOME/bigchaindb_docker/mongodb:/data"` map the host directory `$HOME/bigchaindb_docker/mongodb` to the container directory `/data`; this allows us to have the data persisted on the host machine, you can read more in the [official Docker documentation](https://docs.docker.com/engine/tutorials/dockervolumes) `$HOME/bigchaindb_docker/tendermint:/tendermint` to persist Tendermint data. `bigchaindb/bigchaindb:all-in-one` the image to use. All the options after the container name are passed on to the entrypoint inside the container. ```text $ docker ps | grep bigchaindb ``` Send your first transaction using . Assuming you have Docker installed, you would proceed as follows. In a terminal shell: ```text git clone git@github.com:bigchaindb/bigchaindb.git cd bigchaindb/ ``` Build the Docker image: ```text docker build --file Dockerfile-all-in-one --tag <tag/name:latest> . ``` Now you can use your own image to run BigchainDB all-in-one container.
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_create_operator_class.md

title: CREATE OPERATOR CLASS statement [YSQL] headerTitle: CREATE OPERATOR CLASS linkTitle: CREATE OPERATOR CLASS description: Use the CREATE OPERATOR CLASS statement to create an operator class. menu: v2.18: identifier: ddlcreateoperator_class parent: statements type: docs Use the `CREATE OPERATOR CLASS` statement to create an operator class. {{%ebnf%}} createoperatorclass, operatorclassas {{%/ebnf%}} See the semantics of each option in the . See the semantics of `strategynumber` and `supportnumber` in another page of the [PostgreSQL docs][postgresql-docs-xindex]. Basic example. ```plpgsql yugabyte=# CREATE OPERATOR CLASS myopclass FOR TYPE int4 USING btree AS OPERATOR 1 <, OPERATOR 2 <=; ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: ip6.md

Specify a static IPv6 address for the <<container|pod>>, for example fd46:db93:aa76:ac37::10. This option can only be used if the <<container|pod>> is joined to only a single network - i.e., --network=network-name is used at most once - and if the <<container|pod>> is not joining another container's network namespace via --network=container:_id_. The address must be within the network's IPv6 address pool. To specify multiple static IPv6 addresses per <<container|pod>>, set multiple networks using the --network option with a static IPv6 address specified for each using the `ip6` mode for that option.
Project: Pravega (App Definition and Development / Streaming & Messaging)
File: bindings.md

<!-- Copyright Pravega Authors. 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. --> Pravega supports the following client libraries: () () In addition to the connectors provided by the Pravega organization, open-source contributors have also created connectors for external projects: () connects .NET languages to
Project: Kyverno (Provisioning / Security & Compliance)
File: NOTE.md

All of the following tests in this directory have been copied (for now) to kyverno/policies where they rightfully belong. Once we are executing tests from that repo in this one, we can remove all the cases. add-emptydirsizelimit add-external-secret-prefix add-image-as-env-var add-node-affinity add-pod-priorityclassname add-tolerations add-volume-deployment annotate-base-images inject-env-var-from-image-label k10-minimum-retention replace-ingress-hosts
Project: KubeCarrier (App Definition and Development / Application Definition & Image Build)
File: Zenhub.md

As an Open Source community, it is necessary for our work, communication, and collaboration to be done in the open. GitHub provides a central repository for code, pull requests, issues, and documentation. When applicable, we will use Google Docs for design reviews, proposals, and other working documents. While GitHub issues, milestones, and labels generally work pretty well, the Loodse team has found that product planning requires some additional tooling that GitHub projects do not offer. In our effort to minimize tooling while enabling product management insights, we have decided to use to overlay product and project tracking on top of GitHub. ZenHub is a GitHub application that provides Kanban visualization, Epic tracking, fine-grained prioritization, and more. It's primary backing storage system is existing GitHub issues along with additional metadata stored in ZenHub's database. If you are an user or Developer, you do not need to use ZenHub for your regular workflow (e.g to see open bug reports or feature requests, work on pull requests). However, if you'd like to be able to visualize the high-level project goals and roadmap, you will need to use the free version of ZenHub. ZenHub can be integrated within the GitHub interface using their . In addition, you can use their dedicated web application.
Project: YugabyteDB (App Definition and Development / Database)
File: dcl_drop_policy.md

title: DROP POLICY statement [YSQL] headerTitle: DROP POLICY linkTitle: DROP POLICY description: Use the DROP POLICY statement to remove the specified row level security policy from the table. menu: v2.18: identifier: dcldroppolicy parent: statements type: docs Use the `DROP POLICY` statement to remove the specified row level security policy from the table. Note that if all policies for a table are removed and the table still has `ENABLE ROW LEVEL SECURITY`, then a default deny all policy will be applied for the table. {{%ebnf%}} drop_policy {{%/ebnf%}} Where `name` is the name of the policy to be removed. `table_name` is the name of the table that the policy is on. `CASCADE` / `RESTRICT` don't have any effect because table policies don't have any dependent objects. Drop a policy. ```plpgsql yugabyte=# DROP POLICY p1 ON table_foo; ```
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-mesh-deploy.md

layout: default title: mesheryctl-mesh-deploy permalink: reference/mesheryctl/mesh/deploy redirect_from: reference/mesheryctl/mesh/deploy/ type: reference display-title: "false" language: en command: mesh subcommand: deploy Deploy infrastructure to the Kubernetes cluster Deploy infrastructure to the connected Kubernetes cluster <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl mesh deploy [flags] </div> </pre> Deploy a infrastructure from an interactive on the default namespace <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl mesh deploy </div> </pre> Deploy infrastructure <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl mesh deploy linkerd </div> </pre> Deploy Linkerd mesh on a specific namespace <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl mesh deploy linkerd --namespace linkerd-ns </div> </pre> Deploy Linkerd mesh and wait for it to be deployed <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl mesh deploy linkerd --watch </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for deploy -n, --namespace string Kubernetes namespace to be used for deploying the validation tests and sample workload (default "default") -t, --token string Path to token for authenticating to Meshery API -w, --watch Watch for events and verify operation (in beta testing) </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -v, --verbose verbose output </div> </pre> Usage of mesheryctl mesh deploy Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: logging-in.md

id: logging-in title: Logging into Backstage description: Getting up and running with Backstage and your identity provider Audience: All This guide will provide a quick tutorial on how to log in to your Backstage instance. It should be used as both an introduction to Backstage's authentication system as well as a debugging guide for any issues you may have while logging in. You should have already and completed the Github OAuth app setup defined in . Run your Backstage app with `yarn dev`. Navigate to `http://localhost:3000`. If you're not already logged in, you should see a login screen like this, To login, you should choose the "Github" provider and click the "Sign in" button. This will redirect you to a Github OAuth page. Verify that the scopes mentioned on that page match the setup you did in . Once you click "Confirm", you will be brought back to the Backstage interface and signed in! If you are already logged in, you will be automatically brought to your Backstage instance. Once you've logged in, find the "Settings" item in the navigation bar to the left. Click it and you will see your profile. If you see your profile picture and name from Github here, congratulations! You've successfully set up a Github authentication integration. <!-- Would like to have more FAQs here for help instead of funneling to Discord --> If you don't see your profile picture and name, check that you followed all of the steps in . If you have, search for similar issues on .
Project: StarRocks (App Definition and Development / Database)
File: char_length.md

displayed_sidebar: "English" This function returns the length of a string. For multi-byte characters, it returns the number of characters. It currently only supports utf8 coding. Note: This function is also named as character_length. ```Haskell INT char_length(VARCHAR str) ``` ```Plain Text MySQL > select char_length("abc"); +--+ | char_length('abc') | +--+ | 3 | +--+ ``` CHARLENGTH, CHARACTERLENGTH
Project: Flink (App Definition and Development / Streaming & Messaging)
File: windows.md

title: "Windows" weight: 2 type: docs aliases: /docs/dev/python/datastream/operators/windows.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. --> <meta http-equiv="refresh" content="0; url={{< ref "docs/dev/datastream/operators/windows" >}} "/>
Project: YugabyteDB (App Definition and Development / Database)
File: yba_register.md

Register a YugabyteDB Anywhere customer using yba cli Register a YugabyteDB Anywhere customer using yba cli. If non-interactive mode is set, provide the host, name, email, password and environment using flags. ``` yba register [flags] ``` ``` yba register -f -n <name> -e <email> -p <password> -H <host> ``` ``` -n, --name string [Optional] Name of the user. Required for non-interactive usage -e, --email string [Optional] Email for the user. Required for non-interactive usage -p, --password string [Optional] Password for the user. Password must contain at least 8 characters and at least 1 digit , 1 capital , 1 lowercase and 1 of the !@#$^&* (special) characters. Required for non-interactive usage. Use single quotes ('') to provide values with special characters. --environment string [Optional] Environment of the installation. Allowed values: dev, demo, stage, prod. (default "dev") -f, --force [Optional] Bypass the prompt for non-interactive usage. -h, --help help for register ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - yba - Command line tools to manage your YugabyteDB Anywhere (Self-managed Database-as-a-Service) resources.
Project: Tetragon (Provisioning / Security & Compliance)
File: network-observability.md

title: "Network observability" weight: 3 description: "Monitor TCP connect using kprobe hooks" To view TCP connect events, apply the example TCP connect `TracingPolicy`: ```bash kubectl apply -f https://raw.githubusercontent.com/cilium/tetragon/main/examples/tracingpolicy/tcp-connect.yaml ``` To start monitoring events in the `xwing` pod run the Tetragon CLI: ```bash kubectl logs -n kube-system -l app.kubernetes.io/name=tetragon -c export-stdout -f | tetra getevents -o compact --namespace default --pod xwing ``` In another terminal, start generate a TCP connection. Here we use curl. ```bash kubectl exec -it xwing -- curl http://cilium.io ``` The output in the first terminal will capture the new connect and write, ```bash process default/xwing /usr/bin/curl http://cilium.io connect default/xwing /usr/bin/curl tcp 10.244.0.6:34965 -> 104.198.14.52:80 sendmsg default/xwing /usr/bin/curl tcp 10.244.0.6:34965 -> 104.198.14.52:80 bytes 73 close default/xwing /usr/bin/curl tcp 10.244.0.6:34965 -> 104.198.14.52:80 exit default/xwing /usr/bin/curl http://cilium.io 0 ``` To disable the TracingPolicy run: ```bash kubectl delete -f https://raw.githubusercontent.com/cilium/tetragon/main/examples/tracingpolicy/tcp-connect.yaml ```
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: CHANGELOG-v2021.03.17.md

title: Changelog | KubeDB description: Changelog menu: docs_{{.version}}: identifier: changelog-kubedb-v2021.03.17 name: Changelog-v2021.03.17 parent: welcome weight: 20210317 product_name: kubedb menuname: docs{{.version}} sectionmenuid: welcome url: /docs/{{.version}}/welcome/changelog-v2021.03.17/ aliases: /docs/{{.version}}/CHANGELOG-v2021.03.17/ Prepare for release v0.2.1 (#19) Prepare for release v0.4.1 (#158) Fix Various Issues (#156) Add individual certificate issuer (#155) Add secretName to Elasticsearch userSpec (#725) Add printable Distribution field for DB Versions (#723) Add default organizational unit (#726) Update for release Stash@v2021.03.11 (#724) Prepare for release v0.17.1 (#596) Update for release Stash@v2021.03.11 (#595) Prepare for release v0.17.1 (#486) Use user provided secret for Elasticsearch internal users (#485) Update for release Stash@v2021.03.11 (#484) Prepare for release v0.17.1 (#289) Default enable mutating webhook for KubeDB Enterprise (#288) Add Elasticsearch and Redis OpsRequest Validator (#287) Update perconaxtradb task names Add MongoDBOpsRequest Validator (#286) Update kubedb chart values (#285) Allow overriding official registry in catalog (#284) Update stash task names (#282) Pass registry parameter from unified chart (#283) Use stash catalog from installer repo (#281) Remove namespace from db version crs (#280) Prepare for release v0.1.1 (#58) Update for release Stash@v2021.03.11 (#57) Prepare for release v0.10.1 (#292) Prepare for release v0.10.1 (#385) Update for release Stash@v2021.03.11 (#383) Prepare for release v0.10.1 (#378) Update for release Stash@v2021.03.11 (#376) Prepare for release v0.17.1 (#400) Prepare for release v0.4.1 (#192) Update for release Stash@v2021.03.11 (#191) Prepare for release v0.1.1 (#14) Prepare for release v0.4.1 (#153) Prepare for release v0.17.1 (#483) Update for release Stash@v2021.03.11 (#482) Prepare for release v0.4.1 (#171) Update for release Stash@v2021.03.11 (#170) Prepare for release v0.10.1 (#315) Prepare for release v0.4.1 (#133) Prepare for release v0.2.1 (#111) Don't explicitly set RestoreSession labels (#110)
Project: YugabyteDB (App Definition and Development / Database)
File: type_int.md

title: Integer and counter data types [YCQL] headerTitle: Integer and counter data types linkTitle: Integer and counter description: There are several different data types for integers of different value ranges. Integers can be set, inserted, incremented, and decremented. menu: preview: parent: api-cassandra weight: 1420 aliases: /preview/api/cassandra/type_int /preview/api/ycql/type_int type: docs There are several different data types for integers of different value ranges. Integers can be set, inserted, incremented, and decremented while `COUNTER` can only be incremented or decremented. We've extend Apache Cassandra to support increment and decrement operators for integer data types. Datatype | Min | Max | |--|--| `TINYINT` | -128 | 127 | `SMALLINT` | -32,768 | 32,767 | `INT` or `INTEGER` | -2,147,483,648 | 2,147,483,647 | `BIGINT` | 9,223,372,036,854,775,808 | 9,223,372,036,854,775,807 | `COUNTER` | 9,223,372,036,854,775,808 | 9,223,372,036,854,775,807 | `VARINT` | unbounded | unbounded | The following keywords are used to specify a column of type integer for different constraints including its value ranges. ``` type_specification ::= TINYINT | SMALLINT | INT | INTEGER | BIGINT | VARINT | COUNTER integer_literal ::= [ + | - ] digit [ { digit | , } ... ] ``` Columns of type `TINYINT`, `SMALLINT`, `INT`, `INTEGER`, `BIGINT` or `VARINT` can be part of the `PRIMARY KEY`. Values of different integer data types are comparable and convertible to one another. Values of integer data types are convertible but not comparable to floating point number. Values of floating point data types are not convertible to integers. `COUNTER` is an alias of `BIGINT` but has additional constraints. Columns of type `COUNTER` cannot be part of the`PRIMARY KEY`. If a column is of type `COUNTER`, all non-primary-key columns must also be of type `COUNTER`. Column of type `COUNTER` cannot be set or inserted. They must be incremented or decremented. If a column of type `COUNTER` is NULL, its value is replaced with zero when incrementing or decrementing. ```sql example> CREATE TABLE items(id INT PRIMARY KEY, item_count BIGINT); ``` ```sql example> INSERT INTO items(id, item_count) VALUES(1, 1); ``` ```sql example> INSERT INTO items(id, item_count) VALUES(2, 2); ``` ```sql example> UPDATE items SET item_count = 5 WHERE id = 1; ``` ```sql example> UPDATE items SET itemcount = itemcount + 1 WHERE id = 2; ``` ```sql example> SELECT * FROM items; ``` ``` id | item_count -+ 2 | 3 1 | 5 ``` ```sql example> CREATE TABLE itemcounters(id INT PRIMARY KEY, itemcounter COUNTER); ``` For counter type, null values are treated as 0. ```sql example> UPDATE itemcounters SET itemcounter = item_counter + 1 WHERE id = 1; ``` ```sql example> SELECT * FROM item_counters; ``` ``` id | item_counter -+-- 1 | 1 ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_spanner_database.md

+++ title = "googlespannerdatabase resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlespannerdatabase" identifier = "inspec/resources/gcp/googlespannerdatabase.md googlespannerdatabase resource" parent = "inspec/resources/gcp" +++ A `googlespannerdatabase` is used to test a Google Database resource ```ruby describe googlespannerdatabase(project: 'chef-gcp-inspec', instance: 'spinstance', name: 'spdatabase') do it { should exist } its('name') { should match 'spdatabase' } end ``` Properties that can be accessed from the `googlespannerdatabase` resource: `name` : A unique identifier for the database, which cannot be changed after the instance is created. Values are of the form \*[a-z0-9]. `instance` : The instance to create the database on. Ensure the is enabled for the current project.
Project: KICS (Provisioning / Security & Compliance)
File: e592a0c5-5bdb-414c-9066-5dba7cdea370.md

title: IAM Access Analyzer Not Enabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: e592a0c5-5bdb-414c-9066-5dba7cdea370 Query name: IAM Access Analyzer Not Enabled Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsorganizationsorganization" "example2" { awsserviceaccess_principals = ["access-analyzer.amazonaws.com"] } ``` ```tf title="Negative test num. 1 - tf file" /*resource "awsorganizationsorganization" "example" { awsserviceaccess_principals = ["access-analyzer.amazonaws.com"] } resource "awsaccessanalyzeranalyzer" "examplee" { dependson = [awsorganizations_organization.example] analyzer_name = "example" type = "ORGANIZATION" } */ ```