cwielenb/CNCF-Dataset huggingface dataset:
Project: ShardingSphere (App Definition and Development / Database)
File: credits.en.md

title: Credits disableToc: true Thanks to them <i class="fas fa-heart"></i> for making Open Source Software a better place ! {{% ghcontributors "https://api.github.com/repos/matcornic/hugo-theme-learn/contributors?per_page=100" %}} And a special thanks to for his work on , a fork of hugo-theme-learn. v2.0.0 of this theme is inspired by his work. - generation of diagram and flowchart from text in a similar manner as markdown - the iconic font and CSS framework - The Write Less, Do More, JavaScript Library - Lunr enables you to provide a great search experience without the need for external, server-side, search services... - Progressive and customizable autocomplete component - copy text to clipboard - Javascript syntax highlighter - A JavaScript toolkit that allows web developers to use new CSS3 and HTML5 features while maintaining a fine level of control over browsers that don't support - Continuous deployement and hosting of this documentation
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.148.md

layout: release date: 2023-09-27 tag: v0.6.148 [Helm] Values descriptions @leecalcote (#8935) [Docs] Update Helm Chart docs. @MUzairS15 (#8934) [Playground] Increase max file upload size. @leecalcote (#8765) [Server] Do not refresh token when status code returned is `403`. @MUzairS15 (#8900) Fix Dashboard Component @aabidsofi19 (#8888) fix useeffect and fetching @aabidsofi19 (#8943) fix: select all button issue meshery @captain-Akshay (#8933) Add a nullish check @aabidsofi19 (#8937) fix: Change prettier to error, and added eol to be LF @nebula-aac (#8916) [extensions] Fix Collaborator Extension Point Re-rendering @theBeginner86 (#8904) Fix for Navigation @Jougan-0 (#8877) [UI] feat: Setup prettier and moved lint-staged to its own file @nebula-aac (#8827) Revert "[extensions] Fix Collaborator Extension Point Re-rendering" @theBeginner86 (#8903) [extensions] Fix Collaborator Extension Point Re-rendering @theBeginner86 (#8893) [extensions] Fix Collaborator Extension Point Re-rendering @theBeginner86 (#8904) add functionality to dynamically update the URL @goldfishdolphin (#8899) fix useeffect and fetching @aabidsofi19 (#8943) fix: Change prettier to error, and added eol to be LF @nebula-aac (#8916) fix: #8911 @Sumit21kumar (#8914) Changed pertainting to pertaining @nwanduka (#8920) Updated docs regarding linting/formatting in ui @akhilender-bongirwar (#8926) fix: Typo in Contributing to Meshery Server documentation #8924 @SAF2k (#8927) Typo in Contributing to Meshery Server/signoff @Ayush9026 (#8928) [DOC] fix: all the typos @captain-Akshay (#8930) add functionality to dynamically update the URL @goldfishdolphin (#8899) Thank you to our contributors for making this release possible: @Ayush9026, @Chadha93, @Jougan-0, @MUzairS15, @SAF2k, @Sumit21kumar, @aabidsofi19, @akhilender-bongirwar, @captain-Akshay, @goldfishdolphin, @leecalcote, @nebula-aac, @nwanduka and @theBeginner86
Project: Seata (App Definition and Development / Database)
File: 1.7.1.md

Add changes here for all PR submitted to the develop branch. <!-- Please add the `changes` to the following location(feature/bugfix/optimize/test) based on the type of PR --> ] docker image supports JVM parameter injection ] case of the pk col-name in the business sql is inconsistent with the case in the table metadata, resulting in a rollback failure ] change some fields type of TableMetaCache to avoid integer overflow ] fix the problem that the parameter prefix requirement of the setAttachment method in sofa-rpc is not met ] fix XA transaction start exception and rollback failure ] insert executor keywords unescape ] fix oracle column alias cannot find ] optimize docker default timezone ] support the nacos application name property ] unified log output directory ] upgrade some deprecated github actions ] optimize: publish images based on java `8`, `8-slim`, `17`, `17-slim` ] fix some dependencies vulnerability ] fix some serializer vulnerabilities ] XXX Thanks to these contributors for their code commits. Please report an unintended omission. <!-- Please make sure your Github ID is in the list below --> Also, we receive many valuable issues, questions and advices from our community. Thanks for you all.
Project: Apache Storm (App Definition and Development / Streaming & Messaging)
File: Trident-spouts.md

