cwielenb/CNCF-Dataset huggingface dataset:
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: release-notes-template.md

id: v1.1.0 title: v1.1.0 description: Backstage Release v1.1.0 These are the release notes for the v1.1.0 release of . A huge thanks to the whole team of maintainers and contributors as well as the amazing Backstage Community for the hard work in getting this release developed and done. <short description>. Contributed by in This release does not contain any security fixes. <or> @backstage/<package-name>, please upgrade to the latest version if you are using this module. We recommend that you keep your Backstage project up to date with this latest release. For more guidance on how to upgrade, check out the documentation for . Below you can find a list of links and references to help you learn about and start using this new release. , , and Backstage's for discussions and support Backstage , , and Sign up for our if you want to be informed about what is happening in the world of Backstage.
Project: Devfile (App Definition and Development / Application Definition & Image Build)
File: MAINTAINERS.md

Official list of Devfile projects maintainers. Please keep the below list sorted in ascending order. | Maintainer | GitHub ID | Affiliation | | | | -- | | Andreas Resios | @resios | AWS | | Angel Misevski | @amisevsk | Red Hat | | Elson Yuen | @elsony | Red Hat | | Ida Olsen | @miaida | AWS | | Mario Loriedo | @l0rd | Red Hat | | Stevan Le Meur | @slemeur | Red Hat | | Tomas Kral | @kadel | Red Hat |
Project: KICS (Provisioning / Security & Compliance)
File: 73e42469-3a86-4f39-ad78-098f325b4e9f.md

title: MySQL SSL Connection Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 73e42469-3a86-4f39-ad78-098f325b4e9f Query name: MySQL SSL Connection Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: Make sure that for MySQL Database Server, 'Enforce SSL connection' is enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="17" resource "azurermmysqlserver" "positive1" { name = "webflux-mysql-${var.environment}${randominteger.rndint.result}" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name administrator_login = "webflux-${var.environment}" administratorloginpassword = random_string.password.result skuname = "BGen5_2" storage_mb = 5120 version = "5.7" autogrowenabled = true backupretentiondays = 7 infrastructureencryptionenabled = true publicnetworkaccess_enabled = true sslenforcementenabled = false } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermmysqlserver" "negative1" { name = "webflux-mysql-${var.environment}${randominteger.rndint.result}" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name administrator_login = "webflux-${var.environment}" administratorloginpassword = random_string.password.result skuname = "BGen5_2" storage_mb = 5120 version = "5.7" autogrowenabled = true backupretentiondays = 7 infrastructureencryptionenabled = true publicnetworkaccess_enabled = true sslenforcementenabled = true } ```
Project: Apache StreamPipes (App Definition and Development / Streaming & Messaging)
File: RELEASE_VALIDATION.md

<!-- ~ 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. ~ --> An Apache StreamPipes release consists of a single source release starting from version 0.69.0: streampipes To validate and test a release candidate, please visit our validation guide:
Project: VoltDB (App Definition and Development / Database)
File: CommandLogging.md

