cwielenb/CNCF-Dataset huggingface dataset:
Project: YDB (App Definition and Development / Database)
File: datatypes_primitive_number.md

| Type | Description | Notes | | -- | -- | -- | | `Bool ` | Boolean value. | | `Int8` | A signed integer.<br/>Acceptable values: from -2<sup>7</sup> to 2<sup>7</sup>1. | | `Int16` | A signed integer.<br/>Acceptable values: from 2<sup>15</sup> to 2<sup>15</sup>1. | | `Int32` | A signed integer.<br/>Acceptable values: from 2<sup>31</sup> to 2<sup>31</sup>1. | | `Int64` | A signed integer.<br/>Acceptable values: from 2<sup>63</sup> to 2<sup>63</sup>1. | | `Uint8` | An unsigned integer.<br/>Acceptable values: from 0 to 2<sup>8</sup>1. | | `Uint16` | An unsigned integer.<br/>Acceptable values: from 0 to 2<sup>16</sup>1. | | `Uint32` | An unsigned integer.<br/>Acceptable values: from 0 to 2<sup>32</sup>1. | | `Uint64` | An unsigned integer.<br/>Acceptable values: from 0 to 2<sup>64</sup>1. | | `Float` | A real number with variable precision, 4 bytes in size. | {% if featuremaptables %}Can't be used in the primary key{% endif %} | | `Double` | A real number with variable precision, 8 bytes in size. | {% if featuremaptables %}Can't be used in the primary key{% endif %} | | `Decimal` | A real number with the specified precision, up to 35 decimal digits | {% if featuremaptables %}When used in table columns, the precision is fixed: Decimal(22,9){% endif %} | {% if featuremaptables %} |`DyNumber` | A binary representation of a real number with an accuracy of up to 38 digits.<br/>Acceptable values: positive numbers from 110<sup>-130</sup> up to 110<sup>126</sup>1, negative numbers from -110<sup>126</sup>1 to -110<sup>-130</sup>, and 0.<br/>Compatible with the `Number` type in AWS DynamoDB. It's not recommended for {{ backendnamelower }}-native applications. | | {% endif %}
Project: ArangoDB (App Definition and Development / Database)
File: implicit_failure_error_make_error_code_copy_constructor.md

+++ title = "`basicoutcome(const failuretype<EC> &)`" description = "Implicit error-from-failure-type-sugar copy constructor. Available if `predicate::enablemakeerrorcodecompatible_conversion<void, EC, void, void>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "implicit-constructors", "tagged-constructors"] weight = 531 +++ Implicit error-from-failure-type-sugar copy constructor used to disambiguate the construction of the error type. Calls {{% api "void onoutcomecopyconstruction(T *, U &&) noexcept" %}} with `this` and `const failuretype<EC> &`. Requires: `predicate::enablemakeerrorcodecompatible_conversion<void, EC, void, void>` is true. Complexity: Same as for the `error_type` constructor which accepts `EC`. Constexpr, triviality and noexcept of underlying operations is propagated.
Project: KICS (Provisioning / Security & Compliance)
File: a4d32883-aac7-42e1-b403-9415af0f3846.md

title: Serverless API Access Logging Setting Undefined hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: a4d32883-aac7-42e1-b403-9415af0f3846 Query name: Serverless API Access Logging Setting Undefined Platform: ServerlessFW Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Serverless FW API should have HTTP Access Logging enabled<br> ```yml title="Positive test num. 1 - yml file" hl_lines="17" service: myservice frameworkVersion: '2' provider: name: aws logs: httpApi: format: '{ "requestId":"$context.requestId", "ip": "$context.identity.sourceIp", "requestTime":"$context.requestTime", "httpMethod":"$context.httpMethod","routeKey":"$context.routeKey", "status":"$context.status","protocol":"$context.protocol", "responseLength":"$context.responseLength" }' restApi: accessLogging: false format: 'requestId: $context.requestId' executionLogging: true level: INFO fullExecutionData: true role: arn:aws:iam::123456:role roleManagedExternally: false websocket: accessLogging: true format: 'requestId: $context.requestId' executionLogging: true level: INFO fullExecutionData: true frameworkLambda: true ``` ```yml title="Negative test num. 1 - yml file" service: myservice frameworkVersion: '2' provider: name: aws logs: httpApi: format: '{ "requestId":"$context.requestId", "ip": "$context.identity.sourceIp", "requestTime":"$context.requestTime", "httpMethod":"$context.httpMethod","routeKey":"$context.routeKey", "status":"$context.status","protocol":"$context.protocol", "responseLength":"$context.responseLength" }' restApi: accessLogging: true format: 'requestId: $context.requestId' executionLogging: true level: INFO fullExecutionData: true role: arn:aws:iam::123456:role roleManagedExternally: false websocket: accessLogging: true format: 'requestId: $context.requestId' executionLogging: true level: INFO fullExecutionData: true frameworkLambda: true ```
Project: NeuVector (Provisioning / Security & Compliance)
File: CONTRIBUTING.md

