cwielenb/CNCF-Dataset huggingface dataset:
Project: Apache RocketMQ (App Definition and Development / Streaming & Messaging)
File: Configuration_TLS.md

This section introduce TLS configuration in RocketMQ. User can generate certification files using OpenSSL. Suggested to generate files in Linux. ```shell openssl req -newkey rsa:2048 -keyout carsaprivate.pem -x509 -days 365 -out ca.pem ``` ```shell openssl req -newkey rsa:2048 -keyout server_rsa.key -out server.csr ``` ```shell openssl x509 -req -days 365 -in server.csr -CA ca.pem -CAkey carsaprivate.pem -CAcreateserial -out server.pem ``` ```shell openssl req -newkey rsa:2048 -keyout client_rsa.key -out client.csr ``` ```shell openssl x509 -req -days 365 -in client.csr -CA ca.pem -CAkey carsaprivate.pem -CAcreateserial -out client.pem ``` ```shell openssl pkcs8 -topk8 -v1 PBE-SHA1-RC4-128 -in server_rsa.key -out server.key ``` ```shell openssl pkcs8 -topk8 -v1 PBE-SHA1-RC4-128 -in client_rsa.key -out client.key ``` Create tls.properties, correctly configure the path and password of the generated certificates. ```properties tls.test.mode.enable=false tls.server.need.client.auth=require tls.server.keyPath=/opt/certFiles/server.key tls.server.keyPassword=123456 tls.server.certPath=/opt/certFiles/server.pem tls.server.authClient=false tls.server.trustCertPath=/opt/certFiles/ca.pem ``` If you need to authenticate the client connection, you also need to add the following content to the file. ```properties tls.client.keyPath=/opt/certFiles/client.key tls.client.keyPassword=123456 tls.client.certPath=/opt/certFiles/client.pem tls.client.authServer=false tls.client.trustCertPath=/opt/certFiles/ca.pem ``` Edit the configuration file under the rocketmq/bin path to make tls.properties configurations take effect. The value of "tls.config.file" needs to be replaced by the file path created in step 2. Add following content in JAVA_OPT: ```shell JAVAOPT="${JAVAOPT} -Dtls.server.mode=enforcing -Dtls.config.file=/opt/rocketmq-4.9.3/conf/tls.properties" ``` Add following content in JAVA_OPT: ```shell JAVAOPT="${JAVAOPT} -Dorg.apache.rocketmq.remoting.ssl.mode=enforcing -Dtls.config.file=/opt/rocketmq-4.9.3/conf/tls.properties -Dtls.enable=true" ``` Create tlsclient.properties using by client. Add following content: ```properties tls.client.keyPath=/opt/certFiles/client.key tls.client.keyPassword=123456 tls.client.certPath=/opt/certFiles/client.pem tls.client.trustCertPath=/opt/certFiles/ca.pem ``` Add following parameters in JVM. The value of "tls.config.file" needs to be replaced by the file path we created: ```properties -Dtls.client.authServer=true -Dtls.enable=true -Dtls.test.mode.enable=false -Dtls.config.file=/opt/certs/tlsclient.properties ``` Enable TLS for client linke following: ```Java public class ExampleProducer { public static void main(String[] args) throws Exception { DefaultMQProducer producer = new DefaultMQProducer("pleaserenameuniquegroupname"); //setUseTLS should be true producer.setUseTLS(true); producer.start(); // Send messages as usual. producer.shutdown(); } } ```
Project: Trivy (Provisioning / Security & Compliance)
File: shell-completion.md

Below is example steps to enable shell completion feature for `trivy` cli: ```bash $ echo $SHELL /bin/zsh # For this example it is zsh, but will be vary depend on your $SHELL, maybe /bin/bash or /bin/fish ``` ``` bash $ trivy completion zsh -h Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: echo "autoload -U compinit; compinit" >> ~/.zshrc To load completions in your current shell session: source <(trivy completion zsh); compdef _trivy trivy To load completions for every new session, execute once: trivy completion zsh > "${fpath[1]}/_trivy" trivy completion zsh > $(brew --prefix)/share/zsh/site-functions/_trivy You will need to start a new shell for this setup to take effect. ``` ```bash echo "autoload -U compinit; compinit" >> ~/.zshrc source <(trivy completion zsh); compdef _trivy trivy trivy completion zsh > "${fpath[1]}/_trivy" ``` ```bash $ trivy [tab] aws -- scan aws account completion -- Generate the autocompletion script for the specified shell config -- Scan config files for misconfigurations filesystem -- Scan local filesystem help -- Help about any command image -- Scan a container image kubernetes -- scan kubernetes cluster module -- Manage modules plugin -- Manage plugins repository -- Scan a repository rootfs -- Scan rootfs sbom -- Scan SBOM for vulnerabilities server -- Server mode version -- Print the version ```
Project: ClickHouse (App Definition and Development / Database)
File: uniqexact.md

