cwielenb/CNCF-Dataset huggingface dataset:
Project: VMClarity (Provisioning / Security & Compliance)
File: GOALS.md

Increase the adoption of VMClarity:One of the primary goals of VMClarity is to reduce the number of vulnerable VMs in the world. We hope to do this by getting more people involved in the project. This involves feature development, marketing efforts, improving the user experience, and providing additional documentation and resources to make it easier for users to get started. Improve the accuracy of VMClarity:Another goal is to enhance the accuracy across all supported types of threat detection by improving the analysis and result merging logic performed by VMClarity to reduce false positives. This involves researching and developing improved algorithms and heuristics used by VMClarity. Expand VMClarity's functionality:A third goal is to expand the functionality of VMClarity by adding additional tools to each family, adding additional families of threats to detect, and integrating with other security tools to provide a more comprehensive security solution. Foster a community around VMClarity:VMClarity will only be successful if we foster a community of users and developers around the project. The health of VMClarity depends on organizing events, creating a forum for users to drive requirements and use cases, and contributing to open-source projects related to VMClarity. Building a strong community around VMClarity will help it be more widely adopted and more effective at detecting and managing virtual machine threats.
Project: The Update Framework (TUF) (Provisioning / Security & Compliance)
File: PULL_REQUEST_TEMPLATE.md

<!-- Before submitting a pull request: Run linter and tests locally: Use "tox" Ensure your commits are signed-off-by: Use "commit --signoff" Make sure new code has tests and is documented For more info, see docs/CONTRIBUTING.rst Once commits are signed off and tested, describe the purpose and contents of the pull request below. --> Description of the changes being introduced by the pull request: Fixes #<ISSUE NUMBER>
Project: Chef InSpec (Provisioning / Security & Compliance)
File: inspec-init-resource.md

`inspec init resource` generates the scaffold of InSpec core resources or resource pack, which can extend the scope of InSpec resources support. `inspec init resource --help` ``` Usage: inspec init resource RESOURCE_NAME [options] Options: [--prompt], [--no-prompt] # Interactively prompt for information to put in your generated resource. [--overwrite], [--no-overwrite] # Overwrite existing files [--layout=LAYOUT] # File layout, either 'resource-pack' or 'core' [--template=TEMPLATE] # Which type of resource template to use [--supports-platform=SUPPORTS_PLATFORM] # the platform supported by this resource [--description=DESCRIPTION] # the description of this resource [--class-name=CLASS_NAME] # Class Name for your resource. [--path=PATH] # Subdirectory under which to create files [--log-level=LOG_LEVEL] # Set the log level: info (default), debug, warn, error [--log-location=LOG_LOCATION] # Location to send diagnostic log messages to. (default: $stdout or Inspec::Log.error) Generates an InSpec resource, which can extend the scope of InSpec resources support ``` `inspec init resource` command requires few details about the resource to be added. This can be added using command line prompt or by passing them as the options like for e.g `--layout`,`--template`, `--description`, `--class-name`, etc. `--layout` Available layout type are `resource-pack` and `core`. The default layout type is "resource-pack". `--template` Available resource template type are `plural` and `basic`. The default layout type is "basic". `inspec init resource <inspec-resource-name> --layout "resource-pack" --template "basic" --prompt false` `inspec init resource <inspec-resource-name> --layout "resource-pack" --template "plural" --prompt false` `inspec init resource <inspec-resource-name> --layout "core" --template "basic" --prompt false` `inspec init resource <inspec-resource-name> --layout "core" --template "plural" --prompt false`
Project: ThreatMapper (Provisioning / Security & Compliance)
File: manage-users.md

