cwielenb/CNCF-Dataset huggingface dataset:
Project: FoundationDB (App Definition and Development / Database)
File: tenantTester.md

Overview -- Tenant testing is an optional extension to the core binding tester that enables testing of the tenant API. This testing is enabled by adding some additional instructions and modifying the behavior of some existing instructions. Additional State and Initialization -- Your tester should store an additional piece of state tracking the active tenant that is to be used to create transactions. This tenant must support an unset state, in which case transactions will be created directly on the database. New Instructions The tenant API introduces some new operations: Pops the top item off of the stack as TENANT_NAME. Creates a new tenant in the database with the name TENANT_NAME. May optionally push a future onto the stack. Pops the top item off of the stack as TENANT_NAME. Deletes the tenant with the name TENANT_NAME from the database. May optionally push a future onto the stack. Pops the top item off of the stack as TENANT_NAME. Opens the tenant with name TENANT_NAME and stores it as the active tenant. Then, waits on a future that initializes the tenant ID. When complete, pushes the string "SETACTIVETENANT" onto the stack. Unsets the active tenant. Pops the top 3 items off of the stack as BEGIN, END, & LIMIT. Performs a range read of the tenant management keyspace in a language-appropriate way using these parameters. The resulting range of n tenant names are packed into a tuple as [t1,t2,t3,...,tn], and this single packed value is pushed onto the stack. Attempts to resolve the active tenant's ID. Pushes the string "GOTTENANTID" onto the stack if an ID was successfully read after waiting on the ID future. Pushes the string "NOACTIVETENANT" if there is no active tenant. Updates to Existing Instructions -- Some existing operations in the binding tester will have slightly modified behavior when tenants are enabled. When creating a new transaction, the active tenant should be used. If no active tenant is set, then the transaction should be created as normal using the database. Similar to the DATABASE suffix, an operation with the TENANT suffix indicates that the operation should be performed on the current active tenant object. If there is no active tenant, then the operation should be performed on the database as if _DATABASE was specified. In any case where the operation suffixed with _DATABASE is allowed to push a future onto the stack, the same operation suffixed with _TENANT is also allowed to push a future onto the stack. If your binding does not support operations directly on a tenant object, you should simulate it using an anonymous transaction. Remember that set and clear operations must immediately commit (with appropriate retry behavior!). Operations that can include the _TENANT prefix are: GET_TENANT GETKEYTENANT GETRANGETENANT GETRANGESTARTSWITHTENANT GETRANGESELECTOR_TENANT SET_TENANT CLEAR_TENANT CLEARRANGETENANT CLEARRANGESTARTSWITHTENANT ATOMICOPTENANT
Project: Shifu (Provisioning / Automation & Configuration)
File: telemetry-service-MQTT.md

Telemetry Service is a standalone service that takes telemetry data collected by `deviceShifu` and fan-out it to designated endpoints for future process. This doc aims to provide a design on how to fan-out telemetry to MQTT endpoints. Let telemetry service support pushing telemetries to MQTT endpoints. Let telemetry service support any random endpoints Let telemetry service serve as MQTT broker. Telemetry will be served as an HTTP server. deviceShifu will push the telemetries collected from physical devices to telemetry service, and telemetry service would then fan-out the telemetries to the endpoints specified by user. Request Struct: ```go type TelemetryRequest struct { RawData []byte `json:"rawData,omitempty"` MQTTSetting *MQTTSetting `json:"mqttSetting,omitempty"` } ``` For every push telemetry event, the telemetry service will fan-out raw-data to the user-config MQTT endpoint ```mermaid graph LR; deviceShifu -->|TelemetryRequest| TelemetryService; TelemetryService -->|RawData| MQTTEndpoint; ``` TelemetryService would have 2 methods, one extract rawData and endpoint settings, the other push the rawData to the endpoint according to the settings extracted from the first one. ```go func HandleTelemetryRequest(request *TelemetryRequest) err { ... rawData, mqttSetting, err := parseTelemetryRequest() if err != nil { return err } sendToMQTTEndPoint(rawData, &mqttSettings) ... } func parseTelemetryRequest(request TelemetryRequest) ([]byte, v1alpha1.MQTTSetting, err) { // Parse telemetry request } func sendToMQTTEndPoint(rawData []byte, mqttSettings *v1alpha1.MQTTSetting) err { // Fan-out rawData to mqtt broker } ```
Project: KubeArmor (Provisioning / Security & Compliance)
File: deployment_models.md

