cwielenb/CNCF-Dataset huggingface dataset:
Project: Beam (App Definition and Development / Streaming & Messaging)
File: windowing-and-triggering.md

type: languages title: "Beam DSLs: SQL" aliases: /documentation/dsls/sql/windowing-and-triggering/ <!-- 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. --> You can use Beam's windowing semantics in two ways: you can configure windowing on your input `PCollections` before passing them to a `BeamSql` transform you can use windowing extensions in your windowing query, which will override the windowing of your input `PCollections` Triggering can only be used by setting it on your input `PCollections`; there are no SQL extensions for specifying triggering. This section covers the use of SQL extensions to directly apply windowing. Beam SQL supports windowing functions specified in `GROUP BY` clause. `TIMESTAMP` field is required in this case. It is used as event timestamp for rows. Supported windowing functions: `TUMBLE`, or fixed windows. Example of how define a fixed window with duration of 1 hour: ``` SELECT f_int, COUNT(*) FROM PCOLLECTION GROUP BY f_int, TUMBLE(f_timestamp, INTERVAL '1' HOUR) ``` `HOP`, or sliding windows. Example of how to define a sliding windows for every 30 minutes with 1 hour duration: ``` SELECT f_int, COUNT(*) FROM PCOLLECTION GROUP BY f_int, HOP(f_timestamp, INTERVAL '30' MINUTE, INTERVAL '1' HOUR) ``` `SESSION`, session windows. Example of how to define a session window with 5 minutes gap duration: ``` SELECT f_int, COUNT(*) FROM PCOLLECTION GROUP BY f_int, SESSION(f_timestamp, INTERVAL '5' MINUTE) ``` Note: When no windowing function is specified in the query, then windowing strategy of the input `PCollections` is unchanged by the SQL query. If windowing function is specified in the query, then the windowing function of the `PCollection` is updated accordingly, but trigger stays unchanged.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: PULL_REQUEST_TEMPLATE.md

Deprecation notice: The website is being migrated to https://github.com/apache/beam/tree/master/website Please create new pull requests against the above repo. Please add a meaningful description for your change here. Once your pull request has been opened and assigned a number, please edit the URL below, replacing `PULLREQUESTNUMBER` with the number of your pull request. https://apache-beam-website-pull-requests.storage.googleapis.com/PULLREQUESTNUMBER/index.html Finally, it will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
Project: Chef Habitat (App Definition and Development / Application Definition & Image Build)
File: containers.md

+++ title = "Chef Habitat and Containers" description = "Chef Habitat and Containers" gh_repo = "habitat" [menu] [menu.habitat] title = "Chef Habitat and Containers" identifier = "habitat/containers/containers" parent = "habitat/containers" weight = 10 +++ Examples: and Containers enable you to build an immutable snapshot of your runtime environment, including your operating system, system libraries, application libraries, and application. The container is built with a CLI tool, and then pushed to a container-specific artifact repository, known as a container registry. Chef Habitat is not a container format and exports your application to the container format of your choice. Chef Habitat builds more secure containers by exporting your application and any of its runtime dependencies directly into the container. When you build your application with Chef Habitat, your application takes ownership of the entire toolchain of its runtime dependencies. As a result, you no longer have to rely on a large operating system and unnecessary system libraries. This enables you to include only the binaries your application uses inside your container, which can decrease your container size. By eliminating the need for a large operating system, you also avoid including binaries that an attacker could use, which further increases the security of your container. Visit the section of the docs to find more details about how containers are built with Chef Habitat. Finally, allows all of your application's runtime dependencies to be audited at any time. If a brand new vulnerability is revealed, makes it easy to programmatically inspect and audit the entire toolchain of your runtime environment without needing to worry about how your containers got built in the first place. If your situation requires it, Chef Habitat makes it simple to switch from containerized to non-containerized workloads. This is because Chef Habitat packages only have a requirement on the kernel version of your operating system. (Linux: kernel 2.6.32 or later, Windows: Windows Server 2008 R2 or later and Windows 7 64-bit or later). You can take the same .hart file you use to export to a Docker container and run it on a virtual machine or bare metal. By only requiring the kernel, Chef Habitat gives you the ability to switch container formats or to switch to non-containerized workloads without significant rework.
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-dashboard.md