slug: /en/sql-reference/aggregate-functions/reference/uniqexact sidebar_position: 191 Calculates the exact number of different argument values. ``` sql uniqExact(x[, ...]) ``` Use the `uniqExact` function if you absolutely need an exact result. Otherwise use the function. The `uniqExact` function uses more memory than `uniq`, because the size of the state has unbounded growth as the number of different values increases. Arguments The function takes a variable number of parameters. Parameters can be `Tuple`, `Array`, `Date`, `DateTime`, `String`, or numeric types. See Also
Project: CockroachDB (App Definition and Development / Database)
File: 20150810_select_from_index.md

Feature Name: selectfromindex Status: completed Start Date: 2015-08-10 RFC PR: Cockroach Issue: Extend the SELECT syntax to allow an optional index to be specified in table references. The current table reference syntax is `table` or `database.table`. This syntax would be extended to allow `table@index` and `database.table@index`. Only the column names that are part of the index will be made available to the rest of the query. For example, consider the following table: ```sql CREATE TABLE test ( a INT PRIMARY KEY, b TEXT, c BOOLEAN, CONSTRAINT foo INDEX (b, c) ) ``` The new syntax can be used to restrict the query to only using the index `foo`: ```sql SELECT * FROM test@foo ``` It will be an error to access columns that are not part of the index: ```sql SELECT a FROM test@foo WHERE a > 2 ``` As indexes are optional in SQL, it is difficult to know when an index is used to satisfy a query which in turn makes it difficult to use the existing logic test infrastructure to test correctness of index scans. Providing for specification of an index to read from will make testing of index scans easier and meshes with our desire to allow explicitness in queries. Note that this proposal is essentially a very strict form of an index hint or forced index hint functionality. It is possible we'll adjust the semantics in the future. The grammar will be extended to allow an `@index` suffix to table names. `planner.Select` will be enhanced to select the index to use (if specified). `scanNode` will be enhanced to understand scanning from secondary indexes. This latter work is required to support secondary index scans. Providing an SQL extension inhibits portability. It is expected this functionality will primarily be used for testing. If necessary, we can restrict this functionality to only be available under a flag. There are likely unforeseen interactions with joins. Testing of index scans can use a different test harness than the existing SQL logic test infrastructure. Instead of adding a new delimiter for index specification, we could overload the dot-separated notation for qualified names. For example, `table.index` or `database.table.index`. This would remove the need to adjust the grammar but would add ambiguity as to whether the first element in a qualified name is a table or a database.
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.12.3.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Record IO: seariliizing a byte buffer to CSV fails if buffer contains bytes less than 16. | Major | . | David Bowen | Milind Bhandarkar | | | LocalFileSystem gets a NullPointerException when tries to recover from ChecksumError | Major | fs | Hairong Kuang | Hairong Kuang | | | Lack of logging of exceptions in MapOutputLocation.getFile | Major | . | Owen O'Malley | Devaraj Das | | | the user output/logs are broken from the web ui | Major | . | Owen O'Malley | Arun C Murthy | | | MapTask should wait for the status reporting thread to die before invoking the TaskUmbilicalProtocol.done(taskid) | Major | . | Devaraj Das | Doug Cutting | | | Du command takes a noticable longer time to execute on a large dfs than the 0.11 release | Major | . | Hairong Kuang | Hairong Kuang | | | Reducers don't make "progress" while iterating through values | Major | . | Owen O'Malley | Owen O'Malley | | | task Tracker should be restarted if its jetty http server cannot serve get-map-output files | Major | . | Runping Qi | Devaraj Das |
Project: Tarantool (App Definition and Development / Database)
File: bug_report.md

name: Bug report about: Create a report to help us improve. labels: bug Bug description A clear and concise description of what the bug is. OS: [e.g. Linux/MacOS/FreeBSD/OpenBSD] OS Version: [e.g. Debian 11, FreeBSD 11] Architecture: [amd64, arm] Place `tarantool --version` output here. Steps to reproduce Run two tarantool instances iteractively. Type '...' in console 1. Type '...' in console 2. or reproducer script: ``` <your code here> ``` How to run: Just type `tarantool test.lua`. Actual behavior A clear and concise description of what you see. Expected behavior A clear and concise description of what you expected to happen.
Project: KICS (Provisioning / Security & Compliance)
File: 0e32d561-4b5a-4664-a6e3-a3fa85649157.md

