cwielenb/CNCF-Dataset huggingface dataset:
Project: Chef InSpec (Provisioning / Security & Compliance)
File: inspec-init-plugin.md

`inspec init plugin` generates the scaffold of InSpec plugin, which can extend the functionality of InSpec itself. `inspec init plugin --help` ``` Usage: inspec init plugin PLUGIN_NAME [options] Options: [--prompt], [--no-prompt] # Interactively prompt for information to put in your generated plugin. [--detail=DETAIL] # How detailed of a plugin to generate. 'full' is a normal full gem with tests; 'core' has tests but no gemspec; 'test-fixture' is stripped down for a test fixture. [--author-email=AUTHOR_EMAIL] # Author Email for gemspec [--author-name=AUTHOR_NAME] # Author Name for gemspec [--description=DESCRIPTION] # Multi-line description of the plugin [--summary=SUMMARY] # One-line summary of your plugin [--license-name=LICENSE_NAME] # The name of a license [--activator=one two three] # A list of plugin activator, in the form type1:name1, type2:name2, etc [--hook=one two three] # Legacy name for --activator - Deprecated. [--homepage=HOMEPAGE] # A URL for your project, often a GitHub link [--module-name=MODULE_NAME] # Module Name for your plugin package. Will change plugin name to CamelCase by default. [--copyright=COPYRIGHT] # A copyright statement, to be added to LICENSE [--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 plugin, which can extend the functionality of InSpec itself. ``` `inspec init plugin` command requires few details about the plugin to be added. This can be added using command line prompt or by passing them as the options like for e.g `--author-name`,`--author-email`, `--description`, `--module-name`, etc. `--detail` This option can be used to skip generation of test files or gemspec file. Available values `full`, `core` or `test-fixture`. `--activator` Available activator type are `clicommand`, `reporter` and `streamingreporter`. The default activator type is "cli_command". Usage: `inspec init pluign <inspec-plugin-name> --activator "clicommand:mytest"` `OR` `inspec init plugin <inspec-plugin-reporter-name> --activator "reporter:my_reporter"` `OR` `inspec init plugin <inspec-plugin-streaming-reporter-name> --activator "streamingreporter:mystreaming_reporter"` Note: The InSpec plugin generator can currently only generate one activator of each type. `--hook` Legacy name for `--activator` - Deprecated.
Project: Meshery (Provisioning / Automation & Configuration)
File: grafana-agent.md

layout: integration title: Grafana Agent subtitle: Operational dashboards for your data with Grafana and Meshery image: /assets/img/integrations/grafana-agent/icons/color/grafana-agent-color.svg permalink: extensibility/integrations/grafana-agent docURL: https://docs.meshery.io/extensibility/integrations/grafana-agent description: integrations-category: Observability and Analysis integrations-subcategory: Monitoring registrant: Artifact Hub components: name: pod-logs colorIcon: assets/img/integrations/grafana-agent/components/pod-logs/icons/color/pod-logs-color.svg whiteIcon: assets/img/integrations/grafana-agent/components/pod-logs/icons/white/pod-logs-white.svg description: featureList: [ "Meshery discovers your Grafana servers", "Easily import existing Grafana dashboards and panels into Meshery", "Integrate your boards and panels and new insights and metrics" ] 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: Pravega (App Definition and Development / Streaming & Messaging)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: '' assignees: '' Describe the bug A clear and concise description of what the bug is, including the expected behavior and what has been observed. To Reproduce Steps to reproduce the behavior: Go to '...' Click on '....' Scroll down to '....' See error Screenshots If applicable, add screenshots to help explain your problem. Additional information Add any other information about the problem here, including the root cause if known.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.0.1-en.md

