cwielenb/CNCF-Dataset huggingface dataset:
Project: Meshery (Provisioning / Automation & Configuration)
File: extensibility.md

layout: default title: Extensibility permalink: extensibility type: Extensibility abstract: 'Meshery has an extensible architecture with several different types of extension points.' language: en list: exclude Meshery has an extensible architecture with several different types of extension points. <!-- via , different and different . Meshery also offers a REST API. --> Meshery is not just an application. It is a set of microservices where the central component is itself called Meshery. Integrators may extend Meshery by taking advantage of designated Extension Points. Extension points come in various forms and are available through Mesherys architecture. Figure: Extension points available throughout Meshery <!-- Messaging Framework (CloudEvents and NATS) --> The following points of extension are currently incorporated into Meshery. {% assign sorted = site.pages | sort: "extensibility" %} <ul> {% for item in sorted %} {% if item.type=="Extensibility" and item.list!="exclude" and item.language !="es" -%} <li><a href="{{ site.baseurl }}{{ item.url }}">{{ item.title }}</a> {% if item.abstract != " " %} {{ item.abstract }} {% endif %} </li> {% endif %} {% endfor %} </ul>
Project: ClickHouse (App Definition and Development / Database)
File: v23.3.21.26-lts.md

sidebar_position: 1 sidebar_label: 2024 Fix reading from sparse columns after restart (). Fix buffer overflow in CompressionCodecMultiple (). Remove nonsense from SQL/JSON (). Fix crash in arrayEnumerateRanked (). Fix crash when using input() in INSERT SELECT JOIN (). Remove recursion when reading from S3 (). Cancel PipelineExecutor properly in case of exception in spawnThreads (). Detect io_uring in tests (). Cancel PipelineExecutor properly in case of exception in spawnThreads ().
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: 02-backends.md

id: backends title: Backend Instances sidebar_label: Backend description: Backend instances This is the main entry point for creating a backend. It does not have any functionality in and of itself, but is simply responsible for wiring things together. It is up to you to decide how many different backends you want to deploy. You can have all features in a single one, or split things out into multiple smaller deployments. Below is a simple example of a backend that installs only the catalog plugin and starts it up. ```ts import { createBackend } from '@backstage/backend-defaults'; import scaffolderPlugin from '@backstage/plugin-scaffolder-backend'; // Create your backend instance const backend = createBackend(); // Install desired features backend.add(import('@backstage/plugin-catalog-backend/alpha')); // Features can also be installed using an explicit reference backend.add(scaffolderPlugin()); // Start up the backend backend.start(); ``` We call `createBackend` to create a new backend instance, which is responsible for wiring together all of the features that we provide to the app. It also provides default implementations of all for use in plugins. No real work is done at the point of creating the backend though, it's all deferred to the `backend.start()` call. To add any feature to a backend instance you use the `.add(...)` method. Features are either plugins, modules, or service factories. You can read more about building plugins and modules in the , as well as how to install services factories in the . Once you have added all desired features we call the `.start()` method. This causes the backend to start up and initialize all features. When starting up the backend will validate all features to make sure that there are no conflicts. For example making sure that there are no circular dependencies. Underneath the hood, `createBackend` calls `createSpecializedBackend` from `@backstage/backend-app-api` which is responsible for actually creating the backend instance, without any services or features. You can think of `createBackend` more of a 'batteries included' approach, while `createSpecializedBackend` is more low level. As mentioned previously there's also the ability to create multiple of these backends in your project so that you can split apart your backend and deploy different backends that can scale independently of each other. For instance you might choose to deploy a backend with only the catalog plugin enabled, and one with just the scaffolder plugin enabled.
Project: YDB (App Definition and Development / Database)
File: when_use.md