layout: default title: mesheryctl-system-dashboard permalink: reference/mesheryctl/system/dashboard redirect_from: reference/mesheryctl/system/dashboard/ type: reference display-title: "false" language: en command: system subcommand: dashboard Open Meshery UI in browser. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system dashboard [flags] </div> </pre> Open Meshery UI in browser <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system dashboard </div> </pre> Open Meshery UI in browser and use port-forwarding (if default port is taken already) <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system dashboard --port-forward </div> </pre> Open Meshery UI in browser and use port-forwarding, listen on port 9081 locally, forwarding traffic to meshery server in the pod <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system dashboard --port-forward -p 9081 </div> </pre> (optional) skip opening of MesheryUI in browser. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system dashboard --skip-browser </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for dashboard -p, --port int (optional) Local port that is not in use from which traffic is to be forwarded to the server running inside the Pod. (default 9081) --port-forward (optional) Use port forwarding to access Meshery UI --skip-browser (optional) skip opening of MesheryUI in browser. </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -c, --context string (optional) temporarily change the current context. -v, --verbose verbose output -y, --yes (optional) assume yes for user interactive prompts. </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: ko (App Definition and Development / Application Definition & Image Build)
File: ko_create.md

Create the input files with image references resolved to built/pushed image digests. This sub-command finds import path references within the provided files, builds them into Go binaries, containerizes them, publishes them, and then feeds the resulting yaml into "kubectl create". ``` ko create -f FILENAME [flags] ``` ``` ko create -f config/ ko create --preserve-import-paths -f config/ ko create --local -f config/ cat config.yaml | ko create -f - ko apply -f config -- --namespace=foo --kubeconfig=cfg.yaml ``` ``` --bare Whether to just use KODOCKERREPO without additional context (may not work properly with --tags). -B, --base-import-paths Whether to use the base path without MD5 hash after KODOCKERREPO (may not work properly with --tags). --disable-optimizations Disable optimizations when building Go code. Useful when you want to interactively debug the created container. -f, --filename strings Filename, directory, or URL to files to use to create the resource -h, --help help for create --image-label strings Which labels (key=value) to add to the image. --image-refs string Path to file where a list of the published image references will be written. --insecure-registry Whether to skip TLS verification on the registry -j, --jobs int The maximum number of concurrent builds (default GOMAXPROCS) -L, --local Load into images to local docker daemon. --oci-layout-path string Path to save the OCI image layout of the built images --platform strings Which platform to use when pulling a multi-platform base. Format: all | <os>* -P, --preserve-import-paths Whether to preserve the full import path after KODOCKERREPO. --push Push images to KODOCKERREPO (default true) -R, --recursive Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory. --sbom string The SBOM media type to use (none will disable SBOM synthesis and upload, also supports: spdx, cyclonedx, go.version-m). (default "spdx") --sbom-dir string Path to file where the SBOM will be written. -l, --selector string Selector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l key1=value1,key2=value2) --tag-only Include tags but not digests in resolved image references. Useful when digests are not preserved when images are repopulated. -t, --tags strings Which tags to use for the produced image instead of the default 'latest' tag (may not work properly with --base-import-paths or --bare). (default [latest]) --tarball string File to save images tarballs ``` ``` -v, --verbose Enable debug logs ``` - Rapidly iterate with Go, Containers, and Kubernetes.
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: watches.md

title: Define Watches in Helm-based operators linkTitle: Define Watches weight: 200 description: Specification for the `watches.yaml` file in Helm-based operators. The Watches file contains a list of mappings from custom resources, identified by it's Group, Version, and Kind, to a Helm chart. The Operator expects this mapping file in a predefined location: `/opt/helm/watches.yaml` The follow tables describes the fields in an entry in `watches.yaml`: | Field | Description | | :- | :- | | group | The group of the Custom Resource that you will be watching. | | version | The version of the Custom Resource that you will be watching. | | kind | The kind of the Custom Resource that you will be watching. | | chart | The path to the helm chart to use when reconciling this GVK. | | watchDependentResources | Enable watching resources that are created by helm (default: `true`). | | overrideValues | Values to be used for overriding Helm chart's defaults. For additional information see the . | | selector | The conditions that a resource's labels must satisfy in order to get reconciled. For additional information see . | For reference, here is an example of a simple `watches.yaml` file: ```yaml group: foo.example.com version: v1alpha1 kind: Foo chart: helm-charts/foo overrideValues: image.repository: quay.io/mycustomrepo watchDependentResources: false selector: matchExpressions: {key: testLabel, operator: Exists, values: []} ```
Project: CloudARK KubePlus (App Definition and Development / Application Definition & Image Build)
File: TESTS.md