title: ECR Repository Not Encrypted With CMK hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 0e32d561-4b5a-4664-a6e3-a3fa85649157 Query name: ECR Repository Not Encrypted With CMK Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Encryption URL: ECR repositories should be encrypted with customer-managed keys to meet stricter security and compliance requirements on access control, monitoring, and key rotation<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1 18" resource "awsecrrepository" "foo" { name = "bar" imagetagmutability = "IMMUTABLE" imagescanningconfiguration { scanonpush = true } } resource "awsecrrepository" "fooX" { name = "barX" imagetagmutability = "IMMUTABLE" imagescanningconfiguration { scanonpush = true } encryption_configuration { encryption_type = "AES256" } } ``` ```tf title="Negative test num. 1 - tf file" resource "awsecrrepository" "foo2" { name = "bar" imagetagmutability = "IMMUTABLE" imagescanningconfiguration { scanonpush = true } encryption_configuration { encryption_type = "KMS" kms_key = "arn:aws:kms:us-west-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab" } } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: backstage.md

layout: integration title: Backstage subtitle: Collaborative and visual infrastructure as code for Backstage image: /assets/img/integrations/backstage/icons/color/backstage-color.svg permalink: extensibility/integrations/backstage docURL: https://docs.meshery.io/extensibility/integrations/backstage description: integrations-category: App Definition and Development integrations-subcategory: Application Definition & Image Build registrant: Artifact Hub components: featureList: [ "Restore order to your microservices and infrastructure and enables your product teams to ship high-quality code quickly without compromising autonomy.", "Unifies all your infrastructure tooling, services, and documentation to create a streamlined development environment from end to end.", "Easily create, maintain, find, and use technical documentation, using a docs like code approach" ] 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: 6-02-OVA-upgrade-advanced.md

Test 6-02 - OVA Advanced Upgrade ======= To verify that an OVA version of Harbor can be upgraded when the number of OVA params increases. User guide, installation guide of Harbor OVA version. This test requires an upgrade binary of Harbor. A running version of older version of Harbor OVA version. A vCenter, at least an ESX host. A linux host with Docker CLI installed (Docker client). When the number of params of OVA changes, the old OVA needs to have special handling of upgrading. TBD TBD None
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_alert_delete-receiver.md

title: kbcli alert delete-receiver Delete alert receiver. ``` kbcli alert delete-receiver NAME [flags] ``` ``` kbcli alert delete-receiver my-receiver ``` ``` -h, --help help for delete-receiver ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - Manage alert receiver, include add, list and delete receiver.
Project: Rundeck (Provisioning / Automation & Configuration)
File: ISSUE_TEMPLATE.md

Issue type: Bug report/Enhancement Request <!-- NOTE: For enhancements: Please search the existing Issues and look at the for your idea before posting. --> <!-- Please fill in the blanks below. --> My Rundeck detail Rundeck version: install type: (rpm,deb,war,launcher?) OS Name/version: DB Type/version: mysql? postgres? h2?.. Expected Behavior How to Reproduce
Project: KubeLinter (Provisioning / Security & Compliance)
File: using-kubelinter.md

You can run KubeLinter both locally and on your CI systems. After you've , use the `lint` command and provide: <!-- tabs:start --> The path to your Kubernetes `yaml` file: ```bash kube-linter lint /path/to/yaml-file.yaml ``` The path to a directory containing your Kubernetes `yaml` files: ```bash kube-linter lint /path/to/directory/containing/yaml-files/ ``` The path to a directory containing the `Chart.yaml` file: ```bash kube-linter lint /path/to/directory/containing/Chart.yaml-file/ ``` <!-- tabs:end --> [!NOTE] To get structured output, use the `--format` option. For example, Use `--format=json` to get the output in JSON format. Use `--format=sarif` to get the output in the . If you are using the for managing Git pre-commit hooks, you can install and use KubeLinter as a pre-commit hook. To do this, add the following to your `.pre-commit-config.yaml`: ```yaml repo: https://github.com/stackrox/kube-linter rev: 0.6.0 # kube-linter version hooks: id: kube-linter ``` The includes the following pre-commit hooks: `kube-linter`: Clones, builds, and installs KubeLinter locally (by using `go get`). `kube-linter-system`: Runs the KubeLinter binary. You must and add it to your path before running this pre-commit hook. `kube-linter-docker`: Pulls the KubeLinter docker image, mounts the project directory in the container, and runs the `kube-linter` command. You must before running this pre-commit hook. This section covers kube-linter command syntax, describes the command operations, and provides some common command examples. Use the following syntax to run KubeLinter commands: ```bash kube-linter [resource] [command] [options] ``` where `resource`, `command`, and `options` are: `resource` specifies the resources on which you want to perform operations. For example, `checks` or `templates`. `command` specifies the operation that you want to perform, for example, `kube-linter lint`. Or the operation you want to perform on a specified resource, for example, `kube-linter checks list`. `options` specifies options for each command. For example, you can use the `-c` or `--config` option to specify a configuration file. Use the `--help` (or `-h`) option to get a complete list of resources and commands. The `--help` option lists CLI reference information about available resources, commands, and their options. For example, to find all resources, run the following command: ```bash kube-linter --help ``` to find available commands for a specific resource, run the following command: ```bash kube-linter checks --help ``` to find available options for a specific command, run the following command: ```bash kube-linter lint --help ```
Project: KICS (Provisioning / Security & Compliance)
File: eee107f9-b3d8-45d3-b9c6-43b5a7263ce1.md