{{ ydb-short-name }} can be used as an alternative solution in the following cases: When using NoSQL systems, if strong data consistency is required. When using NoSQL systems, if you need to make transactional updates to data stored in different rows of one or more tables. In systems that need to process and store large amounts of data and allow for virtually unlimited horizontal scalability (using industrial clusters of 5000+ nodes, processing millions of RPS, and storing petabytes of data). In low-load systems, when supporting a separate DB instance would be a waste of money (consider using {{ ydb-short-name }} in serverless mode instead). In systems with unpredictable or seasonally fluctuating load (you can add/reduce computing resources on request and/or in serverless mode). In high-load systems that shard load across relational DB instances. When developing a new product with no reliable load forecast or with an expected high load beyond the capabilities of conventional relational databases.
Project: Sonobuoy (Provisioning / Security & Compliance)
File: issue1388.md

v0.53.0 v0.53.1 When running `sonobuoy run --mode=certified-conformance` the `E2E_SKIP` value is not properly cleared, leading to `disruptive` tests being skipped. In certified-conformance mode, all tests must be run to be valid for submission to the CNCF so this bug would invalidate your results. You can manually work-around this issue by adding an extra flag at the end of your command: ``` sonobuoy run --mode=certified-conformance --plugin-env e2e.E2E_SKIP ``` This will set the focus value to conformance as expected and then remove the E2E_SKIP value. Use a patched version of Sonobuoy. After this bug was reported and patched, we released v0.53.2. Thanks to for reporting the original issue: https://github.com/vmware-tanzu/sonobuoy/issues/1388
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_bench_list.md

title: kbcli bench list List all benchmarks. ``` kbcli bench list [flags] ``` ``` kbcli bench list ``` ``` -A, --all-namespaces If present, list the requested object(s) across all namespaces. Namespace in current context is ignored even if specified with --namespace. -h, --help help for list -l, --selector string Selector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. ``` ``` --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 ``` - Run a benchmark.
Project: KICS (Provisioning / Security & Compliance)
File: 671211c5-5d2a-4e97-8867-30fc28b02216.md

title: API Gateway Method Does Not Contains An API Key hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 671211c5-5d2a-4e97-8867-30fc28b02216 Query name: API Gateway Method Does Not Contains An API Key Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: An API Key should be required on a method request.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1 13" resource "awsapigateway_method" "positive1" { restapiid = awsapigatewayrestapi.MyDemoAPI.id resourceid = awsapigatewayresource.MyDemoResource.id http_method = "GET" authorization = "NONE" } resource "awsapigateway_method" "positive2" { restapiid = awsapigatewayrestapi.MyDemoAPI.id resourceid = awsapigatewayresource.MyDemoResource.id http_method = "GET" authorization = "NONE" apikeyrequired = false } ``` ```tf title="Negative test num. 1 - tf file" resource "awsapigateway_method" "negative1" { restapiid = awsapigatewayrestapi.MyDemoAPI.id resourceid = awsapigatewayresource.MyDemoResource.id http_method = "GET" authorization = "NONE" apikeyrequired = true } ```
Project: StarRocks (App Definition and Development / Database)
File: json_object.md

displayed_sidebar: "English" Converts one or more key-value pairs to a JSON object that consists of the key-value pairs. The key-value pairs are sorted by key in dictionary order. ```Haskell json_object(key, value, ...) ``` `key`: a key in the JSON object. Only the VARCHAR data type is supported. `value`: a value in the JSON object. Only `NULL` values and the following data types are supported: STRING, VARCHAR, CHAR, JSON, TINYINT, SMALLINT, INT, BIGINT, LARGEINT, DOUBLE, FLOAT, and BOOLEAN. Returns a JSON object. If the total number of keys and values is an odd number, the JSON_OBJECT function fills `NULL` in the last field. Example 1: Construct a JSON object that consists of values of different data types. ```plaintext mysql> SELECT json_object('name', 'starrocks', 'active', true, 'published', 2020); -> {"active": true, "name": "starrocks", "published": 2020} ``` Example 2: Construct a JSON object by using nested JSON_OBJECT functions. ```plaintext mysql> SELECT jsonobject('k1', 1, 'k2', jsonobject('k2', 2), 'k3', json_array(4, 5)); -> {"k1": 1, "k2": {"k2": 2}, "k3": [4, 5]} ``` Example 3: Construct an empty JSON object. ```plaintext mysql> SELECT json_object(); -> {} ```
Project: Apache Hadoop (App Definition and Development / Database)
File: pull_request_template.md

