cwielenb/CNCF-Dataset huggingface dataset:
Project: Meshery (Provisioning / Automation & Configuration)
File: kubedb-metrics.md

layout: integration title: Kubedb Metrics subtitle: Collaborative and visual infrastructure as code for Kubedb Metrics image: /assets/img/integrations/kubedb-metrics/icons/color/kubedb-metrics-color.svg permalink: extensibility/integrations/kubedb-metrics docURL: https://docs.meshery.io/extensibility/integrations/kubedb-metrics description: integrations-category: App Definition and Development integrations-subcategory: Database registrant: Artifact Hub components: featureList: [ "KubeDB simplifies many of the difficult or tedious management tasks of running a production grade databases on private and public clouds. Maintain one stack for all your stateless and stateful applications and simplify the operational complexity.", "Standard Kubernetes is all you need. If you can run Kubernetes, you can provision and manage databases using KubeDB. Use standard Kubernetes CLI and API to provision and manage databases.", "KubeDB uses Persistent Volume Claims (PVC) to dynamically provision disks for database instances. Using appropriately defined StorageClasses, KubeDB provisioned database instances are designed to scale from small development workloads up to performance-intensive workloads on private and public cloud environments." ] 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: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: avro.md

Avro is very popular in streaming data pipeline. Now seatunnel supports Avro format in kafka connector. This is an example to generate data from fake source and sink to kafka with avro format. ```bash env { parallelism = 1 job.mode = "BATCH" } source { FakeSource { row.num = 90 schema = { fields { c_map = "map<string, string>" c_array = "array<int>" c_string = string c_boolean = boolean c_tinyint = tinyint c_smallint = smallint c_int = int c_bigint = bigint c_float = float c_double = double c_bytes = bytes c_date = date c_decimal = "decimal(38, 18)" c_timestamp = timestamp c_row = { c_map = "map<string, string>" c_array = "array<int>" c_string = string c_boolean = boolean c_tinyint = tinyint c_smallint = smallint c_int = int c_bigint = bigint c_float = float c_double = double c_bytes = bytes c_date = date c_decimal = "decimal(38, 18)" c_timestamp = timestamp } } } resulttablename = "fake" } } sink { Kafka { bootstrap.servers = "kafkaCluster:9092" topic = "testavrotopicfakesource" format = avro } } ``` This is an example read data from kafka with avro format and print to console. ```bash env { parallelism = 1 job.mode = "BATCH" } source { Kafka { bootstrap.servers = "kafkaCluster:9092" topic = "testavrotopic" resulttablename = "kafka_table" kafka.auto.offset.reset = "earliest" format = avro formaterrorhandle_way = skip schema = { fields { id = bigint c_map = "map<string, smallint>" c_array = "array<tinyint>" c_string = string c_boolean = boolean c_tinyint = tinyint c_smallint = smallint c_int = int c_bigint = bigint c_float = float c_double = double c_decimal = "decimal(2, 1)" c_bytes = bytes c_date = date c_timestamp = timestamp } } } } sink { Console { sourcetablename = "kafka_table" } } ```
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: container-image.eg.md

```yaml apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: busybox spec: components: name: busybox type: webservice properties: image: busybox cmd: ["sleep", "86400"] traits: type: sidecar properties: name: sidecar-nginx image: nginx type: container-image properties: containers: containerName: busybox image: busybox-1.34.0 imagePullPolicy: IfNotPresent containerName: sidecar-nginx image: nginx-1.20 ```
Project: Tremor (App Definition and Development / Streaming & Messaging)
File: pathsegments.md

The `PathSegments` rule specifies the continuation of a path rule. |Form Variation|Description| ||| |`.<Ident>`|A terminal segment dereferencing a record field| |`<Ident><PathSegments>`|A non-terminal segment dereferencing a record field| |`[<Selector>]`|A range or index segment dereferencing an array| |`[<Selector>]`|A terminal range or index segment dereferencing an array| |`[<Selector>]<PathSegments>`|A non-terminal range or index segment dereferencing an array|
Project: YugabyteDB (App Definition and Development / Database)
File: 11-group-by.md