title: Trident Spouts layout: documentation documentation: true Like in the vanilla Storm API, spouts are the source of streams in a Trident topology. On top of the vanilla Storm spouts, Trident exposes additional APIs for more sophisticated spouts. There is an inextricable link between how you source your data streams and how you update state (e.g. databases) based on those data streams. See for an explanation of this understanding this link is imperative for understanding the spout options available. Regular Storm spouts will be non-transactional spouts in a Trident topology. To use a regular Storm IRichSpout, create the stream like this in a TridentTopology: ```java TridentTopology topology = new TridentTopology(); topology.newStream("myspoutid", new MyRichSpout()); ``` All spouts in a Trident topology are required to be given a unique identifier for the stream this identifier must be unique across all topologies run on the cluster. Trident will use this identifier to store metadata about what the spout has consumed in Zookeeper, including the txid and any metadata associated with the spout. You can configure the Zookeeper storage of spout metadata via the following configuration options: `transactional.zookeeper.servers`: A list of Zookeeper hostnames `transactional.zookeeper.port`: The port of the Zookeeper cluster `transactional.zookeeper.root`: The root dir in Zookeeper where metadata is stored. Metadata will be stored at the path <root path>/<spout id> By default, Trident processes a single batch at a time, waiting for the batch to succeed or fail before trying another batch. You can get significantly higher throughput and lower latency of processing of each batch by pipelining the batches. You configure the maximum amount of batches to be processed simultaneously with the "topology.max.spout.pending" property. Even while processing multiple batches simultaneously, Trident will order any state updates taking place in the topology among batches. For example, suppose you're doing a global count aggregation into a database. The idea is that while you're updating the count in the database for batch 1, you can still be computing the partial counts for batches 2 through 10. Trident won't move on to the state updates for batch 2 until the state updates for batch 1 have succeeded. This is essential for achieving exactly-once processing semantics, as outline in . Here are the following spout APIs available: : The most general API that can support transactional or opaque transactional semantics. Generally you'll use one of the partitioned flavors of this API rather than this one directly. : A non-transactional spout that emits batches of tuples at a time : A transactional spout that reads from a partitioned data source (like a cluster of Kafka servers) : An opaque transactional spout that reads from a partitioned data source And, like mentioned in the beginning of this tutorial, you can use regular IRichSpout's as well.
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: 404.md

layout: global title: 404 Not Found license: | Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You 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. Sorry, but the page you were trying to view does not exist. It looks like this was the result of either: a mistyped address an out-of-date link
Project: YugabyteDB (App Definition and Development / Database)
File: func_setval.md

title: setval() function [YSQL] headerTitle: setval() linkTitle: setval() description: Set and return the value for the specified sequence. menu: v2.18: identifier: api-ysql-exprs-setval parent: api-ysql-exprs type: docs Use the `setval(sequencename, value, iscalled)` function to set and return the value for the specified sequence. `UPDATE` privilege on the sequence is required to call this function. Calling the function with two parameters defaults `is_called` to `true`, meaning that the `nextval` will advance the sequence prior to returning the value, and `currval` will also return the specified value. When called with `is_called` set to `false`, `nextval` will return the specified value and the value reported by `currval` will not be changed. `setval()` returns just the value of its second argument. Specify the name of the sequence. Specify the value of the sequence. Set `is_called` to `true` or `false`. ```plpgsql yugabyte=# CREATE SEQUENCE s; ``` ``` CREATE SEQUENCE ``` Use `setval` with `is_called` set to `true`: ```sql yugabyte=# SELECT setval('s', 21); yugabyte=# SELECT setval('s', 21, true); -- the same command as above yugabyte=# SELECT nextval('s'); ``` ```output nextval 22 (1 row) ``` Use `setval` with `is_called` set to `false`: ```sql yugabyte=# SELECT setval('s', 21, false); yugabyte=# SELECT nextval('s'); ``` ```output nextval 21 (1 row) ``` {{< note title="Note" >}} `setval` changes are immediately visible in other transactions and are not rolled back if the transaction is rolled back. {{< /note >}}
Project: KICS (Provisioning / Security & Compliance)
File: a5530bd7-225a-48f9-91bb-f40b04200165.md

