cwielenb/CNCF-Dataset huggingface dataset:
Project: StackRox (Provisioning / Security & Compliance)
File: run-e2e-tests-README.md

`run-e2e-tests.sh` aims to provide a secure and accessible method for running E2E tests that typically are only supported in CI. It does this by importing test credentials from hashicorp vault and using the same test container that CI uses. This should facilitate a test development workflow where the overhead to make changes to test code and verify those changes is minimal. By default this test runner emulates CI and relies on the output of `make tag` to determine which images are deployed via `deploy/` scripts. When local changes are made this tag goes `-dirty` and that suffix is dropped to facilitate local changes to tests without the need to build and push `-dirty` images. In order to satisfy the tight coupling between the `deploy/` scripts and roxctl version, a matching `roxctl` is pulled from the public image and supplied to the test container as `/usr/local/bin/roxctl`. A `-t` flag can be used to set a particular version and override the default behaviour of `make tag`. There are a number of required steps to get access to vault: Log in to the secrets collection manager at https://selfservice.vault.ci.openshift.org/secretcollection?ui=true (This is a Red Hat-ism and will require SSO) Ask in #epic-ci-improvement to be added to the collections required for this test: stackrox-stackrox-initial and stackrox-stackrox-e2e-tests. Login to the vault at: https://vault.ci.openshift.org/ui/vault/secrets (Use OIDC) You should see these secret collections under kv/ Copy a 'token' from that UI and enter it at the prompt when running the `run-e2e-tests.sh` script. (You can skip the prompt by setting this to a VAULT_TOKEN environment variable) The 'token' will expire hourly and you will need to renew it through the vault UI. For basic usage see `run-e2e-tests.sh -h` Configure only: ``` run-e2e-tests.sh -c qa ``` Run a single suite (assumes a prior config step was executed): ``` run-e2e-tests.sh -d qa DeploymentTest ``` The `-d` option collects debug for failing tests under `/tmp/qa-tests-backend-logs/` similar to how CI tests operate. Run basic acceptance tests (BAT): ``` run-e2e-tests.sh qa ``` Only run tests (assumes a prior config step was executed): ``` run-e2e-tests.sh --test-only qa ``` Run tests repeatedly: ``` run-e2e-tests.sh --spin-cycle=100 qa IntegrationsSplunkViolationsTest ``` Run a gradle task (assumes a prior config step was executed): ``` run-e2e-tests.sh qa testParallel ``` Run everything just like CI: ``` run-e2e-tests.sh -d e2e ``` TBD - split configuration from test. separate the various test facets (roxctl, integration, destructive, etc)
Project: StackRox (Provisioning / Security & Compliance)
File: whats-this.md

`defaults/` directory ====================== This directory provides a set of files that provide a lighter-weight interface for configuring defaults in the Helm chart, allowing the use of template expressions (including referencing previously applied defaults) without requiring (an excessive amount of) template control structures (such as `{{ if kindIs "invalid" ... }}` to determine if a value has already been set). After applying some "bootstrap" configuration (such as for making available API server resources visible in a uniform manner), each `.yaml` file in this directory is processed in an order determined by its name (hence the `NN-` prefixes). Each YAML file consists of multiple documents (separated by `` lines) that are rendered as templates and then merged into the effective configuration, giving strict preference to already set values. Having a deterministic order is important for being able to rely on previously configured values (either specified by the user or applied as a default). For example, the file ```yaml group: setting: "foo" anotherSetting: 3 group: derivedSetting: {{ printf "%s-%d" .rox.group.setting .rox.group.anotherSetting }} ``` combined with the command-line setting `--set group.setting=bar` will result in the following "effective" configuration: ```yaml group: setting: "bar" # user-specified value takes precedence - default value "foo" not applied anotherSetting: 3 # default value derivedSetting: bar-3 # combination of user-specified value and default value; "pure" default without ``` Caveats: Templating instructions must be contained to a single document within the multi-document YAML files. In particular, the `` separator must not be within a conditionally rendered block, or emitted by templating code. It is recommended to contain dependencies between default settings to a single YAML file. While the `NN-` prefixes ensure a well-defined application order of individual files, having dependent blocks in the same file adds clarity.
Project: Apache Storm (App Definition and Development / Streaming & Messaging)
File: storm-jms-spring.md

