cwielenb/CNCF-Dataset huggingface dataset:
Project: Artifact Hub (App Definition and Development / Application Definition & Image Build)
File: GOVERNANCE.md

This document defines the project governance for Artifact Hub including how someone become a maintainer, how decisions are made, how changes are made to the governance, and more. Anyone can propose a change to Artifact Hub. This includes the code, the documentation, and even the governance. Details on contributing can be found in the file. Maintainers are responsible for the development and operation of the project. This includes but is not limited to: Reviewing and merging pull requests The operation of artifacthub.io Refining the projects governance Overseeing the resolution and disclosure of security issues Managing financial decision related to the project Changes to maintainers use the following rules: New maintainers can be added with a vote. The vote must happen in a tracked location (e.g., mailing list, GitHub issue, etc). If a maintainer is inactive for > 6 months they will automatically be removed unless a super-majority of the other maintainers agrees to extend the period of inactivity. This is useful when there is a known period of inactivity and a maintainer will be returning. A maintainer may step down at any time and remove themselves. If a maintainer needs to be removed, a super-majority vote of the other maintainer is required. This vote needs to happen in a tracked location. There are 3 ways decisions can be made for non-code related decisions. Those are: is the default method to make decisions. When a lazy-consensus decision cannot be made it will move to a vote unless otherwise specified in this governance. Some decisions require a super-majority of maintainer to approve. Those include: Changes to the governance Removing a maintainer Licensing and intellectual property changes Changes to source code requires a maintainer to approve the changes.
Project: ArangoDB (App Definition and Development / Database)
File: on_outcome_construction.md

+++ title = "`static void onoutcomeconstruction(T *, U &&) noexcept`" description = "(>= Outcome v2.2.0) Hook invoked by the implicit constructors of `basic_outcome`." categories = ["observer-policies"] weight = 450 +++ One of the constructor hooks for {{% api "basicoutcome<T, EC, EP, NoValuePolicy>" %}}, generally invoked by the implicit constructors of `basicoutcome`. See each constructor's documentation to see which specific hook it invokes. Requires: Always available. Guarantees: Never throws an exception.
Project: KICS (Provisioning / Security & Compliance)
File: 3505094c-f77c-4ba0-95da-f83db712f86c.md

title: S3 Bucket with Unsecured CORS Rule hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 3505094c-f77c-4ba0-95da-f83db712f86c Query name: S3 Bucket with Unsecured CORS Rule Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: If the CORS (Cross-Origin Resource Sharing) rule is defined in an S3 bucket, it should be secure<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="5" name: Create s3 bucket2 community.aws.awss3cors: name: mys3bucket state: present rules: allowed_origins: http://www.example.com/ allowed_methods: GET POST PUT DELETE HEAD allowed_headers: Authorization expose_headers: x-amz-server-side-encryption x-amz-request-id maxageseconds: 30000 ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="5" name: Create s3 bucket4 awss3cors: name: mys3bucket2 state: present rules: allowed_origins: http://www.example.com/ allowed_methods: GET POST PUT DELETE HEAD allowed_headers: Authorization expose_headers: x-amz-server-side-encryption x-amz-request-id maxageseconds: 30000 ``` ```yaml title="Negative test num. 1 - yaml file" name: Create s3 bucket community.aws.awss3cors: name: mys3bucket3 state: present rules: allowed_origins: http://www.example.com/ allowed_methods: GET POST allowed_headers: Authorization expose_headers: x-amz-server-side-encryption x-amz-request-id maxageseconds: 30000 ``` ```yaml title="Negative test num. 2 - yaml file" name: Create s3 bucket1 awss3cors: name: mys3bucket4 state: present rules: allowed_origins: http://www.example.com/ allowed_methods: GET POST allowed_headers: Authorization expose_headers: x-amz-server-side-encryption x-amz-request-id maxageseconds: 30000 ```
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: support.md

title: Support | KubeDB description: Support menu: docs_{{ .version }}: identifier: support-cli name: Support parent: welcome weight: 10 menuname: docs{{ .version }} sectionmenuid: welcome url: /docs/{{ .version }}/welcome/support/ aliases: /docs/{{ .version }}/support/ To speak with us, please leave a message on . To receive product announcements, follow us on . If you have found a bug with KubeDB or want to request for new features, please .
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_debug_mysql.md