5.0.1 is built on . Same as 5.0.0. 5.0.0 (like 4.4.x) had Erlang/OTP version number in the package name. This is because we wanted to release different flavor packages (on different Elixir/Erlang/OTP platforms). However the long package names also causes confusion, as users may not know which to choose if there were more than one presented at the same time. Going forward, (starting from 5.0.1), packages will be released in both default (short) and flavored (long) package names. For example: `emqx-5.0.1-otp24.2.1-1-ubuntu20.04-amd64.tar.gz`, but only the default one is presented to the users: `emqx-5.0.1-ubuntu20.04-amd64.tar.gz`. In case anyone wants to try a different flavor package, it can be downlowded from the public s3 bucket, for example: https://s3.us-west-2.amazonaws.com/packages.emqx/emqx-ce/v5.0.1/emqx-5.0.1-otp24.2.1-1-ubuntu20.04-arm64.tar.gz Exceptions: Windows package is always presented with short name (currently on Erlang/OTP 24.2.1). Elixir package name is flavored with both Elixir and Erlang/OTP version numbers, for example: `emqx-5.0.1-elixir1.13.4-otp24.2.1-1-ubuntu20.04-amd64.tar.gz` Removed management API auth for prometheus scraping endpoint /api/v5/prometheus/stats Added more TCP options for exhook (gRPC) connections. HTTP Servers used for authentication and authorization will now indicate the result via the response body. Bulk subscribe/unsubscribe APIs Added exclusive subscription Provide authentication counter metrics Do not allow admin user self-deletion After restart, ensure to copy `cluster-override.conf` from the clustered node which has the greatest `tnxid`. A bug fix ported from 4.x: allow deleting subscriptions from `client.subscribe` hookpoint callback result. Fixed Erlang distribution over TLS Made possible to override authentication configs from environment variables Made authentication passwords in Mnesia database backward compatible to 4.x, so we can support data migration better. Fix plugins upload for rpm/deb installations Sync data/authz/acl.conf and data/certs from clustered nodes after a new node joins the cluster Ensure auto-retry of failed resources Fix the issue that the count of `packets.connack.auth_error` is inaccurate when the client uses a protocol version below MQTT v5.0 to access Rate limiter interface is hidden so far, it's subject to a UX redesign. QUIC library upgraded to 0.0.14. Now the default packages will be released withot otp version number in the package name. Renamed config exmpale file name in `etc` dir.
Project: VoltDB (App Definition and Development / Database)
File: VirtualizeOrContainerize.md

VoltDB has been deployed in production in AWS, Azure, VMWare, Xen, KVM & Docker. We've run it in test environments in Google Compute, SoftLayer, VirtualBox, Vagrant and more. Our goal is to make installing VoltDB as simple as installing Java 8 and unpacking the tarball from our website. Relevant Documentation -- The primary getting-started guide is here: https://voltdb.com/run-voltdb-virtualized-containerized-or-cloud There is some additional information on running VoltDB on Docker on our Github wiki page, though it may or may not be 100% up to date. https://github.com/VoltDB/voltdb/wiki/Docker-&-VoltDB-Clustering-Intro Guide to Performance and Customization Section 8.3: Configuring NTP in a Hosted, Virtual, or Cloud Environment https://docs.voltdb.com/PerfGuide/ntpCloud.php Additional Notes -- VoltDB requires Transparent Huge Pages (THP) to be disabled. When running Virtualized, you may want to turn off THP on the host and guest kernels. When using Docker or other container tech, you need to turn off THP on the host kernel. https://voltdb.com/blog/linux-transparent-huge-pages-and-voltdb https://docs.voltdb.com/AdminGuide/adminmemmgt.php
Project: Flink (App Definition and Development / Streaming & Messaging)
File: select-distinct.md

title: "SELECT DISTINCT" weight: 5 type: docs <!-- 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. --> {{< label Batch >}} {{< label Streaming >}} If `SELECT DISTINCT` is specified, all duplicate rows are removed from the result set (one row is kept from each group of duplicates). ```sql SELECT DISTINCT id FROM Orders ``` For streaming queries, the required state for computing the query result might grow infinitely. State size depends on number of distinct rows. You can provide a query configuration with an appropriate state time-to-live (TTL) to prevent excessive state size. Note that this might affect the correctness of the query result. See for details {{< top >}}
Project: KubeVirt (App Definition and Development / Application Definition & Image Build)
File: disk-expansion.md

For some storage methods, Kubernetes may support expanding storage in-use (allowVolumeExpansion feature). KubeVirt can respond to it by making the additional storage available for the virtual machines. This feature is currently off by default, and requires enabling a feature gate. To enable it, add the ExpandDisks feature gate in the kubevirt object: kubectl edit kubevirt -n kubevirt kubevirt ```yaml spec: configuration: developerConfiguration: featureGates: ExpandDisks ``` Enabling this feature does two things: Notify the virtual machine about size changes If the disk is a Filesystem PVC, the matching file is expanded to the remaining size (while reserving some space for file system overhead).
Project: CDK for Kubernetes (CDK8s) (Provisioning / Automation & Configuration)
File: bug.md

