cwielenb/CNCF-Dataset huggingface dataset:
Project: Shifu (Provisioning / Automation & Configuration)
File: telemetry-service-MinIO.md

Telemetry Service is a standalone service that takes telemetry data collected by `deviceShifu` and fan-out it to designated endpoints for future process. Let telemetry service support pushing telemetries to MinIO endpoints. Let telemetry service support get/list objects. Telemetry will be served as an HTTP server. deviceShifu get the file content from physical devices, then send the content to telemetry service, telemetry service will upload file to MinIO, file would name like `{device-name}/{time(RFC3339)}.{file-extension}`, file-extension and bucket will be set by MinIOSetting. Request Struct: ```go type TelemetryRequest struct { RawData []byte `json:"rawData,omitempty"` MinIOSetting *MinIOSetting `json:"minIOSetting,omitempty"` } type MinIOSetting struct { Secret *string `json:"Secret,omitempty"` AccessKey *string `json:"AccessKey,omitempty"` SecretKey *string `json:"SecretKey,omitempty"` RequestTimeoutMS *int64 `json:"RequestTimeoutMS,omitempty"` Bucket *string `json:"Bucket,omitempty"` FileExtension *string `json:"FileExtension,omitempty"` ServerAddress *string `json:"ServerAddress,omitempty"` } ``` Requesting process ```mermaid graph TD deviceShifu -->|Get file content| Device Device -->|Return content| deviceShifu deviceShifu -->|Send request| TelemetryService TelemetryService -->|Save file| MinIO ``` If you want to upload a big file(like 2~200mb), you need set a larger timeout, you can set telemetryTimeoutInMilliseconds(when deviceShifu get file from Device) at configmap.yaml, then you should set RequestTimeoutMS at telemetryservice.yaml. There is an example in `examples/minioTelemetryService/deployment/`.
Project: ClickHouse (App Definition and Development / Database)
File: v20.8.6.6-lts.md

Backported in : Fix bug with MySQL database. When MySQL server used as database engine is down some queries raise Exception, because they try to get tables from disabled server, while it's unnecessary. For example, query `SELECT ... FROM system.parts` should work only with MergeTree tables and don't touch MySQL database at all. (). Backported in : Fixed the inconsistent behaviour when a part of return data could be dropped because the set for its filtration wasn't created. (). Backported in : Fix processing of very large entries in replication queue. Very large entries may appear in ALTER queries if table structure is extremely large (near 1 MB). This fixes . (). Backported in : Fix DROP TABLE for Distributed (racy with INSERT). (). Backported in : Fix rapid growth of metadata when using MySQL Master -> MySQL Slave -> ClickHouse MaterializeMySQL Engine, and `slaveparallelworker` enabled on MySQL Slave, by properly shrinking GTID sets. This fixes . (). Backported in : Now when parsing AVRO from input the LowCardinality is removed from type. Fixes . (). Backported in : Fixed . (). Backported in : Fix rare silent crashes when query profiler is on and ClickHouse is installed on OS with glibc version that has (supposedly) broken asynchronous unwind tables for some functions. This fixes . This fixes . ().
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: opa-dotnet-asp-core.md

title: ASP.NET Core OPA Authorization labels: category: application layer: network type: poweredbyopa code: https://github.com/me-viper/OpaDotNet.Extensions https://www.nuget.org/packages/OpaDotNet.Extensions.AspNetCore/ inventors: andriikurochka Open Policy Agent (OPA) ASP.NET core authorization infrastructure
Project: ClickHouse (App Definition and Development / Database)
File: v21.5.5.12-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Kafka storage may support parquet format messages. (). Backported in : Some `ALTER PARTITION` queries might cause `Part A intersects previous part B` and `Unexpected merged part C intersecting drop range D` errors in replication queue. It's fixed. Fixes . (). Backported in : Fixed using const `DateTime` value vs `DateTime64` column in WHERE. ... (). Backported in : Bug: explain pipeline with` select xxx final `shows wrong pipeline: ``` dell123 :) explain pipeline select z from prewheremoveselect_final final;. (). Backported in : Fix race condition which could happen in RBAC under a heavy load. This PR fixes , ,. (). Backported in : Fix abnormal server termination due to hdfs becoming not accessible during query execution. Closes . (). Backported in : Fix wrong typo at StorageMemory, this bug was introduced at , now fixed, Closes . ().
Project: YugabyteDB (App Definition and Development / Database)
File: yba_provider_kubernetes_list.md

