cwielenb/CNCF-Dataset huggingface dataset:
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_fault_list.md

title: kbcli fault list List chaos resources. ``` kbcli fault list [flags] ``` ``` kbcli fault list kbcli fault list --kind kbcli fault list podchaos ``` ``` -h, --help help for list --kind Print chaos resource kind. ``` ``` --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 ``` - Inject faults to pod.
Project: YugabyteDB (App Definition and Development / Database)
File: extension-uuid-ossp.md

title: uuid-ossp extension headerTitle: uuid-ossp extension linkTitle: uuid-ossp description: Using the uuid-ossp extension in YugabyteDB menu: v2.18: identifier: extension-uuid-ossp parent: pg-extensions weight: 20 type: docs The module provides functions to generate universally unique identifiers (UUIDs) using one of several standard algorithms. First, enable the extension: ```sql CREATE EXTENSION "uuid-ossp"; ``` Connect using `ysqlsh` and run the following: ```sql SELECT uuidgeneratev1(), uuidgeneratev4(), uuid_nil(); ``` ```output uuidgeneratev1 | uuidgeneratev4 | uuid_nil --+--+-- 69975ce4-d827-11e9-b860-bf2e5a7e1380 | 088a9b6c-46d8-4276-852b-64908b06a503 | 00000000-0000-0000-0000-000000000000 (1 row) ```
Project: Meshery (Provisioning / Automation & Configuration)
File: gerrit-operator.md