title: Service Account Lookup Set To False hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: a5530bd7-225a-48f9-91bb-f40b04200165 Query name: Service Account Lookup Set To False Platform: Kubernetes Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: When using kube-apiserver command, the '--service-account-lookup' flag should be set to true<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: ["--service-account-lookup=false"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: ["--service-account-lookup=true"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 2 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: [] restartPolicy: OnFailure ```
Project: KICS (Provisioning / Security & Compliance)
File: about.md

<img alt="KICS - Keeping Infrastructure as Code Secure" src="../img/logo/kicsnewlogo2022dark.png#only-light#gh-light-mode-only" width="250"> <img alt="KICS - Keeping Infrastructure as Code Secure" src="../img/logo/kicsnewlogo2022white.png#only-dark#gh-dark-mode-only" width="250"> is the global leader in software security solutions for modern enterprise software development. Checkmarx delivers the industrys most comprehensive Software Security Platform that unifies with DevOps and provides static and interactive application security testing, software composition analysis and developer AppSec awareness and training programs to reduce and remediate risk from software vulnerabilities. Checkmarx is trusted by more than 40 percent of the Fortune 100 and half of the Fortune 50, including leading organizations such as SAP, Samsung and Salesforce.com. <img alt="Checkmarx" src="../img/logo-cx-horizontal_new.jpg" width="200"> Contact KICS core team at or join the . Infrastructure as Code (IaC) is the creation, provisioning and configuration of software-defined compute (SDC), network and storage infrastructure through machine-readable definition files, rather than physical hardware configuration or interactive configuration tools. IaC automates the manual tasks usually associated with computing infrastructure configuration and implementation. By doing this, you can: Speed up configuration and implementation of new computing infrastructure Reduce the cost and resource needed to scale and manage large infrastructure Eliminate the inconsistencies that inevitably occur when multiple individuals manually configure new equipment or applications. The core concepts of Infrastructure as Code are: Defined in code Stored in a repository Declarative or Imperative Idempotence and Consistency Push or Pull Main Benefits of Infrastructure as Code: Fully automated deployment Consistent environments Repeatable process Reusable components ("DRY") Documented Architecture Infrastructure as Code testing examines configuration definitions and scripts used to instantiate infrastructure to ensure the resulting resources are secure. IaC security testing tools must be able to consume configuration files and scripts in relevant formats, apply tests to ensure conformance with common configuration hardening standards (i.e., Center for Internet Security Benchmarks and many others), identify security issues associated with specific operational environments, identify embedded secrets, and perform other tests supporting organization-specific standards and compliance requirements. Optionally, tools can automatically remediate errors (e.g., changing read/write permissions on storage resources). This capability specifically examines IaC testing in the context of the development process, however tools may also support examination of deployed production instances and responding to issues identified in those systems.
Project: FOSSA (Provisioning / Security & Compliance)
File: nuget.md

Ideal/Minimum One more more of the following: formatted file in your directory. file present in your project. Commonly with an ending such as `.csproj`, `xproj`, `vbproj` and others. `project.assets.json` `packages.config` `project.json` Directories containing any of the files listed above are considered NuGet projects.
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: topaz.md

title: Topaz labels: category: authorization layer: application type: poweredbyopa inventors: aserto software: topaz code: https://github.com/aserto-dev/topaz tutorials: https://www.topaz.sh https://github.com/aserto-dev/topaz#quickstart blogs: https://www.aserto.com/blog/topaz-oss-cloud-native-authorization-combines-opa-zanzibar docs_features: go-integration: note: | Topaz's Authorizer component makes use of the Rego API to evaluate policies to make authorization decisions for connected applications. Topaz is an open source authorization service providing fine grained, real-time, policy based access control for applications and APIs. Topaz uses OPA as its decision engine, and includes an embedded database that stores subjects, relations, and objects, inspired by the Google Zanzibar data model. Topaz can be deployed as a sidecar or microservice in your cloud.
Project: TiDB (App Definition and Development / Database)
File: 2021-10-09-select-for-update-of-tables.md

Author(s): Tracking Issue: https://github.com/pingcap/tidb/issues/28689 If specific tables are named in a locking clause, then only rows coming from those tables are locked. Any other tables used in the SELECT are simply read as usual. In a multi-table join scenario, simply using the for update clause locks all the rows read in the tables participating in the join. The lock granularity is too coarse, and some of the tables participating in the join may not need to be subsequently updated. In MySQL 8.0, the `of tables` option was introduced to support locking only the specified tables. The first thing is that the parser should support the `of tables` syntax. This has not been supported before. Store the table names in `SelectLockInfo`. This feature is achieved by storing the information in `StmtCtx` and using the table names in StmtCtx to filter the keys that need to be locked when reading all the keys that need to be locked. Compatibility with MySQL 8.0 has been enhanced here. Since the `of tables` syntax was not supported before, it does not break any compatibility.
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: adr008-default-catalog-file-name.md

id: adrs-adr008 title: 'ADR008: Default Catalog File Name' description: Architecture Decision Record (ADR) log on Default Catalog File Name While the spec for the catalog file format is well described in , guidance was not provided as to the name of the catalog file. Following discussion in , a decision was made. The catalog file should be named ```shell catalog-info.yaml ``` This name is a default, not a requirement. The catalog file will work with Backstage regardless of its name.
Project: ThreatMapper (Provisioning / Security & Compliance)
File: sboms.md

title: Generating SBOMs As part of the vulnerability scanning process, the ThreatMapper sensor interrogates the running workloads and hosts and generates a runtime SBOM (Software Bill of Materials) for each target. This runtime SBOM is forwarded to the Management Console for vulnerability matching. Not all production workloads go through a formal supply-chain analysis process during CI (continuous integration), and workloads can be patched and updated during runtime. Often, the SBOM coverage is far from complete and risks being out-of-date to the runtime state. ThreatMapper caches runtime SBOMs for scanned workloads, and makes these available for inspection through the UI and API. The runtime SBOM enumerates all the packages and software items deployed in the workload, which may drift from the at-build-time SBOM. SBOMs are associated with vulnerability scans. Navigate to the Vulnerabilities > View All Scans results page, and locate the scan for which you would like to obtain the SBOM: You can page through the SBOM results, or download the results as a detailed JSON file:
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.4.0-beta.2.md

layout: release date: 2020-7-8 tag: v0.4.0-beta.2 Meshery Added initial kubeconfig. Mesheryctl Removed fatal error due to missing `meshery.yaml`. Documentation Updated Kuma adapter logo in Meshery Docs. Added network ports to the adapters table. Added providers screenshot. Added all supported platforms to list. Added nighthawk as a load generator. Fixed broken link in EKS page.
Project: StarRocks (App Definition and Development / Database)
File: SHOW_FILE.md

displayed_sidebar: "English" You can execute the SHOW FILE statement to view the information about a file stored in a database. :::tip Users with any privilege on the database to which a file belongs can perform this operation. If a file belongs to a database, all users that have access to this database can use this file. ::: ```SQL SHOW FILE [FROM database] ``` The file information returned by this statement is as follows: `FileId`: the globally unique ID of the file. `DbName`: the database to which the file belongs. `Catalog`: the category to which the file belongs. `FileName`: the name of the file. `FileSize`: the size of the file. The unit is bytes. `MD5`: the message-digest algorithm that is used to check the file. View the file stored in `my_database`. ```SQL SHOW FILE FROM my_database; ```
Project: YugabyteDB (App Definition and Development / Database)
File: managed-freetrial.md

title: Start a free trial linkTitle: Start a free trial description: Start a free trial of YugabyteDB Managed to conduct POCs and performance testing. headcontent: Explore all YugabyteDB Managed features menu: preview_yugabyte-cloud: identifier: managed-freetrial parent: yugabytedb-managed weight: 20 type: docs To go beyond the capabilities of the , start a free trial to receive free credits towards creating and exploring other features in YugabyteDB Managed. To start a free trial: . . Click Start Free Trial to display the Start Your Free Trial form. If you have a promo code, enter it and click Start Free Trial to start your trial right away. Otherwise, enter your contact details and click Start Free Trial. A free trial link is sent to your email. Click the link in the email to get started. After the free trial begins, you can use your credits to create dedicated clusters in a , including: Single region multi zone Replicated across regions Partition by region Read replicas <!-- any time. You won't be charged until your credits are used.--> Add a payment method any time. You won't be charged until your credits are used. Only one free trial can be applied to an account. The free trial features the Professional plan. Enterprise plan features are not included. Not all regions are available during free trials. After your trial ends, depending on your plan, you may lose access to some features.
Project: KICS (Provisioning / Security & Compliance)
File: 678fd659-96f2-454a-a2a0-c2571f83a4a3.md

title: RDP Access Is Not Restricted hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 678fd659-96f2-454a-a2a0-c2571f83a4a3 Query name: RDP Access Is Not Restricted Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Networking and Firewall URL: Check if the Google compute firewall allows unrestricted RDP access. Allowed ports should not contain RDP port 3389<br> ```tf title="Positive test num. 1 - tf file" hl_lines="25 12 36" resource "googlecomputefirewall" "positive1" { name = "test-firewall" network = googlecomputenetwork.default.name direction = "INGRESS" allow { protocol = "icmp" } allow { protocol = "tcp" ports = ["80", "8080", "1000-2000","3389"] } source_tags = ["web"] source_ranges = ["0.0.0.0/0"] } resource "googlecomputefirewall" "positive2" { name = "test-firewall" network = googlecomputenetwork.default.name allow { protocol = "udp" ports = ["80", "8080", "1000-2000","21-3390"] } source_tags = ["web"] source_ranges = ["::/0"] } resource "googlecomputefirewall" "positive3" { name = "test-firewall" network = googlecomputenetwork.default.name allow { protocol = "all" } source_tags = ["web"] source_ranges = ["::/0"] } ``` ```tf title="Negative test num. 1 - tf file" resource "googlecomputefirewall" "negative1" { name = "test-firewall" network = googlecomputenetwork.default.name allow { protocol = "icmp" } allow { protocol = "tcp" ports = ["80", "8080", "1000-2000"] } source_tags = ["web"] } ```