Welcome to Kubernetes. We are excited about the prospect of you joining our ! The Kubernetes community abides by the CNCF . Here is an excerpt: As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities. We have full documentation on how to get started contributing here: <! If your repo has certain guidelines for contribution, put them here ahead of the general k8s resources --> Kubernetes projects require that you sign a Contributor License Agreement (CLA) before we can accept your pull requests - Main contributor documentation, or you can just jump directly to the - Common resources for existing developers - We have a diverse set of mentorship programs available that are always looking for volunteers! <! Custom Information - if you're copying this template for the first time you can add custom content here, for example: - Replace `kubernetes-users` with your slack channel string, this will send users directly to your channel. -->
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-perf.md

layout: default title: mesheryctl-perf permalink: reference/mesheryctl/perf redirect_from: reference/mesheryctl/perf/ type: reference display-title: "false" language: en command: perf subcommand: nil Performance Management Performance Management & Benchmarking. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl perf [flags] </div> </pre> Run performance test: <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl perf apply test-3 --name "a quick stress test" --url http://192.168.1.15/productpage --qps 300 --concurrent-requests 2 --duration 30s </div> </pre> List performance profiles: <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl perf profile sam-test </div> </pre> List performance results: <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl perf result sam-test </div> </pre> Display Perf profile in JSON or YAML: <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl perf result -o json </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl perf result -o yaml </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for perf -o, --output-format string (optional) format to display in [json|yaml] -t, --token string (required) Path to meshery auth config -y, --yes (optional) assume yes for user interactive prompts. </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -v, --verbose verbose output </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: StackRox (Provisioning / Security & Compliance)
File: pull_request_template.md

A detailed explanation of the changes in your PR. Feel free to remove this section if it is overkill for your PR, and the title of your PR is sufficiently descriptive. [ ] Investigated and inspected CI test results [ ] Unit test and regression tests added [ ] Evaluated and added CHANGELOG entry if required [ ] Determined and documented upgrade steps and merge into ) If any of these don't apply, please comment below. TODO(replace-me) Use this space to explain how you validated that your change functions exactly how you expect it. Feel free to attach JSON snippets, curl commands, screenshots, etc. Apply a simple benchmark: would the information you provided convince any reviewer or any external reader that you did enough to validate your change. It is acceptable to assume trust and keep this section light, e.g. as a bullet-point list. It is acceptable to skip testing in cases when CI is sufficient, or it's a markdown or code comment change only. It is also acceptable to skip testing for changes that are too taxing to test before merging. In such case you are responsible for the change after it gets merged which includes reverting, fixing, etc. Make sure you validate the change ASAP after it gets merged or explain in PR when the validation will be performed. Explain here why you skipped testing in case you did so. Have you created automated tests for your change? Explain here which validation activities you did manually and why so. In addition to reviewing code here, reviewers must also review testing and request further testing in case the performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the performed testing and you are satisfied with it.
Project: KOTS (App Definition and Development / Application Definition & Image Build)
File: redaction-reports.md