<img src="../.gitbook/assets/deployment-models.png" width="768" class="center" alt="Deployment Models"> KubeArmor supports following deployment models: Kubernetes orchestrated deployment with KubeArmor deployed as a daemonset. Containerized deployment with KubeArmor deployed in systemd mode on the VM/EC2/Bare-Metal instance. Non-containerized applications with KubeArmor deployed in systemd mode.
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.2.6.1.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Blocker | DN startup may cause severe data loss* <!-- markdown --> Public service notice: Every restart of a 2.6.x or 2.7.0 DN incurs a risk of unwanted block deletion. Apply this patch if you are running a pre-2.7.1 release. | Major | create() always retried with hardcoded timeout when file already exists with open lease* Proxy level retries will not be done on AlreadyBeingCreatedExeption for create() op. | Major | Allow appending to existing SequenceFiles* Existing sequence files can be appended.
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-qry-select-file.md

layout: global title: File displayTitle: File license: | 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. You can query a file with a specified format directly with SQL. ```sql fileformat.`filepath` ``` file_format* Specifies a file format for a given file path, could be TEXTFILE, ORC, PARQUET, etc. file_path* Specifies a file path with a given format. ```sql -- PARQUET file SELECT * FROM parquet.`examples/src/main/resources/users.parquet`; ++--+-+ | name|favoritecolor|favoritenumbers| ++--+-+ |Alyssa| null| [3, 9, 15, 20]| | Ben| red| []| ++--+-+ -- ORC file SELECT * FROM orc.`examples/src/main/resources/users.orc`; ++--+-+ | name|favoritecolor|favoritenumbers| ++--+-+ |Alyssa| null| [3, 9, 15, 20]| | Ben| red| []| ++--+-+ -- JSON file SELECT * FROM json.`examples/src/main/resources/people.json`; +-+-+ | age| name| +-+-+ |null|Michael| | 30| Andy| | 19| Justin| +-+-+ ```
Project: ClickHouse (App Definition and Development / Database)
File: detach.md

slug: /en/sql-reference/statements/detach sidebar_position: 43 sidebar_label: DETACH title: "DETACH Statement" Makes the server "forget" about the existence of a table, a materialized view, a dictionary, or a database. Syntax ``` sql DETACH TABLE|VIEW|DICTIONARY|DATABASE [IF EXISTS] [db.]name [ON CLUSTER cluster] [PERMANENTLY] [SYNC] ``` Detaching does not delete the data or metadata of a table, a materialized view, a dictionary or a database. If an entity was not detached `PERMANENTLY`, on the next server launch the server will read the metadata and recall the table/view/dictionary/database again. If an entity was detached `PERMANENTLY`, there will be no automatic recall. Whether a table, a dictionary or a database was detached permanently or not, in both cases you can reattach them using the query. System log tables can be also attached back (e.g. `querylog`, `textlog`, etc.). Other system tables can't be reattached. On the next server launch the server will recall those tables again. `ATTACH MATERIALIZED VIEW` does not work with short syntax (without `SELECT`), but you can attach it using the `ATTACH TABLE` query. Note that you can not detach permanently the table which is already detached (temporary). But you can attach it back and then detach permanently again. Also, you can not the detached table, or with the same name as detached permanently, or replace it with the other table with query. The `SYNC` modifier executes the action without delay. Example Creating a table: Query: ``` sql CREATE TABLE test ENGINE = Log AS SELECT * FROM numbers(10); SELECT * FROM test; ``` Result: ``` text number 0 1 2 3 4 5 6 7 8 9 ``` Detaching the table: Query: ``` sql DETACH TABLE test; SELECT * FROM test; ``` Result: ``` text Received exception from server (version 21.4.1): Code: 60. DB::Exception: Received from localhost:9000. DB::Exception: Table default.test does not exist. ``` See Also
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-login.md

