cwielenb/CNCF-Dataset huggingface dataset:
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_options.md

title: kbcli options Print the list of flags inherited by all commands. ``` kbcli options [flags] ``` ``` kbcli options ``` ``` -h, --help help for options ``` ``` --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 ```
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: fix-12768.en.md

Fixed an issue which may occur when performing rolling upgrade, especially when upgrading from a version earlier than 5.4.0. When the cluster is empty (more precisely, routing tables are empty), try to additionally ask the cluster nodes for the routing schema in use, to make more informed decision about routing storage schema upon startup. This should make routing storage schema less likely to diverge across cluster nodes, especially when the cluster is composed of different versions of EMQX. The version also logs instructions for how to manually resolve if conflict is detected in a running cluster.
Project: KICS (Provisioning / Security & Compliance)
File: bdf8dcb4-75df-4370-92c4-606e4ae6c4d3.md

title: Redshift Publicly Accessible hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: bdf8dcb4-75df-4370-92c4-606e4ae6c4d3 Query name: Redshift Publicly Accessible Platform: CloudFormation Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: AWS Redshift Clusters must not be publicly accessible, which means the attribute 'PubliclyAccessible' must be set to false<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="17 4" Resources: myCluster: Type: "AWS::Redshift::Cluster" Properties: DBName: "mydb" MasterUsername: "master" MasterUserPassword: Ref: "MasterUserPassword" NodeType: "ds2.xlarge" ClusterType: "single-node" Tags: Key: foo Value: bar myCluster2: Type: "AWS::Redshift::Cluster" Properties: PubliclyAccessible: true DBName: "mydb" MasterUsername: "master" MasterUserPassword: Ref: "MasterUserPassword" NodeType: "ds2.xlarge" ClusterType: "single-node" Tags: Key: foo Value: bar ``` ```json title="Positive test num. 2 - json file" hl_lines="5 30" { "Resources": { "myCluster": { "Type": "AWS::Redshift::Cluster", "Properties": { "NodeType": "ds2.xlarge", "ClusterType": "single-node", "Tags": [ { "Key": "foo", "Value": "bar" } ], "DBName": "mydb", "MasterUsername": "master", "MasterUserPassword": { "Ref": "MasterUserPassword" } } }, "myCluster2": { "Type": "AWS::Redshift::Cluster", "Properties": { "Tags": [ { "Key": "foo", "Value": "bar" } ], "PubliclyAccessible": true, "DBName": "mydb", "MasterUsername": "master", "MasterUserPassword": { "Ref": "MasterUserPassword" }, "NodeType": "ds2.xlarge", "ClusterType": "single-node" } } } } ``` ```yaml title="Negative test num. 1 - yaml file" Resources: myCluster: Type: "AWS::Redshift::Cluster" Properties: PubliclyAccessible: false DBName: "mydb" MasterUsername: "master" MasterUserPassword: Ref: "MasterUserPassword" NodeType: "ds2.xlarge" ClusterType: "single-node" Tags: Key: foo Value: bar ``` ```json title="Negative test num. 2 - json file" { "Resources": { "myCluster": { "Type": "AWS::Redshift::Cluster", "Properties": { "MasterUserPassword": { "Ref": "MasterUserPassword" }, "NodeType": "ds2.xlarge", "ClusterType": "single-node", "Tags": [ { "Value": "bar", "Key": "foo" } ], "PubliclyAccessible": false, "DBName": "mydb", "MasterUsername": "master" } } } } ```
Project: KICS (Provisioning / Security & Compliance)
File: ce30e584-b33f-4c7d-b418-a3d7027f8f60.md

title: Always Admit Admission Control Plugin Set hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ce30e584-b33f-4c7d-b418-a3d7027f8f60 Query name: Always Admit Admission Control Plugin Set Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: When using kube-apiserver command, the '--enable-admission-plugins' flag should not have 'AlwaysAdmit' plugin<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: ["--enable-admission-plugins=AlwaysAdmit", "--admission-control-config-file=path/to/plugin/config/file.yaml"] 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: [] 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","--enable-admission-plugins=EventRateLimit", "--admission-control-config-file=path/to/plugin/config/file.yaml"] args: [] restartPolicy: OnFailure ```
Project: StarRocks (App Definition and Development / Database)
File: month.md

