cwielenb/CNCF-Dataset huggingface dataset:
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.0.2.md

Delete edgedevice from the name field of all virtual devices / profiles by @xiaoyu0803 in https://github.com/Edgenesis/shifu/pull/136 Custom Metadata support in EdgeDevice CRD by @tomqin93 in https://github.com/Edgenesis/shifu/pull/143 Refactor deviceShifu build and push in Makefile by @tomqin93 in https://github.com/Edgenesis/shifu/pull/144 Development Guide for Mac and Windows by @tomqin93 in https://github.com/Edgenesis/shifu/pull/121 v0.0.1 Changelog by @tomqin93 in https://github.com/Edgenesis/shifu/pull/131 Update contact information in README.md by @saiyan86 in https://github.com/Edgenesis/shifu/pull/132 [Issue #129] Fix some documentation errors by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/134 deviceShifu doc by @saiyan86 in https://github.com/Edgenesis/shifu/pull/137 [Issue #145] fix the wrong go version in document by @13316272689 in https://github.com/Edgenesis/shifu/pull/146 Bump github.com/gopcua/opcua from 0.3.4 to 0.3.5 by @dependabot in https://github.com/Edgenesis/shifu/pull/135 Bump k8s.io/apimachinery from 0.24.1 to 0.24.2 in /deviceshifu/pkg/mockdevice/mockdevice by @dependabot in https://github.com/Edgenesis/shifu/pull/140 Bump k8s.io/client-go from 0.24.1 to 0.24.2 by @dependabot in https://github.com/Edgenesis/shifu/pull/139 [Issue #123] Update devcontainer by @tomqin93 in https://github.com/Edgenesis/shifu/pull/147 Bump sigs.k8s.io/controller-runtime from 0.12.1 to 0.12.2 in /k8s/crd by @dependabot in https://github.com/Edgenesis/shifu/pull/150 Bump up Kustomize, controller-gen and kube-rbac-proxy versions by @tomqin93 in https://github.com/Edgenesis/shifu/pull/151 @MrLeea-13155bc made their first contribution in https://github.com/Edgenesis/shifu/pull/134 @13316272689 made their first contribution in https://github.com/Edgenesis/shifu/pull/146 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.0.1...v0.0.2
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.4.4.md

layout: release date: 2020-8-27 tag: v0.4.4 Features Added timeout in golang-ci lint Moved to Gorilla/mux for server routing Migrated to golangci-lint Initialised nighthawk load generator interface Maintenance Updated meshmap branch to latest on master branch Made page heading title bold Moved meshery adapter for osm Documentation Added extra RVM notes for Windows Users Added SMI screenshot and description Added the current version of osm Bug fixes Auto detecting kube configuration Fixed the footer social bar
Project: ShardingSphere (App Definition and Development / Database)
File: _index.en.md