title: Managing Users The first Management Console user is created through the process. This is a one-time process; further users must be invited to the Console by an existing Admin user. An admin user can invite users by two methods: Generate an invitation link for a named email address, and then provide that link to the user Configure an email relay for the Management Console, then use the Management Console to invite users by email Go to Settings > User Management and select Send Invite Enter the user's email, select the desired role, and click "Get an invite link" Copy-and-paste the invite link and share it with the user. Links are valid for a short period of time only. You should configure an Email relay first, so that invitation emails can be sent. Go to Settings > Email Configuration Select the mailer type :::info For more information, see . ::: First, provide: An appropriate Google Workspace email address (one for which you can generate an App Password) The SMTP server and port, for example `smtp.google.com`, port `465` You will need to generate an App Password: Go to Under Select App, chose Others* and enter a name, for example, "ThreatMapper" Click the Generate* button. If the 'App Password' facility is not available, please refer to your Google Workspace administrator. Copy the password that has been generated, and enter it into App Password field. Save settings. :::info For more information, see . ::: Provide an email address to identify the email sender Specify an Provide the Access and Secret keys (see here: ) Save the email configuration. Go to Settings > User Management and select Send Invite. Provide: The email address of the user to invite The role the user should be given This will send an invitation to the user with a registration link (URL). The URL is valid for 24 hours only.
Project: StarRocks (App Definition and Development / Database)
File: bitor.md

displayed_sidebar: "English" Returns the bitwise OR of two numeric expressions. ```Haskell BITOR(x,y); ``` `x`: This expression must evaluate to any of the following data types: TINYINT, SMALLINT, INT, BIGINT, LARGEINT. `y`: This expression must evaluate to any of the following data types: TINYINT, SMALLINT, INT, BIGINT, LARGEINT. `x` and `y` must agree in data type. The return value has the same type as `x`. If any value is NULL, the result is NULL. ```Plain Text mysql> select bitor(3,0); +-+ | bitor(3, 0) | +-+ | 3 | +-+ 1 row in set (0.00 sec) ```
Project: Checkov (Provisioning / Security & Compliance)
File: bitbucket_configuration.md

layout: default title: bitbucket_configuration resource scans nav_order: 1 | | Id | Type | Entity | Policy | IaC | Resource Link | |-|--|-|-|-|-|| | 0 | CKVBITBUCKET1 | bitbucketconfiguration | * | Merge requests should require at least 2 approvals | bitbucketconfiguration | |
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_clusterdefinition_describe.md

title: kbcli clusterdefinition describe Describe ClusterDefinition. ``` kbcli clusterdefinition describe [flags] ``` ``` kbcli clusterdefinition describe myclusterdef ``` ``` -h, --help help for describe ``` ``` --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 ``` - ClusterDefinition command.
Project: Apache RocketMQ (App Definition and Development / Streaming & Messaging)
File: deploy_guide.md