title: Storm JMS Integration layout: documentation documentation: true Create a Spring applicationContext.xml file that defines one or more destination (topic/queue) beans, as well as a connection factory. <?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://www.springframework.org/schema/beans" xmlns:amq="http://activemq.apache.org/schema/core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd"> <amq:queue id="notificationQueue" physicalName="backtype.storm.contrib.example.queue" /> <amq:topic id="notificationTopic" physicalName="backtype.storm.contrib.example.topic" /> <amq:connectionFactory id="jmsConnectionFactory" brokerURL="tcp://localhost:61616" /> </beans>
Project: CloudEvents (App Definition and Development / Streaming & Messaging)
File: partitioning.md

This extension defines an attribute for use by message brokers and their clients that support partitioning of events, typically for the purpose of scaling. Often in large scale systems, during times of heavy load, events being received need to be partitioned into multiple buckets so that each bucket can be separately processed in order for the system to manage the incoming load. A partitioning key can be used to determine which bucket each event goes into. The entity sending the events can ensure that events that need to be placed into the same bucket are done so by using the same partition key on those events. As with the main , the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in . However, the scope of these key words is limited to when this extension is used. For example, an attribute being marked as "REQUIRED" does not mean it needs to be in all CloudEvents, rather it needs to be included only when this extension is being used. Type: `String` Description: A partition key for the event, typically for the purposes of defining a causal relationship/grouping between multiple events. In cases where the CloudEvent is delivered to an event consumer via multiple hops, it is possible that the value of this attribute might change, or even be removed, due to protocol semantics or business processing logic within each hop. Examples: The ID of the entity that the event is associated with Constraints: REQUIRED MUST be a non-empty string
Project: Chef InSpec (Provisioning / Security & Compliance)
File: etc_hosts.md

+++ title = "etc_hosts resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "etc_hosts" identifier = "inspec/resources/os/etchosts.md etchosts resource" parent = "inspec/resources/os" +++ Use the `etc_hosts` Chef InSpec audit resource to test rules set to match IP addresses with hostnames. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.37.6 of InSpec. An etc/hosts rule specifies an IP address and what its hostname is along with optional aliases it can have. Use the `.where` clause to match a property to one or more rules in the hosts file: describe etchosts.where { ipaddress == 'value' } do its('primary_name') { should cmp 'hostname' } its('allhostnames') { should cmp 'list' } end Use the optional resource parameter to give an alternative path to the hosts file: describe etchosts('path/to/hosts').where { ipaddress == 'value' } do its('primary_name') { should cmp 'hostname' } its('allhostnames') { should cmp 'list' } end where `ip_address` is the IP address of the hostname in either ipv4 or ipv6 format. `primary_name` is the name associated with the IP address. `allhostnames` is a list including the primary_name as the first entry followed by any alias names the host has. The `ip_address` property returns a string array of ip addresses specified in the etc/hosts file. its('ip_address') { should cmp '127.0.1.154' } The `primaryname` property returns a string array of primarynames specified in the etc/hosts file. its('primary_name') { should cmp 'localhost' } The `allhostnames` property returns a two-dimensional string array where each entry has the primary_name first followed by any aliases. its('allhostnames') { should cmp 'list' } describe etchosts.where { primaryname == 'localhost' } do its('ip_address') { should cmp '127.0.1.154' } end describe etchosts.where { ipaddress == '::1' } do its('primary_name') { should cmp 'localhost' } end describe etchosts.where { ipaddress == '127.0.1.154' } do its('allhostnames') { should eq [['localhost', 'localhost.localdomain', 'localhost4', 'localhost4.localdomain4'], ['localhost', 'localhost.localdomain', 'localhost6', 'localhost6.localdomain6']] } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}}
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: v1.7.1.md

