cwielenb/CNCF-Dataset huggingface dataset:
Project: Harbor (Provisioning / Container Registry)
File: 2-05-DB-user-delete-image.md

Test 2-05 - User Delete Images (DB Mode) ======= To verify that a non-admin user can delete images when users are managed locally by Harbor (DB mode). User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against a local database. ( auth_mode is set to db_auth* .) The user data is stored in a local database. A linux host with Docker CLI installed (Docker client). At least a non-admin user. NOTE: In below test, user A is non-admin user. User A and project X, Y should be replaced by longer and meaningful names. Log in to UI as user A (non-admin). Create a project X so that the user has the project admin role. On a Docker client, log in as User A and run `docker push` to push an image to the project X, e.g. projectX/myimage:v1. Push a second image with different tag to project X, e.g. projectX/myimage:v2 . Push an image with different name to project X, e.g. projectX/newimage:v1 . Run `docker pull` to verify images can be pulled successfully. In UI, delete the three images one by one. On a Docker client, log in as User A and run `docker pull` to pull the three deleted images of project X. In UI, delete project X. Run `docker pull` to pull the three deleted images of the project X. Step 7, images should be deleted successfully. Step 9, project X should be deleted successfully. Step 8,10, docker client should report error message. None
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_bench_tpcc_cleanup.md

title: kbcli bench tpcc cleanup Cleanup data for TPCC. ``` kbcli bench tpcc cleanup [flags] ``` ``` -h, --help help for cleanup ``` ``` --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 --check-all Run all consistency checks --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 --count int Total execution count, 0 means infinite -D, --db string Database name (default "kb_test") --disable-compression If true, opt-out of response compression for all requests to the server -d, --driver string Database driver: mysql (default "mysql") --dropdata Cleanup data before prepare -H, --host string Database host (default "127.0.0.1") --ignore-error Ignore error when running workload --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --interval duration Output interval time (default 5s) --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version --max-procs int runtime.GOMAXPROCS -n, --namespace string If present, the namespace scope for this CLI request --partition-type int Partition type (1 - HASH, 2 - RANGE, 3 - LIST (like HASH), 4 - LIST (like RANGE) (default 1) --parts int Number to partition warehouses (default 1) -p, --password string Database password (default "sakila") -P, --port int Database port (default 3306) --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 --silence Don't print error when running workload -T, --threads int Thread concurrency (default 1) --time duration Total execution time (default 2562047h47m16.854775807s) --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 -U, --user string Database user (default "root") --warehouses int Number of warehouses (default 4) ``` - Run a TPCC benchmark.
Project: Chef Infra (Provisioning / Automation & Configuration)
File: SUPPORT_QUESTION.md

name: Support Question about: If you have a question , please check out our Slack! We use GitHub issues to track bugs and feature requests. If you need help please post to our Mailing List or join the Chef Community Slack. Chef Community Slack at http://community-slack.chef.io/. Chef Mailing List https://discourse.chef.io/ Support issues opened here will be closed and redirected to Slack or Discourse.
Project: StarRocks (App Definition and Development / Database)
File: abs.md

displayed_sidebar: "English" Returns the absolute value of the numeric value `x`. If the input value is NULL, NULL is returned. ```Haskell ABS(x); ``` `x`: the numeric value or expression. Supported data types: DOUBLE, FLOAT, LARGEINT, BIGINT, INT, SMALLINT, TINYINT, DECIMALV2, DECIMAL32, DECIMAL64, DECIMAL128. The data type of the return value is the same as the type of `x`. ```Plain Text mysql> select abs(-1); ++ | abs(-1) | ++ | 1 | ++ 1 row in set (0.00 sec) ``` abs, absolute
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-exp-connections.md

layout: default title: mesheryctl-exp-connections permalink: reference/mesheryctl/exp/connections redirect_from: reference/mesheryctl/exp/connections/ type: reference display-title: "false" language: en command: exp subcommand: connections Manage connections Manage connections <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl exp connections [flags] </div> </pre> List all the connections <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl exp connections list </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for connections </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> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: StarRocks (App Definition and Development / Database)
File: get_json_double.md