name: "\U0001F41B Bug Report" about: Report a bug title: '' labels: bug, needs-triage assignees: '' <!--Please make sure to read the "Reporting Issues" section of the contribution guide before submitting an issue https://github.com/cdk8s-team/cdk8s/blob/master/CONTRIBUTING.md#reporting-issues --> <!--description of the bug:--> <!--minimal amount of code that causes the bug (if possible) or a reference:--> <!--what is the error message you are seeing?--> Framework Version: OS: <!-- e.g. detailed explanation, stacktraces, related issues, suggestions on how to fix, links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc --> This is :bug: Bug Report
Project: OpenSCAP (Provisioning / Security & Compliance)
File: windows.md

Windows Support Removal === We are removing Windows from supported platforms for OpenSCAP. This is not a revolutionary change in the project development process, but rather a formal declaration of the current state of things. Meaning? === The core developers will not: Try to debug, resolve or fix any problems with the scanner functionality on Windows platform Produce release builds The core developers will: Make sure that OpenSCAP is buildable on Windows for the entire lifetime of version 1.3.x The last somewhat working release for Windows is . But why? === Ever since the support was introduced (1.3) the code that covers it has been undermaintained. The support was introduced in the hope that developers, who are interested in the Windows platform, would join the community and help properly maintain it. It never happened. The codebase is now degraded to the state when OpenSCAP is no longer usable on that platform. It works for me, Id like to continue using it! === It most likely means that youve managed to fix the code base and support all the changes that happen in the ecosystem of the platform. This also means that you are able to do your own builds. We wont try to break the build system or the code in a way that it would be incompatible with Windows, so you can safely use the latest version of the OpenSCAP for as long as you wish. Moreover, if you are interested in supporting the Windows version officially (fixing and maintaining it on a quality level) we would be more than happy to have you as a part of our community. Just let us know.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: environment-variables-and-placeholders.md

title: Environment variables and placeholders description: KubeBlocks Environment Variables and Placeholders keywords: [environment variables, placeholders] sidebar_position: 10 sidebar_label: Environment variables and placeholders The following variables are injected by KubeBlocks into each pod. | Name | Description | | : | :- | | KBPODNAME | K8s Pod Name | | KB_NAMESPACE | K8s Pod Namespace | | KBSANAME | KubeBlocks Service Account Name | | KB_NODENAME | K8s Node Name | | KB_HOSTIP | K8s Host IP address | | KB_PODIP | K8s Pod IP address | | KB_PODIPS | K8s Pod IP addresses | | KBPODUID | POD UID (`pod.metadata.uid`) | | KBCLUSTERNAME | KubeBlocks Cluster API object name | | KBCOMPNAME | Running pod's KubeBlocks Cluster API object's `.spec.components.name` | | KBCLUSTERCOMP_NAME | Running pod's KubeBlocks Cluster API object's `<.metadata.name>-<.spec.components.name>` | | KBREPLICACOUNT | Running pod's component's replica | | KBCLUSTERUID | Running pods' KubeBlocks Cluster API object's `metadata.uid` | | KBCLUSTERUIDPOSTFIX8 | Last eight digits of KBCLUSTERUID | | KB{ordinal}HOSTNAME | Running pod's hostname, where `{ordinal}` is the ordinal of pod. <br /> N/A if workloadType=Stateless. | | KBPODFQDN | Running pod's fully qualified domain name (FQDN). <br /> N/A if workloadType=Stateless. | | Name | Description | | : | :- | | POD_ORDINAL | Pod ordinal | | POD_FQDN | Pod FQDN (fully qualified domain name) | | POD_NAME | Pod Name | | Name | Description | | : | :- | | UUID | Generate a random UUID v4 string. | | UUID_B64 | Generate a random UUID v4 BASE64 encoded string. | | UUIDSTRB64 | Generate a random UUID v4 string then BASE64 encoded. | | UUID_HEX | Generate a random UUID v4 HEX representation. | | HEADLESSSVCFQDN | Headless service FQDN placeholder, value pattern - `$(CLUSTERNAME)-$(1STCOMPNAME)-headless.$(NAMESPACE).svc`, where 1STCOMP_NAME is the 1st component that provide `ClusterDefinition.spec.componentDefs[].service` attribute. | | SVCFQDN | Service FQDN placeholder, value pattern - `$(CLUSTERNAME)-$(1STCOMPNAME).$(NAMESPACE).svc`, where 1STCOMPNAME is the 1st component that provide `ClusterDefinition.spec.componentDefs[].service` attribute. | | SVCPORT{PORTNAME} | A ServicePort's port value with specified port name, i.e, a servicePort JSON struct: <br /> `{"name": "mysql", "targetPort": "mysqlContainerPort", "port": 3306}`, and "$(SVCPORT_mysql)" in the connection credential value is 3306. | | RANDOM_PASSWD | Random 8 characters |
Project: StarRocks (App Definition and Development / Database)
File: Querybook.md