layout: integration title: Gerrit Operator subtitle: Collaborative and visual infrastructure as code for Gerrit Operator image: /assets/img/integrations/gerrit-operator/icons/color/gerrit-operator-color.svg permalink: extensibility/integrations/gerrit-operator docURL: https://docs.meshery.io/extensibility/integrations/gerrit-operator description: integrations-category: App Definition and Development integrations-subcategory: Source Version Control registrant: Artifact Hub components: name: gerrit-group-member colorIcon: assets/img/integrations/gerrit-operator/components/gerrit-group-member/icons/color/gerrit-group-member-color.svg whiteIcon: assets/img/integrations/gerrit-operator/components/gerrit-group-member/icons/white/gerrit-group-member-white.svg description: name: gerrit-group colorIcon: assets/img/integrations/gerrit-operator/components/gerrit-group/icons/color/gerrit-group-color.svg whiteIcon: assets/img/integrations/gerrit-operator/components/gerrit-group/icons/white/gerrit-group-white.svg description: name: gerrit-merge-request colorIcon: assets/img/integrations/gerrit-operator/components/gerrit-merge-request/icons/color/gerrit-merge-request-color.svg whiteIcon: assets/img/integrations/gerrit-operator/components/gerrit-merge-request/icons/white/gerrit-merge-request-white.svg description: name: gerrit-project-access colorIcon: assets/img/integrations/gerrit-operator/components/gerrit-project-access/icons/color/gerrit-project-access-color.svg whiteIcon: assets/img/integrations/gerrit-operator/components/gerrit-project-access/icons/white/gerrit-project-access-white.svg description: name: gerrit-project colorIcon: assets/img/integrations/gerrit-operator/components/gerrit-project/icons/color/gerrit-project-color.svg whiteIcon: assets/img/integrations/gerrit-operator/components/gerrit-project/icons/white/gerrit-project-white.svg description: name: gerrit-replication-config colorIcon: assets/img/integrations/gerrit-operator/components/gerrit-replication-config/icons/color/gerrit-replication-config-color.svg whiteIcon: assets/img/integrations/gerrit-operator/components/gerrit-replication-config/icons/white/gerrit-replication-config-white.svg description: name: gerrit colorIcon: assets/img/integrations/gerrit-operator/components/gerrit/icons/color/gerrit-color.svg whiteIcon: assets/img/integrations/gerrit-operator/components/gerrit/icons/white/gerrit-white.svg description: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: ClickHouse (App Definition and Development / Database)
File: v21.4.5.46-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Disable settings `usehedgedrequests` and `asyncsocketfor_remote` because there is an evidence that it may cause issues. (). Backported in : Server might fail to start if `datatypedefault_nullable` setting is enabled in default profile, it's fixed. Fixes . (). Backported in : QueryAliasVisitor to prefer alias for ASTWithAlias if subquery was optimized to constant. Fixes . Fixes . (). Backported in : Fixed `Not found column` error when selecting from `MaterializeMySQL` with condition on key column. Fixes . (). Backported in : Fixed the behavior when disabling `inputformatwithnamesuse_header ` setting discards all the input with CSVWithNames format. This fixes . (). Backported in : Fixed simple key dictionary from DDL creation if primary key is not first attribute. Fixes . (). Backported in : Fixed very rare (distributed) race condition between creation and removal of ReplicatedMergeTree tables. It might cause exceptions like `node doesn't exist` on attempt to create replicated table. Fixes . (). Backported in : Fix possible crash in case if `unknown packet` was received form remote query (with `asyncsocketfor_remote` enabled). Maybe fixes . (). Backported in : `ORDER BY` with `COLLATE` was not working correctly if the column is in primary key (or is a monotonic function of it) and the setting `optimizereadinorder` is not turned off. This closes . Workaround for older versions: turn the setting `optimizereadinorder` off. (). Backported in : Remove support for `argMin` and `argMax` for single `Tuple` argument. The code was not memory-safe. The feature was added by mistake and it is confusing for people. These functions can be reintroduced under different names later. This fixes and reverts . (). Backported in : Kafka storage may support `arrow` and `arrowstream` format messages. (). Backported in : - Bug fix for `deltaSum` aggregate function in counter reset case ... (). Backported in : Fix bug that does not allow cast from empty array literal, to array with dimensions greater than 1. Closes . (). Backported in : When modify column's default value without datatype, and this column is used as ReplacingMergeTree's parameter like column `b` in the below example, then the server will core dump: ``` CREATE TABLE altertest (a Int32, b DateTime) ENGINE = ReplacingMergeTree(b) ORDER BY a; ALTER TABLE altertest MODIFY COLUMN `b` DEFAULT now(); ``` the sever throw error: ``` 2021.04.22 09:48:00.685317 (). Backported in : Fix `columns` function when multiple joins in select query. Closes . (). Fix logical error in stress tests (). Fix integration tests for Hedged requests (). System dictionaries virtual key column ().
Project: ArangoDB (App Definition and Development / Database)
File: on_outcome_move_construction.md

+++ title = "`static void onoutcomemove_construction(T *, U &&) noexcept`" description = "(>= Outcome v2.2.0) Hook invoked by the converting move constructors of `basic_outcome`." categories = ["observer-policies"] weight = 450 +++ One of the constructor hooks for {{% api "basicoutcome<T, EC, EP, NoValuePolicy>" %}}, generally invoked by the converting move constructors of `basicoutcome` (NOT the standard move constructor). See each constructor's documentation to see which specific hook it invokes. Requires: Always available. Guarantees: Never throws an exception.
Project: CloudARK KubePlus (App Definition and Development / Application Definition & Image Build)
File: Operator-Maturity-Model.md

The Kubernetes Operator pattern has become popular as it allows packaging applications in Kubernetes native manner. An Operator enables creating multiple instances of the application that they are managing. This makes them a key building block in enabling SaaS based delivery of the applications. Today, DevOps teams are using community or in-house developed Kubernetes Operators to offer SaaS on Kubernetes. We have developed this Kubernetes Operator maturity model to evaluate an Operator's readiness for supporting SaaS use-cases. This model has emerged from our experience of working alongside Operator authors as well as enterprises who are adopting Kubernetes and are using Operators. The model consists of a set of guidelines related to consumability, security, and multi-tenancy. The guidelines are available . Operators that satisfy these properties are easy to consume in multi-Operator setups, support multi-tenant workloads and are portable across cloud providers. If you are an Operator author, use this model as a guiding framework when developing your Operator to fit real-life multi-Operator environments. If you are a Platform Engineer/DevOps Engineer, use this model for evaluating Operators for your platform needs.
Project: Konveyor (App Definition and Development / Application Definition & Image Build)
File: releases.md