`go test` is used for testing. A running PostgreSQL server is required, with the ability to log in. The database to connect to test with is "pqgotest," on "localhost" but these can be overridden using [environment variables](https://www.postgresql.org/docs/9.3/static/libpq-envars.html). Example: PGHOST=/run/postgresql go test A benchmark suite can be run as part of the tests: go test -bench . Run a postgres container: ``` docker run --expose 5432:5432 postgres ``` Run tests: ``` PGHOST=localhost PGPORT=5432 PGUSER=postgres PGSSLMODE=disable PGDATABASE=postgres go test ```
Project: KICS (Provisioning / Security & Compliance)
File: 7b47138f-ec0e-47dc-8516-e7728fe3cc17.md

title: PostgreSQL Log Connections Not Set hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 7b47138f-ec0e-47dc-8516-e7728fe3cc17 Query name: PostgreSQL Log Connections Not Set Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Make sure that for PostgreSQL Database, server parameter 'log_connections' is set to 'ON'<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="37 7 13 19 25 31" name: Update PostgreSQL Server setting azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_connections value: off name: Update PostgreSQL Server setting2 azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_connections value: Off name: Update PostgreSQL Server setting3 azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_connections value: OFF name: Update PostgreSQL Server setting4 azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_connections value: "off" name: Update PostgreSQL Server setting5 azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_connections value: "Off" name: Update PostgreSQL Server setting6 azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_connections value: "OFF" ``` ```yaml title="Negative test num. 1 - yaml file" name: Update PostgreSQL Server setting azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_connections value: on name: Update PostgreSQL Server setting2 azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_connections value: On name: Update PostgreSQL Server setting3 azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_connections value: ON name: Update PostgreSQL Server setting4 azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_connections value: on name: Update PostgreSQL Server setting5 azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_connections value: On name: Update PostgreSQL Server setting6 azure.azcollection.azurermpostgresqlconfiguration: resource_group: myResourceGroup server_name: myServer name: log_connections value: ON ```
Project: SpiceDB (App Definition and Development / Database)
File: CODE-OF-CONDUCT.md

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 are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality. Examples of unacceptable behavior by participants include: The use of sexualized language or imagery Personal attacks Trolling or insulting/derogatory comments Public or private harassment Publishing others private information, such as physical or electronic addresses, without explicit permission Other unethical or unprofessional conduct Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct. By adopting this Code of Conduct, project maintainers commit themselves to fairly and consistently applying these principles to every aspect of managing this project. Project maintainers who do not follow or enforce the Code of Conduct may be permanently removed from the project team. This code of conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an issue or contacting one or more of the project maintainers. This Code of Conduct is adapted from the Contributor Covenant, version 1.2.0, available
Project: ClickHouse (App Definition and Development / Database)
File: v22.12.2.25-stable.md

sidebar_position: 1 sidebar_label: 2023 Backported in : In rare cases, we don't rebuild binaries, because another task with a similar prefix succeeded. E.g. `binarydarwin` didn't restart because `binarydarwin_aarch64`. (). Backported in : Retry the integration tests on compressing errors. (). Backported in : . (). Backported in : Fix parsing of bad version from compatibility setting. (). Backported in : Fix possible crash in case function `IN` with constant arguments was used as a constant argument together with `LowCardinality`. Fixes . (). Bump libdivide (to gain some new optimizations) (). Add some settings under `compatibility` (). Fix deadlock in StorageSystemDatabases (). Get rid of global Git object (). Add check for submodules sanity (). Implement a custom central checkout action (). Fix crash on delete from materialized view ().
Project: YDB (App Definition and Development / Database)
File: cast_examples.md

SELECT CAST("12345" AS Double), -- 12345.0 CAST(1.2345 AS Uint8), -- 1 CAST(12345 AS String), -- "12345" CAST("1.2345" AS Decimal(5, 2)), -- 1.23 CAST("xyz" AS Uint64) IS NULL, -- true, because it failed CAST(-1 AS Uint16) IS NULL, -- true, a negative integer cast to an unsigned integer CAST([-1, 0, 1] AS List<Uint8?>), -- [null, 0, 1] --The item type is optional: the failed item is cast to null. CAST(["3.14", "bad", "42"] AS List<Float>), -- [3.14, 42] --The item type is not optional: the failed item has been deleted. CAST(255 AS Uint8), -- 255 CAST(256 AS Uint8) IS NULL -- true, out of range
Project: KICS (Provisioning / Security & Compliance)
File: 1e5f5307-3e01-438d-8da6-985307ed25ce.md

title: VM Not Attached To Network hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 1e5f5307-3e01-438d-8da6-985307ed25ce Query name: VM Not Attached To Network Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: No Network Security Group is attached to the Virtual Machine<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="3" name: Create a VM with a custom image azurermvirtualmachine: resource_group: myResourceGroup name: testvm001 vmsize: StandardDS1_v2 admin_username: adminUser admin_password: password01 image: customimage001 ``` ```yaml title="Negative test num. 1 - yaml file" name: Create a VM with a custom image azurermvirtualmachine: resource_group: myResourceGroup name: testvm001 vmsize: StandardDS1_v2 admin_username: adminUser admin_password: password01 image: customimage001 network_interfaces: testvm001 ```
Project: Apache Hadoop (App Definition and Development / Database)
File: MasterWorker.md

<! 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. See accompanying LICENSE file. --> MaWo is a YARN service based framework which handles Master Worker based workload. This is an app which can take an input job specification with tasks, their expected durations and have a Master dish the tasks off to a predetermined set of workers. The components will be responsible to finish the job within specific time duration. MaWo app is a YARN Service Application. It has mainly two components. Master Read MaWo-Payload file and create a queue of Tasks Register Worker Assign tasks to worker nodes Monitor status of Tasks Log Task status Worker Send heartbeat to Worker Execute Task
Project: Meshery (Provisioning / Automation & Configuration)
File: aws-efs-controller.md

layout: integration title: AWS Elastic File System subtitle: Collaborative and visual infrastructure as code for AWS Elastic File System image: /assets/img/integrations/aws-efs-controller/icons/color/aws-efs-controller-color.svg permalink: extensibility/integrations/aws-efs-controller docURL: https://docs.meshery.io/extensibility/integrations/aws-efs-controller description: integrations-category: Cloud Native Storage integrations-subcategory: Cloud Native Storage registrant: GitHub components: name: access-point colorIcon: assets/img/integrations/aws-efs-controller/components/access-point/icons/color/access-point-color.svg whiteIcon: assets/img/integrations/aws-efs-controller/components/access-point/icons/white/access-point-white.svg description: name: file-system colorIcon: assets/img/integrations/aws-efs-controller/components/file-system/icons/color/file-system-color.svg whiteIcon: assets/img/integrations/aws-efs-controller/components/file-system/icons/white/file-system-white.svg description: name: mount-target colorIcon: assets/img/integrations/aws-efs-controller/components/mount-target/icons/color/mount-target-color.svg whiteIcon: assets/img/integrations/aws-efs-controller/components/mount-target/icons/white/mount-target-white.svg description: name: adopted-resource colorIcon: assets/img/integrations/aws-efs-controller/components/adopted-resource/icons/color/adopted-resource-color.svg whiteIcon: assets/img/integrations/aws-efs-controller/components/adopted-resource/icons/white/adopted-resource-white.svg description: name: field-export colorIcon: assets/img/integrations/aws-efs-controller/components/field-export/icons/color/field-export-color.svg whiteIcon: assets/img/integrations/aws-efs-controller/components/field-export/icons/white/field-export-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