title: Kubectl-Dba Debug Mysql menu: docs_{{ .version }}: identifier: kubectl-dba-debug-mysql name: Kubectl-Dba Debug Mysql parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Debug helper for mysql database ``` kubectl-dba debug mysql [flags] ``` ``` kubectl dba debug mysql -n demo sample-mysql --operator-namespace kubedb ``` ``` -h, --help help for mysql -o, --operator-namespace string the namespace where the kubedb operator is installed (default "kubedb") ``` ``` --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/runner/.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 --default-seccomp-profile-type string Default seccomp profile --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 --password string Password for basic authentication to the API server --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 --username string Username for basic authentication to the API server ``` - Debug any Database issue
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_ssl_policy.md

+++ title = "googlecomputessl_policy resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputessl_policy" identifier = "inspec/resources/gcp/googlecomputesslpolicy.md googlecomputesslpolicy resource" parent = "inspec/resources/gcp" +++ A `googlecomputessl_policy` is used to test a Google SslPolicy resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputessl_policy(project: 'chef-gcp-inspec', name: 'inspec-gcp-ssl-policy') do it { should exist } its('mintlsversion') { should eq 'TLS12' } its('profile') { should eq 'CUSTOM' } its('customfeatures') { should include 'TLSECDHEECDSAWITHAES256GCMSHA384' } its('customfeatures') { should include 'TLSECDHERSAWITHAES256GCMSHA384' } end describe googlecomputessl_policy(project: 'chef-gcp-inspec', name: 'nonexistent') do it { should_not exist } end ``` Properties that can be accessed from the `googlecomputessl_policy` resource: `creation_timestamp` : Creation timestamp in RFC3339 text format. `description` : An optional description of this resource. `id` : The unique identifier for the resource. `name` : Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression `?` which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash. `profile` : Profile specifies the set of SSL features that can be used by the load balancer when negotiating SSL with clients. If using `CUSTOM`, the set of SSL features to enable must be specified in the `customFeatures` field. Possible values: COMPATIBLE MODERN RESTRICTED CUSTOM `mintlsversion` : The minimum version of SSL protocol that can be used by the clients to establish a connection with the load balancer. Possible values: TLS10 TLS11 TLS12 `enabled_features` : The list of features enabled in the SSL policy. `custom_features` : A list of features enabled when the selected profile is CUSTOM. The method returns the set of features that can be specified in this list. This field must be empty if the profile is not CUSTOM. `fingerprint` : Fingerprint of this resource. A hash of the contents stored in this object. This field is used in optimistic locking. `warnings` : If potential misconfigurations are detected for this SSL policy, this field will be populated with warning messages. `code` : A warning code, if applicable. `message` : A human-readable description of the warning code. Ensure the is enabled for the current project.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: presentation-materials.md

title: "Beam Presentation Materials" aliases: /learn/presentation-materials/ /contribute/presentation-materials/ <!-- 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. --> Are you interested in learning more about Apache Beam or giving a talk about Apache Beam? Excellent! The Apache Beam community has created this collection of materials to help you get started. The community periodically reviews these materials to ensure they are accurate and up-to-date. <div class="panel panel-default table-container-wrapper"> <div class="panel-body"> <iframe src="https://drive.google.com/embeddedfolderview?id=0B-IhJZh9Ab52a3JLVXFWMDltcHM&resourcekey=0-VP9gZcuYGybKzNARikCEnQ#list" width="700" height="300" frameborder="0"></iframe> </div> </div> These materials can be used by anyone. If you do use these materials, please remember to give credit to the authors cited in each presentation. These materials include speaker notes and you can view them by clicking `View` and selecting `Show speaker notes`. Some presentations have `[Long]` or `[Short]` in their name, such as the Apache Beam Model, which means there are two different presentations (a long and short version) depending on your needs and time constraints. If you have any questions about these materials, please ask on the mailing list. The Apache Beam community is looking for feedback on these materials to improve them over time. If you deliver a presentation based on these materials, we'd love to hear from you on the mailing list. Please share your thoughts, questions you were asked, and (if available and appropriate) a link to the recording of your talk so the rest of the Apache Beam community can benefit from it. The Apache Beam community is always looking for new core content and contributions! If you are interested in contributing new content, we recommend you first search the to see if your idea currently has an open issue. If it does not, send an email to the mailing list or open a new issue in the using the website component. Based on community submissions or contributions, the Beam community collaboratively reviews or creates new content and then adds it to this shared space for everyone to use. If you encounter missing, incorrect, or out of date material, please make a comment in the presentation or send an email to the mailing list.
Project: KICS (Provisioning / Security & Compliance)
File: dc1ab429-1481-4540-9b1d-280e3f15f1f8.md

title: Serverless Function Without X-Ray Tracing hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: dc1ab429-1481-4540-9b1d-280e3f15f1f8 Query name: Serverless Function Without X-Ray Tracing Platform: CloudFormation Severity: <span style="color:#edd57e">Low</span> Category: Observability URL: AWS Serverless Function should have Tracing enabled. For this, property 'Tracing' should have the value 'Active'<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="7" AWSTemplateFormatVersion: '2010-09-09' Transform: AWS::Serverless-2016-10-31 Description: AWS SAM template with a simple API definition Resources: Function1: Type: AWS::Serverless::Function Properties: PackageType: Image ImageUri: account-id.dkr.ecr.region.amazonaws.com/ecr-repo-name:image-name ImageConfig: Command: "app.lambda_handler" EntryPoint: "entrypoint1" WorkingDirectory: "workDir" Tags: Key: Type Value: AWS Serverless Function ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="19" AWSTemplateFormatVersion: '2010-09-09' Transform: AWS::Serverless-2016-10-31 Description: AWS SAM template with a simple API definition Resources: Function2: Type: AWS::Serverless::Function Properties: PackageType: Image ImageUri: account-id.dkr.ecr.region.amazonaws.com/ecr-repo-name:image-name ImageConfig: Command: "app.lambda_handler" EntryPoint: "entrypoint1" WorkingDirectory: "workDir" Tags: Key: Type Value: AWS Serverless Function Tracing: PassThrough ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: '2010-09-09' Transform: AWS::Serverless-2016-10-31 Description: AWS SAM template with a simple API definition Resources: Function3: Type: AWS::Serverless::Function Properties: PackageType: Image ImageUri: account-id.dkr.ecr.region.amazonaws.com/ecr-repo-name:image-name ImageConfig: Command: "app.lambda_handler" EntryPoint: "entrypoint1" WorkingDirectory: "workDir" Tags: Key: Type Value: AWS Serverless Function Tracing: Active ```
Project: YugabyteDB (App Definition and Development / Database)
File: txn_rollback.md