List Kubernetes YugabyteDB Anywhere providers List Kubernetes YugabyteDB Anywhere providers ``` yba provider kubernetes list [flags] ``` ``` -h, --help help for list ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -n, --name string [Optional] The name of the provider for the action. Required for create, delete, describe, update. -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage a YugabyteDB Anywhere K8s provider
Project: Meshery (Provisioning / Automation & Configuration)
File: osm-past-results.md

layout: past-results-layout title: Meshery-OSM Past Results permalink: installation/compatibility-matrix/meshery-osm-past-results abstract: a complete compatibility matrix and project test status dashboard. language: en display-title: "false" list: exclude type: "project" service-mesh: "meshery-osm" subheading: Meshery-OSM
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_routes.md

+++ title = "googlecomputeroutes resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputeroutes" identifier = "inspec/resources/gcp/googlecomputeroutes.md googlecomputeroutes resource" parent = "inspec/resources/gcp" +++ A `googlecomputeroutes` is used to test a Google Route resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputeroutes(project: 'chef-gcp-inspec') do its('count') { should be >= 1 } its('dest_ranges') { should include '15.0.0.0/24' } its('nexthopips') { should include '10.2.0.1' } its('priorities') { should include '100' } end ``` Properties that can be accessed from the `googlecomputeroutes` resource: See the resource for more information. `dest_ranges` : an array of `googlecomputeroute` dest_range `descriptions` : an array of `googlecomputeroute` description `names` : an array of `googlecomputeroute` name `networks` : an array of `googlecomputeroute` network `priorities` : an array of `googlecomputeroute` priority `tags` : an array of `googlecomputeroute` tags `nexthopgateways` : an array of `googlecomputeroute` nexthopgateway `nexthopinstances` : an array of `googlecomputeroute` nexthopinstance `nexthopips` : an array of `googlecomputeroute` nexthopip `nexthopvpn_tunnels` : an array of `googlecomputeroute` nexthopvpn_tunnel `nexthopnetworks` : an array of `googlecomputeroute` nexthopnetwork `nexthopilbs` : an array of `googlecomputeroute` nexthopilb This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: istio.md

If you want to get pipeline vertices running on Istio, so that they are able to talk to other services with Istio enabled, one approach is to whitelist the ports that Numaflow uses. To whitelist the ports, add `traffic.sidecar.istio.io/excludeInboundPorts` and `traffic.sidecar.istio.io/excludeOutboundPorts` annotations to your vertex configuration: ```yaml apiVersion: numaflow.numaproj.io/v1alpha1 kind: Pipeline metadata: name: my-pipeline spec: vertices: name: my-vertex metadata: annotations: sidecar.istio.io/inject: "true" traffic.sidecar.istio.io/excludeOutboundPorts: "4222" # Nats JetStream port traffic.sidecar.istio.io/excludeInboundPorts: "2469" # Numaflow vertex metrics port udf: container: image: my-udf-image:latest ... ``` If you want to apply same configuration to all the vertices, use : ```yaml apiVersion: numaflow.numaproj.io/v1alpha1 kind: Pipeline metadata: name: my-pipeline spec: templates: vertex: metadata: annotations: sidecar.istio.io/inject: "true" traffic.sidecar.istio.io/excludeOutboundPorts: "4222" # Nats JetStream port traffic.sidecar.istio.io/excludeInboundPorts: "2469" # Numaflow vertex metrics port vertices: name: my-vertex-1 udf: container: image: my-udf-1-image:latest name: my-vertex-2 udf: container: image: my-udf-2-image:latest ... ```
Project: Meshery (Provisioning / Automation & Configuration)
File: buildpacks.md