displayed_sidebar: "English" Returns the month for a given date. The return value ranges from 1 to 12. The `date` parameter must be of the DATE or DATETIME type. ```Haskell INT MONTH(DATETIME date) ``` ```Plain Text MySQL > select month('1987-01-01'); +--+ |month('1987-01-01 00:00:00') | +--+ | 1 | +--+ ``` MONTH
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: v1.2.0-next.3-changelog.md

52c02ac02b: Don't set the background color on an Avatar component that has a picture. 3603014e0e: Add ARIA landmark( `<main>`), & label and a heading to OAuthRequestDialog. Removed nested interactive control (button). 2025d7c123: Properly highlight `SidebarSubmenuItem` dropdown items on hover, use ellipsis styling on long labels in `SidebarSubmenu`, allow `icon` and `to` properties to be optional on `SidebarSubmenuItem`, and fix `SidebarPage` padding to be responsive to pinned state 69093c5f91: Display entity titles in `StarredEntities` home page card (if defined) and don't show entities which no longer exist Updated dependencies @backstage/core-components@0.9.4-next.2 447e060872: Add support for 'oidc' as authProvider for kubernetes authentication and adds optional 'oidcTokenProvider' config value. This will allow users to authenticate to kubernetes cluster using id tokens obtained from the configured auth provider in their backstage instance. Updated dependencies @backstage/plugin-kubernetes-common@0.2.10-next.1 @backstage/core-components@0.9.4-next.2 447e060872: Add support for 'oidc' as authProvider for kubernetes authentication and adds optional 'oidcTokenProvider' config value. This will allow users to authenticate to kubernetes cluster using id tokens obtained from the configured auth provider in their backstage instance. Updated dependencies @backstage/plugin-kubernetes-common@0.2.10-next.1 447e060872: Add support for 'oidc' as authProvider for kubernetes authentication and adds optional 'oidcTokenProvider' config value. This will allow users to authenticate to kubernetes cluster using id tokens obtained from the configured auth provider in their backstage instance. 2025d7c123: Include namespace in `MyGroupSidebarItem` if not default and remove root item routing if there are multiple groups Updated dependencies @backstage/core-components@0.9.4-next.2 cc8ddd0979: revert dependency `event-source-polyfill` to `1.0.25` Updated dependencies @backstage/core-components@0.9.4-next.2 cc8ddd0979: revert dependency `event-source-polyfill` to `1.0.25` Updated dependencies @backstage/core-components@0.9.4-next.2
Project: Chef InSpec (Provisioning / Security & Compliance)
File: aws.md