title: ROLLBACK statement [YSQL] headerTitle: ROLLBACK linkTitle: ROLLBACK description: Use the ROLLBACK statement to roll back the current transactions. menu: v2.18: identifier: txn_rollback parent: statements type: docs Use the `ROLLBACK` statement to roll back the current transactions. All changes included in this transactions will be discarded. {{%ebnf%}} rollback {{%/ebnf%}} ```sql ROLLBACK [ TRANSACTION | WORK ] ``` Add optional keyword has no effect. Add optional keyword has no effect.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.1.5-build.3.en.md

This change allows to set the minReadySeconds for the StatefulSet. This allows to add a gap between the restarts of each pod by upgrade or restart command. Add `node.brokerpoolsize`, `node.genericpoolsize`, `node.channelcleanupbatch_size` options to EMQX configuration. Tuning these options can significantly improve performance if cluster interconnect network latency is high. Improved retained message publishing latency by consolidating multiple index update operations into a single mnesia activity, leveraging the new APIs introduced in mria 0.6.0. Improved the placeholder syntax of rule engine. The parameters of actions support using placeholder syntax to dynamically fill in the content of strings. The format of the placeholder syntax is `${key}`. Before this improvement, the `key` in `${key}` could only contain letters, numbers, and underscores. Now the `key` supports any UTF8 characters. Improve the error reason of the `datetounix_ts` to make more sense. Prevent client disconnected when sending large payloads with debug/trace logging is enabled. Increase `emqxroutersup` restart intensity. The goal is to tolerate occasional crashes that can happen under relatively normal conditions and don't seem critical to shutdown the whole app (emqx). For example, mria write/delete call delegated from a replicant to a core node by `emqxrouterhelper` may fail, if the core node is being stopped / restarted / not ready. Reintroduce `cacerts` TLS client option as a deprecated option. This fixes issues found when trying to upgrade from 5.1.3 where that option is set in the configuration files or persisted in EMQX Operator settings.
Project: ClickHouse (App Definition and Development / Database)
File: named-collection.md

slug: /en/sql-reference/statements/create/named-collection sidebar_label: NAMED COLLECTION Creates a new named collection. Syntax ```sql CREATE NAMED COLLECTION [IF NOT EXISTS] name [ON CLUSTER cluster] AS key_name1 = 'some value' [[NOT] OVERRIDABLE], key_name2 = 'some value' [[NOT] OVERRIDABLE], key_name3 = 'some value' [[NOT] OVERRIDABLE], ... ``` Example ```sql CREATE NAMED COLLECTION foobar AS a = '1', b = '2' OVERRIDABLE; ``` Related statements See Also
Project: YugabyteDB (App Definition and Development / Database)
File: anywhere-api.md