layout: integration title: Buildpacks subtitle: Collaborative and visual infrastructure as code for Buildpacks image: /assets/img/integrations/buildpacks/icons/color/buildpacks-color.svg permalink: extensibility/integrations/buildpacks docURL: https://docs.meshery.io/extensibility/integrations/buildpacks description: integrations-category: App Definition and Development integrations-subcategory: Application Definition & Image Build registrant: Artifact Hub components: featureList: [ "Transform application source code into OCI images.", "Enable for swift rebasing of images and modular control over images.", "Replace Dockerfiles in the app development lifecycle." ] 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: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.11.22.md

RabbitMQ `3.11.22` is a maintenance release in the `3.11.x` . This release series . Please refer to the upgrade section from if upgrading from a version prior to 3.11.0. This release requires Erlang 25 and supports Erlang versions up to `25.3.x`. has more details on Erlang version requirements for RabbitMQ. As of 3.11.0, RabbitMQ requires Erlang 25. Nodes will fail to start on older Erlang releases. Erlang 25 as our new baseline means much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation available to all RabbitMQ 3.11 users. Release notes can be found on GitHub at . Quorum queue replica management operations over the HTTP API now can be disabled. This can be useful in environments where replica management is done by the platform team and tooling, and should not be exposed to cluster users. Contributed by @SimonUnge (AWS). GitHub issue: LDAP plugin did not interpolate values with non-ASCII characters correctly. GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.22.tar.xz` instead of the source tarball produced by GitHub.
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.15.2.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | separate website from user documentation | Major | documentation | Doug Cutting | Doug Cutting | | | Doc on Streaming | Major | documentation | Runping Qi | Rob Weltman | | | include hadoop-default.html in subversion | Minor | documentation | Doug Cutting | | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | In CHANGES.txt, move HADOOP-1851 & HADOOP-1231 to INCOMPATIBLE CHANGES section | Blocker | documentation | Devaraj Das | Arun C Murthy | | | TaskGraphServlet does not set Content-Type | Major | . | Paul Saab | | | | distcp between two clusters does not work if it is run on the target cluster | Critical | util | Murtaza A. Basrai | Doug Cutting | | | hdfsListDirectory in libhdfs does not scale | Blocker | . | Christian Kunz | Christian Kunz | | | last TaskCompletionEvent gets added to the job after the job is marked as completed | Blocker | . | Alejandro Abdelnur | Devaraj Das | | | Jobs fail because job.xml exists | Major | . | Johan Oskarsson | Johan Oskarsson | | | dfs -cat multiple files fail with 'Unable to write to output stream.' | Blocker | . | Koji Noguchi | Raghu Angadi | | | NameNode could delete wrong edits file when there is an error | Major | . | Raghu Angadi | dhruba borthakur | | | wrong usage of mapred.local.dir.minspacestart | Critical | . | Christian Kunz | Amareshwari Sriramadasu | | | final map output not evenly distributed across multiple disks | Blocker | . | Christian Kunz | Arun C Murthy | | | Dropping records at reducer. InMemoryFileSystem NPE. | Blocker | . | Koji Noguchi | Devaraj Das | | | German locale makes NameNode web interface crash | Minor | . | Matthias Friedrich | Matthias Friedrich |
Project: StarRocks (App Definition and Development / Database)
File: weeks_sub.md

displayed_sidebar: "English" Subtracts a specified number of weeks from a datetime or date value. ```Haskell DATETIME weeks_sub(DATETIME expr1, INT expr2); ``` `expr1`: the original date. It must be of the `DATETIME` type. `expr2`: the number of weeks. It must be of the `INT` type. Returns a `DATETIME` value. `NULL` is returned if the date does not exist. ```Plain select weeks_sub('2022-12-22',2); +-+ | weeks_sub('2022-12-22', 2) | +-+ | 2022-12-08 00:00:00 | +-+ ```
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace.md

title: "Command - devspace" sidebar_label: devspace Welcome to the DevSpace! DevSpace accelerates developing, deploying and debugging applications with Docker and Kubernetes. Get started by running the init command in one of your projects: devspace init ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --disable-profile-activation If true will ignore all profile activations -h, --help help for devspace --inactivity-timeout int Minutes the current user is inactive (no mouse or keyboard interaction) until DevSpace will exit automatically. 0 to disable. Only supported on windows and mac operating systems (default 180) --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 strings The DevSpace profiles to apply. Multiple profiles are applied in the order they are specified --profile-parent strings One or more profiles that should be applied before the specified profile (e.g. devspace dev --profile-parent=base1 --profile-parent=base2 --profile=my-profile) --profile-refresh If true will pull and re-download profile parent sources --restore-vars If true will restore the variables from kubernetes before loading the config --save-vars If true will save the variables to kubernetes after loading the config --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context DEPRECATED: 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) --vars-secret string The secret to restore/save the variables from/to, if --restore-vars or --save-vars is enabled (default "devspace-vars") ``` ``` ```
Project: KICS (Provisioning / Security & Compliance)
File: 3e09413f-471e-40f3-8626-990c79ae63f3.md