Podman 1.6.4+ for index image manipulation access to Konveyor Tackle2 repos The Konveyor Tackle2 new release procedure consist of a few steps summarized below: Create a new release branch on Konveyor Tackle2 Operator repo Create and submit PR preparing bundle manifests for the new release branch Once merged, bundle images for new release will be automatically built on Quay.io Build new index images and push new metadata to Quay.io We use semantic versioning convention (semver) for stable releases, release branches should be in the form of v<semver> Create a new release branch in Tackle2 operator repo, for example `v2.0.0` Create a PR for the new release branch Run `tools/cut-release.py --version 2.0.0 --project-path .` Review changes, commmit, and submit the PR against new release branch for review Once the release PR is ready and merged, add it to the index image and push to quay.io `tools/push-release-metadata.py --old-version 1.9.9 --new-version 2.0.0` Create or refresh existing konveyor-tackle catalog source and validate `oc create -f konveyor-operator-catalog.yaml`
Project: KICS (Provisioning / Security & Compliance)
File: 00481784-25aa-4a55-8633-3136dfcf4f37.md

title: Yum Clean All Missing hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 00481784-25aa-4a55-8633-3136dfcf4f37 Query name: Yum Clean All Missing Platform: Dockerfile Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: Need to use 'yum clean all' after using a 'yum install' command to clean package cached data and reduce image size<br> ```dockerfile title="Positive test num. 1 - dockerfile file" hl_lines="12" FROM alpine:3.5 RUN apk add --update py2-pip RUN yum install COPY requirements.txt /usr/src/app/ RUN pip install --no-cache-dir -r /usr/src/app/requirements.txt COPY app.py /usr/src/app/ COPY templates/index.html /usr/src/app/templates/ EXPOSE 5000 CMD ["python", "/usr/src/app/app.py"] FROM alpine:3.4 RUN yum clean all \ yum -y install ``` ```dockerfile title="Negative test num. 1 - dockerfile file" FROM alpine:3.5 RUN apk add --update py2-pip RUN yum install \ yum clean all COPY requirements.txt /usr/src/app/ RUN pip install --no-cache-dir -r /usr/src/app/requirements.txt COPY app.py /usr/src/app/ COPY templates/index.html /usr/src/app/templates/ EXPOSE 5000 CMD ["python", "/usr/src/app/app.py"] FROM alpine:3.4 RUN yum -y install \ yum clean all ``` ```dockerfile title="Negative test num. 2 - dockerfile file" FROM golang:1.16 AS builder WORKDIR /go/src/github.com/foo/href-counter/ RUN go get -d -v golang.org/x/net/html COPY app.go ./ RUN CGO_ENABLED=0 GOOS=linux go build -a -installsuffix cgo -o app . RUN yum clean all \ yum -y install FROM alpine:latest RUN apk --no-cache add ca-certificates WORKDIR /root/ COPY --from=builder /go/src/github.com/foo/href-counter/app ./ CMD ["./app"] RUN useradd -ms /bin/bash patrick USER patrick ```
Project: Meshery (Provisioning / Automation & Configuration)
File: 11-01-2023-23-58-11_26aea5c6.md

timestamp: "2023-11-01 23:57:41 UTC Wed" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "*name" k8s-distro: minikube k8s-version: "v1.22.2" service-mesh: Consul service-mesh-version: "v1.2.2" tests: consul-client: null consul-server: null overall-status: "failing"
Project: StarRocks (App Definition and Development / Database)
File: base64_decode_binary.md