This hotfix release addresses a change made in how actor timers are validated during creation. Specifically, `DueTime` can be set to 0 to have a reminder fire immediately. Additionally, this hotfix addresses an issue in the Apache Pulsar pubsub component preventing the use of namespaces when publishing to topics. Lastly, there is a fix to avoid a nil dereference crash on the sidecar when using API logging feature in gRPC API. An Actor Timer with a `DueTime` of `0` will now pass validation allowing timers to fire immediately. The correct value the Pulsar topic is now specified on publishing, allowing the use of namespaces. Registering an Actor Timer with a `DueTime` of `0` would fail and the Timer would not be started. A change introduced in release 1.6 caused Timers to be invalidated if their `DueTime` was in the past. However, when the `DueTime` is 0, signifying an immediate fire, it is set in Dapr to the current time. After it was set to the current time, it would later be compared to the current time again. As these time comparisons did not share the value for current time, it is almost guaranteed that the `DueTime` would now appear to be in the past. Revert the code to pre-1.6 behavior which allows `DueTimes` to be in the past as that still equates to firing immediately. When enabling the API logging preview feature, a nil reference can occur and crash the sidecar. Logic for API logging in gRPC assumed gRPC `info` object was always not nil, however it has been reported that it could be nil when invoking an actor as per issue . Add a nil check for API logging preview feature in gRPC API.
Project: KICS (Provisioning / Security & Compliance)
File: 5fb49a69-8d46-4495-a2f8-9c8c622b2b6e.md