title: "GROUP BY" In this exercise we will query the products table and group the results by product\id, then product\name, and finally unit\price_. ``` SELECT product_id, product_name, unit_price FROM products GROUP BY product_id, product_name, unit_price; ``` This query should return 77 rows In this exercise we will query the orders table and group the results by employee\id, while only returning the total counts of order\id. ``` SELECT count(order_id), employee_id FROM orders GROUP BY employee_id; ``` This query should return 9 rows
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.24.md

layout: release date: 2024-02-26 tag: v0.7.24 store token and session on domain instead of subdomain @MUzairS15 (#10419) [Add]: Relationship between StorageClass and other k8s components @pandeyshubham03 (#10357) [Add]: Relationship between Job and other k8s resources @pandeyshubham03 (#10380) [Docker] Fix failing docker build @MUzairS15 (#10397) Ripul handoo/relationship/pod distribution budget @RipulHandoo (#10273) add: Relationship for IngressClass and other k8s resources @RipulHandoo (#10355) add: Relationship between Controller revision and other k8s resources @RipulHandoo (#10299) Updated the version in meshery-nsm-deployment.yaml @anirudh-hegde (#10388) regenerate error codes for mesheryctl @MUzairS15 (#10405) fix: failing golint-ci test for mesheryctl @RipulHandoo (#10384) [bug] Fix patterns filtering @sudhanshutech (#10363) Update theme @aabidsofi19 (#10409) Complete Rtk migration for `Connections` @sudhanshutech (#10362) [Adapter] Add support for Nighthawk @leecalcote (#10361) [UI] Enhance title and description of Environments #10364 @izuca (#10395) [bug] Fix patterns filtering @sudhanshutech (#10363) add: defined relationship link @RipulHandoo (#10401) [chore] update `golangci-lint` action to `v4` @MUzairS15 (#10400) [Adapter] Add support for Nighthawk @leecalcote (#10361) Bugs Fix @iArchitSharma (#10411) chore: remove anchor tags from frontmatter variable abstract @dextrot (#10403) [Adapter] Add support for Nighthawk @leecalcote (#10361) [Docs] Enhance Build and Release page with link to test plan @leecalcote (#10383) Update Dockerfile @MUzairS15 (#10390) Thank you to our contributors for making this release possible: @MUzairS15, @RipulHandoo, @aabidsofi19, @alphaX86, @anirudh-hegde, @dextrot, @iArchitSharma, @izuca, @l5io, @leecalcote, @pandeyshubham03, @sudhanshutech, @vishalvivekm and l5io
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_drop_tablespace.md

title: DROP TABLESPACE statement [YSQL] headerTitle: DROP TABLESPACE linkTitle: DROP TABLESPACE description: Use the DROP TABLESPACE statement to remove a tablespace from the cluster. menu: preview: identifier: ddldroptablespace parent: statements aliases: /preview/api/ysql/commands/ddldroptablespace/ type: docs Use the `DROP TABLESPACE` statement to remove a tablespace from the cluster. {{%ebnf%}} drop_tablespace {{%/ebnf%}} Only the owner or a superuser can drop a tablespace. Before dropping it, ensure that the tablespace is devoid of all database objects. Be aware that even if the current database isn't using the tablespace, objects from other databases might still occupy it. Additionally, the DROP operation may encounter issues if the tablespace is specified in the `temp_tablespaces` setting of any active session, as there could be temporary files or objects present in the tablespace. Under normal operation, an error is raised if the tablespace does not exist. Adding `IF EXISTS` will quietly ignore any non-existent tablespaces specified. Specify the name of the tablespace to be dropped. See and for full guides.
Project: ArangoDB (App Definition and Development / Database)
File: try_operation_return_as.md

+++ title = "`decltype(auto) tryoperationreturn_as(X)`" description = "Default implementation of `tryoperationreturnas(X)` ADL customisation point for `BOOSTOUTCOME_TRY`." +++ This default implementation preferentially returns whatever the input type's `.as_failure()` member function returns. `basicresult` and `basicoutcome` provide such a member function, see {{% api "auto as_failure() const &" %}}. If `.as_failure()` is not available, it will also match any `.error()` member function, which it wraps into a failure type sugar using {{% api "failure(T &&, ...)" %}}. Requires: That the expression `std::declval<T>().as_failure()` and/or `std::declval<T>().error()` is a valid expression. Namespace: `BOOSTOUTCOMEV2_NAMESPACE` Header: `<boost/outcome/try.hpp>`
Project: Kapitan (Provisioning / Automation & Configuration)
File: documentation.md

comments: true tags: community Our documentation usully prevents new users from adopting Kapitan. Help us improve by contributing with fixes and keeping it up-to-date. Write articles on Kapitan and share your way of working. Inspire others, and reach out to have your article published / endorsed by us. Find something odd? Let us know or change it yourself: you can edit pages of this website on Github by clicking the pencil icon at the top right of this page! We use to generate our gh-pages from `.md` files under docs/ folder. Updating our gh-pages is therefore a two-step process. Submit a PR for our master branch that updates the `.md` file(s). Test how the changes would look like when deployed to gh-pages by serving it on localhost: Edit the `strict` property in `mkdocs.yml` and set it to `false`. `make localservedocumentation` Now the documentation site should be available at . Once the above PR has been merged, use `mkdocs gh-deploy` command to push the commit that updates the site content to your own gh-pages branch. Make sure that you already have this gh-pages branch in your fork that is up-to-date with our gh-pages branch such that the two branches share the commit history (otherwise Github would not allow PRs to be created). ```text COMMITMSG="your commit message to replace" make mkdocsgh_deploy ``` After it's pushed, create a PR that targets our gh-pages branch from your gh-pages branch.
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_list_clusters.md

title: "Command - devspace list clusters" sidebar_label: devspace list clusters Lists all connected clusters ``` devspace list clusters [flags] ``` ``` List all connected user clusters Example: devspace list clusters ``` ``` --all Show all available clusters including hosted DevSpace cloud clusters -h, --help help for clusters --provider string Cloud Provider to use ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile string The devspace profile to use (if there is any) --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) ```
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: feat-12251.en.md

Optimize performance of the RocksDB-based persistent session. Reduce RAM usage and frequency of database requests. Introduce dirty session state to avoid frequent mria transactions Introduce an intermediate buffer for the persistent messages Use separate tracks of PacketIds for QoS1 and QoS2 messages Limit the number of continuous ranges of inflight messages to one per stream
Project: KICS (Provisioning / Security & Compliance)
File: 5915c20f-dffa-4cee-b5d4-f457ddc0151a.md

title: Empty Array hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 5915c20f-dffa-4cee-b5d4-f457ddc0151a Query name: Empty Array Platform: OpenAPI Severity: <span style="color:#5bc0de">Info</span> Category: Structure and Semantics URL: All array fields should not be empty<br> ```json title="Positive test num. 1 - json file" hl_lines="43" { "openapi": "3.0.0", "info": { "title": "Simple API overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response", "content": { "application/json": { "examples": { "foo": { "value": { "versions": [ { "status": "CURRENT", "updated": "2011-01-21T11:33:21Z", "id": "v2.0", "links": [ { "href": "http://127.0.0.1:8774/v2/", "rel": "self" } ] } ] } } } } } } } } } }, "security": [] } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="25" openapi: 3.0.0 info: title: Simple API overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response content: application/json: examples: foo: value: versions: status: CURRENT updated: "2011-01-21T11:33:21Z" id: v2.0 links: href: http://127.0.0.1:8774/v2/ rel: self security: [] ``` ```json title="Negative test num. 1 - json file" { "openapi": "3.0.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response", "content": { "application/json": { "examples": { "foo": { "value": { "versions": [ { "status": "CURRENT", "updated": "2011-01-21T11:33:21Z", "id": "v2.0", "links": [ { "href": "http://127.0.0.1:8774/v2/", "rel": "self" } ] } ] } } } } } } } } } }, "security": [ { "OAuth2": [ "scope1", "scope2" ] } ], "components": { "securitySchemes": [ { "exampleSecurity": { "type": "http", "scheme": "basic" } } ] } } ``` ```yaml title="Negative test num. 2 - yaml file" openapi: 3.0.0 info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response content: application/json: examples: foo: value: versions: status: CURRENT updated: "2011-01-21T11:33:21Z" id: v2.0 links: href: http://127.0.0.1:8774/v2/ rel: self security: OAuth2: scope1 scope2 components: securitySchemes: exampleSecurity: type: http scheme: basic ```
Project: FOSSA (Provisioning / Security & Compliance)
File: bundler.md

Ideal `bundler` installed locally `Gemfile` or `Gemfile.lock` file present in your project Minimum `Gemfile.lock` file present in your project Directories containing `Gemfile` or `Gemfile.lock` files are considered Ruby projects. Subdirectory scans are not affected by the discovery of a Ruby project.
Project: KICS (Provisioning / Security & Compliance)
File: 3d658f8b-d988-41a0-a841-40043121de1e.md

title: Secrets As Environment Variables hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 3d658f8b-d988-41a0-a841-40043121de1e Query name: Secrets As Environment Variables Platform: Kubernetes Severity: <span style="color:#edd57e">Low</span> Category: Secret Management URL: Container should not use secrets as environment variables<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="17 12 30" apiVersion: v1 kind: Pod metadata: name: secret-env-pod spec: containers: name: mycontainer image: redis env: name: SECRET_USERNAME valueFrom: secretKeyRef: name: mysecret key: username name: SECRET_PASSWORD valueFrom: secretKeyRef: name: mysecret key: password restartPolicy: Never apiVersion: v1 kind: Pod metadata: name: envfrom-secret spec: containers: name: envars-test-container image: nginx envFrom: secretRef: name: test-secret ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: secret-env-pod spec: containers: name: mycontainer image: redis restartPolicy: Never ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: count.md

title: "Count" <!-- 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. --> {{< localstorage language language-py >}} {{< button-pydoc path="apache_beam.transforms.combiners" class="Count" >}} Counts the number of elements within each aggregation. In the following example, we create a pipeline with two `PCollection`s of produce. Then, we apply `Count` to get the total number of elements in different ways. We use `Count.Globally()` to count all elements in a `PCollection`, even if there are duplicate elements. {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHONCountGlobally" show="countglobally" >}} {{< /playground >}} We use `Count.PerKey()` to count the elements for each unique key in a `PCollection` of key-values. {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHONCountPerKey" show="countper_key" >}} {{< /playground >}} We use `Count.PerElement()` to count the only the unique elements in a `PCollection`. {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHONCountPerElement" show="countper_element" >}} {{< /playground >}} N/A {{< button-pydoc path="apache_beam.transforms.combiners" class="Count" >}}
Project: VMClarity (Provisioning / Security & Compliance)
File: SECURITY.md

This document outlines security procedures and general policies for the VMClarity project. The VMClarity team and community take all security bugs in VMClarity seriously. Thank you for improving the security of VMClarity. We appreciate your efforts and responsible disclosure and will make every effort to acknowledge your contributions. Report security bugs by emailing `oss-security@cisco.com`. The lead maintainer will acknowledge your email within 48 hours, and will send a more detailed response within 48 hours indicating the next steps in handling your report. After the initial reply to your report, the security team will endeavor to keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance. When the security team receives a security bug report, they will assign it to a primary handler. This person will coordinate the fix and release process, involving the following steps: Confirm the problem and determine the affected versions. Audit code to find any potential similar problems. Prepare fixes for all releases still under maintenance. These fixes will be released as quickly as possible. If you have suggestions on how this process could be improved please submit a pull request.
Project: KICS (Provisioning / Security & Compliance)
File: 3e293410-d5b8-411f-85fd-7d26294f20c9.md

title: VPC Without Network Firewall hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 3e293410-d5b8-411f-85fd-7d26294f20c9 Query name: VPC Without Network Firewall Platform: CloudFormation Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: VPC should have a Network Firewall associated<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="3" AWSTemplateFormatVersion: '2010-09-09' Resources: myVPC11: Type: AWS::EC2::VPC Properties: CidrBlock: 10.0.0.0/16 EnableDnsSupport: 'false' EnableDnsHostnames: 'false' InstanceTenancy: dedicated SampleFirewall: Type: AWS::NetworkFirewall::Firewall Properties: FirewallName: SampleFirewallName FirewallPolicyArn: !Ref SampleFirewallPolicy VpcId: !Ref myVPC SubnetMappings: SubnetId: !Ref SampleSubnet1 SubnetId: !Ref SampleSubnet2 Description: Firewall description goes here ``` ```json title="Positive test num. 2 - json file" hl_lines="21" { "AWSTemplateFormatVersion": "2010-09-09", "Resources": { "SampleFirewall": { "Properties": { "Description": "Firewall description goes here", "FirewallName": "SampleFirewallName", "FirewallPolicyArn": "SampleFirewallPolicy", "SubnetMappings": [ { "SubnetId": "SampleSubnet1" }, { "SubnetId": "SampleSubnet2" } ], "VpcId": "myVPC" }, "Type": "AWS::NetworkFirewall::Firewall" }, "myVPC11": { "Properties": { "CidrBlock": "10.0.0.0/16", "EnableDnsHostnames": "false", "EnableDnsSupport": "false", "InstanceTenancy": "dedicated" }, "Type": "AWS::EC2::VPC" } } } ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: '2010-09-09' Resources: myVPC1: Type: AWS::EC2::VPC Properties: CidrBlock: 10.0.0.0/16 EnableDnsSupport: 'false' EnableDnsHostnames: 'false' InstanceTenancy: dedicated SampleFirewall: Type: AWS::NetworkFirewall::Firewall Properties: FirewallName: SampleFirewallName FirewallPolicyArn: !Ref SampleFirewallPolicy VpcId: !Ref myVPC1 SubnetMappings: SubnetId: !Ref SampleSubnet1 SubnetId: !Ref SampleSubnet2 Description: Firewall description goes here ``` ```json title="Negative test num. 2 - json file" { "AWSTemplateFormatVersion": "2010-09-09", "Resources": { "SampleFirewall": { "Properties": { "Description": "Firewall description goes here", "FirewallName": "SampleFirewallName", "FirewallPolicyArn": "SampleFirewallPolicy", "SubnetMappings": [ { "SubnetId": "SampleSubnet1" }, { "SubnetId": "SampleSubnet2" } ], "VpcId": "myVPC1" }, "Type": "AWS::NetworkFirewall::Firewall" }, "myVPC1": { "Properties": { "CidrBlock": "10.0.0.0/16", "EnableDnsHostnames": "false", "EnableDnsSupport": "false", "InstanceTenancy": "dedicated" }, "Type": "AWS::EC2::VPC" } } } ```
Project: ArangoDB (App Definition and Development / Database)
File: move_constructor.md

+++ title = "`basicresult(basicresult &&)`" description = "Move constructor. Constexpr, triviality and noexcept propagating." categories = ["constructors", "implicit-constructors", "move-constructors"] weight = 110 +++ Move constructor. Requires: that `valuetype` and `errortype` both implement a move constructor. Complexity: Same as for `valuetype`'s and `errortype`'s move constructors. Constexpr, triviality and noexcept of underlying operations is propagated. Guarantees: If an exception is thrown during the operation, the object is left in a partially completed state, as per the normal rules for the same operation on a `struct`.