VoltDB uses Command Logging to continuously save to disk the latest state of the data maintained in main memory. Rather than updating data on disk in a logical structure similar to how it is stored in memory, it relies on snapshots to provide a given checkpoint and stores the commands that modified the state from that checkpoint in an append-only log. This improves performance by using continuous writes to disk rather than random disk I/O, so that the disk persistence is able to keep up with the high rate of transaction processing that VoltDB achieves in memory. Snapshots are taken automatically as needed to keep disk usage and recovery from excessively growing. Command logging is configured in the deployment file and set at startup. It has a few configurable options: mode (synchronous or asynchronous) frequency (fsync to disk when given time in milliseconds or number of transactions have elapsed, whichever comes first) log size (size in MB the command log should grow before a snapshot is taken) path for command log files path for command log snapshots Here is a typical configuration that uses asynchronous mode and is well suited for development and production deployments on servers that have only a single disk: <?xml version="1.0"?> <deployment> <cluster sitesperhost="8"/> <commandlog enabled="true" synchronous="false"> <frequency time="200" transactions="100000"/> </commandlog> <httpd enabled="true"> <jsonapi enabled="true" /> </httpd> </deployment> Here is a more advanced command log configuration using synchronous mode with a separate fast disk dedicated for the command log: <?xml version="1.0"?> <deployment> <cluster sitesperhost="8"/> <paths> <commandlog path="/fastdisk/voltdb/command_log/" /> <commandlogsnapshot path="/maindisk/voltdb/commandlogsnapshot/" /> </paths> <commandlog enabled="true" synchronous="true" logsize="5120"> <frequency time="2" transactions="500"/> </commandlog> <httpd enabled="true"> <jsonapi enabled="true" /> </httpd> </deployment> This allows the frequency for fsync to disk to be set to 1-2 milliseconds or a smaller number of transactions, because the disk is either an SSD or has a battery-backed write cache, and it is dedicated mainly to the command log so writes won't be impeded by snapshots or other disk I/O such as log4j files or export files. The log size is set to 5GB rather than the default 1GB, which reduces the frequency of command log snapshots, but for high write throughput workloads results in a fairly typical frequency rather than running continuously. Reference: Describes in more detail how command logging works. Contains an excellent step-by-step description of the configurable options of command logging and the hardware considerations. An academic computer science paper that describes the reasoning behind command logging.
Project: KICS (Provisioning / Security & Compliance)
File: 1b44e234-3d73-41a8-9954-0b154135280e.md

title: Shielded VM Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 1b44e234-3d73-41a8-9954-0b154135280e Query name: Shielded VM Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Compute instances must be launched with Shielded VM enabled, which means the attribute 'shieldedinstanceconfig' must be defined and its sub attributes 'enablesecureboot', 'enablevtpm' and 'enableintegrity_monitoring' must be set to true<br> ```tf title="Positive test num. 1 - tf file" hl_lines="2 38 10 60 49 19 28" data "googlecomputeinstance" "appserver1" { name = "primary-application-server" zone = "us-central1-a" } data "googlecomputeinstance" "appserver2" { name = "primary-application-server" zone = "us-central1-a" shieldedinstanceconfig { enablesecureboot = true enable_vtpm = true } } data "googlecomputeinstance" "appserver3" { name = "primary-application-server" zone = "us-central1-a" shieldedinstanceconfig { enablesecureboot = true enableintegritymonitoring = true } } data "googlecomputeinstance" "appserver4" { name = "primary-application-server" zone = "us-central1-a" shieldedinstanceconfig { enable_vtpm = true enableintegritymonitoring = true } } data "googlecomputeinstance" "appserver5" { name = "primary-application-server" zone = "us-central1-a" shieldedinstanceconfig { enablesecureboot = false enable_vtpm = true enableintegritymonitoring = true } } data "googlecomputeinstance" "appserver6" { name = "primary-application-server" zone = "us-central1-a" shieldedinstanceconfig { enablesecureboot = true enable_vtpm = false enableintegritymonitoring = true } } data "googlecomputeinstance" "appserver7" { name = "primary-application-server" zone = "us-central1-a" shieldedinstanceconfig { enablesecureboot = true enable_vtpm = true enableintegritymonitoring = false } } ``` ```tf title="Negative test num. 1 - tf file" data "googlecomputeinstance" "appserver" { name = "primary-application-server" zone = "us-central1-a" shieldedinstanceconfig { enablesecureboot = true enable_vtpm = true enableintegritymonitoring = true } } ```
Project: YugabyteDB (App Definition and Development / Database)
File: unq-containing-paths.md