Support bundles are sanitized with user-provided redactors. Statistics on what redactors were activated and where should be provided. Users can see what redactors were activated, and what lines they affected. Users cannot see what, specifically, was redacted. If multiple redactors triggered on the same line, users cannot see what redaction is attributable to which redactor. Users create custom redactors for support bundles, and it can be difficult to validate that they are functioning. Redaction reports allow users to see that their redactors are having an effect. Troubleshoot is modified to collect information on what redactions were applied, and where. This information is then returned when generating a support bundle via the API, or POSTed with the completed bundle if generated from the CLI. Kots stores this in postgres, and makes it available to the UI via a REST api. Redactions are collected and stored as the following objects by troubleshoot: ```go type RedactionList struct { ByRedactor mapRedaction ByFile mapRedaction } type Redaction struct { RedactorName string CharactersRemoved int Line int File string } ``` These are then exposed via GET at `/api/v1/troubleshoot/supportbundle/{bundleId}/redactions` with a response type that includes error/success: ```go type GetSupportBundleRedactionsResponse struct { Redactions redact.RedactionList `json:"redactions"` Success bool `json:"success"` Error string `json:"error,omitempty"` } ``` Redactions can be set for a bundle with a PUT to the same path (`/api/v1/troubleshoot/supportbundle/{bundleId}/redactions`) with the following structure: ```go type PutSupportBundleRedactions struct { Redactions redact.RedactionList `json:"redactions"` } ``` Redaction reports will be stored as a new mediumtext column 'redactions' in the 'supportbundle' table. Within troubleshoot, the ResultRequest type is modified to add a URI to upload redaction reports to: ```go type ResultRequest struct { URI string `json:"uri" yaml:"uri"` Method string `json:"method" yaml:"method"` RedactURI string `json:"redactUri" yaml:"redactUri"` // the URI to POST redaction reports to } ``` When kotsadm generates troubleshoot specs, RedactURI will be populated with the proper value. (This is already done for URI here) Some information leakage from redaction reports is possible, but should be minimal - limited to 'this was an IP address' and similar.
Project: Trivy (Provisioning / Security & Compliance)
File: chainguard.md

Trivy supports the following scanners for OS packages. | Scanner | Supported | | :--: | :-: | | SBOM | | | Vulnerability | | | License | | The table below outlines the features offered by Trivy. | Feature | Supported | | :--: | :-: | | Detect unfixed vulnerabilities | - | | | | Same as . Chainguard offers its own security advisories, and these are utilized when scanning Chainguard for vulnerabilities. Everything else is the same as . See . Same as .
Project: Harbor (Provisioning / Container Registry)
File: 10-08-User-can-not-pull-image-exceed-vulnerability-severity-setting.md

10-08 user can not pull image exceed vulnerability severity ======= To verify user can not pull image exceed vulnerability severity setting. User guide. This test requires that one Harbor instance is running and available. Harbor is installed with trivy enable. A Linux host with Docker client installed. Trivy has been updated to the latest. Login harbor as admin. Go to configuration. Set vulnerability severity limit to medium and save configuration. Push some images with vulnerability and scan them. On a docker client, user pull an image with high vulnerability severity. Step5 pull request should be refused. None
Project: StarRocks (App Definition and Development / Database)
File: ADMIN_SHOW_REPLICA_STATUS.md

displayed_sidebar: "English" This statement is used to show the status of replicas for a table or a partition. :::tip This operation requires the SYSTEM-level OPERATE privilege. You can follow the instructions in to grant this privilege. ::: ```sql ADMIN SHOW REPLICA STATUS FROM [dbname.]tblname [PARTITION (p1, ...)] [where_clause] ``` ```sql where_clause: WHERE STATUS [!]= "replica_status" ``` ```plain text replica_status: OK: The replica is healthy DEAD: The Backend of replica is not available VERSION_ERROR: The replica data version is missing SCHEMA_ERROR: The schema hash of replica is incorrect MISSING: The replica does not exist ``` View the status of all replicas of the table. ```sql ADMIN SHOW REPLICA STATUS FROM db1.tbl1; ``` View the replica of a partition with the status of VERSION_ERROR. ```sql ADMIN SHOW REPLICA STATUS FROM tbl1 PARTITION (p1, p2) WHERE STATUS = "VERSION_ERROR"; ``` View all unhealthy replicas of the table. ```sql ADMIN SHOW REPLICA STATUS FROM tbl1 WHERE STATUS != "OK"; ```
Project: Dex (Provisioning / Security & Compliance)
File: README.md