+++ title = "Chef InSpec and AWS" draft = false gh_repo = "inspec" [menu] [menu.inspec] title = "AWS" identifier = "inspec/cloud/aws" parent = "inspec/cloud" +++ Chef InSpec has resources for auditing AWS. With Chef InSpec 4 or greater, you can create a profile for testing AWS resources with `inspec init profile`: ```bash $ inspec init profile --platform aws <PROFILE_NAME> Create new profile at /Users/me/<PROFILE_NAME> Creating directory libraries Creating file README.md Creating directory controls Creating file controls/example.rb Creating file inspec.yml Creating file inputs.yml Creating file libraries/.gitkeep ``` Assuming the `inputs.yml` file contains your AWS project ID, you can execute this sample profile using the following command: ```bash inspec exec <PROFILENAME> --input-file=<PROFILENAME>/inputs.yml -t gcp:// ``` Chef InSpec uses the standard AWS authentication mechanisms. Typically, you will create an IAM user specifically for auditing activities. Create an IAM user in the AWS console, with your choice of username. Check the box marked "Programmatic Access." On the Permissions screen, choose Direct Attach. Select the AWS-managed IAM profile named "ReadOnlyAccess." If you wish to restrict the user further, you may do so; see individual Chef InSpec resources to identify which permissions are required. After generating the key, record the access key ID and secret key. You may provide the credentials to Chef InSpec by setting the following environment variables: `AWSREGION`, `AWSACCESSKEYID`, and `AWSSECRETACCESSKEY`. You may also use `AWSPROFILE`, or if you are using MFA, `AWSSESSIONTOKEN`. See the for details. Once you have your environment variables set, you can verify your credentials by running: ```bash $ inspec detect -t aws:// == Platform Details Name: aws Families: cloud, api Release: aws-sdk-v2.10.125 ``` Look for a file in your home directory named `~/.aws/credentials`. If it does not exist, create it. Choose a name for your profile; here, we're using the name 'auditing'. Add your credentials as a new profile, in INI format: ```bash [auditing] awsaccesskey_id = AKIA.... awssecretaccess_key = 1234....abcd ``` You may now run Chef InSpec using the `--target` / `-t` option, using the format `-t aws://region/profile`. For example, to connect to the Ohio region using a profile named 'auditing', use `-t aws://us-east-2/auditing`. To verify your credentials, run: ```bash $ inspec detect -t aws:// == Platform Details Name: aws Families: cloud, api Release: aws-sdk-v2.10.125 ``` {{< inspec/inspec_resources platform="aws" >}}
Project: KICS (Provisioning / Security & Compliance)
File: 8d7758a7-d9cd-499a-a83e-c9bdcbff728d.md

title: Nifcloud NAS Has Public Ingress NAS Security Group Rule hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 8d7758a7-d9cd-499a-a83e-c9bdcbff728d Query name: Nifcloud NAS Has Public Ingress NAS Security Group Rule Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Networking and Firewall URL: An ingress nas security group rule allows traffic from /0<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "nifcloudnassecurity_group" "positive" { group_name = "nasgroup001" availability_zone = "east-11" rule { cidr_ip = "0.0.0.0/0" } } ``` ```tf title="Negative test num. 1 - tf file" resource "nifcloudnassecurity_group" "negative" { group_name = "nasgroup001" availability_zone = "east-11" rule { cidr_ip = "10.0.0.0/16" } } ```
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: Phoenix.md

Phoenix source connector Read Phoenix data through . Support Batch mode and Streaming mode. The tested Phoenix version is 4.xx and 5.xx On the underlying implementation, through the jdbc driver of Phoenix, execute the upsert statement to write data to HBase. Two ways of connecting Phoenix with Java JDBC. One is to connect to zookeeper through JDBC, and the other is to connect to queryserver through JDBC thin client. Tips: By default, the (thin) driver jar is used. If you want to use the (thick) driver or other versions of Phoenix (thin) driver, you need to recompile the jdbc connector module supports query SQL and can achieve projection effect. if you use phoenix (thick) driver the value is `org.apache.phoenix.jdbc.PhoenixDriver` or you use (thin) driver the value is `org.apache.phoenix.queryserver.client.Driver` if you use phoenix (thick) driver the value is `jdbc:phoenix:localhost:2182/hbase` or you use (thin) driver the value is `jdbc:phoenix:thin:url=http://localhost:8765;serialization=PROTOBUF` Source plugin common parameters, please refer to for details use thick client drive ``` Jdbc { driver = org.apache.phoenix.jdbc.PhoenixDriver url = "jdbc:phoenix:localhost:2182/hbase" query = "select age, name from test.source" } ``` use thin client drive ``` Jdbc { driver = org.apache.phoenix.queryserver.client.Driver url = "jdbc:phoenix:thin:url=http://sparke2ephoenix_sink:8765;serialization=PROTOBUF" query = "select age, name from test.source" } ``` Add Phoenix Source Connector
Project: ClickHouse (App Definition and Development / Database)
File: v23.8.3.48-lts.md