title: Restricting a set of paths to the smaller set that contains them all headerTitle: Restricting a set of paths to just the unique longest paths that contain them all linkTitle: Unique containing paths description: This section shows how restricting a set of paths to the smaller set that contains them all provides a compact way to visualize find_paths() results. menu: v2.18: identifier: unq-containing-paths parent: traversing-general-graphs weight: 70 type: docs Before trying the code in this section, make sure that you have created the "edges" table (see ) and installed all the code shown in the section . Start by defining an example undirected cyclic graph and by computing all the paths from a selected start node: ```plpgsql delete from edges; alter table edges drop constraint if exists edges_chk cascade; alter table edges add constraint edgeschk check(node1 <> node_2); insert into edges(node1, node2) values ('n01', 'n02'), ('n02', 'n03'), ('n03', 'n04'), ('n04', 'n05'), ('n05', 'n06'), ('n06', 'n07'), ('n07', 'n08'), ('n01', 'n09'), ('n09', 'n05'), ('n05', 'n10'), ('n10', 'n08'); -- Implement the denormalization. insert into edges(node1, node2) select node2 as node1, node1 as node2 from edges; ``` Re-create the simpler implementation of "findpaths()" that implements the cycle prevention code, shown at . Now generate the paths that start at the node "n01"_, restrict these to just the shortest paths, and restrict these further to the set of longest unique containing paths: ```plpgsql call findpaths(startnode => 'n01'); call restricttoshortestpaths('rawpaths', 'temp_paths'); call restricttounqcontainingpaths('temppaths', 'unqcontaining_paths'); \t on select t from listpaths('unqcontaining_paths'); \t off ``` This is the result: ```output path # cardinality path -- - 1 4 n01 > n02 > n03 > n04 2 5 n01 > n09 > n05 > n06 > n07 3 5 n01 > n09 > n05 > n10 > n08 ``` These are the unique containing paths of the shortest paths from the raw paths. Here they are. The pictures are numbered with the value assigned by (see the implementation of ): For contrast, do this: ```plpgsql call restricttounqcontainingpaths('rawpaths', 'temppaths'); call restricttolongestpaths('temppaths', 'unqcontainingpaths'); \t on select t from listpaths('unqcontaining_paths'); \t off ``` This is the result: ```output path # cardinality path -- - 1 6 n01 > n02 > n03 > n04 > n05 > n09 2 6 n01 > n09 > n05 > n04 > n03 > n02 3 9 n01 > n02 > n03 > n04 > n05 > n06 > n07 > n08 > n10 4 9 n01 > n02 > n03 > n04 > n05 > n10 > n08 > n07 > n06 ``` These are longest paths from the unique containing paths of the raw paths. Here they are. The pictures are again numbered with the value assigned by `row_number()`. These two pictures together provide a very compact way to understand the meaning of the set of twenty-six distinct raw paths produced by `call findpaths(startnode=>'n01')`.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: 09_io_avro.md

Prompt: Write a sample Java code snippet that reads data from an Avro file using Apache Beam. Response: Your Apache Beam pipeline can read data from Apache Avro files using the AvroIO connector. Here is an example of how to achieve this: ```java import org.apache.avro.Schema; import org.apache.avro.generic.GenericRecord; import org.apache.beam.sdk.Pipeline; import org.apache.beam.sdk.extensions.avro.AvroIO; import org.apache.beam.sdk.options.Default; import org.apache.beam.sdk.options.Description; import org.apache.beam.sdk.options.PipelineOptions; import org.apache.beam.sdk.options.PipelineOptionsFactory; import org.apache.beam.sdk.transforms.DoFn; import org.apache.beam.sdk.transforms.ParDo; import org.slf4j.Logger; import org.slf4j.LoggerFactory; public class ReadGenericAvroIO { private static final Logger LOG = LoggerFactory.getLogger(ReadGenericAvroIO.class); // Define pipeline options for the pipeline public interface ReadAvroOptions extends PipelineOptions { @Description("Path to the Avro file to read from") @Default.String("gs://<your-bucket-name]/[your-object-name]/filename.avro") String getInput(); void setInput(String value); } public static void main(String[] args) { // Create pipeline options to parse command-line arguments ReadAvroOptions options = PipelineOptionsFactory.fromArgs(args).withValidation().as(ReadAvroOptions.class); // Create a pipeline Pipeline p = Pipeline.create(options); // Declare the schema of the Avro file String fields = "[{ \"name\": \"months\", \"type\": \"string\" }, { \"name\": \"amount\", \"type\": \"string\" }]"; String schema = "{\"type\": \"record\", \"name\": \"AvroRecord\",\"fields\":" + fields + "}"; // Parse the schema string into a Schema object Schema avroSchema = new Schema.Parser().parse(schema); // Read the Avro file using the AvroIO connector p.apply(AvroIO.readGenericRecords(avroSchema).from(options.getInput())) // Parse the GenericRecord object into a string and log it .apply("Parse and log", ParDo.of(new DoFn<GenericRecord, String>() { @ProcessElement public void processElement(ProcessContext c) { GenericRecord record = c.element(); String message = "Month: " + record.get("month") + ". Amount: " + record.get("amount"); LOG.info(message); c.output(message); } })); // Execute the pipeline p.run(); } } ``` The `ReadAvroOptions` interface is used to define the command-line argument `--input`, which specifies the path to the Avro file. This code uses pipeline options to define the required argument.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: feat-12781.en.md

