cwielenb/CNCF-Dataset huggingface dataset:
Project: Beam (App Definition and Development / Streaming & Messaging)
File: beam-has-a-logo.md

title: "Apache Beam has a logo!" date: 2016-02-22 10:21:48 -0800 categories: beam update website aliases: /beam/update/website/2016/02/22/beam-has-a-logo.html authors: jamesmalone <!-- 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. --> One of the major benefits of Apache Beam is the fact that it unifies both both batch and stream processing into one powerful model. In fact, this unification is so important, the name Beam itself comes from the union of Batch + strEAM = Beam When the project started, we wanted a logo which was both appealing and visually represented this unification. <!--more--> Thanks to the amazing work of Stephanie Smythies, the Apache Beam project now has a logo. drum roll - Presenting, the Apache Beam Logo! <img src="/images/beamlogos.png" alt="Apache Beam Logo"> We are excited about this logo because it is simple, bright, and shows the unification of bath and streaming, as beams of light, within the 'B'. We will base our future website and documentation design around this logo and its coloring. We will also make various permutations and resolutions of this logo available in the coming weeks. For any questions or comments, send an email to the `dev@` email list for Apache Beam.
Project: Redpanda (App Definition and Development / Streaming & Messaging)
File: 04_ducktape_failure.md

name: Create ci-failure issue (ducktape) about: A ducktape test is failing in CI title: CI Failure (key symptom) in `Class.method` labels: kind/bug, ci-failure assignees: '' <!-- Before creating an issue look through existing ci-issues to avoid duplicates https://github.com/redpanda-data/redpanda/issues?q=is%3Aissue+is%3Aopen+label%3Aci-failure --> https://link.to/failing/build <!-- Copy the summary from the "Failed Tests" section of report.html --> ``` Module: rptest.tests.module Class: ClassTest Method: test_methods Arguments: { "if_present": true } ``` <!-- Copy the summary from report.txt if it's too vague to differentiate key symptoms (e.g. TimeoutError is thrown for multiple reason so it makes to dig deeper) - fetch the tarball, check debug and redpanda logs --> ``` testid: rptest.tests.module.ClassTest.testmethods.if_present=True status: FAIL run time: 4 minutes 21.145 seconds TimeoutError("Something is wrong") Traceback (most recent call last): File "/usr/local/lib/python3.10/dist-packages/ducktape/tests/runner_client.py", line 135, in run data = self.run_test() File "/usr/local/lib/python3.10/dist-packages/ducktape/tests/runnerclient.py", line 227, in runtest return self.test_context.function(self.test) File "/usr/local/lib/python3.10/dist-packages/ducktape/mark/_mark.py", line 476, in wrapper return functools.partial(f, args, kwargs)(wargs, **wkwargs) File "/root/tests/rptest/utils/mode_checks.py", line 63, in f return func(args, *kwargs) File "/root/tests/rptest/services/cluster.py", line 35, in wrapped r = f(self, args, *kwargs) File "/root/tests/rptest/tests/module.py", line 105, in test_methods raise TimeoutError("Something is wrong") ducktape.errors.TimeoutError ```
Project: YugabyteDB (App Definition and Development / Database)
File: session-audit-logging-ysql.md