This document introduces how to deploy auto failover RocketMQ-on-DLedger Group. RocketMQ-on-DLedger Group is a broker group with same name, needs at least 3 nodes, elect a Leader by Raft algorithm automatically, the others as Follower, replicating data between Leader and Follower for system high available. RocketMQ-on-DLedger Group can failover automatically, and maintains consistent. RocketMQ-on-DLedger Group can scale up horizontal, that is, can deploy any RocketMQ-on-DLedger Groups providing services external. each RocketMQ-on-DLedger Group needs at least 3 machines.(assuming 3 in this document) write 3 configuration files, advising refer to the directory of conf/dledger 's example configuration file. key configuration items: | name | meaning | example | | | | | | enableDLegerCommitLog | whether enable DLedger | true | | dLegerGroup | DLedger Raft Group's name, advising maintain consistent to brokerName | RaftNode00 | | dLegerPeers | DLedger Group's nodes port infos, each node's configuration stay consistent in the same group.| n0-127.0.0.1:40911;n1-127.0.0.1:40912;n2-127.0.0.1:40913 | | dLegerSelfId | node id, must belongs to dLegerPeers; each node is unique in the same group. | n0 | | sendMessageThreadPoolNums | the count of sending thread, advising set equal to the cpu cores. | 16 | the following presents an example configuration conf/dledger/broker-n0.conf. ``` brokerClusterName = RaftCluster brokerName=RaftNode00 listenPort=30911 namesrvAddr=127.0.0.1:9876 storePathRootDir=/tmp/rmqstore/node00 storePathCommitLog=/tmp/rmqstore/node00/commitlog enableDLegerCommitLog=true dLegerGroup=RaftNode00 dLegerPeers=n0-127.0.0.1:40911;n1-127.0.0.1:40912;n2-127.0.0.1:40913 dLegerSelfId=n0 sendMessageThreadPoolNums=16 ``` Startup stays consistent with the old version. `nohup sh bin/mqbroker -c conf/dledger/xxx-n0.conf & ` `nohup sh bin/mqbroker -c conf/dledger/xxx-n1.conf & ` `nohup sh bin/mqbroker -c conf/dledger/xxx-n2.conf & ` If old cluster deployed in Master mode, then each Master needs to be transformed into a RocketMQ-on-DLedger Group. If old cluster deployed in Master-Slave mode, then each Master-Slave group needs to be transformed into a RocketMQ-on-DLedger Group. execute kill command, or call `bin/mqshutdown broker`. Each node in RocketMQ-on-DLedger group is compatible with old Commitlog, but Raft replicating process works on the adding message only. So, to avoid occurring exceptions, old Commitlog must be consistent. If old cluster deployed in Master-Slave mode, it maybe inconsistent after shutdown. Advising use md5sum to check at least 2 recently Commitlog file, if occur inconsistent, maintain consistent by copy. Although RocketMQ-on-DLedger Group can deployed with 2 nodes, it lacks failover ability(at least 3 nodes can tolerate one node fail). Make sure that both Master and Slave's Commitlog is consistent, then prepare 3 machines, copy old Commitlog from Master to this 3 machines(BTW, copy the config directory). Then, go ahead to set configurations. Refer to New cluster deployment. Refer to New cluster deployment.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_subnetworks.md

+++ title = "googlecomputesubnetworks resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputesubnetworks" identifier = "inspec/resources/gcp/googlecomputesubnetworks.md googlecomputesubnetworks resource" parent = "inspec/resources/gcp" +++ A `googlecomputesubnetworks` is used to test a Google Subnetwork resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputesubnetworks(project: 'chef-gcp-inspec', region: 'europe-west2') do its('ipcidrranges') { should include '10.2.0.0/16' } its('subnetwork_names') { should include 'inspec-subnet' } end ``` describe googlecomputesubnetworks(project: 'chef-inspec-gcp', region: 'europe-west2') do its('count') { should be <= 100} end describe googlecomputesubnetworks(project: 'chef-inspec-gcp', region: 'europe-west2') do its('subnetwork_ids') { should include 12345678975432 } end describe googlecomputesubnetworks(project: 'chef-inspec-gcp', region: 'europe-west2') do its('subnetwork_names') { should include "subnetwork-name" } end describe googlecomputesubnetworks(project: 'chef-inspec-gcp', region: 'europe-west2') do its('subnetwork_networks') { should not include "network-name" } end Properties that can be accessed from the `googlecomputesubnetworks` resource: See the resource for more information. `creation_timestamps` : an array of `googlecomputesubnetwork` creation_timestamp `descriptions` : an array of `googlecomputesubnetwork` description `gateway_addresses` : an array of `googlecomputesubnetwork` gateway_address `subnetwork_ids` : an array of `googlecomputesubnetwork` id `ipcidrranges` : an array of `googlecomputesubnetwork` ipcidrrange `subnetwork_names` : an array of `googlecomputesubnetwork` name `networks` : an array of `googlecomputesubnetwork` network `purposes` : (Beta only) an array of `googlecomputesubnetwork` purpose `roles` : (Beta only) an array of `googlecomputesubnetwork` role `secondaryipranges` : an array of `googlecomputesubnetwork` secondaryipranges `privateipgoogle_accesses` : an array of `googlecomputesubnetwork` privateipgoogle_access `regions` : an array of `googlecomputesubnetwork` region `log_configs` : an array of `googlecomputesubnetwork` log_config This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.11-patch.2.md

layout: release date: 2024-01-18 tag: v0.7.11-patch.2 Update grafana_helper.go @eltociear (#9981) [Server] Fix remote pattern upload @MUzairS15 (#10014) [Server] Validate `userid` and handle remote provider responses on failure correctly. @MUzairS15 (#10015) [bug] Fix Remote Design file upload @theBeginner86 (#10013) [UI] Fix publishing design @Yashsharma1911 (#9990) [MeshModel Category] Database category icon added @ritiksaxena124 (#10006) Thank you to our contributors for making this release possible: @MUzairS15, @Yashsharma1911, @eltociear, @leecalcote, @ritiksaxena124 and @theBeginner86
Project: KICS (Provisioning / Security & Compliance)
File: c3b9f7b0-f5a0-49ec-9cbc-f1e346b7274d.md

title: S3 Bucket Logging Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: c3b9f7b0-f5a0-49ec-9cbc-f1e346b7274d Query name: S3 Bucket Logging Disabled Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Server Access Logging should be enabled on S3 Buckets so that all changes are logged and trackable<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="6" name: "Create S3 bucket" amazon.aws.s3_bucket: name: mys3bucket state: present debugbotocoreendpoint_logs: false ``` ```yaml title="Negative test num. 1 - yaml file" amazon.aws.s3_bucket: name: mys3bucket state: present debugbotocoreendpoint_logs: true ```
Project: YugabyteDB (App Definition and Development / Database)
File: unsubscribe.md