Added metrics related to EMQX durable storage to Prometheus. New metrics: `emqxdsegress_batches` `emqxdsegressbatchesretry` `emqxdsegressbatchesfailed` `emqxdsegress_messages` `emqxdsegress_bytes` `emqxdsegressflushtime` `emqxdsstorebatchtime` `emqxdsbuiltinnexttime` `emqxdsstoragebitfieldltscounterseek` `emqxdsstoragebitfieldltscounternext` `emqxdsstoragebitfieldltscountercollision` Note: these metrics are only visible when session persistence is enabled. Number of persisted messages has been also added to the dashboard.
Project: ShardingSphere (App Definition and Development / Database)
File: show-migration-source-storage-units.en.md

+++ title = "SHOW MIGRATION SOURCE STORAGE UNITS" weight = 5 +++ The `SHOW MIGRATION SOURCE STORAGE UNITS` syntax is used to query the registered migration source storage units {{< tabs >}} {{% tab name="Grammar" %}} ```sql ShowStorageUnit ::= 'SHOW' 'MIGRATION' 'SOURCE' 'STORAGE' 'UNITS' ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} | Column | Description | |--|| | name | Storage unit name | | type | Storage unit type | | host | Storage unit host | | port | Storage unit port | | db | Database name | | attribute | Storage unit attribute | Query registered migration source storage units ```sql SHOW MIGRATION SOURCE STORAGE UNITS; ``` ```sql mysql> SHOW MIGRATION SOURCE STORAGE UNITS; ++-+--++-++++++--++ | name | type | host | port | db | connectiontimeoutmilliseconds | idletimeoutmilliseconds | maxlifetimemilliseconds | maxpoolsize | minpoolsize | readonly | otherattributes | ++-+--++-++++++--++ | ds1 | MySQL | 127.0.0.1 | 3306 | migrationds_0 | | | | | | | | ++-+--++-++++++--++ 1 row in set (0.01 sec) ``` `SHOW`, `MIGRATION`, `SOURCE`, `STORAGE`, `UNITS`
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: memcachedOperatorDown.md

No running memcached-operator-controller-manager pods were detected in the last 5 min. Complete failure in the <code>Memcached</code> CR lifecycle management. i.e. launching a new <code>Memcached</code> instance or shutting down an existing one. Observe the status of the memcached-operator-controller-manager deployment: <code>kubectl get deploy memcached-operator-controller-manager -n mecmached-operator-system -o yaml</code> There can be several reasons for the memcached-operator-controller-manager pod to be down, identify the root cause and fix it. Check the status of the memcached-operator-controller-manager deployment to find out more information. The following command will provide the associated events and show if there are any issues with pulling an image, crashing pod, etc. <code>kubectl describe deploy memcached-operator-controller-manager -n memcached-operator-system</code> Check if there are issues with the nodes. For example, if they are in a NotReady state. </code>kubectl get nodes</code>
Project: KICS (Provisioning / Security & Compliance)
File: 3ab1f27d-52cc-4943-af1d-43c1939e739a.md

title: S3 Bucket Access to Any Principal hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 3ab1f27d-52cc-4943-af1d-43c1939e739a Query name: S3 Bucket Access to Any Principal Platform: Ansible Severity: <span style="color:#ff0000">Critical</span> Category: Access Control URL: Checks if the S3 bucket is accessible for all users<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4" name: Create a simple s3 bucket with a policy amazon.aws.s3_bucket: name: mys3bucket policy: Version: "2012-10-17" Id: "sqspolicy" Statement: Sid: First Effect: Allow Principal: "*" Action: "*" Resource: ${awssqsqueue.q.arn} Condition: ArnEquals: aws:SourceArn: ${awssnstopic.example.arn} ``` ```yaml title="Negative test num. 1 - yaml file" name: Create a simple s3 bucket with a policy amazon.aws.s3_bucket: name: mys3bucket policy: Version: '2012-10-17' Id: sqspolicy Statement: Sid: First Effect: Deny Principal: '*' Action: '*' Resource: ${awssqsqueue.q.arn} Condition: ArnEquals: aws:SourceArn: ${awssnstopic.example.arn} ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_target_pools.md

+++ title = "googlecomputetarget_pools resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputetarget_pools" identifier = "inspec/resources/gcp/googlecomputetargetpools.md googlecomputetargetpools resource" parent = "inspec/resources/gcp" +++ A `googlecomputetarget_pools` is used to test a Google TargetPool resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputetarget_pools(project: 'chef-gcp-inspec', region: 'europe-west2') do its('names') { should include 'inspec-gcp-target-pool' } its('sessionaffinities') { should include 'CLIENTIP' } end ``` Properties that can be accessed from the `googlecomputetarget_pools` resource: See the resource for more information. `backup_pools` : an array of `googlecomputetargetpool` backuppool `creation_timestamps` : an array of `googlecomputetargetpool` creationtimestamp `descriptions` : an array of `googlecomputetarget_pool` description `failover_ratios` : an array of `googlecomputetargetpool` failoverratio `health_checks` : an array of `googlecomputetargetpool` healthcheck `ids` : an array of `googlecomputetarget_pool` id `instances` : an array of `googlecomputetarget_pool` instances `names` : an array of `googlecomputetarget_pool` name `session_affinities` : an array of `googlecomputetargetpool` sessionaffinity `regions` : an array of `googlecomputetarget_pool` region 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: YugabyteDB (App Definition and Development / Database)
File: ddl_drop_database.md