sidebar_position: 1 sidebar_label: 2023 Backported in : Enable allowremovestalemovingparts by default. (). Backported in : ProfileEvents added ContextLockWaitMicroseconds event. (). Backported in : Enrich `changed_images.json` with the latest tag from master for images that are not changed in the pull request. (). Backported in : Remove redundant `clickhouse-keeper-client` symlink. (). Backported in : We build and upload them for every push, which isn't worth it. (). Fix: moved to prewhere condition actions can lose column (). Fix: parallel replicas over distributed with preferlocalhostreplica=1 (). Fix possible error 'URI contains invalid characters' in s3 table function (). Check for overflow before addition in `analysisOfVariance` function (). reproduce and fix the bug in removeSharedRecursive (). Fix aggregate projections with normalized states (). Fix possible parsing error in WithNames formats with disabled inputformatwithnamesuse_header (). Fix zero copy garbage (). Fix race in `ColumnUnique` (). Fix serialization of `ColumnDecimal` (). Fix virtual columns having incorrect values after ORDER BY (). Fix Keeper segfault during shutdown (). Rebuild minmaxcountprojection when partition key gets modified (). Test libunwind changes. (). Use pathlib.Path in S3Helper, rewrite build reports, improve small things (). Properly re-initialize ZooKeeper fault injection (). Fix segfault in system.zookeeper (). Update automated commit status comment (). Adjusting `num_streams` by expected work in StorageS3 ().
Project: KICS (Provisioning / Security & Compliance)
File: 1e0ef61b-ad85-4518-a3d3-85eaad164885.md

title: DB Security Group With Public Scope hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 1e0ef61b-ad85-4518-a3d3-85eaad164885 Query name: DB Security Group With Public Scope Platform: Terraform Severity: <span style="color:#ff0000">Critical</span> Category: Networking and Firewall URL: The IP address in a DB Security Group should not be '0.0.0.0/0' (IPv4) or '::/0' (IPv6). If so, any IP can access it<br> ```tf title="Positive test num. 1 - tf file" hl_lines="5" resource "awsdbsecurity_group" "positive1" { name = "rds_sg" ingress { cidr = "0.0.0.0/0" } } ``` ```tf title="Negative test num. 1 - tf file" resource "awsdbsecurity_group" "negative1" { name = "rds_sg" ingress { cidr = "10.0.0.0/25" } } ```
Project: StarRocks (App Definition and Development / Database)
File: xx_hash3_64.md

displayed_sidebar: "English" Returns the 64-bit xxhash3 hash value of the input string. xxhash364 has better performance than by using AVX2 instruction and has state-of-art hash quality which is broadly integrated with many software. This function is supported from v3.2.0. ```Haskell BIGINT XXHASH364(VARCHAR input, ...) ``` ```Plain Text MySQL > select xxhash364(null); +-+ | xxhash364(NULL) | +-+ | NULL | +-+ MySQL > select xxhash364("hello"); +-+ | xxhash364('hello') | +-+ | -7685981735718036227 | +-+ MySQL > select xxhash364("hello", "world"); +-+ | xxhash364('hello', 'world') | +-+ | 7001965798170371843 | +-+ ``` XXHASH364,HASH,xxHash3
Project: KICS (Provisioning / Security & Compliance)
File: 7dfb316c-a6c2-454d-b8a2-97f147b0c0ff.md