displayed_sidebar: "English" This function analyzes and gets the floating point 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 DOUBLE getjsondouble(VARCHAR jsonstr, VARCHAR jsonpath) ``` Get the value whose key is "k1" ```Plain Text MySQL > SELECT getjsondouble('{"k1":1.3, "k2":"2"}', "$.k1"); +-+ | getjsondouble('{"k1":1.3, "k2":"2"}', '$.k1') | +-+ | 1.3 | +-+ ``` Get the second element in the array whose key is "my.key" ```Plain Text MySQL > SELECT getjsondouble('{"k1":"v1", "my.key":[1.1, 2.2, 3.3]}', '$."my.key"[1]'); ++ | getjsondouble('{"k1":"v1", "my.key":[1.1, 2.2, 3.3]}', '$."my.key"[1]') | ++ | 2.2 | ++ ``` Get the first element in the array whose path is k1.key -> k2. ```Plain Text MySQL > SELECT getjsondouble('{"k1.key":{"k2":[1.1, 2.2]}}', '$."k1.key".k2[0]'); ++ | getjsondouble('{"k1.key":{"k2":[1.1, 2.2]}}', '$."k1.key".k2[0]') | ++ | 1.1 | ++ ``` GETJSONDOUBLE,GET,JSON,DOUBLE
Project: SlimToolkit (Provisioning / Security & Compliance)
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. -->
Project: Meshery (Provisioning / Automation & Configuration)
File: kubevela.md

layout: integration title: Kubevela subtitle: Collaborative and visual infrastructure as code for Kubevela image: /assets/img/integrations/kubevela/icons/color/kubevela-color.svg permalink: extensibility/integrations/kubevela docURL: https://docs.meshery.io/extensibility/integrations/kubevela description: integrations-category: App Definition and Development integrations-subcategory: Application Definition & Image Build registrant: Artifact Hub components: 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: KubeArmor (Provisioning / Security & Compliance)
File: log-del.md

```sh kubectl exec -it nginx-77b4fdf86c-x7sdm -- bash root@nginx-77b4fdf86c-x7sdm:/# rm ~/.bash_history rm: cannot remove '/root/.bash_history': Permission denied root@nginx-77b4fdf86c-x7sdm:/# rm ~/.bash_history rm: cannot remove '/root/.bash_history': Permission denied ``` ``` { "Action": "Block", "ClusterName": "0-trust", "ContainerID": "20a6333c6a46e0da32b3062f0ba76e9aed4fc5ef51f5ee8aec5b980963cedea3", "ContainerImage": "docker.io/library/nginx:latest@sha256:32da30332506740a2f7c34d5dc70467b7f14ec67d912703568daff790ab3f755", "ContainerName": "nginx", "Data": "syscall=SYS_UNLINKAT flags=", "Enforcer": "AppArmor", "HostName": "aditya", "HostPID": 43917, "HostPPID": 43266, "Labels": "app=nginx", "NamespaceName": "default", "Operation": "File", "Owner": { "Name": "nginx", "Namespace": "default", "Ref": "Deployment" }, "PID": 392, "PPID": 379, "ParentProcessName": "/usr/bin/bash", "PodName": "nginx-77b4fdf86c-x7sdm", "PolicyName": "DefaultPosture", "ProcessName": "/usr/bin/rm", "Resource": "/root/.bash_history", "Result": "Permission denied", "Source": "/usr/bin/rm /root/.bash_history", "Timestamp": 1696577978, "Type": "MatchedPolicy", "UpdatedTime": "2023-10-06T07:39:38.182538Z", "cluster_id": "4291", "component_name": "kubearmor", "instanceGroup": "0", "instanceID": "0", "tenant_id": "167", "workload": "1" } ```
Project: GraphScope (App Definition and Development / Database)
File: code_style_guide.md