layout: default title: mesheryctl-system-login permalink: reference/mesheryctl/system/login redirect_from: reference/mesheryctl/system/login/ type: reference display-title: "false" language: en command: system subcommand: login Authenticate to a Meshery Server Authenticate to the Local or a Remote Provider of a Meshery Server The authentication mode is web-based browser flow <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system login [flags] </div> </pre> Login with the Meshery Provider of your choice: the Local Provider or a Remote Provider. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system login </div> </pre> Login with the Meshery Provider by specifying it via -p or --provider flag. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system login -p Meshery </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for login -p, --provider string login Meshery with specified provider </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -c, --context string (optional) temporarily change the current context. -v, --verbose verbose output -y, --yes (optional) assume yes for user interactive prompts. </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: gitlab.md

Not needed for \most\ installs, but this is configured to integrate Lagoon with GitLab for user and group authentication. in GitLab for a user with admin access. Create system hooks under `your-gitlab.com/admin/hooks` pointing to: `webhookhandler.lagoon.example.com` and define a random secret token. Enable repository update events Update `lagoon-core-values.yml`: ```yaml title="lagoon-core-values.yml" api: additionalEnvs: GITLABAPIHOST: <<URL of GitLab example: https://your-gitlab.com>> GITLABAPITOKEN: << Personal Access token with Access to API >> GITLABSYSTEMHOOK_TOKEN: << System Hook Secret Token >> webhook-haondler: additionalEnvs: GITLABAPIHOST: <<URL of GitLab example: https://your-gitlab.com>> GITLABAPITOKEN: << Personal Access token with Access to API >> GITLABSYSTEMHOOK_TOKEN: << System Hook Secret Token >> webhooks2tasks: additionalEnvs: GITLABAPIHOST: <<URL of GitLab example: https://your-gitlab.com>> GITLABAPITOKEN: << Personal Access token with Access to API >> GITLABSYSTEMHOOK_TOKEN: << System Hook Secret Token >> ``` Helm update the `lagoon-core` helmchart. If you've already created users in Keycloak, delete them. Run the following command in an API pod: ```bash title="Sync with GitLab" yarn sync:gitlab:all ```
Project: ClickHouse (App Definition and Development / Database)
File: all.md

slug: /en/sql-reference/statements/select/all sidebar_label: ALL If there are multiple matching rows in the table, then `ALL` returns all of them. `SELECT ALL` is identical to `SELECT` without `DISTINCT`. If both `ALL` and `DISTINCT` specified, exception will be thrown. `ALL` can also be specified inside aggregate function with the same effect(noop), for instance: ```sql SELECT sum(ALL number) FROM numbers(10); ``` equals to ```sql SELECT sum(number) FROM numbers(10); ```
Project: KICS (Provisioning / Security & Compliance)
File: a6d27cf7-61dc-4bde-ae08-3b353b609f76.md

title: Cloudfront Viewer Protocol Policy Allows HTTP hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: a6d27cf7-61dc-4bde-ae08-3b353b609f76 Query name: Cloudfront Viewer Protocol Policy Allows HTTP Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: Checks if the connection between CloudFront and the viewer is encrypted<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="50 20" name: example1 community.aws.cloudfront_distribution: state: present caller_reference: unique test distribution ID origins: id: 'my test origin-000111' domain_name: www.example.com origin_path: /production custom_headers: header_name: MyCustomHeaderName header_value: MyCustomHeaderValue defaultcachebehavior: targetoriginid: 'my test origin-000111' forwarded_values: query_string: true cookies: forward: all headers: '*' viewerprotocolpolicy: allow-all smooth_streaming: true compress: true allowed_methods: items: GET HEAD cached_methods: GET HEAD name: example2 community.aws.cloudfront_distribution: state: present caller_reference: unique test distribution ID origins: id: 'my test origin-000111' domain_name: www.example.com origin_path: /production custom_headers: header_name: MyCustomHeaderName header_value: MyCustomHeaderValue cache_behaviors: targetoriginid: 'my test origin-000111' forwarded_values: query_string: true cookies: forward: all headers: '*' viewerprotocolpolicy: allow-all smooth_streaming: true compress: true allowed_methods: items: GET HEAD cached_methods: GET HEAD ``` ```yaml title="Negative test num. 1 - yaml file" name: example1 community.aws.cloudfront_distribution: state: present caller_reference: unique test distribution ID origins: id: my test origin-000111 domain_name: www.example.com origin_path: /production custom_headers: header_name: MyCustomHeaderName header_value: MyCustomHeaderValue defaultcachebehavior: targetoriginid: my test origin-000111 forwarded_values: query_string: true cookies: forward: all headers: '*' viewerprotocolpolicy: https-only smooth_streaming: true compress: true allowed_methods: items: GET HEAD cached_methods: GET HEAD name: example2 community.aws.cloudfront_distribution: state: present caller_reference: unique test distribution ID origins: id: my test origin-000111 domain_name: www.example.com origin_path: /production custom_headers: header_name: MyCustomHeaderName header_value: MyCustomHeaderValue cache_behaviors: targetoriginid: my test origin-000111 forwarded_values: query_string: true cookies: forward: all headers: '*' viewerprotocolpolicy: https-only smooth_streaming: true compress: true allowed_methods: items: GET HEAD cached_methods: GET HEAD ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.10.13.md