displayed_sidebar: "English" Querybook supports querying and visualizing both internal data and external data in StarRocks. Make sure that you have finished the following preparations: Clone and download the Querybook repository. ```SQL git clone git@github.com:pinterest/querybook.git cd querybook ``` Create a file named `local.txt` under the `requirements` folder in the project's root directory. ```SQL touch requirements/local.txt ``` Add the required packages. ```SQL echo -e "starrocks\nmysqlclient" > requirements/local.txt ``` Start the container. ```SQL make ``` Visit and add a new query engine: Take note of the following points: For Language, select Starrocks. For Executor, select sqlalchemy. For Connection_string, enter a URI in the StarRocks SQLAlchemy URI format as below: ```SQL starrocks://<User>:<Password>@<Host>:<Port>/<Catalog>.<Database> ``` The parameters in the URI are described as follows: `User`: the username that is used to log in to your StarRocks cluster, for example, `admin`. `Password`: the password that is used to log in to your StarRocks cluster. `Host`: the FE host IP address of your StarRocks cluster. `Port`: the FE query port of your StarRocks cluster, for example, `9030`. `Catalog`: the target catalog in your StarRocks cluster. Both internal and external catalogs are supported. `Database`: the target database in your StarRocks cluster. Both internal and external databases are supported.
Project: KICS (Provisioning / Security & Compliance)
File: 14a457f0-473d-4d1d-9e37-6d99b355b336.md

