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

title: kbcli playground Bootstrap or destroy a playground KubeBlocks in local host or cloud. ``` -h, --help help for playground ``` ``` --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 ``` - Destroy the playground KubeBlocks and kubernetes cluster. - Bootstrap a kubernetes cluster and install KubeBlocks for playground.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_migration_list.md

title: kbcli migration list List migration tasks. ``` kbcli migration list [NAME] [flags] ``` ``` kbcli migration list kbcli migration list mytask kbcli migration list mytask -o yaml kbcli migration list mytask -o json kbcli migration list mytask -o wide ``` ``` -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 -o, --output format prints the output in the specified format. Allowed values: table, json, yaml, wide (default table) -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. --show-labels When printing, show all labels as the last column (default hide labels column) ``` ``` --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 ``` - Data migration between two data sources.
Project: Open Application Model (App Definition and Development / Application Definition & Image Build)
File: 8.practical_considerations.md

This section provides additional guidance on practical considerations for implementors. The model is currently in Rough Draft, working toward Working Draft. After Working Draft, the specification will become a Final Specification (e.g., 1.0). During Rough Draft, no part of the model is considered stable During Working Draft, features may be added, and issues fixed. Breaking changes may occur, but as an irregularity During Final Specification, the model will only be updated with errata, grammatical fixes, and clearly marked "clarifying text" Once a Final Specification is released (e.g., 1.0), a new version of the spec (e.g., 1.1) may be started at the rough draft phase. The media types for schematics will be defined when the model enters Working Draft status. Preliminarily, the media types will be of the form: `application/oam.TYPE.v1+json`, where `TYPE` is replaced by the name of the type (e.g. `component`). This model, in its current form, does not mandate a specific set of security policies. However, it does provide guidance on certain aspects of security: OCI/Docker images MUST be referenced by SHA wherever possible File formats MUST be converted to a canonical format so that they can be hashed When these two conditions are satisfied, systems can be constructed in which a digest verification of schematics will preserve the immutability of all components of the system. To wit, if a schematic references an image with a hash, then the process to verify the digest of the schematic also ensures that the image pulled has the same reference used to generate the schematic. Other security details, such as network transport security or securing data at rest, are considered beyond the scope of this model. | Previous | Next | | - |-| | | |
Project: SPIFFE (Provisioning / Key Management)
File: ANDREW_JESSUP.md

Nomination submitted by @evan2645: Andrew has been a champion for SPIFFE since its practical inception. Drawing on his previous experience as an engineer and product manager at Google and elsewhere, Andrew has been instrumental in helping to breathe life into SPIFFE in its early days. He understands the landscape well, and is a strong user advocate with focus on usability and totality. Should he accept this nomination, I think he'd bring a wealth of value and perspective to the SSC. Andrew answered the following questions in support of his nomination. What makes you a good fit for the SPIFFE Steering Committee? I was one of the co-founders of Scytale and led the first draft of the SPIRE design doc (based on Joe Beda's white paper) in 2017. Since then I've spent most of my professional energy helping to catalyse the SPIFFE community, understanding what members of that community are trying to achieve with the SPIFFE project (including over 100 interviews with community members) as well as building an understanding of the markets and industry segments adjacent to SPIFFE (such as secrets management, service mesh, certificate management and IAM). What aspects of SSC participation are you most excited about? As SPIFFE grows and evolves I'm hoping to use the insight I've gained from the last 4 years of working with the community to help identify unmet needs (such as transitive identity and delegated claims), help the SSC and maintainers evaluate the potential benefits and risks of different design decisions, and help to be a conduit between the SSC and maintainers and the community at large. GitHub Handle: @ajessup Email Address: ajessup@gmail.com LinkedIn Profile: https://www.linkedin.com/in/andrewjessup/ Current Affiliation: HPE
Project: YugabyteDB (App Definition and Development / Database)
File: perf_explain.md