This document provides the coding style guidelines for GraphScope's codebase, which includes C++, Python, Rust, Java, and shell scripts. Adhering to consistent coding standards across the codebase promotes maintainability, readability, and code quality. We follow the for coding standards in C++. We follow the code style for Python coding standards. We follow the , with the GraphScope custom for coding standards in Rust. we follow the for coding standards in Java. We follow the for coding standards in shell script. GraphScope uses different linters and checkers for each language to enforce code style rules: C++: and Python: Rust: Java: Each linter can be included in the build process to ensure that the code adheres to the style guide. Below are the commands to check the code style in each language: For C++, format and lint the code by the MakeFile command: ```bash $ make graphscope_clformat $ make graphscope_cpplint ``` For Python: Install dependencies first: ```bash $ pip3 install -r coordinator/requirements-dev.txt ``` Check the style: ```bash $ pushd python $ python3 -m isort --check --diff . $ python3 -m black --check --diff . $ python3 -m flake8 . $ popd $ pushd coordinator $ python3 -m isort --check --diff . $ python3 -m black --check --diff . $ python3 -m flake8 . ``` For Rust, we provide a shell script to do the format check: ```bash $ cd interactive_engine/executor $ ./check_format.sh ``` For Java: Download the google-java-format tool: ```bash $ wget https://github.com/google/google-java-format/releases/download/v1.13.0/google-java-format-1.13.0-all-deps.jar ``` Check the style: ```bash $ filestoformat=$(git ls-files *.java) $ java -jar google-java-format-1.13.0-all-deps.jar --aosp --skip-javadoc-formatting -i $filestoformat ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-image-unmount.1.md

% podman-image-unmount 1 podman\-image\-unmount - Unmount an image's root filesystem podman image unmount [options] image [...] podman image umount [options] image [...] Unmounts the specified images' root file system, if no other processes are using it. Image storage increments a mount counter each time an image is mounted. When an image is unmounted, the mount counter is decremented, and the image's root filesystem is physically unmounted only when the mount counter reaches zero indicating no other processes are using the mount. An unmount can be forced with the --force flag. All of the currently mounted images are unmounted. Force the unmounting of specified images' root file system, even if other processes have mounted it. Note: Other processes using the file system can fail if the mount point is removed without their knowledge. Unmount image with a given ID: ``` podman image unmount imageID ``` Unmount multiple images with given IDs: ``` podman image unmount imageID1 imageID2 imageID3 ``` Unmount all images: ``` podman image unmount --all ``` , ,
Project: LinuxKit (Provisioning / Automation & Configuration)
File: platform-openstack.md

LinuxKit interacts with OpenStack through its native APIs, providing basic support for pushing images and launching virtual instances. Supported (tested) versions of the relevant OpenStack APIs are: Keystone v3 Glance v2 Nova v2 Neutron v2 LinuxKit's support for OpenStack includes configuring access to your cloud as detailed in the official documentation. ami (Amazon Machine image) vhd (Hyper-V) vhdx (Hyper-V) vmdk (VMware Disk) raw (Raw disk image) qcow2 (Qemu disk image) iso (ISO9660 compatible CD-ROM image) A compatible image needs to have the correct extension (must match one from above) in order to be supported by the `linuxkit push openstack` command. The `openstack` backend will use the filename extension to determine the image type, and use the filename as a label for the new image. Images generated with Moby can be uploaded into OpenStack's image service with `linuxkit push openstack`, plus a few options. For example: ```shell ./linuxkit push openstack \ -img-name=LinuxKitTest ./linuxkit.iso ``` Virtual machines can be launched using `linuxkit run openstack`. As an example: ```shell linuxkit run openstack \ -flavor=hotdog -keyname=deadline_ed25519 \ -sec-groups=allow_ssh,nginx \ -network c5d02c5f-c625-4539-8aed-1dab3aa85a0a \ LinuxKitTest ``` This will create a new instance with the same name as the image, and if successful will return the newly-created instance's UUID. You can then check the boot logs as follows, e.g: ```shell $ openstack console log show 7cdd4d53-78b3-47c7-9a77-ba8a3f60548d [..] linuxkit-fa163ec840c9 login: root (automatic login) Welcome to LinuxKit! NOTE: This system is namespaced. The namespace you are currently in may not be the root. [..] ```
Project: ORY Hydra (Provisioning / Key Management)
File: TrustedOAuth2JwtGrantJsonWebKey.md