title: S3 Bucket Object Not Encrypted hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 5fb49a69-8d46-4495-a2f8-9c8c622b2b6e Query name: S3 Bucket Object Not Encrypted Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: S3 Bucket Object should have server-side encryption enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="14" resource "awss3bucket" "examplebucket" { bucket = "examplebuckettftest" acl = "private" versioning { enabled = true } objectlockconfiguration { objectlockenabled = "Enabled" } } resource "awss3bucketobject" "examplebucketobject" { key = "someobject" bucket = awss3bucket.examplebucket.id source = "index.html" } ``` ```tf title="Negative test num. 1 - tf file" resource "awss3bucket" "examplebucket" { bucket = "examplebuckettftest" acl = "private" versioning { enabled = true } objectlockconfiguration { objectlockenabled = "Enabled" } } resource "awss3bucketobject" "examplebucketobject" { key = "someobject" bucket = awss3bucket.examplebucket.id source = "index.html" serversideencryption = "AES256" } ```
Project: YugabyteDB (App Definition and Development / Database)
File: sismember.md

title: SISMEMBER linkTitle: SISMEMBER description: SISMEMBER menu: preview: parent: api-yedis weight: 2290 aliases: /preview/api/redis/sismember /preview/api/yedis/sismember type: docs `SISMEMBER key member_value` This command is a predicate for whether or not a value is a member of a set that is associated with the given `key`. If the `key` is associated with a value that is not a set, an error is raised. If the `key` does not exist, its associated set is empty, and the command returns 0. If the `member` belongs to the given set, an integer of 1 is returned. Returns 1 if the specified member exists. Returns 0 otherwise. ```sh $ SADD yuga_world "America" ``` ``` 1 ``` ```sh $ SISMEMBER yuga_world "America" ``` ``` 1 ``` ```sh $ SISMEMBER yuga_world "Moon" ``` ``` 0 ``` , , ,
Project: Fluvio (App Definition and Development / Streaming & Messaging)
File: release_checklist.md

name: New Release Checklist about: Process to follow for running the Fluvio release title: "[Release Checklist]:" labels: tracking assignees: '' The following checklist covers all the steps for running release. For more detail, refer to with this checklist template and docs. Verify if they are up to date or will need updates [ ] Inform team that release is about to begin [ ] Ensure no merges are in flight [ ] Create a PR for release [ ] Update `VERSION` and `CHANGELOG.md` files (do not place a \n in the VERSION file, it breaks the CI) [ ] Merge the PR (Retry at least once if failure) If you are doing a prelease stop here before publishing crates. Only run publish crates for the finalized release. succeeds (Retry at least once if failure) [ ] Announce new release in Discord [ ] To close this issue, create a PR for post release updates and use `release_template.md` Add form data `template=release_template.md` to the PR URL while creating in order to use template e.g. https://github.com/infinyon/fluvio/compare/master...username:your-branch?expand=1&template=release_template.md or `gh pr create --template=release_template.md` a closes issue #x in the body will automatically close this issue on merge. To get a starting point for generating release notes the view-changelog script can be used. git cliff is used to generate a changelog update. The view-changelog script can be used to view the new entries or modifty the CHANGELOG.md file. To view the changelog updates: `actions/view-changelog.sh` or to prepend the updates (some post editing is still usually required): `actions/view-changelog.sh modify`
Project: YugabyteDB (App Definition and Development / Database)
File: CONTRIBUTING.md

In order to accept your pull request, we need you to submit a CLA. You only need to do this once, so if you've done this for another Facebook open source project, you're good to go. If you are submitting a pull request for the first time, just let us know that you have completed the CLA and we can cross-check with your GitHub username. Complete your CLA here: <https://code.facebook.com/cla> If you prefer to sign a paper copy, we can send you a PDF. Send us an e-mail or create a new github issue to request the CLA in PDF format. By contributing to RocksDB, you agree that your contributions will be licensed under the .
Project: Pravega (App Definition and Development / Streaming & Messaging)
File: lts-auto-recovery-steps.md

<!-- Copyright Pravega Authors. 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. --> The following procedure describes online method of doing the LTS recovery. The online method of recovering Pravega from the data in LTS does not require the admin to manually copy metadata chunks. The online method currently only supports filesystem storage type. Having pravega installed with data generated on it. ### Stop traffic ### Enabling admin gateway. ``` kubectl edit pk -n <namespace> ``` And update/add the below properties inside `spec.pravega.options` ```agsl pravegaservice.admin.gateway.port: "9999" pravegaservice.admin.gateway.enable: "true" ``` ### Bringing down controller replicas to 0. ``` kubectl edit pk -n <namespace> ``` And change the value of `controllerReplicas` to 0. ### Executing backup script. ``` ./ltsrecoverybackup.sh ``` This script will call `flush-to-storage` command and save epochs to LTS. ### on PV. ### . ### Uninstall Pravega services. Uninstall pravega, pravega-operator, bookkeeper, bookkeeper-operator, zookeeper, and zookeeper-operator. ### . ### Start pravega Install zookeeper-operator, zookeeper, bookkeeper-operator, bookkeeper, pravega-operator and pravega and start using it. ### Start traffic
Project: StarRocks (App Definition and Development / Database)
File: map_concat.md

displayed_sidebar: "English" Returns the union of the input maps. If a key is found in multiple maps, this function keeps only the last value among these maps, called LAST WIN. For example, `SELECT map_concat(map{1:3},map{1:'4'});` returns `{1:"4"}`. This function is supported from v3.1 onwards. ```Haskell ANYMAP mapconcat(anymap0, anymap1...) ``` `any_mapN`: the map values you want to union. All maps must share a common type. If data types of the input maps are not the same, the return type is the common supertype of the input maps. Returns a MAP of the common supertype of the input maps. ```Plain mysql> SELECT map_concat(map('a',1, 'b',2), map('c',3)); ++ | map_concat(map{'a':1,'b':2}, map{'c':3}) | ++ | {"c":3,"a":1,"b":2} | ++ mysql> select map_concat(map{1:3},map{'3.323':3}); +--+ | map_concat(map{1:3}, map{'3.323':3}) | +--+ | {"3.323":3,"1":3} | +--+ mysql> select map_concat(map{1:3},map{1:'4', 3:'5',null:null}, null); +--+ | map_concat(map{1:3}, map{1:'4',3:'5',NULL:NULL}, NULL) | +--+ | {null:null,1:"4",3:"5"} | +--+ ```
Project: YugabyteDB (App Definition and Development / Database)
File: expr_ocall.md

title: Operators [YCQL] headerTitle: YCQL operators linkTitle: Operators description: Combine multiple expressions using YCQL operators supported in YugabyteDB. menu: v2.18: parent: api-cassandra weight: 1360 type: docs An expression with operators is a compound expression that combines multiple expressions using built-in operators. The following sections discuss the YCQL operators in YugabyteDB. | Operator | Description | |-|-| | `EXISTS`, `NOT EXISTS` | predicate for existence of a row | `EXISTS` and `NOT EXISTS` can only be used in the `IF` clause. | Operator | Description | |-|-| | `-` | numeric negation | | `+` | no-op | | `NOT` | Logical (boolean) negation | Unary `-` and `+` can only be used with constant expressions such as `-77`. | Operator | Description | |-|-| | `OR`, `AND`| Logical (boolean) expression | | `=`, `!=`, `<`, `<=`, `>`, `>=` | Comparison expression | | `+` | Addition, append, or prepend | | `-` | Subtraction or removal | | `*` | Multiplication. Not yet supported | | `/` | Division. Not yet supported | | `ISNULL`, `IS NOT NULL` | Not yet supported comparison expression. | The first argument of comparison operators must be a column. For example, `column_name = 7`. Comparing `NULL` with others always yields a `false` value. Operator `ISNULL` or `IS NULL` must be used when comparing with `NULL`. When `+` and `-` are applied to a NULL argument of `COUNTER` data type, the NULL expression is replaced with a zero value before the computation. When these operators are applied to a NULL expression of all other numeric data types, the computed value is always NULL. Operator `+` either prepends or appends a value to a LIST while operator `-` removes elements from LIST. Operator `+` inserts new distinct elements to a MAP or SET while operator `-` removes elements from them.
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: TDengine.md

TDengine source connector Read external data source data through TDengine. supports query SQL and can achieve projection effect. | name | type | required | default value | |-|--|-|| | url | string | yes | - | | username | string | yes | - | | password | string | yes | - | | database | string | yes | | | stable | string | yes | - | | lower_bound | long | yes | - | | upper_bound | long | yes | - | the url of the TDengine when you select the TDengine e.g. ``` jdbc:TAOS-RS://localhost:6041/ ``` the username of the TDengine when you select the password of the TDengine when you select the database of the TDengine when you select the stable of the TDengine when you select the lower_bound of the migration period the upper_bound of the migration period ```hocon source { TDengine { url : "jdbc:TAOS-RS://localhost:6041/" username : "root" password : "taosdata" database : "power" stable : "meters" lower_bound : "2018-10-03 14:38:05.000" upper_bound : "2018-10-03 14:38:16.800" resulttablename = "tdengine_result" } } ```
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: v1.8.2.md

Dapr 1.8.0 introduced a regression in the direct messaging package, used internally within Dapr to invoke other services and actors, which adversely impacted the operation of resiliency and could, in some situations, cause `daprd` to panic. This issue impacts all users that have enabled the `Resiliency` preview feature in Dapr 1.8.01.8.1, even when no resiliency policies are configured. Because of a mistaken import statement, an old version of a dependency was used in two occurrences, including in the direct messaging package. In the most critical scenario, when service or actor invocation was used and Dapr had the `Resiliency` feature enabled (even if no resiliency policies were configured), errors that should have been permanent (ie. that should not have caused Dapr to retry the operation) were instead considered transient. This had multiple consequences including having Dapr retry operations that should not have been retried and, in some occurrences, could have caused `daprd` to panic. The incorrect import statements have been fixed, so Dapr now behaves as expected (and does not panic) when it encounters a non-retriable error in service and actor invocation.