title: YugabyteDB Anywhere REST API headerTitle: REST API linkTitle: REST API description: REST API YugabyteDB Anywhere. headcontent: Manage YugabyteDB Anywhere accounts and deployments using the REST API menu: stable_yugabyte-platform: parent: anywhere-automation identifier: anywhere-api weight: 10 type: docs The YugabyteDB Anywhere REST API allows you to deploy and manage universes programmatically. Some examples of what you can accomplish using this API include: Create and manage YBA provider configurations Deploy and manage universes Pause and resume universes Perform software upgrades Run on-demand backups and restores Resize nodes If you use Python, check out the Jupyter notebooks in the for examples of performing various tasks using the API. {{< sections/2-boxes >}} {{< sections/bottom-image-box title="Get Started" description="Manage YugabyteDB Anywhere using the API." buttonText="API Documentation" buttonUrl="https://api-docs.yugabyte.com/docs/yugabyte-platform/" >}} {{< /sections/2-boxes >}}
Project: YugabyteDB (App Definition and Development / Database)
File: yba_provider_onprem_node_add.md

Add a node instance to YugabyteDB Anywhere on-premises provider Add a node instance to YugabyteDB Anywhere on-premises provider ``` yba provider onprem node add [flags] ``` ``` --instance-type string [Required] Instance type of the node as describe in the provider. --ip string [Required] IP address of the node instance. --region string [Required] Region name of the node. --zone string [Required] Zone name of the node. --node-name string [Optional] Node name given by the user. --ssh-user string [Optional] SSH user to access the node instances. --node-configs stringArray [Optional] Node configurations. Provide the following comma separated fields as key-value pairs: "type=<type>,value=<value>". Each config needs to be added using a separate --node-configs flag. Example: --node-configs type=S3CMD,value=<value> --node-configs type=CPU_CORES,value=<value> -h, --help help for add ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -n, --name string [Optional] The name of the provider for the action. Required for create, delete, describe, instance-types and nodes. -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage YugabyteDB Anywhere onprem node instances
Project: Druid (App Definition and Development / Database)
File: zookeeper.md

id: zookeeper title: "ZooKeeper" <!-- ~ 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. --> Apache Druid uses (ZK) for management of current cluster state. Apache Druid supports ZooKeeper versions 3.5.x and above. :::info Note: Starting with Apache Druid 0.22.0, support for ZooKeeper 3.4.x has been removed Starting with Apache Druid 31.0.0, support for Zookeeper-based segment loading has been removed. ::: The operations that happen over ZK are leader election Segment "publishing" protocol from leader election and task management We use the Curator recipe to perform leader election at path ``` ${druid.zk.paths.coordinatorPath}/_COORDINATOR ``` The `announcementsPath` and `servedSegmentsPath` are used for this. All processes publish themselves on the `announcementsPath`, specifically, they will create an ephemeral znode at ``` ${druid.zk.paths.announcementsPath}/${druid.host} ``` Which signifies that they exist. They will also subsequently create a permanent znode at ``` ${druid.zk.paths.servedSegmentsPath}/${druid.host} ``` And as they load up segments, they will attach ephemeral znodes that look like ``` ${druid.zk.paths.servedSegmentsPath}/${druid.host}/segmentidentifier_ ``` Processes like the and can then watch these paths to see which processes are currently serving which segments.
Project: StarRocks (App Definition and Development / Database)
File: seconds_sub.md

displayed_sidebar: "English" Subtracts a time interval from a date value. The time interval is in seconds. ```Haskell DATETIME seconds_sub(DATETIME|DATE date, INT seconds); ``` `date`: the time expression. It must be of the DATETIME type. `seconds`: the time interval you want to substract, in seconds. It must be of the INT type. Returns a value of the DATETIME type. If the input value is of the DATE type, the hour, minute, and seconds parts are processed as `00:00:00`. ```Plain Text select seconds_sub('2022-01-01 01:01:01', 2); ++ | seconds_sub('2022-01-01 01:01:01', 2) | ++ | 2022-01-01 01:00:59 | ++ select seconds_sub('2022-01-01 01:01:01', -1); +-+ | seconds_sub('2022-01-01 01:01:01', -1) | +-+ | 2022-01-01 01:01:02 | +-+ select seconds_sub('2022-01-01', 1); ++ | seconds_sub('2022-01-01', 1) | ++ | 2021-12-31 23:59:59 | ++v ```