<!-- Thanks for sending a pull request! If this is your first time, please read our contributor guidelines: https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute Make sure your PR title starts with JIRA issue id, e.g., 'HADOOP-17799. Your PR title ...'. --> [ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')? [ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation? ? [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, `NOTICE-binary` files?
Project: KICS (Provisioning / Security & Compliance)
File: e2d834b7-8b25-4935-af53-4a60668dcbe0.md

title: Azure Instance Using Basic Authentication hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: e2d834b7-8b25-4935-af53-4a60668dcbe0 Query name: Azure Instance Using Basic Authentication Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Best Practices URL: Azure Instances should use SSH Key instead of basic authentication<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="1" name: Create a VM with a custom image azurermvirtualmachine: resource_group: myResourceGroup name: testvm001 vmsize: StandardDS1_v2 admin_username: adminUser admin_password: password01 image: customimage001 os_type: Linux ``` ```yaml title="Negative test num. 1 - yaml file" name: Create a VM with a custom image azurermvirtualmachine: resource_group: myResourceGroup name: testvm001 vmsize: StandardDS1_v2 sshpasswordenabled: false sshpublickeys: path: ~/.ssh/id_rsa.pub key_data: somegeneratedkeydata image: customimage001 os_type: Linux ```
Project: Meshery (Provisioning / Automation & Configuration)
File: falco.md

layout: integration title: Falco subtitle: Collaborative and visual infrastructure as code for Falco image: /assets/img/integrations/falco/icons/color/falco-color.svg permalink: extensibility/integrations/falco docURL: https://docs.meshery.io/extensibility/integrations/falco description: integrations-category: Provisioning integrations-subcategory: Security & Compliance registrant: Artifact Hub components: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: KubeArmor (Provisioning / Security & Compliance)
File: README.md

Install ginkgo `go install -mod=mod github.com/onsi/ginkgo/v2/ginkgo` `kubectl` needs to be installed ``` mkdir $BASE/newsuite && cd $BASE/newsuite ginkgo bootstrap # This adds the skeleton for a new testcase ``` Refer to `$BASE/smoke` folder. For making assertions in testspec using gomega, . By default, running a `make` in the `KubeArmor/tests` folders runs all the tests. Check the ginkgo command in for options used (such as `--flake-attempts`, `--timeout` etc) used. Other ways of executing the testsuites: Execute all testsuites using `ginkgo -r` Execute specific testsuite using `ginkgo --focus "Smoke"` ... where `Smoke` is the name of the testsuite. Execute specific testcase/testspec. Check . Stop on first failure `ginkgo -r --fail-fast` Note: Why is `--flake-attempts=5` used in `Makefile`? Lot of times, on resource constrained VMs provided by GH actions, the events from kubearmor are lost. This is essentially a performance issue, but currently we are rerunning the tests. Yes, the tests assumes that there exists a k8s setup already operational.
Project: Druid (App Definition and Development / Database)
File: simple-client-sslcontext.md

id: simple-client-sslcontext title: "Simple SSLContext Provider Module" <!-- ~ 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. --> This Apache Druid module contains a simple implementation of that will be injected to be used with HttpClient that Druid processes use internally to communicate with each other. To learn more about Java's SSL support, please refer to guide. |Property|Description|Default|Required| |--|--|-|--| |`druid.client.https.protocol`|SSL protocol to use.|`TLSv1.2`|no| |`druid.client.https.trustStoreType`|The type of the key store where trusted root certificates are stored.|`java.security.KeyStore.getDefaultType()`|no| |`druid.client.https.trustStorePath`|The file path or URL of the TLS/SSL Key store where trusted root certificates are stored.|none|yes| |`druid.client.https.trustStoreAlgorithm`|Algorithm to be used by TrustManager to validate certificate chains|`javax.net.ssl.TrustManagerFactory.getDefaultAlgorithm()`|no| |`druid.client.https.trustStorePassword`|The or String password for the Trust Store.|none|yes| The following table contains optional parameters for supporting client certificate authentication: |Property|Description|Default|Required| |--|--|-|--| |`druid.client.https.keyStorePath`|The file path or URL of the TLS/SSL Key store containing the client certificate that Druid will use when communicating with other Druid services. If this is null, the other properties in this table are ignored.|none|yes| |`druid.client.https.keyStoreType`|The type of the key store.|none|yes| |`druid.client.https.certAlias`|Alias of TLS client certificate in the keystore.|none|yes| |`druid.client.https.keyStorePassword`|The or String password for the Key Store.|none|no| |`druid.client.https.keyManagerFactoryAlgorithm`|Algorithm to use for creating KeyManager, more details .|`javax.net.ssl.KeyManagerFactory.getDefaultAlgorithm()`|no| |`druid.client.https.keyManagerPassword`|The or String password for the Key Manager.|none|no| |`druid.client.https.validateHostnames`|Validate the hostname of the server. This should not be disabled unless you are using and know that standard hostname validation is not needed.|true|no| This lists all the possible values for the above mentioned configs among others provided by Java implementation.
Project: ShardingSphere (App Definition and Development / Database)
File: show-unloaded-single-tables.en.md

+++ title = "SHOW UNLOADED SINGLE TABLES" weight = 4 +++ The `SHOW UNLOADED SINGLE TABLES` syntax is used to query unloaded single tables. {{< tabs >}} {{% tab name="Grammar" %}} ```sql showUnloadedSingleTables::= 'SHOW' 'UNLOADED' 'SINGLE' 'TABLES' ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} | Column | Description | |-|| | table_name | Single table name | | storageunitname | The storage unit name where the single table is located | Query unloaded single tables. ```sql SHOW UNLOADED SINGLE TABLES; ``` ```sql mysql> SHOW UNLOADED SINGLE TABLES; ++-+ | tablename | storageunit_name | ++-+ | tsingle | ds1 | ++-+ 1 row in set (0.01 sec) ``` `SHOW`, `UNLOADED`, `SINGLE`, `TABLES`
Project: KICS (Provisioning / Security & Compliance)
File: 3641d5b4-d339-4bc2-bfb9-208fe8d3477f.md

title: API Gateway Method Does Not Contains An API Key hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 3641d5b4-d339-4bc2-bfb9-208fe8d3477f Query name: API Gateway Method Does Not Contains An API Key Platform: CloudFormation Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: An API Key should be required on a method request.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="7" AWSTemplateFormatVersion: "2010-09-09" Description: ApiGateway Resources: MockMethod: Type: 'AWS::ApiGateway::Method' Properties: ApiKeyRequired: false RestApiId: !Ref MyApi ResourceId: !GetAtt MyApi RootResourceId HttpMethod: GET AuthorizationType: NONE Integration: Type: MOCK MethodResponses: StatusCode : "200" ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="6" AWSTemplateFormatVersion: "2010-09-09" Description: ApiGateway Resources: MockMethod1: Type: 'AWS::ApiGateway::Method' Properties: RestApiId: !Ref MyApi ResourceId: !GetAtt MyApi RootResourceId HttpMethod: GET AuthorizationType: NONE Integration: Type: MOCK MethodResponses: StatusCode : "200" ``` ```json title="Positive test num. 3 - json file" hl_lines="13" { "AWSTemplateFormatVersion": "2010-09-09", "Description": "ApiGateway", "Resources": { "MockMethod": { "Type": "AWS::ApiGateway::Method", "Properties": { "MethodResponses": [ { "StatusCode": "200" } ], "ApiKeyRequired": false, "RestApiId": "MyApi", "ResourceId": [ "MyApi", "RootResourceId" ], "HttpMethod": "GET", "AuthorizationType": "NONE", "Integration": { "Type": "MOCK" } } } } } ``` <details><summary>Positive test num. 4 - json file</summary> ```json hl_lines="6" { "Description": "ApiGateway", "Resources": { "MockMethod1": { "Type": "AWS::ApiGateway::Method", "Properties": { "ResourceId": [ "MyApi", "RootResourceId" ], "HttpMethod": "GET", "AuthorizationType": "NONE", "Integration": { "Type": "MOCK" }, "MethodResponses": [ { "StatusCode": "200" } ], "RestApiId": "MyApi" } } }, "AWSTemplateFormatVersion": "2010-09-09" } ``` </details> ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: "2010-09-09" Description: ApiGateway Resources: MockMethod: Type: 'AWS::ApiGateway::Method' Properties: ApiKeyRequired: true RestApiId: !Ref MyApi ResourceId: !GetAtt MyApi RootResourceId HttpMethod: "" AuthorizationType: NONE Integration: Type: MOCK MethodResponses: StatusCode : "200" ``` ```json title="Negative test num. 2 - json file" { "AWSTemplateFormatVersion": "2010-09-09", "Description": "ApiGateway", "Resources": { "MockMethod": { "Type": "AWS::ApiGateway::Method", "Properties": { "Integration": { "Type": "MOCK" }, "MethodResponses": [ { "StatusCode": "200" } ], "ApiKeyRequired": true, "RestApiId": "MyApi", "ResourceId": [ "MyApi", "RootResourceId" ], "HttpMethod": "", "AuthorizationType": "NONE" } } } } ```
Project: StarRocks (App Definition and Development / Database)
File: now.md

displayed_sidebar: "English" Returns the current date and time. From 3.1.6 onwards, this function can accept a precision input (`p`), which represents the number of digits to retain after seconds. A maximum of 6 digits can be retained (accurate to the microsecond). The digits after `p` are padded with 0. If `p` is not specified, a DATETIME value accurate to the second is returned. The following example returns date and time values when different precision is specified. ```plaintext mysql > select now(),now(1),now(2),now(3),now(4),now(5),now(6)\G row * now(): 2023-12-08 13:46:45 now(1): 2023-12-08 13:46:45.100000 now(2): 2023-12-08 13:46:45.110000 now(3): 2023-12-08 13:46:45.115000 now(4): 2023-12-08 13:46:45.115800 now(5): 2023-12-08 13:46:45.115840 now(6): 2023-12-08 13:46:45.115843 ``` This function may return different results for different time zones. For more information, see . ```Haskell DATETIME NOW() DATETIME NOW(INT p) ``` `p`: optional, the specified precision, that is, the number of digits to retain after seconds. It must be an INT value within the range of [1,6]. `select now(0)` is equivalent to `select now()`. If `p` is not specified, this function returns a DATETIME value accurate to the second. If `p` is specified, this function returns a date and time value of the specified precision. ```Plain Text MySQL > select now(); ++ | now() | ++ | 2019-05-27 15:58:25 | ++ MySQL > select now(),now(1),now(2),now(3),now(4),now(5),now(6)\G row * now(): 2023-12-08 13:46:45 now(1): 2023-12-08 13:46:45.100000 now(2): 2023-12-08 13:46:45.110000 now(3): 2023-12-08 13:46:45.115000 now(4): 2023-12-08 13:46:45.115800 now(5): 2023-12-08 13:46:45.115840 now(6): 2023-12-08 13:46:45.115843 ``` NOW, now