title: Session-level audit logging in YSQL headerTitle: Session-level audit logging in YSQL linkTitle: Session-level audit logging description: Session-level audit logging in YSQL. menu: v2.16: identifier: session-audit-logging-1-ysql parent: audit-logging weight: 760 type: docs <ul class="nav nav-tabs-alt nav-tabs-yb"> <li > <a href="../session-audit-logging-ysql/" class="nav-link active"> <i class="icon-postgres" aria-hidden="true"></i> YSQL </a> </li> </ul> Session logging is enabled for per user session basis. Enable session logging for all DML and DDL statements and log all relations in DML statements. ```sql set pgaudit.log = 'write, ddl'; set pgaudit.log_relation = on; ``` Enable session logging for all commands except MISC and raise audit log messages as NOTICE. In this example session audit logging is used for logging DDL and SELECT statements. Note that the insert statement is not logged because the WRITE class is not enabled. SQL statements are shown below. Open the YSQL shell (ysqlsh), specifying the `yugabyte` user and prompting for the password. ```sh $ ./ysqlsh -U yugabyte -W ``` When prompted for the password, enter the yugabyte password. You should be able to log in and see a response like below. ```output ysqlsh (11.2-YB-2.5.0.0-b0) Type "help" for help. yugabyte=# ``` Enable `pgaudit` extension on the YugabyteDB cluster. ```sql \c yugabyte yugabyte; CREATE EXTENSION IF NOT EXISTS pgaudit; ``` Enable session audit logging in YugabyteDB cluster. ```sql set pgaudit.log = 'read, ddl'; ``` ```sql create table account ( id int, name text, password text, description text ); insert into account (id, name, password, description) values (1, 'user1', 'HASH1', 'blah, blah'); select * from account; ``` You should output similar to the following in the logs: ```output 2020-11-09 19:19:09.262 UTC [3710] LOG: AUDIT: SESSION,1,1,DDL,CREATE TABLE,TABLE,public.account,"create table account ( id int, name text, password text, description text );",<not logged> 2020-11-09 19:19:19.619 UTC [3710] LOG: AUDIT: SESSION,2,1,READ,SELECT,,,"select * from account;",<not logged> ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: log-driver.md

Logging driver for the container. Currently available options are k8s-file, journald, none, passthrough and passthrough-tty, with json-file aliased to k8s-file for scripting compatibility. (Default journald). The podman info command below displays the default log-driver for the system. ``` $ podman info --format '{{ .Host.LogDriver }}' journald ``` The passthrough driver passes down the standard streams (stdin, stdout, stderr) to the container. It is not allowed with the remote Podman client, including Mac and Windows (excluding WSL2) machines, and on a tty, since it is vulnerable to attacks via TIOCSTI. The passthrough-tty driver is the same as passthrough except that it also allows it to be used on a TTY if the user really wants it.
Project: YugabyteDB (App Definition and Development / Database)
File: yba_completion_bash.md

Generate the autocompletion script for bash Generate the autocompletion script for the bash shell. This script depends on the 'bash-completion' package. If it is not installed already, you can install it via your OS's package manager. To load completions in your current shell session: source <(yba completion bash) To load completions for every new session, execute once: yba completion bash > /etc/bash_completion.d/yba yba completion bash > $(brew --prefix)/etc/bash_completion.d/yba You will need to start a new shell for this setup to take effect. ``` yba completion bash ``` ``` -h, --help help for bash --no-descriptions disable completion descriptions ``` ``` -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") -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) ``` - Generate the autocompletion script for the specified shell
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: feat-12520.en.md

Implement log throttling. The feature reduces the number of potentially flooding logged events by dropping all but the first event within a configured time window. Throttling is applied to the following log events: authentication_failure, authorizationpermissiondenied, cannotpublishtotopicduetonot_authorized, cannotpublishtotopicduetoquota_exceeded, connectionrejectedduetolicenselimitreached, droppedmsgduetomqueueisfull.
Project: Meshery (Provisioning / Automation & Configuration)
File: operator-framework.md

layout: integration title: Operator Framework subtitle: Collaborative and visual infrastructure as code for Operator image: /assets/img/integrations/operator-framework/icons/color/operator-framework-color.svg permalink: extensibility/integrations/operator-framework docURL: https://docs.meshery.io/extensibility/integrations/operator framework description: integrations-category: App Definition and Development integrations-subcategory: Application Definition & Image Build registrant: Artifact Hub components: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: Harbor (Provisioning / Container Registry)
File: 5-04-OVA-HTTPS.md

Test 5-04 - OVA Uses HTTPS ======= To verify that an OVA version of Harbor can set up for HTTPS. User guide, installation guide of Harbor OVA version. This test requires an OVA binary of Harbor. A vCenter, at least an ESX host, and a network that supports DHCP. A linux host with Docker CLI installed (Docker client). TBD TBD None
Project: Harbor (Provisioning / Container Registry)
File: 4-01-DB-user-view-logs.md

Test 4-01 - User Views Logs (DB Mode) ======= To verify that a non-admin user can views logs when users are managed locally by Harbor (DB mode). User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against a local database. ( auth_mode is set to db_auth* .) The user data is stored in a local database. A linux host with Docker CLI installed (Docker client). On a Docker client host, use `docker login <harbor_host>` command to log in as a non-admin user. Run some `docker push` and `docker pull` commands to push images to the registry and pull from the registry. Log in to the UI as the non-admin user. Delete a few images from the project. View the logs of the project. Try below search criteria to see if the search result is correct: push only pull only pull and push delete only all push and delete different date ranges date range and push All operations in Step 2 & 4 should be logged. Logs can be viewed in Step 5, check if the time and operations are correct. Logs can be filtered in Step 6. None
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: CLI-002-self-hosted-init-and-uninstall-behaviors.md