title: Google Compute SSL Policy Weak Cipher In Use hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 14a457f0-473d-4d1d-9e37-6d99b355b336 Query name: Google Compute SSL Policy Weak Cipher In Use Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: This query confirms if Google Compute SSL Policy Weak Chyper Suits is Enabled, to do so we need to check if TLS is TLS12, because other version have Weak Chypers<br> ```tf title="Positive test num. 1 - tf file" hl_lines="8 3" resource "googlecomputessl_policy" "positive1" { name = "custom-ssl-policy" mintlsversion = "TLS11" profile = "CUSTOM" customfeatures = ["TLSECDHEECDSAWITHAES256GCMSHA384", "TLSECDHERSAWITHAES256GCM_SHA384"] } resource "googlecomputessl_policy" "positive2" { name = "custom-ssl-policy" profile = "CUSTOM" customfeatures = ["TLSECDHEECDSAWITHAES256GCMSHA384", "TLSECDHERSAWITHAES256GCM_SHA384"] } ``` ```tf title="Negative test num. 1 - tf file" resource "googlecomputessl_policy" "negative1" { name = "custom-ssl-policy" mintlsversion = "TLS12" profile = "CUSTOM" customfeatures = ["TLSECDHEECDSAWITHAES256GCMSHA384", "TLSECDHERSAWITHAES256GCM_SHA384"] } ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: TESTING.md

The testsuite depends on an OpenLDAP server. slapd(8) and the CLI must be installed for it to work. However there is no need to configure the server. The testsuite takes care of starting its own server and configuring it. It won't conflict with the system OpenLDAP server instance. The testsuite needs the following modules to be available: `bdb` `memberof` `refint` As with all other RabbitMQ subprojects, ``` sh make tests ``` will run all test suites.
Project: Meshery (Provisioning / Automation & Configuration)
File: kubernetes-secret-generator.md

layout: integration title: Kubernetes Secret Generator subtitle: Collaborative and visual infrastructure as code for Kubernetes Secret Generator image: /assets/img/integrations/kubernetes-secret-generator/icons/color/kubernetes-secret-generator-color.svg permalink: extensibility/integrations/kubernetes-secret-generator docURL: https://docs.meshery.io/extensibility/integrations/kubernetes-secret-generator description: integrations-category: Security & Compliance integrations-subcategory: Uncategorized registrant: Artifact Hub components: name: basic-auth colorIcon: assets/img/integrations/kubernetes-secret-generator/components/basic-auth/icons/color/basic-auth-color.svg whiteIcon: assets/img/integrations/kubernetes-secret-generator/components/basic-auth/icons/white/basic-auth-white.svg description: name: ssh-key-pair colorIcon: assets/img/integrations/kubernetes-secret-generator/components/ssh-key-pair/icons/color/ssh-key-pair-color.svg whiteIcon: assets/img/integrations/kubernetes-secret-generator/components/ssh-key-pair/icons/white/ssh-key-pair-white.svg description: name: string-secret colorIcon: assets/img/integrations/kubernetes-secret-generator/components/string-secret/icons/color/string-secret-color.svg whiteIcon: assets/img/integrations/kubernetes-secret-generator/components/string-secret/icons/white/string-secret-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: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: install-kubeblocks-with-helm.md

title: Install KubeBlocks with Helm description: Install KubeBlocks on the existing Kubernetes clusters with Helm keywords: [taints, affinity, tolerance, install, kbcli, KubeBlocks] sidebar_position: 3 sidebar_label: Install KubeBlocks KubeBlocks is kubernetes-native, you can use Helm to install it. :::note If you install KubeBlocks with Helm, to uninstall it, you have to use Helm too. Make sure you have and installed. ::: <table> <tr> <th colspan="3">Resource Requirements</th> </tr > <tr> <td >Control Plane</td> <td colspan="2">It is recommended to create 1 node with 4 cores, 4GB memory and 50GB storage. </td> </tr > <tr > <td rowspan="4">Data Plane</td> <td> MySQL </td> <td>It is recommended to create at least 3 nodes with 2 cores, 4GB memory and 50GB storage. </td> </tr> <tr> <td> PostgreSQL </td> <td>It is recommended to create at least 2 nodes with 2 cores, 4GB memory and 50GB storage. </td> </tr> <tr> <td> Redis </td> <td>It is recommended to create at least 2 nodes with 2 cores, 4GB memory and 50GB storage. </td> </tr> <tr> <td> MongoDB </td> <td>It is recommended to create at least 3 nodes with 2 cores, 4GB memory and 50GB storage. </td> </tr> </table> Use Helm and follow the steps below to install KubeBlocks. Create dependent CRDs. ```bash kubectl create -f https://github.com/apecloud/kubeblocks/releases/download/v0.8.1/kubeblocks_crds.yaml ``` Add Helm repo. ```bash helm repo add kubeblocks https://apecloud.github.io/helm-charts helm repo update ``` Install KubeBlocks. ```bash helm install kubeblocks kubeblocks/kubeblocks --namespace kb-system --create-namespace ``` If you want to install KubeBlocks with custom tolerations, you can use the following command: ```bash helm install kubeblocks kubeblocks/kubeblocks --namespace kb-system --create-namespace \ --set-json 'tolerations=[ { "key": "control-plane-taint", "operator": "Equal", "effect": "NoSchedule", "value": "true" } ]' \ --set-json 'dataPlane.tolerations=[{ "key": "data-plane-taint", "operator": "Equal", "effect": "NoSchedule", "value": "true" }]' ``` If you want to install KubeBlocks with a specified version, follow the steps below. View the available versions in . Specify a version with `--version` and run the command below. ```bash helm install kubeblocks kubeblocks/kubeblocks --namespace kb-system --create-namespace --version="x.x.x" ``` :::note By default, the latest release version is installed. ::: Run the following command to check whether KubeBlocks is installed successfully. ```bash kubectl -n kb-system get pods ``` *Result* If the KubeBlocks Workloads are all ready, KubeBlocks has been installed successfully. ```bash NAME READY STATUS RESTARTS AGE kb-addon-snapshot-controller-649f8b9949-2wzzk 1/1 Running 2 (24m ago) 147d kubeblocks-dataprotection-f6dbdbf7f-5fdr9 1/1 Running 2 (24m ago) 147d kubeblocks-6497f7947-mc7vc 1/1 Running 2 (24m ago) 147d ```