RabbitMQ `3.10.13` is a maintenance release in the `3.10.x` . Please refer to the upgrade section from if upgrading from a version prior to 3.10.0. This release requires Erlang 24.2 and supports Erlang 25. has more details on Erlang version requirements for RabbitMQ. Erlang 23 support has reached its . This release of RabbitMQ requires Erlang 24.2 or later versions. Nodes will fail to start on older Erlang releases. Erlang 25 is recommended: it offers much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation. Release notes can be found on GitHub at . Backported a number of free disk space monitor resiliency improvements. GitHub issue: If `handle.exe` is not available, free disk space monitor will now shell out to PowerShell to retrieve the number of open file handles used by the node. GitHub issue: `raft.adaptivefailuredetector.pollinterval` exposes 's `pollinterval` setting to RabbitMQ users. Increasing it can reduce the probability of false positives in clusters where inter-node communication links are used at close to maximum capacity. The default is `5000` (5 seconds). GitHub issue: When both `diskfreelimit.relative` and `diskfreelimit.absolute`, or both `vmmemoryhighwatermark.relative` and `vmmemoryhighwatermark.absolute` are set, the absolute settings will now take precedence. Contributed by @SimonUnge (AWS). GitHub issue: Closing channels will now log a warning if they had any messages pending a . Contributed by @Kiruamvp. GitHub issue: Classic queues with enabled could run into an exception. GitHub issue: When a was cleared, nodes emitted an of the wrong type. GitHub issue: `rabbitmq-queues grow` and `rabbitmq-queues shrink` misformatted the errors they could encounter. Contributed by @gomoripeti (CloudAMQP). GitHub issue: New key supported by `rabbitmqctl listqueues`: `effectivepolicy_definition` that returns merged definitions of regular and effective for the queue. GitHub issue: New HTTP API endpoint, `GET /api/config/effective`, returns effective node configuration. This is an HTTP API counterpart of `rabbitmq-diagnostics environment`. Contributed by @SimonUnge (AWS). GitHub issue: Plugin could fail to boot and halt node boot due to incorrect boot step metadata. GitHub issue: `ra` was upgraded To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.10.13.tar.xz` instead of the source tarball produced by GitHub.
Project: StarRocks (App Definition and Development / Database)
File: element_at.md

displayed_sidebar: "English" Returns the value for the specified key from a key-value pair of a map. If any input parameter is NULL or if the key does not exist in the map, the result is NULL. If you want to retrieve an element from an array, see . This function is supported from v3.0 onwards. ```Haskell elementat(anymap, any_key) ``` `any_map`: a MAP expression from which to retrieve values. `any_key`: a key in the map. If `anykey` exists in `anymap`, the value corresponding to the key will be returned. Otherwise, NULL is returned. ```plain text mysql> select element_at(map{1:3,2:4},1); +--+ | map{1:3,2:4}[1] | +--+ | 3 | +--+ mysql> select element_at(map{1:3,2:4},3); +--+ | map{1:3,2:4}[3] | +--+ | NULL | +--+ mysql> select element_at(map{'a':1,'b':2},'a'); +--+ | map{'a':1,'b':2}['a'] | +--+ | 1 | +--+ ``` ELEMENT_AT, MAP
Project: Meshery (Provisioning / Automation & Configuration)
File: argo-cd.md