Accepted Changes in behavior of `init` and `uninstall` on Self Hosted mode for. Discussed in this . Calling `dapr init` will Install `daprd` binary in `$HOME/.dapr/bin` for Linux/MacOS and `%USERPROFILE%\.dapr\bin` for Windows. Set up the `daprplacement`, `daprredis` and `dapr_zipkin` containers. Create the default `components` folder in `$HOME/.dapr/bin` for Linux/MacOS or `%USERPROFILE\.dapr\bin` for Windows. Create the default components configurations for `pubsub.yaml`, `statestore.yaml` and `zipkin.yaml` in the default `components` folder. Create a default configuration file in `$HOME/.dapr/config.yaml` for Linx/MacOS and `%USERPROFILE%\.dapr\config.yaml` for Windows for enabling tracing by default. Calling `dapr init --slim` will Install the binaries `daprd` and `placement` in `$HOME/.dapr/bin` for Linux/MacOS and `%USERPROFILE%\.dapr\bin` for Windows. Create an empty default `components` folder in `$HOME/.dapr/bin` for Linux/MacOS or `%USERPROFILE\.dapr\bin` for Windows. Calling `dapr uninstall` will Remove the folder containing binaries `bin` the default path `$HOME/.dapr` for Linux/MacOS and `%USERPROFILE%\.dapr` for Windows. Remove the docker dapr_placement if Docker is installed. Calling `dapr uninstall --all` Remove the folder containing binaries `bin` the default path `$HOME/.dapr` for Linux/MacOS and `%USERPROFILE%\.dapr` for Windows. Remove the docker containers daprplacement, daprredis and dapr_zipkin if Docker is installed. Remove the default folder `$HOME/.dapr` in Linux/MacOS and `%USERPROFILE%\.dapr` in Windows. CLI on the init command will fail if a prior installtion exists in the default path `$HOME/.dapr` for Linux/MacOS and `%USERPROFILE%\.dapr` for Windows. There will no longer be an option for `--install-path` during init or during uninstall.* The `dapr` CLI by default will expect the `daprd` in `$HOME/.dapr/bin` for Linux/MacOS and `%USERPROFILE%\.dapr\bin` for Windows. The command `dapr run` will not expect the `daprd` binary to be in the `PATH` variable, it will launch the binary from the default path. All other binaries except `dapr` cli and configurations that dapr needs (on running `dapr init`)will be placed in the path `$HOME/.dapr/bin` for Linux/MacOS and `%USERPROFILE%\.dapr\bin` for Windows.
Project: KICS (Provisioning / Security & Compliance)
File: 617ef6ff-711e-4bd7-94ae-e965911b1b40.md

title: Google Project IAM Binding Service Account has Token Creator or Account User Role hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 617ef6ff-711e-4bd7-94ae-e965911b1b40 Query name: Google Project IAM Binding Service Account has Token Creator or Account User Role Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: Verifies if Google Project IAM Binding Service Account doesn't have an Account User or Token Creator Role associated<br> ```tf title="Positive test num. 1 - tf file" hl_lines="19 29 3 13" resource "googleprojectiam_binding" "positive1" { project = "your-project-id" role = "roles/iam.serviceAccountTokenCreator" members = [ "user:jane@example.com", "serviceAccount:my-other-app@appspot.gserviceacccount.com" ] } resource "googleprojectiam_binding" "positive2" { project = "your-project-id" role = "roles/iam.serviceAccountTokenCreator" member = "serviceAccount:my-other-app@appspot.gserviceacccount.com" } resource "googleprojectiam_binding" "positive3" { project = "your-project-id" role = "roles/iam.serviceAccountUser" members = [ "user:jane@example.com", "serviceAccount:my-other-app@appspot.gserviceacccount.com" ] } resource "googleprojectiam_binding" "positive4" { project = "your-project-id" role = "roles/iam.serviceAccountUser" member = "serviceAccount:my-other-app@appspot.gserviceacccount.com" } ``` ```tf title="Negative test num. 1 - tf file" resource "googleprojectiam_binding" "negative1" { project = "your-project-id" role = "roles/editor" members = [ "user:jane@example.com", ] } ```
Project: LinuxKit (Provisioning / Automation & Configuration)
File: 2017-06-21.md