Name | Type | Description | Notes | - | - | - Kid | Pointer to string | The \&quot;key_id\&quot; is key unique identifier (same as kid header in jws/jwt). | [optional] Set | Pointer to string | The \&quot;set\&quot; is basically a name for a group(set) of keys. Will be the same as \&quot;issuer\&quot; in grant. | [optional] `func NewTrustedOAuth2JwtGrantJsonWebKey() *TrustedOAuth2JwtGrantJsonWebKey` NewTrustedOAuth2JwtGrantJsonWebKey instantiates a new TrustedOAuth2JwtGrantJsonWebKey object This constructor will assign default values to properties that have it defined, and makes sure properties required by API are set, but the set of arguments will change when the set of required properties is changed `func NewTrustedOAuth2JwtGrantJsonWebKeyWithDefaults() *TrustedOAuth2JwtGrantJsonWebKey` NewTrustedOAuth2JwtGrantJsonWebKeyWithDefaults instantiates a new TrustedOAuth2JwtGrantJsonWebKey object This constructor will only assign default values to properties that have it defined, but it doesn't guarantee that properties required by API are set `func (o *TrustedOAuth2JwtGrantJsonWebKey) GetKid() string` GetKid returns the Kid field if non-nil, zero value otherwise. `func (o TrustedOAuth2JwtGrantJsonWebKey) GetKidOk() (string, bool)` GetKidOk returns a tuple with the Kid field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *TrustedOAuth2JwtGrantJsonWebKey) SetKid(v string)` SetKid sets Kid field to given value. `func (o *TrustedOAuth2JwtGrantJsonWebKey) HasKid() bool` HasKid returns a boolean if a field has been set. `func (o *TrustedOAuth2JwtGrantJsonWebKey) GetSet() string` GetSet returns the Set field if non-nil, zero value otherwise. `func (o TrustedOAuth2JwtGrantJsonWebKey) GetSetOk() (string, bool)` GetSetOk returns a tuple with the Set field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *TrustedOAuth2JwtGrantJsonWebKey) SetSet(v string)` SetSet sets Set field to given value. `func (o *TrustedOAuth2JwtGrantJsonWebKey) HasSet() bool` HasSet returns a boolean if a field has been set.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_fault_delete.md

title: kbcli fault delete Delete chaos resources. ``` kbcli fault delete [flags] ``` ``` kbcli fault delete kbcli fault delete podchaos ``` ``` -h, --help help for delete ``` ``` --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: external-secrets (Provisioning / Security & Compliance)
File: ecr.md

ECRAuthorizationTokenSpec uses the GetAuthorizationToken API to retrieve an authorization token. The authorization token is valid for 12 hours. For more information, see in the Amazon Elastic Container Registry User Guide. | Key | Description | | -- | | | username | username for the `docker login` command. | | password | password for the `docker login` command. | | proxy_endpoint | The registry URL to use for this authorization token in a `docker login` command. | | expires_at | time when token expires in UNIX time (seconds since January 1, 1970 UTC). | You can choose from three authentication mechanisms: static credentials using `spec.auth.secretRef` point to a IRSA Service Account with `spec.auth.jwt` use credentials from the from the controller environment ```yaml {% include 'generator-ecr.yaml' %} ``` Example `ExternalSecret` that references the ECR generator: ```yaml {% include 'generator-ecr-example.yaml' %} ```
Project: Checkov (Provisioning / Security & Compliance)
File: Bitbucket Cloud Pipelines.md

layout: default published: true title: Bitbucket Cloud Pipelines nav_order: 2 You can integrate checkov into your Bitbucket Cloud pipelines. This provides a simple, automatic way of applying policies to your Terraform code both during merge request review and as part of your build process. Add a new step in the `bitbucket-pipelines.yml` file in your repository as part of whichever pipelines are appropriate for you. Here is a minimalistic example: ```yaml checkov: &checkov step: name: Checkov image: name: bridgecrew/checkov:latest entrypoint: '/usr/bin/env' 'PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin' script: checkov -d . pipelines: default: <<: *checkov ``` When your pipeline executes, it will run this job. If checkov finds any issues, it will fail the build. For example, I have an S3 bucket that does not have versioning enabled. Checkov detects this and fails the job and pipeline. This will comment on an associated merge request or fail the build depending on the context. Once I have corrected the configuration, checkov verifies that all is well. See the for additional information.