title: DROP DATABASE statement [YSQL] headerTitle: DROP DATABASE linkTitle: DROP DATABASE description: Use the DROP DATABASE statement to remove a database and all of its associated objects from the system. menu: v2.18: identifier: ddldropdatabase parent: statements type: docs Use the `DROP DATABASE` statement to remove a database and all of its associated objects from the system. This is an irreversible statement. A currently-open connection to the database will be invalidated and then closed as soon as the statement is executed using that connection. {{%ebnf%}} drop_database {{%/ebnf%}} Remove a database and all associated objects. All objects that are associated with `database_name` such as tables will be invalidated after the drop statement is completed. All connections to the dropped database would be invalidated and eventually disconnected. Specify the name of the database.
Project: Meshery (Provisioning / Automation & Configuration)
File: rabbitmq-operator.md

layout: integration title: RabbitMQ Operator subtitle: Collaborative and visual infrastructure as code for RabbitMQ Operator image: /assets/img/integrations/rabbitmq-operator/icons/color/rabbitmq-operator-color.svg permalink: extensibility/integrations/rabbitmq-operator docURL: https://docs.meshery.io/extensibility/integrations/rabbitmq-operator description: integrations-category: App Definition and Development integrations-subcategory: Streaming & Messaging registrant: Artifact Hub components: name: rabbitmq-cluster colorIcon: assets/img/integrations/rabbitmq-operator/components/rabbitmq-cluster/icons/color/rabbitmq-cluster-color.svg whiteIcon: assets/img/integrations/rabbitmq-operator/components/rabbitmq-cluster/icons/white/rabbitmq-cluster-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