Using gRPC, a client application can directly call methods on a server application as if it was a local object. The schema for Dex's gRPC API calls is defined in . is an example client program that makes a bunch of API calls to the dex server. For further details on the Dex API refer the . Before running the client or the server, TLS credentials have to be setup for secure communication. Run the `cred-gen` script to create TLS credentials for running this example. This script generates a `ca.crt`, `server.crt`, `server.key`, `client.crt`, and `client.key`. ``` export SAN=IP.1:127.0.0.1 ./examples/grpc-client/cert-gen ``` To verify that the server and client certificates were signed by the CA, run the following commands: ``` openssl verify -CAfile ca.crt server.crt openssl verify -CAfile ca.crt client.crt ``` To expose the gRPC service, the gRPC option must be enabled via the dex config file as shown below. ```yaml grpc: addr: 127.0.0.1:5557 tlsCert: server.crt tlsKey: server.key ``` Start an instance of the dex server with an in-memory data store: ``` ./bin/dex serve examples/grpc-client/config.yaml ``` Finally run the Dex client providing the CA certificate, client certificate and client key as arguments. ``` ./bin/grpc-client -ca-crt=ca.crt -client-crt=client.crt -client-key=client.key ``` Running the gRPC client will cause the following API calls to be made to the server CreatePassword ListPasswords VerifyPassword DeletePassword Run the following command to destroy all the credentials files that were created by the `cert-gen` script: ``` ./examples/grpc-client/cert-destroy ```
Project: KICS (Provisioning / Security & Compliance)
File: 2730c169-51d7-4ae7-99b5-584379eff1bb.md

title: BOM - AWS MSK hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 2730c169-51d7-4ae7-99b5-584379eff1bb Query name: BOM - AWS MSK Platform: CloudFormation Severity: <span style="color:#CCCCCC">Trace</span> Category: Bill Of Materials URL: A list of MSK resources specified. Amazon Managed Streaming for Apache Kafka (Amazon MSK) is a fully managed service that enables you to build and run applications that use Apache Kafka to process streaming data.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="3" Description: MSK Cluster with all properties Resources: TestCluster: Type: 'AWS::MSK::Cluster' Properties: ClusterName: ClusterWithAllProperties KafkaVersion: 2.2.1 NumberOfBrokerNodes: 3 EnhancedMonitoring: PER_BROKER EncryptionInfo: EncryptionAtRest: DataVolumeKMSKeyId: ReplaceWithKmsKeyArn EncryptionInTransit: ClientBroker: TLS InCluster: true OpenMonitoring: Prometheus: JmxExporter: EnabledInBroker: "true" NodeExporter: EnabledInBroker: "true" ConfigurationInfo: Arn: ReplaceWithConfigurationArn Revision: 1 ClientAuthentication: Tls: CertificateAuthorityArnList: ReplaceWithCAArn Tags: Environment: Test Owner: QATeam BrokerNodeGroupInfo: BrokerAZDistribution: DEFAULT InstanceType: kafka.m5.large SecurityGroups: ReplaceWithSecurityGroupId StorageInfo: EBSStorageInfo: VolumeSize: 100 ClientSubnets: ReplaceWithSubnetId1 ReplaceWithSubnetId2 ReplaceWithSubnetId3 ConnectivityInfo: PublicAccess: Type: SERVICEPROVIDEDEIPS ``` ```json title="Positive test num. 2 - json file" hl_lines="4" { "Description": "MSK Cluster with all properties", "Resources": { "TestCluster3": { "Type": "AWS::MSK::Cluster", "Properties": { "ClusterName": "ClusterWithAllProperties", "KafkaVersion": "2.2.1", "NumberOfBrokerNodes": 3, "EnhancedMonitoring": "PER_BROKER", "OpenMonitoring": { "Prometheus": { "JmxExporter": { "EnabledInBroker": "true" }, "NodeExporter": { "EnabledInBroker": "true" } } }, "ConfigurationInfo": { "Arn": "ReplaceWithConfigurationArn", "Revision": 1 }, "ClientAuthentication": { "Tls": { "CertificateAuthorityArnList": [ "ReplaceWithCAArn" ] } }, "Tags": { "Environment": "Test", "Owner": "QATeam" }, "BrokerNodeGroupInfo": { "BrokerAZDistribution": "DEFAULT", "InstanceType": "kafka.m5.large", "SecurityGroups": [ "ReplaceWithSecurityGroupId" ], "StorageInfo": { "EBSStorageInfo": { "VolumeSize": 100 } }, "ClientSubnets": [ "ReplaceWithSubnetId1", "ReplaceWithSubnetId2", "ReplaceWithSubnetId3" ] } } } } } ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: '2010-09-09' Resources: myDistribution: Type: AWS::CloudFront::Distribution Properties: DistributionConfig: Enabled: true ``` ```json title="Negative test num. 2 - json file" { "AWSTemplateFormatVersion": "2010-09-09", "Resources": { "myDistribution": { "Type": "AWS::CloudFront::Distribution", "Properties": { "DistributionConfig": { "Enabled": "true" } } } } } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: linkerd.md

