cwielenb/CNCF-Dataset huggingface dataset:
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_service_account_keys.md

+++ title = "googleserviceaccount_keys resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleserviceaccount_keys" identifier = "inspec/resources/gcp/googleserviceaccountkeys.md googleserviceaccountkeys resource" parent = "inspec/resources/gcp" +++ A `googleserviceaccount_keys` is used to test a Google ServiceAccountKey resource ```ruby describe googleserviceaccountkeys(project: 'chef-gcp-inspec', serviceaccount: "display-name@project-id.iam.gserviceaccount.com") do its('count') { should be <= 1000 } its('keytypes') { shouldnot include 'USER_MANAGED' } end ``` describe googleserviceaccountkeys(project: 'sample-project', serviceaccount: 'sample-account@sample-project.iam.gserviceaccount.com') do its('count') { should be <= 1000} end describe googleserviceaccountkeys(project: 'sample-project', serviceaccount: 'sample-account@sample-project.iam.gserviceaccount.com') do its('key_names'){ should include "projects/sample-project/serviceAccounts/test-sa@sample-project.iam.gserviceaccount.com/keys/c6bd986da9fac6d71178db41d1741cbe751a5080" } end Properties that can be accessed from the `googleserviceaccount_keys` resource: See the resource for more information. `key_names` : an array of `googleserviceaccount_key` name `privatekeytypes` : an array of `googleserviceaccountkey` privatekey_type `key_algorithms` : an array of `googleserviceaccountkey` keyalgorithm `privatekeydata` : an array of `googleserviceaccountkey` privatekey_data `publickeydata` : an array of `googleserviceaccountkey` publickey_data `validaftertimes` : an array of `googleserviceaccountkey` validafter_time `validbeforetimes` : an array of `googleserviceaccountkey` validbefore_time `key_types` : an array of `googleserviceaccountkey` keytype `service_accounts` : an array of `googleserviceaccountkey` serviceaccount `paths` : an array of `googleserviceaccount_key` path This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.
Project: StarRocks (App Definition and Development / Database)
File: VARCHAR.md

displayed_sidebar: "English" VARCHAR(M) A variable-length string. `M` indicates the length of the string. The default value is `1`. Unit: bytes. In versions earlier than StarRocks 2.1, the value range of `M` is [1, 65533]. [Preview] In StarRocks 2.1 and later versions, the value range of `M` is [1, 1048576]. Create a table and specify the column type as VARCHAR. ```SQL CREATE TABLE varcharDemo ( pk INT COMMENT "range [-2147483648, 2147483647]", pd_type VARCHAR(20) COMMENT "range char(m),m in (1-65533) " ) ENGINE=OLAP DUPLICATE KEY(pk) COMMENT "OLAP" DISTRIBUTED BY HASH(pk) ```
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-logs.md

layout: default title: mesheryctl-system-logs permalink: reference/mesheryctl/system/logs redirect_from: reference/mesheryctl/system/logs/ type: reference display-title: "false" language: en command: system subcommand: logs Print logs Print history of Meshery's logs and begin tailing them. It also shows the logs of a specific component. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system logs [flags] </div> </pre> Show logs (without tailing) <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system logs </div> </pre> Starts tailing Meshery server debug logs (works with components also) <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system logs --follow </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system logs meshery-istio </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -f, --follow (Optional) Follow the stream of the Meshery's logs. Defaults to false. -h, --help help for logs </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: Chef InSpec (Provisioning / Security & Compliance)
File: google_project_service.md