displayed_sidebar: "English" Decodes a Base64-encoded string and return a BINARY. This function is supported from v3.0. ```Haskell base64decodebinary(str); ``` `str`: the string to decode. It must be of the VARCHAR type. Returns a value of the VARBINARY type. If the input is NULL or an invalid Base64 string, NULL is returned. If the input is empty, an error is returned. This function accepts only one string. More than one input string causes an error. ```Plain Text mysql> select hex(base64decodebinary(to_base64("Hello StarRocks"))); ++ | hex(base64decodebinary(to_base64('Hello StarRocks'))) | ++ | 48656C6C6F2053746172526F636B73 | ++ mysql> select base64decodebinary(NULL); +--+ | base64decodebinary(NULL) | +--+ | NULL | +--+ ```
Project: Docker Compose (App Definition and Development / Application Definition & Image Build)
File: compose_config.md

<!MARKERGENSTART--> Parse, resolve and render compose file in canonical format `docker compose config`, `docker compose convert` | Name | Type | Default | Description | |:--|:|:--|:-| | `--dry-run` | | | Execute command in dry run mode | | `--format` | `string` | `yaml` | Format the output. Values: [yaml \| json] | | `--hash` | `string` | | Print the service config hash, one per line. | | `--images` | | | Print the image names, one per line. | | `--no-consistency` | | | Don't check model consistency - warning: may produce invalid Compose output | | `--no-interpolate` | | | Don't interpolate environment variables | | `--no-normalize` | | | Don't normalize compose model | | `--no-path-resolution` | | | Don't resolve file paths | | `-o`, `--output` | `string` | | Save to file (default to stdout) | | `--profiles` | | | Print the profile names, one per line. | | `-q`, `--quiet` | | | Only validate the configuration, don't print anything | | `--resolve-image-digests` | | | Pin image tags to digests | | `--services` | | | Print the service names, one per line. | | `--variables` | | | Print model variables and default values. | | `--volumes` | | | Print the volume names, one per line. | <!MARKERGENEND--> `docker compose config` renders the actual data model to be applied on the Docker Engine. It merges the Compose files set by `-f` flags, resolves variables in the Compose file, and expands short-notation into the canonical format.
Project: Scylla (App Definition and Development / Database)
File: getting-started.md

Before you can start using ScyllaDB Alternator, you will have to have an up and running a ScyllaDB cluster configured to expose the Alternator port. This section will guide you through the steps for setting up the cluster: Download the latest stable ScyllaDB image for Docker, by running `docker pull scylladb/scylla:latest` To run this Docker image, follow the instructions in <https://hub.docker.com/r/scylladb/scylla/>, but add to every `docker run` command a `-p 8000:8000` before the image name and `--alternator-port=8000 --alternator-write-isolation=always` at the end. The "alternator-port" option specifies on which port Scylla will listen for the (unencrypted) DynamoDB API, and the "alternator-write-isolation" chooses whether or not Alternator will use LWT for every write. For example, `docker run --name scylla -d -p 8000:8000 scylladb/scylla:latest --alternator-port=8000 --alternator-write-isolation=always`. The `--alternator-https-port=...` option can also be used to enable Alternator on an encrypted (HTTPS) port. Note that in this case, the files `/etc/scylla/scylla.crt` and `/etc/scylla/scylla.key` must be inserted into the image, containing the SSL certificate and key to use. Follow the instructions on the Enjoy your tic-tac-toe game :-) Run the following commands on your machine, this will install boto3 python library which also contains drivers for DynamoDB: ``` sudo pip install --upgrade boto3 ``` The following is a 3 scripts test that creates a table named usertable writes the famous hello world record to it, and then, reads it back. Put the following create table example script in a python file and run it (changing local host to the address of your docker node if you are using docker): ```python import boto3 dynamodb = boto3.resource('dynamodb',endpoint_url='http://localhost:8000', regionname='None', awsaccesskeyid='None', awssecretaccess_key='None') dynamodb.create_table( AttributeDefinitions=[ { 'AttributeName': 'key', 'AttributeType': 'S' }, ], BillingMode='PAYPERREQUEST', TableName='usertable', KeySchema=[ { 'AttributeName': 'key', 'KeyType': 'HASH' }, ]) ``` Put the following write example script in a python file and run it (changing local host to the address of your docker node if you are using docker): ```python import boto3 dynamodb = boto3.resource('dynamodb',endpoint_url='http://localhost:8000', regionname='None', awsaccesskeyid='None', awssecretaccess_key='None') dynamodb.batchwriteitem(RequestItems={ 'usertable': [ { 'PutRequest': { 'Item': { 'key': 'test', 'x' : {'hello': 'world'} } }, } ] }) ``` Put the following read example script in a python file and run it (changing local host to the address of your docker node if you are using docker): ```python import boto3 dynamodb = boto3.resource('dynamodb',endpoint_url='http://localhost:8000', regionname='None', awsaccesskeyid='None', awssecretaccess_key='None') print(dynamodb.batchgetitem(RequestItems={ 'usertable' : { 'Keys': [{ 'key': 'test' }] } })) ``` You should see the record you inserted in step 2 along with some http info printed to screen.
Project: Salt Project (Provisioning / Automation & Configuration)
File: Product-discover-files-README.md