layout: integration title: Linkerd subtitle: Collaborative and visual infrastructure as code for Linkerd image: /assets/img/integrations/linkerd/icons/color/linkerd-color.svg permalink: extensibility/integrations/linkerd docURL: https://docs.meshery.io/extensibility/adapters/linkerd description: integrations-category: Cloud Native Network integrations-subcategory: Service Mesh registrant: Artifact Hub components: featureList: [ "Visually configure and operate Linkerd with real-time topology", "Use Linkerd best practice designs and templates", "Design Linkerd Service Profiles" ] 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: Beam (App Definition and Development / Streaming & Messaging)
File: bounded-splittable-dofn-support-status.md

type: runners title: "Bounded Splittable DoFn Support Status" layout: "capability-template" <!-- 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. --> <!-- Summary table --> {{< documentation/capability-matrix-big cap-data="capability-matrix" cap-view="full" cap-index=1 >}}
Project: in-toto (Provisioning / Security & Compliance)
File: layout-creation-example.md

While it is possible to write an in-toto layout from scratch using a text editor and the JSON format, the preferred way is to use the in-toto model classes provided by the reference implementation. This document shows how to use in-toto's model classes and their convenience methods to create a supply chain layout like the one that is being used in the in-toto demo. Take a look at the for more details about the supply chain represented by this layout. ```python from securesystemslib.signer import CryptoSigner from in_toto.models.layout import Layout, Step, Inspection from in_toto.models.metadata import Metablock alice = CryptoSigner.generate_ed25519() bob = CryptoSigner.generate_ed25519() carl = CryptoSigner.generate_ed25519() layout = Layout() for key in [bob, carl]: keydict = key.publickey.to_dict() keydict["keyid"] = key.publickey.keyid layout.addfunctionarykey(key_dict) layout.setrelativeexpiration(months=4) step_clone = Step(name="clone") stepclone.pubkeys = [bob.publickey.keyid] stepclone.setexpectedcommandfrom_string( "git clone https://github.com/in-toto/demo-project.git") stepclone.addproductrulefrom_string("CREATE demo-project/foo.py") stepclone.addproductrulefrom_string("DISALLOW *") step_update = Step(name="update-version") stepupdate.pubkeys = [bob.publickey.keyid] stepupdate.addmaterialrulefrom_string( "MATCH demo-project/* WITH PRODUCTS FROM clone") stepupdate.addmaterialrulefrom_string("DISALLOW *") stepupdate.addproductrulefrom_string("ALLOW demo-project/foo.py") stepupdate.addproductrulefrom_string("DISALLOW *") step_package = Step(name="package") steppackage.pubkeys = [carl.publickey.keyid] steppackage.setexpectedcommandfrom_string( "tar --exclude '.git' -zcvf demo-project.tar.gz demo-project") steppackage.addmaterialrulefrom_string( "MATCH demo-project/* WITH PRODUCTS FROM update-version") steppackage.addmaterialrulefrom_string("DISALLOW *") steppackage.addproductrulefrom_string("CREATE demo-project.tar.gz") steppackage.addproductrulefrom_string("DISALLOW *") inspection = Inspection(name="untar") inspection.setrunfrom_string("tar xzf demo-project.tar.gz") inspection.addmaterialrulefromstring( "MATCH demo-project.tar.gz WITH PRODUCTS FROM package") inspection.addproductrulefromstring( "MATCH demo-project/foo.py WITH PRODUCTS FROM update-version") layout.steps = [stepclone, stepupdate, step_package] layout.inspect = [inspection] metablock = Metablock(signed=layout) metablock.create_signature(alice) metablock.dump("root.layout") ```