layout: integration title: Argo CD Applications subtitle: Collaborative and visual infrastructure as code for Argo CD Applications image: /assets/img/integrations/argo-cd/icons/color/argo-cd-color.svg permalink: extensibility/integrations/argo-cd docURL: https://docs.meshery.io/extensibility/integrations/argo-cd description: integrations-category: App Definition and Development integrations-subcategory: Continuous Integration & Delivery registrant: Artifact Hub components: name: argo-cd-extension colorIcon: assets/img/integrations/argo-cd/components/argo-cd-extension/icons/color/argo-cd-extension-color.svg whiteIcon: assets/img/integrations/argo-cd/components/argo-cd-extension/icons/white/argo-cd-extension-white.svg description: name: application colorIcon: assets/img/integrations/argo-cd/components/application/icons/color/application-color.svg whiteIcon: assets/img/integrations/argo-cd/components/application/icons/white/application-white.svg description: name: application-set colorIcon: assets/img/integrations/argo-cd/components/application-set/icons/color/application-set-color.svg whiteIcon: assets/img/integrations/argo-cd/components/application-set/icons/white/application-set-white.svg description: name: app-project colorIcon: assets/img/integrations/argo-cd/components/app-project/icons/color/app-project-color.svg whiteIcon: assets/img/integrations/argo-cd/components/app-project/icons/white/app-project-white.svg description: featureList: [ "Gain mastery over Argo as a workflow engine for Kubernetes", "Design application definitions using the intuitive, context-aware visual designer, MeshMap.", "Visualize your declarative, GitOps continuous delivery tool for Kubernetes." ] 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: Meshery (Provisioning / Automation & Configuration)
File: v0.5.0-rc-6.md

layout: release date: 2021-03-17 tag: v0.5.0-rc-6 Added versions for meshsync and broker controllers @kumarabd (#2566) [mesheryctl] consistent formatting of client and server version @aneeshnema (#2563) [meshery] Changes to meshery bash script for better user experience @hexxdump (#2554) Small ui fix for grafana boards @vineethvanga18 (#2562) [mesheryctl] platform: kubernetes support for `system status` command @navendu-pottekkat (#2550) Auto deploy for meshery operator @kumarabd (#2538) [mesheryctl] Add --platform flag to `system context create` to support platform: kubernetes @navendu-pottekkat (#2559) Small ui change in prompt component @vineethvanga18 (#2555) Upgrade Relay to V11.0.0 and minor fixes @dhruv0000 (#2556) generic prompt component @vineethvanga18 (#2544) [CI] [integration] Cypress Testing for the "Discover Cluster" configuration @piyushsingariya (#2551) removed octarine from default listing @aneeshnema (#2545) consistent version and GIT SHA format @aneeshnema (#2552) Fix traefik mesh icon in the settings @utkarsh-pro (#2535) Temporarily removed nginx sm from meshery ui @utkarsh-pro (#2536) [docs] Add Meshery and mesheryctl roadmap into a ROADMAP.md file @navendu-pottekkat (#2525) [Bug Fix] Minor fix for Relay 11.0.0 @dhruv0000 (#2564) Cypress Testing for the "Service Mesh" configuration @piyushsingariya (#2466) Bump elliptic from 6.5.3 to 6.5.4 in /provider-ui @dependabot (#2517) Bump elliptic from 6.5.3 to 6.5.4 in /ui @dependabot (#2524) adding mesheryctl commands doc template @alonsolopezr (#2548)
Project: Carvel (App Definition and Development / Application Definition & Image Build)
File: README_Kinesis.md

The following is a sample class and Lambda function that receives Amazon Kinesis event record data as an input and writes some of the record data to CloudWatch Logs. (Note that anything written to stdout or stderr will be logged as CloudWatch Logs events.) ```go package main import ( "context" "fmt" "github.com/aws/aws-lambda-go/events" "github.com/aws/aws-lambda-go/lambda" ) func handler(ctx context.Context, kinesisEvent events.KinesisEvent) error { for _, record := range kinesisEvent.Records { kinesisRecord := record.Kinesis dataBytes := kinesisRecord.Data dataText := string(dataBytes) fmt.Printf("%s Data = %s \n", record.EventName, dataText) } return nil } func main() { lambda.Start(handler) } ```