title: UNSUBSCRIBE linkTitle: UNSUBSCRIBE description: UNSUBSCRIBE menu: preview: parent: api-yedis weight: 2553 aliases: /preview/api/redis/unsubscribe /preview/api/yedis/unsubscribe type: docs `UNSUBSCRIBE [channel [channel ...]]` This command unsubscribes the client from the specified channel(s). If no channel is specified, the client is unsubscribed from all channels that it has subscribed to. , , , , ,
Project: GraphScope (App Definition and Development / Database)
File: README.md

The project structure refers to (ipycytoscape)[https://github.com/QuantStack/ipycytoscape/tree/1.1.0]. A widget enabling interactive graph visualization with in JupyterLab and the Jupyter notebook. Note that graphscope-jupyter requires jupyterlab 2.x (e.g., `2.3.0a0`) and is known unusable with jupyterlab 3.x. With `mamba`: ``` mamba install -c conda-forge graphscope-jupyter ``` With `conda`: ``` conda install -c conda-forge graphscope-jupyter ``` With `pip`: ```bash pip install graphscope-jupyter ``` If you are using JupyterLab 1.x or 2.x then you will also need to install `nodejs` and the `jupyterlab-manager` extension. You can do this like so: ```bash conda install -c conda-forge nodejs jupyter labextension install @jupyter-widgets/jupyterlab-manager@2 jupyter lab build ``` You may also need to manually enable the nbextension: ```bash jupyter nbextension enable --py [--sys-prefix|--user|--system] graphscope-jupyter ``` (requires npm) While not required, we recommend creating a conda environment to work in: ```bash conda create -n graphscope -c conda-forge jupyterlab nodejs networkx conda activate graphscope git clone https://github.com/alibaba/GraphScope.git cd GraphScope/python/jupyter/graphscope pip install -e . ``` When developing graphscope-jupyter, you need to manually enable the extension with the notebook / lab frontend. For lab, this is done by the command: ``` jupyter labextension install . ``` For classic notebook, you can run: ``` jupyter nbextension install --sys-prefix --symlink --overwrite --py graphscope-jupyter jupyter nbextension enable --sys-prefix --py graphscope-jupyter ``` Note that the `--symlink` flag doesn't work on Windows, so you will here have to run the `install` command every time that you rebuild your extension. For certain installations you might also need another flag instead of `--sys-prefix`, but we won't cover the meaning of those flags here. You need to install and build `npm` packages: ``` npm install && npm run build ``` Every time you change your typescript code it's necessary to build it again: ``` npm run build ``` To continuously monitor the project for changes and automatically trigger a rebuild, start Jupyter in watch mode: ```bash jupyter lab --watch ``` And in a separate session, begin watching the source directory for changes: ```bash npm run watch ``` If you make a change to the python code then you need to restart the notebook kernel to have it take effect. Install necessary dependencies with pip: ``` cd GraphScope/python/jupyter/graphscope pip install -e . ``` We use a shared copyright model that enables all contributors to maintain the copyright on their contributions. This software is licensed under the Apache License 2.0. See the file for details.
Project: StarRocks (App Definition and Development / Database)
File: SHOW_COMPUTE_NODES.md

displayed_sidebar: "English" View all compute nodes in your StarRocks cluster. :::tip Only users with the SYSTEM-level OPERATE privilege or the `cluster_admin` role can perform this operation. ::: ```SQL SHOW COMPUTE NODES ``` The following table describes the parameters returned by this statement. | Parameter | Description | | -- | | | LastStartTime | The last time at which the compute node starts. | | LastHeartbeat | The last time at which the compute node sends a heartbeat. | | Alive | Whether the compute node is available or not. | | SystemDecommissioned | If the value of the parameter is `true`, the compute node is removed from your StarRocks cluster. Before removal, the data in the compute node is cloned. | | ErrMsg | The error message if the compute node fails to send a heartbeat. | | Status | The state of the compute node, which displays in the JSON format. Currently, you can only see the last time at which the compute node sends its state. |
Project: KICS (Provisioning / Security & Compliance)
File: 3ddf3417-424d-420d-8275-0724dc426520.md

title: Lambda Permission Misconfigured hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 3ddf3417-424d-420d-8275-0724dc426520 Query name: Lambda Permission Misconfigured Platform: Ansible Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: Lambda permission may be misconfigured if the action field is not filled in by 'lambda:InvokeFunction'<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="7" name: Lambda S3 notification positive community.aws.lambda_policy: state: present function_name: functionName alias: Dev statement_id: lambda-s3-myBucket-create-data-log action: lambda:CreateFunction principal: s3.amazonaws.com source_arn: arn:aws:s3:eu-central-1:123456789012:bucketName source_account: 123456789012 ``` ```yaml title="Negative test num. 1 - yaml file" name: Lambda S3 notification negative community.aws.lambda_policy: state: present function_name: functionName alias: Dev statement_id: lambda-s3-myBucket-create-data-log action: lambda:InvokeFunction principal: s3.amazonaws.com source_arn: arn:aws:s3:eu-central-1:123456789012:bucketName source_account: 123456789012 ```
Project: Meshery (Provisioning / Automation & Configuration)
File: pushing-pulling-model-images.md

layout: default title: Push or Pull a Model Image permalink: guides/configuration-management/push-pull-model-image type: guides category: configuration language: en list: include abstract: "Push or pull a model image to or from an OCI-compatible image repository." You can push or pull a model image to or from an OCI-compatible image repository using `mesheryctl`. This guide will walk you through the process. ](/assets/img/tasks/models/push-pull-models-oci-registry.svg)
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: overview.md

title: Overview description: An overview of developer docs keywords: [developer docs] sidebar_position: 1 sidebar_label: Developer guides Guides and resources to unleash your development potential. Developer docs include integration tutorials for how to add an add-on to KubeBlocks, API reference, guides for referencing external components and simulating fault injections.
Project: Harbor (Provisioning / Container Registry)
File: 9-15-LDAP-user-delete-signed-images.md

Test 9-15 User delete signed images(LDAP mode) ======= To verify user can delete signed images with content trust enabled. User guide This test requires a Harbor instance is running and available. Harbor is set authenticate against an LDAP or AD server. A Linux host with Docker CLI(Docker client)installed. A non-admin user that has at least one project as project admin. Same as Test 9-05 except that users are from LDAP/AD. Same as Test 9-05. None