title: EXPLAIN statement [YSQL] headerTitle: EXPLAIN linkTitle: EXPLAIN description: Use the EXPLAIN statement to show the execution plan for an statement. If the ANALYZE option is used, the statement will be executed, rather than just planned. menu: v2.18: identifier: perf_explain parent: statements type: docs Use the `EXPLAIN` statement to show the execution plan for an statement. If the `ANALYZE` option is used, the statement will be executed, rather than just planned. In that case, execution information (rather than just the planner's estimates) is added to the `EXPLAIN` result. {{%ebnf%}} explain, option {{%/ebnf%}} Where statement is the target statement (see more ). Execute the statement and show actual run times and other statistics. Create a sample table. ```sql yugabyte=# CREATE TABLE sample(k1 int, k2 int, v1 int, v2 text, PRIMARY KEY (k1, k2)); ``` Insert some rows. ```sql yugabyte=# INSERT INTO sample(k1, k2, v1, v2) VALUES (1, 2.0, 3, 'a'), (2, 3.0, 4, 'b'), (3, 4.0, 5, 'c'); ``` Check the execution plan for simple select (condition will get pushed down). ```sql yugabyte=# EXPLAIN SELECT * FROM sample WHERE k1 = 1; ``` ```output QUERY PLAN Index Scan using sample_pkey on sample (cost=0.00..15.25 rows=100 width=44) Index Cond: (k1 = 1) (2 rows) ``` Check the execution plan for select with complex condition (second condition requires filtering). ```sql yugabyte=# EXPLAIN SELECT * FROM sample WHERE k1 = 2 and floor(k2 + 1.5) = v1; ``` ```output QUERY PLAN Index Scan using sample_pkey on sample (cost=0.00..17.75 rows=100 width=44) Index Cond: (k1 = 2) Filter: (floor(((k2)::numeric + 1.5)) = (v1)::numeric) (3 rows) ``` Check execution with `ANALYZE` option. ```sql yugabyte=# EXPLAIN ANALYZE SELECT * FROM sample WHERE k1 = 2 and floor(k2 + 1.5) = v1; ``` ```output QUERY PLAN Index Scan using sample_pkey on sample (cost=0.00..17.75 rows=100 width=44) (actual time=3.123..3.126 rows=1 loops=1) Index Cond: (k1 = 2) Filter: (floor(((k2)::numeric + 1.5)) = (v1)::numeric) Planning Time: 0.149 ms Execution Time: 3.198 ms Peak Memory Usage: 8 kB (6 rows) ```
Project: KICS (Provisioning / Security & Compliance)
File: f5c45127-1d28-4b49-a692-0b97da1c3a84.md

title: ECS Service Without Running Tasks hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: f5c45127-1d28-4b49-a692-0b97da1c3a84 Query name: ECS Service Without Running Tasks Platform: Ansible Severity: <span style="color:#edd57e">Low</span> Category: Availability URL: ECS Service should have at least 1 task running<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="2" name: ECS Service community.aws.ecs_service: state: present name: test-service cluster: test-cluster task_definition: test-task-definition desired_count: 3 placement_constraints: type: memberOf expression: 'attribute:flavor==test' placement_strategy: type: binpack field: memory ``` ```yaml title="Negative test num. 1 - yaml file" name: ECS Service community.aws.ecs_service: state: present name: test-service cluster: test-cluster task_definition: test-task-definition desired_count: 3 deployment_configuration: minimumhealthypercent: 75 maximum_percent: 150 placement_constraints: type: memberOf expression: 'attribute:flavor==test' placement_strategy: type: binpack field: memory ```
Project: ThreatMapper (Provisioning / Security & Compliance)
File: scanning-ci.md

title: Scanning in CI You can use ThreatMapper to scan artifacts in a CI (Continuous Integration) pipeline. If a vulnerability is detected and the CI build is blocked, ThreatMapper will submit the details to the configured notification services. The ThreatMapper CI action supports several CI pipelines, including CircleCI, GitLab and Jenkins. It blocks a build if the number of CVE violations exceeds a user-defined threshold, or if the total CVE score exceeds a threshold, and notifications are submitted to the configured management console. If a build is not blocked, ThreatMapper silently allows it to proceed. For configuration details, refer to the appropriate , including: * *
Project: kube-hunter (Provisioning / Security & Compliance)
File: KHV050.md

vid: KHV050 title: Read access to Pod service account token categories: [Access Risk] severity: medium Every Pod in Kubernetes is associated with a Service Account which by default has access to the Kubernetes API. This access is made available to Pods by an auto-generated token that is made available to the Pod by Kubernetes. An attacker with access to a Pod can read the token and access the Kubernetes API. It is recommended to explicitly specify a Service Account for all of your workloads (`serviceAccountName` in `Pod.Spec`), and manage their permissions according to the least privilege principle. Consider opting out automatic mounting of SA token using `automountServiceAccountToken: false` on `ServiceAccount` resource or `Pod.spec`.
Project: Pulsar (App Definition and Development / Streaming & Messaging)
File: CONTRIBUTING.md

<!-- 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. --> We would love for you to contribute to Apache Pulsar and make it even better! Please check the before starting to work on the project.
Project: The Update Framework (TUF) (Provisioning / Security & Compliance)
File: README.md

This package provides modules for TUF client implementers. tuf.ngclient.Updater is a class that implements the client workflow described in the TUF specification (see https://theupdateframework.github.io/specification/latest/#detailed-client-workflow) tuf.ngclient.FetcherInterface is an abstract class that client implementers can implement a concrete class of in order to reuse their own networking/download libraries -- a Requests-based implementation is used by default. This package: Aims to be a clean, easy-to-validate reference client implementation written in modern Python At the same time aims to be the library of choice for anyone implementing a TUF client in Python: light-weight, easy to integrate and with minimal required dependencies Is still under development but is planned to become the default client in this implementation (i.e., the older `tuf.client` will be deprecated in the future)
Project: StarRocks (App Definition and Development / Database)
File: DROP_RESOURCE.md

displayed_sidebar: "English" This statement is used to drop an existing resource. Only root or superuser can drop resources. Syntax: ```sql DROP RESOURCE 'resource_name' ``` Drop Spark resource named spark0. ```SQL DROP RESOURCE 'spark0'; ``` Drop Hive resource named hive0. ```SQL DROP RESOURCE 'hive0'; ```
Project: YugabyteDB (App Definition and Development / Database)
File: dcl_create_group.md

title: CREATE GROUP statement [YSQL] headerTitle: CREATE GROUP linkTitle: CREATE GROUP description: Use the CREATE GROUP statement to create a group role. CREATE GROUP is an alias for CREATE ROLE and is used to create a group role. menu: v2.18: identifier: dclcreategroup parent: statements type: docs Use the `CREATE GROUP` statement to create a group role. `CREATE GROUP` is an alias for and is used to create a group role. {{%ebnf%}} create_group, role_option {{%/ebnf%}} See for more details. Create a sample group that can manage databases and roles. ```plpgsql yugabyte=# CREATE GROUP SysAdmin WITH CREATEDB CREATEROLE; ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: get-started-contributing.md

title: "Beam Code Contribution Guide" type: "contribute" layout: "arrow_template" <!-- 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. --> For information on contributing code to Beam, see the . For information on other ways to contribute, see the general .
Project: YDB (App Definition and Development / Database)
File: load-actors-memory.md

Allocates memory blocks of the specified size at certain intervals. After the load is removed, the allocated memory is released. Using this actor, you can test the logic, e.g., whether a certain trigger is fired when the [RSS]{% if lang == "en" %}(https://en.wikipedia.org/wiki/Residentsetsize){% endif %}{% if lang == "ru" %}(https://ru.wikipedia.org/wiki/Residentsetsize){% endif %} limit is reached. {% note info %} This ad-hoc actor is used for testing specific functionality. This is not a load actor. It is designed to check whether something works properly. {% endnote %} | Parameter | Description | | | `DurationSeconds` | Load duration in seconds. | | `BlockSize` | Allocated block size in bytes. | | `IntervalUs` | Interval between block allocations in microseconds. | The following actor allocates blocks of `1048576` bytes every `9000000` microseconds during `3600` seconds and takes up 32 GB while running: ```proto MemoryLoad: { DurationSeconds: 3600 BlockSize: 1048576 IntervalUs: 9000000 } ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: beam-summit-europe.md

title: "Beam Summit Europe 2018" date: 2018-08-21 00:00:01 -0800 categories: blog aliases: /blog/2018/08/21/beam-summit-europe.html authors: mbaetens <!-- 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. --> With a growing community of contributors and users, the Apache Beam project is organising the first European Beam Summit. We are happy to invite you to this event, which will take place in London on October 1st and 2nd of 2018. <!--more--> <img src="/images/blog/Facebook-AD.png" alt="Beam Summit Europe 2018 flyer" height="360" width="640" > The summit is a 2 day, multi-track event. During the first day well host sessions to share use cases from companies using Apache Beam, community driven talks, and a session to discuss the project's roadmap (from the main partners in the project as well as all users planning to contribute to the project and wanting to share their plans). We'll also have break-out sessions that will allow cross team collaboration in multiple sub-topics. The second day will be a "hands-on" day. We will offer an introductory session to Apache Beam. Additionally, we'll host an advanced track for more advanced users with open-table discussions about more complex and newer Apache Beam features. The agenda will grow and be communicated in the coming month, keep an eye on the page. Venue: Dates: 1-2 October 2018 You can register for free on the . With this we are also launching a Call for Papers in case you want to secure a slot for one of the sessions. Please fill out the . Furthermore, in order to keep this event free, we are looking for people to help out at and/or sponsor some parts of the conference. If you (or your company) are interested to help out, please reach out to: <baetensmatthias@gmail.com> or <alex@vanboxel.be>. You can find more info in the Thanks, and we hope to see you at the event! The Events & Meetups Group
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: graphql.md

API interactions in Lagoon are done via GraphQL. In order to authenticate to the API, you need a JWT (JSON Web Token), which will authenticate you against the API via your SSH public key. To generate this token, use the remote shell via the `token` command: ```bash title="Get token" ssh -p [PORT] -t lagoon@[HOST] token ``` Example for amazee.io: ```bash title="Get amazee.io token" ssh -p 32222 -t lagoon@ssh.lagoon.amazeeio.cloud token ``` This will return a long string, which is the JWT token. We also need the URL of the API endpoint. Ask your Lagoon administrator for this. <!-- markdown-link-check-disable-next-line --> On amazee.io this is . Now we need a GraphQL client! Technically this is just HTTP, but we suggest GraphiQL. It has a nice UI that allows you to write GraphQL requests with autocomplete. Download, install and start it. \\] Enter the API endpoint URL. Then click on "Edit HTTP Headers" and add a new Header: "Header name": `Authorization` "Header value": `Bearer [jwt token]` \(make sure that the JWT token has no spaces, that won't work\) Close the HTTP Header overlay \(press ESC\) and now you are ready to make your first GraphQL Request! Enter this on the left window: ```graphql title="Get all projects" query whatIsThere { allProjects { id gitUrl name branches pullrequests productionEnvironment environments { name environmentType } } } ``` And press the button \(or press CTRL+ENTER\). If all went well, you should see your first GraphQL response. The Lagoon GraphQL API can not only display objects and create objects, but it also has the capability to update existing objects. All of Lagoon's GraphQL uses best practices. !!! info Mutation queries in GraphQL modify the data in the data store, and return a value. They can be used to insert, update, and delete data. Mutations are defined as a part of the schema._ Update the branches to deploy within a project: ```graphql title="Update deploy branches" mutation editProjectBranches { updateProject(input:{id:109, patch:{branches:"^(prod|stage|dev|update)$"}}) { id } } ``` Update the production environment within a project: !!! Warning This requires a redeploy in order for all changes to be reflected in the containers. ```graphql title="Update production environment" mutation editProjectProductionEnvironment { updateProject(input:{id:109, patch:{productionEnvironment:"prod"}}) { id } } ``` You can also combine multiple changes into a single query: ```graphql title="Multiple changes" mutation editProjectProductionEnvironmentAndBranches { updateProject(input:{id:109, patch:{productionEnvironment:"prod", branches:"^(prod|stage|dev|update)$"}}) { id } } ```
Project: StarRocks (App Definition and Development / Database)
File: st_x.md

displayed_sidebar: "English" If point is of a valid Point type, return the corresponding X-coordinate value. ```Haskell DOUBLE ST_X(POINT point) ``` ```Plain Text MySQL > SELECT STX(STPoint(24.7, 56.7)); +-+ | stx(stpoint(24.7, 56.7)) | +-+ | 24.7 | +-+ ``` ST_X,ST,X