Time: 9am PDT (12pm EDT, 5pm BST) Meeting location: https://docker.zoom.us/j/779801882 Announcement: Video recording: https://youtu.be/TN3p7dR7r3M Previous meeting notes: Introductions & Administrivia (5 min) signing: followup on last meeting's buildchain security discussion (15 min) current state of signing in LinuxKit, explanation of delegations for auditing propose pinning, policy, removing signatures `landlock` deep dive - @l0kod (30 min) What is it Landlock LSM? What is eBPF? Why do we care? current state of the project, future patchsets and direction architecture deep dive demo Project updates (10 min) Next meeting: 2017-07-05 deep dive TBD we can propose additional deep dives and discussion topics! Scribe: @mgoelzer Next meeting July 5 Recap of Moby Summit slides for and , videos coming soon Lots of bare metal linuxkit interest auditd requested Another Summit at Open Source Summit in LA Package Signing Based on Notary (based on The Update Framework) - implemented in Docker Content Trust in Docker CLI all `linuxkit/` images on Docker Hub are signed by maintainers Guarantees: authenticity integrity freshness survivability after key compromise Linuxkit yaml files container `trust:` block - tells moby builder that you want to verify all images in a given organization or per image control Moby builder will first check the signatures for all images and validate expiration dates before pulling images Future directions: key pinning for signed packages enforce multi-sig thresholds actively remove sigs for old packages (or let them expire) private notary servers Landlock LSM (presentation by @l0kod) - Threat: compromised processes (like browsers) -> privilege escalations -> access data on the system Today we have: access control through SELinux (fine grained) seccomp-bpf (not an AC mechanism) namespaces Landlock is trying to do three things: fine grained control unprivileged embedded in applications Landlock = programmatic access control Landlock rules: written in C compiled down to eBPF bytecode embedded in application application executes Landlock rule loaded into running kernel Example: rule that says application cannot write to files but can write to FIFOs Key data structure: `struct landlock_context` Overview of eBPF (extended Berkeley Packet Filtering) In-kernel bytecode For network filtering, tracing Landlock Roadmap: MVP cgroups new eBPF maps for fs checks unprivileged mode
Project: KICS (Provisioning / Security & Compliance)
File: 0437633b-daa6-4bbc-8526-c0d2443b946e.md

title: SSL Enforce Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 0437633b-daa6-4bbc-8526-c0d2443b946e Query name: SSL Enforce Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: Make sure that for PosgreSQL, the 'Enforce SSL connection' is set to 'ENABLED'<br> ```tf title="Positive test num. 1 - tf file" hl_lines="18 22" resource "azurermpostgresqlserver" "positive1" { name = "example-psqlserver" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name administrator_login = "psqladminun" administratorloginpassword = "H@Sh1CoR3!" skuname = "GPGen5_4" version = "9.6" storage_mb = 640000 backupretentiondays = 7 georedundantbackup_enabled = true autogrowenabled = true publicnetworkaccess_enabled = false sslenforcementenabled = false sslminimaltlsversionenforced = "TLS1_2" } resource "azurermpostgresqlserver" "positive2" { name = "example-psqlserver" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name administrator_login = "psqladminun" administratorloginpassword = "H@Sh1CoR3!" skuname = "GPGen5_4" version = "9.6" storage_mb = 640000 backupretentiondays = 7 georedundantbackup_enabled = true autogrowenabled = true publicnetworkaccess_enabled = false sslminimaltlsversionenforced = "TLS1_2" } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermpostgresqlserver" "negative1" { name = "example-psqlserver" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name administrator_login = "psqladminun" administratorloginpassword = "H@Sh1CoR3!" skuname = "GPGen5_4" version = "9.6" storage_mb = 640000 backupretentiondays = 7 georedundantbackup_enabled = true autogrowenabled = true publicnetworkaccess_enabled = false sslenforcementenabled = true sslminimaltlsversionenforced = "TLS1_2" } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: elasticsearch-operator.md

layout: integration title: Elastic Search subtitle: Collaborative and visual infrastructure as code for Elastic Search image: /assets/img/integrations/elasticsearch-operator/icons/color/elasticsearch-operator-color.svg permalink: extensibility/integrations/elasticsearch-operator docURL: https://docs.meshery.io/extensibility/integrations/elasticsearch-operator description: integrations-category: Observability and Analysis integrations-subcategory: Logging registrant: Artifact Hub components: name: apm-server colorIcon: assets/img/integrations/elasticsearch-operator/components/apm-server/icons/color/apm-server-color.svg whiteIcon: assets/img/integrations/elasticsearch-operator/components/apm-server/icons/white/apm-server-white.svg description: name: elasticsearch colorIcon: assets/img/integrations/elasticsearch-operator/components/elasticsearch/icons/color/elasticsearch-color.svg whiteIcon: assets/img/integrations/elasticsearch-operator/components/elasticsearch/icons/white/elasticsearch-white.svg description: name: kibana colorIcon: assets/img/integrations/elasticsearch-operator/components/kibana/icons/color/kibana-color.svg whiteIcon: assets/img/integrations/elasticsearch-operator/components/kibana/icons/white/kibana-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