title: CloudTrail SNS Topic Name Undefined hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 3e09413f-471e-40f3-8626-990c79ae63f3 Query name: CloudTrail SNS Topic Name Undefined Platform: CloudFormation Severity: <span style="color:#edd57e">Low</span> Category: Observability URL: Check if SNS topic name is set for CloudTrail<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="12 22" AWSTemplateFormatVersion: "2010-09-09" Parameters: OperatorEmail: Description: "Email address to notify when new logs are published." Type: String Resources: myTrail3: DependsOn: BucketPolicy TopicPolicy Type: AWS::CloudTrail::Trail Properties: S3BucketName: Ref: S3Bucket IsLogging: false IsMultiRegionTrail: true myTrail4: DependsOn: BucketPolicy TopicPolicy Type: AWS::CloudTrail::Trail Properties: EnableLogFileValidation: false S3BucketName: Ref: S3Bucket SnsTopicName: "" IsLogging: false IsMultiRegionTrail: true ``` ```json title="Positive test num. 2 - json file" hl_lines="9 23" { "Resources": { "myTrail5": { "DependsOn": [ "BucketPolicy", "TopicPolicy" ], "Type": "AWS::CloudTrail::Trail", "Properties": { "IsMultiRegionTrail": true, "S3BucketName": { "Ref": "S3Bucket" }, "IsLogging": false } }, "myTrail6": { "DependsOn": [ "BucketPolicy", "TopicPolicy" ], "Type": "AWS::CloudTrail::Trail", "Properties": { "EnableLogFileValidation": false, "S3BucketName": { "Ref": "S3Bucket" }, "SnsTopicName": "", "IsLogging": false, "IsMultiRegionTrail": true } } }, "AWSTemplateFormatVersion": "2010-09-09", "Parameters": { "OperatorEmail": { "Description": "Email address to notify when new logs are published.", "Type": "String" } } } ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: "2010-09-09" Parameters: OperatorEmail: Description: "Email address to notify when new logs are published." Type: String Resources: myTrail: DependsOn: BucketPolicy TopicPolicy Type: AWS::CloudTrail::Trail Properties: EnableLogFileValidation: true S3BucketName: Ref: S3Bucket SnsTopicName: Fn::GetAtt: Topic TopicName IsLogging: true IsMultiRegionTrail: true ``` ```json title="Negative test num. 2 - json file" { "AWSTemplateFormatVersion": "2010-09-09", "Parameters": { "OperatorEmail": { "Type": "String", "Description": "Email address to notify when new logs are published." } }, "Resources": { "myTrail2": { "DependsOn": [ "BucketPolicy", "TopicPolicy" ], "Type": "AWS::CloudTrail::Trail", "Properties": { "IsLogging": true, "IsMultiRegionTrail": true, "EnableLogFileValidation": true, "S3BucketName": { "Ref": "S3Bucket" }, "SnsTopicName": { "Fn::GetAtt": [ "Topic", "TopicName" ] } } }, "S3Bucket": { "DeletionPolicy": "Retain", "Type": "AWS::S3::Bucket", "Properties": {} } } } ```
Project: Trivy (Provisioning / Security & Compliance)
File: azure-devops.md

Here is the It's common to use pipelines to build and deploy images on Azure Kubernetes Service (AKS) clusters. While great for image creation, this process often doesn't account for the stale images left behind and can lead to image bloat on cluster nodes. These images can present security issues as they may contain vulnerabilities. By cleaning these unreferenced images, you can remove an area of risk in your clusters. When done manually, this process can be time intensive, which ImageCleaner can mitigate via automatic image identification and removal. Vulnerability is determined based on a trivy scan, after which images with a LOW, MEDIUM, HIGH, or CRITICAL classification are flagged. An updated ImageList will be automatically generated by ImageCleaner based on a set time interval, and can also be supplied manually. This blog explains how to scan your Azure Container Registry-based container images with the integrated vulnerability scanner when they're built as part of your GitHub workflows. To set up the scanner, you'll need to enable Microsoft Defender for Containers and the CI/CD integration. When your CI/CD workflows push images to your registries, you can view registry scan results and a summary of CI/CD scan results. The findings of the CI/CD scans are an enrichment to the existing registry scan findings by Qualys. Defender for Cloud's CI/CD scanning is powered by Aqua Trivy
Project: Hazelcast Jet (App Definition and Development / Streaming & Messaging)
File: test-failure-report.md

name: test-failure report about: template for test failures in testsuite title: '' labels: test-failure assignees: '' master / 3.0-maintenance (commit INSERTCOMMITID_HERE) Failed on INSERTPLATFORMINFORMATIONHERE: INSERTLINKTOJENKINSTESTRESULT_HERE Stacktrace: ``` INSERTSTACKTRACEHERE ``` Standard output: ``` INSERTINTERESTINGPARTOFSTANDARDOUTPUTHERE ```
Project: Docker Compose (App Definition and Development / Application Definition & Image Build)
File: README.md

+ ](https://github.com/docker/compose/releases/latest) ](https://pkg.go.dev/github.com/docker/compose/v2) ](https://github.com/docker/compose/actions?query=workflow%3Aci) ](https://goreportcard.com/report/github.com/docker/compose/v2) ](https://codecov.io/gh/docker/compose) ](https://api.securityscorecards.dev/projects/github.com/docker/compose) Docker Compose is a tool for running multi-container applications on Docker defined using the . A Compose file is used to define how one or more containers that make up your application are configured. Once you have a Compose file, you can create and start your application with a single command: `docker compose up`. Docker Compose is included in for Windows and macOS. You can download Docker Compose binaries from the on this repository. Rename the relevant binary for your OS to `docker-compose` and copy it to `$HOME/.docker/cli-plugins` Or copy it into one of these folders to install it system-wide: `/usr/local/lib/docker/cli-plugins` OR `/usr/local/libexec/docker/cli-plugins` `/usr/lib/docker/cli-plugins` OR `/usr/libexec/docker/cli-plugins` (might require making the downloaded file executable with `chmod +x`) Quick Start -- Using Docker Compose is a three-step process: Define your app's environment with a `Dockerfile` so it can be reproduced anywhere. Define the services that make up your app in `compose.yaml` so they can be run together in an isolated environment. Lastly, run `docker compose up` and Compose will start and run your entire app. A Compose file looks like this: ```yaml services: web: build: . ports: "5000:5000" volumes: .:/code redis: image: redis ``` Contributing Want to help develop Docker Compose? Check out our . If you find an issue, please report it on the . Legacy The Python version of Compose is available under the `v1` .