title: Authentication Without MFA hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: eee107f9-b3d8-45d3-b9c6-43b5a7263ce1 Query name: Authentication Without MFA Platform: Ansible Severity: <span style="color:#edd57e">Low</span> Category: Access Control URL: Users should authenticate with MFA (Multi-factor Authentication) to ensure an extra layer of protection when authenticating<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="9 2" name: Assume an existing role community.aws.stsassumerole: mfaserialnumber: "{{ mfadevices.mfadevices[0].serial_number }}" role_arn: "arn:aws:iam::123456789012:role/someRole" rolesessionname: "someRoleSession" register: assumed_role name: Hello stsassumerole: role_arn: "arn:aws:iam::123456789012:role/someRole" rolesessionname: "someRoleSession" register: assumed_role ``` ```yaml title="Negative test num. 1 - yaml file" name: Assume an existing role community.aws.stsassumerole: mfaserialnumber: '{{ mfadevices.mfadevices[0].serial_number }}' mfa_token: weewew role_arn: arn:aws:iam::123456789012:role/someRole rolesessionname: someRoleSession register: assumed_role name: Hello stsassumerole: mfaserialnumber: '{{ mfadevices.mfadevices[0].serial_number }}' mfa_token: weewew role_arn: arn:aws:iam::123456789012:role/someRole rolesessionname: someRoleSession register: assumed_role ```
Project: YugabyteDB (App Definition and Development / Database)
File: ta-20827.md

title: TA-20827 headerTitle: Correctness issue for queries using SELECT DISTINCT headcontent: 06 Feb 2024 type: docs showRightNav: true cascade: unversioned: true rightNav: hideH2: true type: docs | Product | Affected Versions | Related Issues | Fixed In | | :- | : | :- | :- | | {{<product "ysql">}} | {{<release "2.20.1.x">}} | {{<issue 20827>}} | {{<release "2.20.2.0, 2.21.1.0">}} | The impacted releases contain a correctness issue for queries using the SELECT DISTINCT clause. The queries may return incorrect results when the following conditions are true. BatchNestedLoopJoin is enabled JOIN clause is present in the query A DISTINCT clause is present in the query The table has range indexes The issue does not apply to hash or merge joins. Upgrade to a release with the fix. The issue is based on how the query planner handles the optimization of DISTINCT operations in the presence of join conditions involving columns from the inner relation. The issue concerns a query like `SELECT DISTINCT t2.k FROM t1 JOIN t2 ON t1.k = t2.k`; where a distinct index scan is chosen on table t2 (inner relation). Previously, the planner erroneously treated `t2.k` as a constant during the distinct index scan because the condition `t2.k = <some terms not related to t2>` made it appear constant. However, this assumption is incorrect in batch nested loop joins because a single scan on t2 can return multiple values for `t2.k` matching different values from `t1.k`. The correct behavior is to include `t2.k` in the distinct prefix (the columns used to eliminate duplicates) unless the condition is of the form `t2.k = C`, where `C` is a true constant value. In the case of a nested loop join with `foreach $1 in t1.k do; distinct index scan on t2 where t2.k = $1` , it is correct to treat `t2.k` as a constant and exclude it from the distinct prefix. But for a batch nested loop join with `foreach ($1, ..., $1024) in t1.k do; distinct index scan on t2 where t2.k in ($1, ..., $1024)`, it is incorrect to treat `t2.k` as a constant because the scan can return multiple values for `t2.k`. The issue does not apply to hash or merge joins.
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.1.1.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | cleaning up /tmp/hadoop/mapred/system | Major | . | raghavendra prabhu | Doug Cutting | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | mapred temporary files not deleted | Blocker | . | raghavendra prabhu | Doug Cutting | | | LocalFileSystem.makeAbsolute bug on Windows | Minor | fs | p sutter | Doug Cutting |