2016-11-16 mkr This regards ISSUE 1 https://github.com/markuskramerIgitt/salt-windows-msi/issues/1 uninstall removes the configuration file Heat collects files into XML file salt-windows-msi\wix\MinionMSI\dist-amd64.wxs The entry for conf/minion has a Guid: <Component Id="cmpF3CE08C037F32A1C76DF93B02A6ACB79" Directory="dirA7CC33A34163812EEAF3B20CD074A564" Guid="{357ECA3A-24C0-49C5-9964-6CF9504168C4}"> <File Id="filF7B75C18646D054B4C42FBFF0826EBA7" KeyPath="yes" Source="$(var.dist)\conf\minion" /> </Component> Having a Guid means that Wix treats conf/minion as part of the installation On uninstall, WiX removed all parts of the installation, so also conf/minion. This is unwanted behaviour. Approach 1: FAIL exclude the component BuildDistFragment.xsl does that. It filters out ssm.exe, so ssm.exe is not in salt-windows-msi\wix\MinionMSI\dist-amd64.wxs ssm.exe is added manually in services.wxs. FAILURE (I think) because then conf would not be installed. Approach 2: Remove the GUID of the component. http://stackoverflow.com/questions/11848780/use-ends-with-in-xslt-v1-0 set attribute to a value while copying: http://stackoverflow.com/questions/1137078/xslt-do-not-match-certain-attributes/12919373#12919373
Project: KICS (Provisioning / Security & Compliance)
File: 62232513-b16f-4010-83d7-51d0e1d45426.md

title: OSS Bucket Public Access Enabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 62232513-b16f-4010-83d7-51d0e1d45426 Query name: OSS Bucket Public Access Enabled Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: OSS Bucket should have public access disabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="3" resource "alicloudossbucket" "bucketpublicaccess_enabled2" { bucket = "bucket-170309-acl" acl = "public-read" } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="3" resource "alicloudossbucket" "bucketpublicaccess_enabled3" { bucket = "bucket-170309-acl" acl = "public-read-write" } resource "alicloudossbucket" "bucket-logging" { bucket = "bucket-170309-logging" logging { targetbucket = alicloudoss_bucket.bucket-target.id target_prefix = "log/" } } ``` ```tf title="Negative test num. 1 - tf file" resource "alicloudossbucket" "bucketpublicaccess_enabled1" { bucket = "bucket-170309-acl" acl = "private" } ``` ```tf title="Negative test num. 2 - tf file" resource "alicloudossbucket" "bucketpublicaccess_enabled4" { bucket = "bucket-170309-acl" } ```