+++ title = "googleprojectservice resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleprojectservice" identifier = "inspec/resources/gcp/googleprojectservice.md googleprojectservice resource" parent = "inspec/resources/gcp" +++ A `googleprojectservice` is used to test a Google Service resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googleprojectservice(project: 'chef-gcp-inspec', name: 'maps-android-backend.googleapis.com') do it { should exist } its('state') { should cmp "ENABLED" } end ``` Properties that can be accessed from the `googleprojectservice` resource: `name` : The resource name of the service `parent` : The name of the parent of this service. For example 'projects/123' `state` : Whether or not the service has been enabled for use by the consumer. Possible values: STATE_UNSPECIFIED DISABLED ENABLED `disabledependentservices` : Indicates if dependent services should also be disabled. Can only be turned on if service is disabled. `config` : The service configuration of the available service. `name` : The DNS address at which this service is available. `title` : The product title for this service `apis` : The list of API interfaces exported by this service. `name` : Name of the API `version` : The version of the API Ensure the is enabled for the current project.
Project: Nocalhost (App Definition and Development / Application Definition & Image Build)
File: ISSUE_TEMPLATE.md

Please use the following questions as a guideline to help me answer your issue/question without further inquiry. Thank you. [ ] elastic.v7 (for Elasticsearch 7.x) [ ] elastic.v6 (for Elasticsearch 6.x) [ ] elastic.v5 (for Elasticsearch 5.x) [ ] elastic.v3 (for Elasticsearch 2.x) [ ] elastic.v2 (for Elasticsearch 1.x)
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: v1.10.1.md

Dapr 1.10.0 introduced a regression in pub/sub. When publishing a message, Dapr incorrectly sets the Dapr "app-id" as the `id` field in the Cloud Envelope instead of a UUID value, Additionally, the `source` field was be set to `"Dapr"`, irrespective of the app-id producing the event. This impacts Dapr users who publish messages and who are not using custom cloud events and/or raw paylods. Impacted Dapr version is 1.10.0. The regression was introduced in a code change first merged for Dapr 1.10.0. We adjusted the change and added tests to capture the correctness of the `id` field for the scenario where Dapr is required to produce a new cloud event.
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: 1.9.md

We can't wait for you to try our newest features! Find & Replace Color Code Cluster Environments for Better Differentiation Status and Violation Icons for OPA Rules Popover for Images to List Resources New File and Duplicate File Actions Autosave indicator We hope youll complete it and help us on our mission to improve Monokle by answering a few questions. For more info about these new features and additional updates
Project: Beam (App Definition and Development / Streaming & Messaging)
File: twister2-runner.md

title: "Twister2 Runner Roadmap" <!-- 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. --> This roadmap is in progress. In the meantime, here are available resources: - Issues:
Project: YDB (App Definition and Development / Database)
File: COPYING.md

Traitlets is adapted from enthought.traits, Copyright (c) Enthought, Inc., under the terms of the Modified BSD License. This project is licensed under the terms of the Modified BSD License (also known as New or Revised or 3-Clause BSD), as follows: Copyright (c) 2001-, IPython Development Team All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the IPython Development Team nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The IPython Development Team is the set of all contributors to the IPython project. This includes all of the IPython subprojects. The core team that coordinates development on GitHub can be found here: https://github.com/jupyter/. IPython uses a shared copyright model. Each contributor maintains copyright over their contributions to IPython. But, it is important to note that these contributions are typically only changes to the repositories. Thus, the IPython source code, in its entirety is not the copyright of any single person or institution. Instead, it is the collective copyright of the entire IPython Development Team. If individual contributors want to maintain a record of what changes/contributions they have specific copyright on, they should indicate their copyright in the commit message of the change, when they commit the change to one of the IPython repositories. With this in mind, the following banner should be used in any source code file to indicate the copyright and license terms:
Project: Meshery (Provisioning / Automation & Configuration)
File: operator.md

layout: default title: Operator permalink: concepts/architecture/operator type: components redirect_from: architecture/operator abstract: "Meshery Operator controls and manages the lifecycle of components deployed inside a kubernetes cluster" language: en display-title: "false" list: include <link rel="stylesheet" type="text/css" href="{{ site.baseurl }}/_sass/operator.css"> Meshery Operator is a Kubernetes Operator that deploys and manages the lifecycle of two Meshery components critical to Meshery's operations of Kubernetes clusters. Deploy one Meshery Operator per Kubernetes cluster under management - whether Meshery Server is deploy inside or outside of the clusters under management. It is recommended to deploy one Meshery Operator per cluster. [Meshery Operator and MeshSync]({{ site.baseurl }}/assets/img/architecture/meshery-operator-and-meshsync.svg) [Meshery Operator and MeshSync]({{ site.baseurl }}/assets/img/architecture/meshery-operator-deployment-sequence.svg) Meshery broker is one of the core components of the meshery architecture. This controller manages the lifecycle of broker that meshery uses for data streaming across the cluster and the outside world. See for more information. MeshSync Controller manages the lifecycle of MeshSync that is deployed for resource synchronization for the cluster. See for more information. As a Kubernetes custom controller, Meshery Operator is provisioned and deprovisioned when Meshery Server is connected to or disconnected from Kubernetes cluster. Meshery Server connections to Kubernetes clusters are controlled using Meshery Server clients: `mesheryctl` or Meshery UI. This behavior described below is consistent whether your Meshery deployment is using Docker or Kubernetes as the platform to host the Meshery deployment. Meshery CLI `mesheryctl` initiates connection to Kubernetes cluster when `mesheryctl system start` is executed and disconnects when `mesheryctl system stop` is executed. This behavior is consistent whether your Meshery deployment is using Docker or Kubernetes as the platform to host the Meshery deployment. Meshery UI Meshery UI offers more granular control over the deployment of Meshery Operator in that you can remove Meshery Operator from a Kubernetes cluster without disconnecting Meshery Server from the Kubernetes cluster. You can control the deployment of Meshery Operator using the on/off switch found in the Meshery Operator section of Settings. Yes, Meshery Operator used the Operator SDK.
Project: StarRocks (App Definition and Development / Database)
File: percentile_cont.md

displayed_sidebar: "English" Computes the percentile value of `expr` with linear interpolation. ```Haskell PERCENTILE_CONT (expr, percentile) ``` `expr`: the expression by which to order the values. It must be of numeric data types, DATE, or DATETIME. For example, if you want to find the median score of physics, specify the column that contains the physics scores. `percentile`: the percentile of the value you want to find. It is a constant floating-point number from 0 to 1. For example, if you want to find the median value, set this parameter to `0.5`. Returns a value that is at the specified percentile. If no input value lies exactly at the desired percentile, the result is calculated using linear interpolation of the two nearest input values. The data type is the same as `expr`. This function ignores NULLs. Suppose there is a table named `exam` with the following data. ```Plain select * from exam order by Subject; +--+-+ | Subject | Score | +--+-+ | chemistry | 80 | | chemistry | 100 | | chemistry | NULL | | math | 60 | | math | 70 | | math | 85 | | physics | 75 | | physics | 80 | | physics | 85 | | physics | 99 | +--+-+ ``` Calculate the median score of each subject while ignoring NULLs. Query: ```SQL SELECT Subject, PERCENTILE_CONT (Score, 0.5) FROM exam group by Subject; ``` Result: ```Plain +--+--+ | Subject | percentile_cont(Score, 0.5) | +--+--+ | chemistry | 90 | | math | 70 | | physics | 82.5 | +--+--+ ```
Project: StarRocks (App Definition and Development / Database)
File: json_array.md

displayed_sidebar: "English" Converts each element of an SQL array to a JSON value and returns a JSON array that consists of the JSON values. ```Haskell json_array(value, ...) ``` `value`: an element in the SQL array. 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 array. Example 1: Construct a JSON array that consists of values of different data types. ```plaintext mysql> SELECT json_array(1, true, 'starrocks', 1.1); -> [1, true, "starrocks", 1.1] ``` Example 2: Construct an empty JSON array. ```plaintext mysql> SELECT json_array(); -> [] ```
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: file-explorer.md

The File Explorer shows all files parsed in the folder selected: Excluded files are greyed out. Files containing resource manifests have a number displayed after them, showing the number of resources found in that file. Selecting a file will highlight contained resources in the Navigator and attempt to scroll them into view. The contents of the file will be shown in the source editor to the right, allowing for direct editing of the file. In this screenshot: The argo-rollouts-aggregate-roles.yaml file is selected - the "3" after the filename indicates it contains 3 Kubernetes resources. The 3 ClusterRole resources in the file are highlighed in the Navigator in the middle of the screen. The contents of the file are shown in the editor to the right. While in the File Explorer, the File Action drop down list is available by clicking the ellipsis to the right of the file name. In the File Actions pop up menu, the following actions are available: Add Resource Filter on this file Add to Files: Exclude Copy Path Copy Relative Path Duplicate Rename Delete Open on GitHub Reveal in Finder The same functionality is available for Folders: In the Folder Actions pop up menu, the following actions are available: New Folder New File New Resource Filter on this folder Add to Files: Exclude Copy Path Copy Relative Path Duplicate Rename Delete Open on GutHub Reveal in Finder
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: apiserver.md

The apiserver is enabled by default, but you need some extra works to make it accessible outside the k8s cluster. For development environment, you can use `kubectl port-forward` to access the KubeVela apiserver. ```shell kubectl port-forward --namespace vela-system service/kubevela-vela-core-apiserver 8000:80 ``` For production environment, you can set up Ingress to expose the KubeVela apiserver. ```shell cat <<EOF | kubectl apply -f - apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: kubevela-vela-core-apiserver namespace: vela-system spec: defaultBackend: service: name: kubevela-vela-core-apiserver port: number: 80 EOF ``` ```shell $ kubectl get ingress -n vela-system NAME CLASS HOSTS ADDRESS PORTS AGE kubevela-vela-core-apiserver <none> * <your ip> 80 99m ``` URL ``` POST /v1/namespaces/<namespace>/applications/<application name> ``` Request Body Example ```json { "components": [ { "name": "express-server", "type": "webservice", "properties": { "image": "crccheck/hello-world", "port": 8000 }, "traits": [ { "type": "ingress", "properties": { "domain": "testsvc.example.com", "http": { "/": 8000 } } } ] } ] } ``` ``` DELETE /v1/namespaces/<namespace>/applications/<application name> ```
Project: Gefyra (App Definition and Development / Application Definition & Image Build)
File: guide-request.md

name: Setup Request about: Request a Gefyra guide for a Kubernetes setup title: "[Guide request]: " labels: enhancement assignees: '' <!-- Hi , thank you for submitting a Guide request to Gefyra! Don't forget to replace the title of this issue with a short sentence that describes the Kubernetes distribution/setup of your request! --> Use this section to give a description of what your Kubernetes setup for development contains. Examples: I would like to have the following setup "Kubernetes distribution of A..." "connectivity of B..." "something special..." What do you all think? I would love to see it! I would love to help! Thank you for your request!
Project: OpenAPI (App Definition and Development / Application Definition & Image Build)
File: agenda.md

This agenda gives visibility into discussion topics for the weekly Technical Developer Community (TDC) meetings. Sharing agenda items in advance allows people to plan to attend meetings where they have an interest in specific topics. Whether attending or not, anyone can comment on this issue prior to the meeting to suggest topics or to add comments on planned topics or proposals. Meetings take place over Zoom: , dial-in passcode: 763054 Participants must abide by our . Meetings are recorded for future reference, and for those who are not able to attend in-person. We invite you to feel comfortable to challenge any language or behaviour that is harmful or not inclusive during this meeting. We look forward to your participation, but please consider these acts of etiquette: Remain on mute when not speaking to prevent interruptions. Blur your background to reduce visual distractions. Use the Zoom meeting "Raise Hand" feature to notify the group when you wish to speak. | Blur My Background | Raise Hand | |-|-| | <img width="323" alt="Screenshot of Zoom UI showing the 'Stop Video' and 'Blur My Background' control" src="https://github.com/OAI/OpenAPI-Specification/assets/7367/7e43dbbb-6529-46e6-8b04-4c1aa852d9dd"> | <img width="323" alt="Screenshot of Zoom UI showing the 'Reaction' and 'Raise Hand' control" src="https://github.com/OAI/OpenAPI-Specification/assets/7367/f991722f-4651-40aa-9bc4-7e9a2a165a6a"> | | Topic | Owner | Decision/NextStep | |-|-|-| Intros and governance meta-topics (5 mins) | TDC | | Reports from Special Interest Groups (5 mins) | SIG members | | Any other business (add comments below to suggest topics) | TDC | | | @OAI/tsc | | | @OAI/openapi-maintainers | | | @OAI/triage | | /cc please suggest items for inclusion.
Project: Crux (App Definition and Development / Database)
File: README.md

This project provides two things: A simple test-harness for running tests for the different language clients A proxy server for the http module which helps with: setting up nodes interacting with them (querying, submitting txs) and tearing down nodes without re-starting the jvm for each test To run the tests just run: `./gradlew lang:test-harness:test` To add a new language to the harness, see the `python_test.clj` for an example. You can run a version locally with `./gradlew lang:test-harness:httpProxy`. A server is run on port `3300` when the test harness runs. Once running you can: ``` GET http://localhost:3300/setup GET http://localhost:3300/setup?my-token base_url = http://localhost/<token> POST $base_url/query POST $base_url/tx GET http://localhost:3300/teardown?<token> ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.11.25.md

RabbitMQ `3.11.25` is a maintenance release in the `3.11.x` . This release series . Please refer to the upgrade section from if upgrading from a version prior to 3.11.0. This release requires Erlang 25 and supports Erlang versions up to `25.3.x`. has more details on Erlang version requirements for RabbitMQ. As of 3.11.0, RabbitMQ requires Erlang 25. Nodes will fail to start on older Erlang releases. Erlang 25 as our new baseline means much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation available to all RabbitMQ 3.11 users. Release notes can be found on GitHub at . Avoids a potential exception in the `autoheal` partition handler. Contributed by @Ayanda-D. GitHub issue: `raft.segmentmaxentries` is now validated to prevent the value from overflowing its 16-bit segment file field. Maximum supported value is now ``65535. GitHub issue: Significantly faster Shovel startup in environments where there are many of them (one thousand or more). GitHub issue: User-provided credentials are now obfuscated using an one-off key pair generated on node boot. This keeps sensitive client state information from being logged by the runtime exception logger. GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.25.tar.xz` instead of the source tarball produced by GitHub.