title : Children description : List the child pages of a page Use the children shortcode to list the child pages of a page and the further descendants (children's children). By default, the shortcode displays links to the child pages. | Parameter | Default | Description | |:--|:--|:--| | page | current | Specify the page name (section name) to display children for | | style | "li" | Choose the style used to display descendants. It could be any HTML tag name | | showhidden | "false" | When true, child pages hidden from the menu will be displayed | | description | "false" | Allows you to include a short text under each page in the list. When no description exists for the page, children shortcode takes the first 70 words of your content. | | depth | 1 | Enter a number to specify the depth of descendants to display. For example, if the value is 2, the shortcode will display 2 levels of child pages. Tips: set 999 to get all descendants | | sort | none | Sort children by Weight - to sort on menu order, Name - to sort alphabetically on menu label, Identifier - to sort alphabetically on identifier set in frontmatter, and URL - to sort by URL | {{%/ children /%}} {{% children %}} {{%/ children description="true" /%}} {{%children description="true" %}} {{%/ children depth="3" showhidden="true" /%}} {{% children depth="3" showhidden="true" %}} {{%/ children style="h2" depth="3" description="true" /%}} {{% children style="h2" depth="3" description="true" %}} {{%/ children style="div" depth="999" /%}} {{% children style="div" depth="999" %}}
Project: Meshery (Provisioning / Automation & Configuration)
File: vald-helm-operator.md

layout: integration title: Vald Helm Operator subtitle: Collaborative and visual infrastructure as code for Vald Helm Operator image: /assets/img/integrations/vald-helm-operator/icons/color/vald-helm-operator-color.svg permalink: extensibility/integrations/vald-helm-operator docURL: https://docs.meshery.io/extensibility/integrations/vald-helm-operator description: integrations-category: Provisioning integrations-subcategory: Key Management registrant: Artifact Hub components: name: vald-helm-operator-release colorIcon: assets/img/integrations/vald-helm-operator/components/vald-helm-operator-release/icons/color/vald-helm-operator-release-color.svg whiteIcon: assets/img/integrations/vald-helm-operator/components/vald-helm-operator-release/icons/white/vald-helm-operator-release-white.svg description: name: vald-release colorIcon: assets/img/integrations/vald-helm-operator/components/vald-release/icons/color/vald-release-color.svg whiteIcon: assets/img/integrations/vald-helm-operator/components/vald-release/icons/white/vald-release-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: Kui (App Definition and Development / Application Definition & Image Build)
File: BUG_REPORT.md

name: Bug Report about: Create an issue report. <!-- Hello Thank you for submitting an issue. Before you start, please make sure your issue is understandable and reproducible. To make your issue readable make sure you use valid Markdown syntax. https://guides.github.com/features/mastering-markdown/ --> Describe the bug A clear and concise description of what the bug is. Steps to reproduce the behavior Go to '...' Click on '....' Scroll down to '....' See error Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Code snippets If applicable, add code samples to help explain your problem. System Kui version: Operating system:
Project: Chef InSpec (Provisioning / Security & Compliance)
File: resource.md

+++ title = "{{ .Name }} resource" draft = false gh_repo = "inspec" platform = "<PLATFORM>" [menu] [menu.inspec] title = "{{ .Name }}" identifier = "inspec/resources/<PLATFORM>/{{ .Name }}" parent = "inspec/resources/<PLATFORM>" +++ {{/ Run `hugo new -k resource inspec/resources/RESOURCE_NAME.md` to generate a new resource page. /}} Use the `{{ .Name }}` Chef InSpec audit resource to test the configuration of... {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in Chef InSpec vX.Y.Z. ```ruby describe {{ .Name }} do end ``` `PARAMETER` : PARAMETER DESCRIPTION `PARAMETER` : PARAMETER DESCRIPTION `PROPERTY` : PROPERTY DESCRIPTION `PROPERTY` : PROPERTY DESCRIPTION EXAMPLE DESCRIPTION ```ruby describe {{ .Name }} do end ``` EXAMPLE DESCRIPTION ```ruby describe {{ .Name }} do end ``` {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The `MATCHER_NAME` matcher tests the value of... ```ruby its(`MATCHER_NAME`) { should cmp 'VALUE' } ```
Project: Apache Heron (App Definition and Development / Streaming & Messaging)
File: extending-heron-scheduler.md

id: version-0.20.0-incubating-extending-heron-scheduler title: Implementing a Custom Scheduler sidebar_label: Custom Scheduler original_id: extending-heron-scheduler <!-- 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. --> To run a Heron topology, youll need to set up a scheduler that is responsible for topology management. Note: one scheduler is managing only one topology, for the purpose of better isolation. Heron currently supports the following schedulers out of the box: If you'd like to run Heron on a not-yet-supported system, such as , you can create your own scheduler using Heron's spi, as detailed in the sections below. Java is currently the only supported language for custom schedulers. This may change in the future. In order to create a custom scheduler, you need to import the `heron-spi` library into your project. ```xml <dependency> <groupId>org.apache.heron</groupId> <artifactId>heron-spi</artifactId> <version>{{% heronVersion %}}</version> </dependency> ``` ```groovy dependencies { compile group: "org.apache.heron", name: "heron-spi", version: "{{% heronVersion %}}" } ``` Creating a custom scheduler involves implementing each of the following Java interfaces: Interface | Role | Examples :-- |:- |:-- | Defines the algorithm used to generate physical plan for a topology. | | Defines how the scheduler is launched | , | Defines the scheduler object used to construct topologies | | Uploads the topology to a shared location accessible to the runtime environment of the topology | Heron provides a number of built-in implementations out of box. To run the a custom scheduler, the implementation of the interfaces above must be specified in the . By default, the heron-cli looks for configurations under `${HERON_HOME}/conf/`. The location can be overridden using option `--config-path`. Below is an example showing the command for [topology submission](user-manuals-heron-cli#submitting-a-topology): ```bash $ heron submit [cluster-name-storing-your-new-config]/[role]/[env] \ --config-path [config-folder-path-storing-your-new-config] \ /path/to/topology/my-topology.jar \ biz.acme.topologies.MyTopology ``` The implementation for each of the interfaces listed above must be on Heron's .
Project: Beam (App Definition and Development / Streaming & Messaging)
File: beam-2.6.0.md

title: "Apache Beam 2.6.0" date: 2018-08-10 00:00:01 -0800 categories: blog release aliases: /blog/2018/08/10/beam-2.6.0.html authors: pabloem rfernand <!-- Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> We are glad to present the new 2.6.0 release of Beam. This release includes multiple fixes and new functionality, such as new features in SQL and portability.<!--more--> We also spent a significant amount of time automating the release and fixing continuous integration. For more information, check the [release notes](https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12343392 ). `gRPC/protobuf` is now shaded in the majority of Apache Beam Java modules. A few modules which expose `gRPC/protobuf` on the API surface still maintain a direct dependency. Added support for the `EXISTS` and `LIKE` operators. Implemented `SUM()` aggregations. Fixed issues with the `CASE` expression. Added support for date comparisons. Added unbounded data support to `LIMIT`. Shared libraries for supporting timers and user state are now available for runner integration. Added a Universal Local Runner, which works on a single machine using portability and containerized SDK harnesses. The Flink Runner now accepts jobs using the Job API. Bounded `SplittableDoFn` (SDF) support is now available in all runners (SDF is the new I/O connector API). `HBaseIO` is the first I/O supporting Bounded SDF (using `readAll`). Improved Python `AvroIO` performance. Python `AvroIO` has a `use_fastavro` option that uses `fastavro` instead of `apache/avro`, for a ! Updated various dependency versions. Improvements to stability, performance, and documentation. According to git shortlog, the following 39 people contributed to the 2.6.0 release. Thank you to all contributors! Ahmet Altay, Alan Myrvold, Alexey Romanenko, Andrew Pilloud, Ankur Goenka, Boyuan Zhang, Charles Chen, cclauss, Daniel Oliveira, Elliott Brossard, Eric Beach, Etienne Chauchot, Eugene Kirpichov, Henning Rohde, Ismal Meja, Kai Jiang, Kasia, Kenneth Knowles, Luis Osa, Lukasz Cwik, Maria Garcia Herrero, Mark Liu, Matthias Feys, Pablo Estrada, Rafael Fernandez, Reuven Lax, Robert Bradshaw, Robert Burke, Robin Qiu, Ryan Williams, Scott Wegner, Rui Weng, Sergei Lebedev, Sindy Li, Thomas Weise, Udi Meiri, Valentyn Tymofieiev, XuMingmin, and Yifan Zou.
Project: ShardingSphere (App Definition and Development / Database)
File: document.en.md

+++ title = "Documents Contribute Guide" weight = 3 chapter = true +++ If you want to help contribute shardingsphere documents or websites, we are happy to help you! Anyone can contribute, whether you're new to a project or have been using shardingsphere for a long time, whether you're a self identified developer, end-user, or someone who can't stand typos,can contribute to documents or websites. In the contributor guide, we have mentioned how to submit Issues and pull request. here we will introduce how to submit pull request to document. Familiar with . Familiar with . Familiar with . Familiar with . Fork the master branch of . ``` shardingsphere docs community archetypes content contribute powered-by security team layouts static themes document archetypes content concepts adaptor distsql mode pluggable dev-manual downloads features encrypt governance readwrite-splitting scaling shadow sharding concept principle use-norms test-engine transaction concept principle use-norms others api-change-history faq overview quick-start user-manual shardingsphere-jdbc configuration usage shardingsphere-proxy shardingsphere-sidecar shardingsphere-scaling i18n layouts static themes ``` The ShardingSphere document is written in markdown, processed in Hugo, generated HTML, deployed in branch, and the source code is located in . source is stored in `/document/`. related document sources are stored in `/community/content/`. You can submit questions, edit content, and view other people's changes from . The page template is located in the `layouts/partials/` directory in themes. Anyone with a GitHub account can ask questions (error reports) about shardingsphere documents. If you find an error, ask questions even if you don't know how to fix it. How to ask questions? Attach the problem document link. Describe the problem in detail. Describe the problems caused to users. Propose the repair method. In ,`New issue ` asks your question. Operation steps: Locate the file you want to operate in the master branch directory structure. After the file operation is completed, pull request is raised to the master branch. Unless otherwise specified, please use Hugo `0.70.0` version. asf-site branches are updated by the official on a regular basis, you do not need to submit pull request to asf-site.
Project: ShardingSphere (App Definition and Development / Database)
File: count-encrypt-rule.en.md

+++ title = "COUNT ENCRYPT RULE" weight = 2 +++ The `COUNT ENCRYPT RULE` syntax is used to query the number of encrypt rules for specified database. {{< tabs >}} {{% tab name="Grammar" %}} ```sql CountEncryptRule::= 'COUNT' 'ENCRYPT' 'RULE' ('FROM' databaseName)? databaseName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} When `databaseName` is not specified, the default is the currently used `DATABASE`. If `DATABASE` is not used, `No database selected` will be prompted. | Column | Description | |--|-| | rule_name | rule type | | database | the database to which the rule belongs | | count | the number of the rule | Query the number of encrypt rules for specified database. ```sql COUNT ENCRYPT RULE FROM encrypt_db; ``` ```sql mysql> COUNT ENCRYPT RULE FROM encrypt_db; +--++-+ | rule_name | database | count | +--++-+ | encrypt | encrypt_db | 2 | +--++-+ 1 row in set (0.01 sec) ``` Query the number of encrypt rules for current database. ```sql COUNT ENCRYPT RULE; ``` ```sql mysql> COUNT ENCRYPT RULE; +--++-+ | rule_name | database | count | +--++-+ | encrypt | encrypt_db | 2 | +--++-+ 1 row in set (0.01 sec) ``` `COUNT`, `ENCRYPT`, `RULE`, `FROM`
Project: KICS (Provisioning / Security & Compliance)
File: ade74944-a674-4e00-859e-c6eab5bde441.md

title: Liveness Probe Is Not Defined hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ade74944-a674-4e00-859e-c6eab5bde441 Query name: Liveness Probe Is Not Defined Platform: Kubernetes Severity: <span style="color:#5bc0de">Info</span> Category: Availability URL: In case of an unresponsive container, a Liveness Probe can help your application become more available since it restarts the container. However, it can lead to cascading failures. Define one if you really need it<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="9" apiVersion: v1 kind: Pod metadata: labels: test: liveness name: liveness-exec spec: containers: name: liveness image: k8s.gcr.io/busybox args: /bin/sh -c touch /tmp/healthy; sleep 30; rm -rf /tmp/healthy; sleep 600 ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: labels: test: liveness name: liveness-exec spec: containers: name: liveness image: k8s.gcr.io/busybox args: /bin/sh -c touch /tmp/healthy; sleep 30; rm -rf /tmp/healthy; sleep 600 livenessProbe: exec: command: cat /tmp/healthy initialDelaySeconds: 5 periodSeconds: 5 apiVersion: batch/v1beta1 kind: CronJob metadata: name: hello spec: schedule: "/1 *" jobTemplate: spec: template: spec: containers: name: hello image: busybox imagePullPolicy: IfNotPresent args: /bin/sh -c date; echo Hello from the Kubernetes cluster restartPolicy: OnFailure ```
Project: KICS (Provisioning / Security & Compliance)
File: 19ebaa28-fc86-4a58-bcfa-015c9e22fe40.md

title: Containers With Added Capabilities hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 19ebaa28-fc86-4a58-bcfa-015c9e22fe40 Query name: Containers With Added Capabilities Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Containers should not have extra capabilities allowed<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="43 12" apiVersion: v1 kind: Pod metadata: name: pod2 spec: containers: name: app image: images.my-company.example/app:v4 securityContext: allowPrivilegeEscalation: false capabilities: add: ["NETADMIN", "SYSTIME"] resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" name: log-aggregator image: images.my-company.example/log-aggregator:v6 securityContext: allowPrivilegeEscalation: false resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" apiVersion: v1 kind: Pod metadata: name: pod3 spec: initContainers: name: app image: images.my-company.example/app:v4 securityContext: allowPrivilegeEscalation: false capabilities: add: ["NETADMIN", "SYSTIME"] resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" name: log-aggregator image: images.my-company.example/log-aggregator:v6 securityContext: allowPrivilegeEscalation: false resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" containers: name: app image: images.my-company.example/app:v4 ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: pod1 spec: containers: name: app image: images.my-company.example/app:v4 securityContext: allowPrivilegeEscalation: false resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" name: log-aggregator image: images.my-company.example/log-aggregator:v6 securityContext: allowPrivilegeEscalation: false resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" ``` ```yaml title="Negative test num. 2 - yaml file" apiVersion: v1 kind: Pod metadata: name: pod4 spec: containers: name: app image: images.my-company.example/app:v4 securityContext: allowPrivilegeEscalation: false capabilities: drop: ALL add: NETBINDSERVICE resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" name: log-aggregator image: images.my-company.example/log-aggregator:v6 securityContext: allowPrivilegeEscalation: false resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.10.2.md

RabbitMQ `3.10.2` is a maintenance release in the `3.10.x` release series. Please refer to the upgrade section from if upgrading from a version prior to 3.10.0. This release requires at least Erlang 23.2, and supports Erlang 24 and 25. has more details on Erlang version requirements for RabbitMQ. Release notes can be found on GitHub at . 40 to 50% throughput improvement for some workloads where AMQP 0-9-1 clients consumed from a . GitHub issue: Configuration of fallback secrets for Shovel and Federation credential obfuscation. This feature allows for secret rotation during rolling cluster node restarts. Contributed by Lajos @luos Gerecs. GitHub issue: Reduced memory footprint of individual of quorum queue consumers. GitHub issue: Reduced filesystem I/O contention for workloads where a large number of classic queues v2 (CQv2) were concurrently deleted. GitHub issue: Default log level used a four-character severity abbreviation instead of more common longer format, for example, `warn` instead of `warning`. GitHub issue: `rabbitmq-diagnostics status` now reports crypto library (OpenSSL, LibreSSL, etc) used by the runtime, as well as its version details. GitHub issue: CLI tools failed to run on Erlang 25 because of an old version of Elixir (compiled on Erlang 21) was used in the release pipeline. Erlang 25 no longer loads modules compiled on Erlang 21 or older. `rabbitmqctl setloglevel` documentation clarification. Contributed by Pter @gomoripeti Gmri (CloudAMQP). GitHub issue: `credentials_obfuscation` was upgraded To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.10.2.tar.xz` instead of the source tarball produced by GitHub.