title: DB Instance Storage Not Encrypted hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 7dfb316c-a6c2-454d-b8a2-97f147b0c0ff Query name: DB Instance Storage Not Encrypted Platform: Ansible Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: AWS DB Instance should have its storage encrypted by setting the parameter to 'true'. The storage_encrypted default value is 'false'.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="17 23 7" name: foo community.aws.rds_instance: id: test-encrypted-db state: present engine: mariadb storage_encrypted: False dbinstanceclass: db.t2.medium username: "{{ username }}" password: "{{ password }}" allocatedstorage: "{{ allocatedstorage }}" name: foo2 community.aws.rds_instance: id: test-encrypted-db state: present engine: mariadb storage_encrypted: no dbinstanceclass: db.t2.medium username: "{{ username }}" password: "{{ password }}" allocatedstorage: "{{ allocatedstorage }}" name: foo3 community.aws.rds_instance: id: test-encrypted-db state: present engine: mariadb dbinstanceclass: db.t2.medium username: "{{ username }}" password: "{{ password }}" allocatedstorage: "{{ allocatedstorage }}" ``` ```yaml title="Negative test num. 1 - yaml file" name: foo community.aws.rds_instance: id: test-encrypted-db state: present engine: mariadb storage_encrypted: true dbinstanceclass: db.t2.medium username: '{{ username }}' password: '{{ password }}' allocatedstorage: '{{ allocatedstorage }}' name: foo2 community.aws.rds_instance: id: test-encrypted-db state: present engine: mariadb storage_encrypted: yes dbinstanceclass: db.t2.medium username: '{{ username }}' password: '{{ password }}' allocatedstorage: '{{ allocatedstorage }}' name: foo3 community.aws.rds_instance: id: test-encrypted-db state: present engine: mariadb kmskeyid: sup3rstr0ngK3y dbinstanceclass: db.t2.medium username: '{{ username }}' password: '{{ password }}' allocatedstorage: '{{ allocatedstorage }}' ```
Project: Pulsar (App Definition and Development / Streaming & Messaging)
File: pip-284.md

Apache Pulsar introduced the topic-level policies by . It uses the reader API to read messages and relies on compaction to implement table-like logic in the memory. Introduced new consumer type `TableView` to support the same logic by Public Stable API. Due to a lot of problems caused by the complex topic policy logic is as follows. we can use a new stable `TableView` API instead of previous one. https://github.com/apache/pulsar/pull/20763 https://github.com/apache/pulsar/pull/20613 https://github.com/apache/pulsar/pull/19746 etc... Reduce complex logic. Reuse the public stable API to improve the project quality. none. ```mermaid sequenceDiagram participant client participant topicpolicyservice participant systemeventtopic client ->> topicpolicyservice: Hi, what's the topic policy of `persistent://public/default/test` loop policy update event fetching topicpolicyservice ->> systemeventtopic: Do you have new events?; alt new policy event systemeventtopic ->> topicpolicyservice: Yes, Sure. here you are. else no policy event systemeventtopic ->> topicpolicyservice: No, Please wait for a moment. end; end Note right of topicpolicyservice: Update the local cache table by keeping the latest one; topicpolicyservice -->> client: Here you are. ``` The new implementation will continue reuse the previous system topic `namespace/change_event` to store the topic policy data. and it will change the reading logic from the raw reader to TableView to enhance the robustness. none. none. none. none. none. none. none. none. Without backward compatibility since we will reuse the same system topic `namesapce/change_event`. none. none. none. none. none. Mailing List discussion thread: https://lists.apache.org/thread/9v00sfpfxjpm775vgltkjoxwnllsgskg Mailing List voting thread: https://lists.apache.org/thread/gx43mzh88xp5ttz2gqghfqpz1yq51k60
Project: Beam (App Definition and Development / Streaming & Messaging)
File: beam-summit-site.md

title: "Announcing Beam Summit Site" date: 2019-03-18 00:00:01 -0800 categories: blog aliases: /blog/2019/03/18/beam-summit-site.html authors: aizhamal <!-- 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. --> We are thrilled to announce the launch of our new website dedicated to Beam Summits! The site provides all the information you need towards the upcoming Beam Summits in Europe, Asia and North America in 2019. You will find information about the conference theme, the speakers and sessions, the abstract submission timeline and the registration process, the conference venues and hosting cities - and much more that you will find useful until and during the Beam Summits 2019. We are working to make the website easy to use, so that anyone who is organizing a Beam event can rely on it. You can find the . The pages will be updated on a regular basis, but we also love hearing thoughts from our community! Let us know if you have any questions, comments or suggestions, and help us improve! Also, if you are thinking of organizing a Beam event, please feel free to reach out for support, and to use the code in GitHub as well. We sincerely hope that you like the new Beam Summit website and will find it useful for accessing information. Enjoy browsing around! See you in Berlin! <!--more-->