cwielenb/CNCF-Dataset huggingface dataset:
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: operator-sdk_run.md

title: "operator-sdk run" Run an Operator in a variety of environments This command has subcommands that will deploy your Operator with OLM. ``` -h, --help help for run ``` ``` --plugins strings plugin keys to be used for this subcommand execution --verbose Enable verbose logging ``` - - Deploy an Operator in the bundle format with OLM - Upgrade an Operator previously installed in the bundle format with OLM
Project: Apollo (Provisioning / Automation & Configuration)
File: team.md

The Apollo team is comprised of Members and Contributors. Members have direct access to the source of Apollo project and actively evolve the code-base. Contributors improve the project through submission of patches and suggestions to the Members. The number of Contributors to the project is unbounded. All contributions to Apollo are greatly appreciated, whether for trivial cleanups, big new features or other material rewards. For more information about the community governance model, please refer . Members include Project Management Committee members and committers. The list is in alphabet order. | GitHub ID | Name | Organization | | - | - | | | Anilople | Xiaoquan Wang | Some Bank | | JaredTan95 | Jared Tan | DaoCloud | | kezhenxu94 | Zhenxu Ke | Tetrate | | klboke | Kailing Chen | TapTap | | lepdou | Le Zhang | Tencent | | nobodyiam | Jason Song | Ant Group | | zouyx | Joe Zou | Shein | | GitHub ID | Name | Organization | | -- | - | | | Accelerater | Zhuohao Li | Daocloud | | Anilople | Xiaoquan Wang | Some Bank | | JaredTan95 | Jared Tan | DaoCloud | | kezhenxu94 | Zhenxu Ke | Tetrate | | klboke | Kailing Chen | TapTap | | lepdou | Le Zhang | Tencent | | nisiyong | Stephen Ni | Qihoo 360 | | nobodyiam | Jason Song | Ant Group | | pengweiqhca | Wei Peng | Tuhu | | Shoothzj | ZhangJian He | Huawei | | vdisk-group | Lvqiu Ye | Hundsun | | zouyx | Joe Zou | Shein | <img src="https://opencollective.com/apollo/contributors.svg?width=880&button=false" /> <img src="https://opencollective.com/apollonet/contributors.svg?width=880&button=false" /> Please refer .
Project: Siddhi (App Definition and Development / Streaming & Messaging)
File: README.md

Siddhi Core Libraries ===================== ](https://wso2.org/jenkins/view/wso2-dependencies/job/siddhi/job/siddhi) ](https://github.com/siddhi-io/siddhi/releases) ](https://github.com/siddhi-io/siddhi/releases) ](https://github.com/siddhi-io/siddhi/commits/master) ](https://github.com/siddhi-io/siddhi/commits/master) ](https://codecov.io/gh/siddhi-io/siddhi) ](https://bestpractices.coreinfrastructure.org/projects/2974) ](https://opensource.org/licenses/Apache-2.0) <a target="blank" href="https://siddhi.io/">Siddhi</a> is a cloud native **Streaming** and **Complex Event Processing_ engine that understands Streaming SQL queries in order to capture events from diverse data sources, process them, detect complex conditions, and publish output to various endpoints in real time. Siddhi Core Libraries contains the essential core libraries need for Siddhi execution such as , , , and . Siddhi can run as an embedded Java and Python library, as a micro service on bare metal, VM, and Docker and natively in Kubernetes. Siddhi provides web-based graphical and textual tooling for development. For information on <a target="blank" href="https://siddhi.io/">Siddhi</a> and it's features refer <a target="blank" href="https://siddhi.io/redirect/docs.html">Siddhi Documentation</a>. Download Siddhi Core Libraries; Versions 5.x and above with group id `io.siddhi.` from <a target="_blank" href="https://mvnrepository.com/artifact/io.siddhi/">here</a>. Versions 4.x and lower with group id `org.wso2.siddhi.` from <a target="_blank" href="https://mvnrepository.com/artifact/org.wso2.siddhi/">here</a>. Download Siddhi tooling and runtime distributions <a target="_blank" href="https://siddhi.io/redirect/download.html">here</a>. Get started with Siddhi in a few minutes by following the <a target="_blank" href="https://siddhi.io/redirect/quick-start.html">Siddhi Quick Start Guide</a>. For more information on using Siddhi refer <a target="_blank" href="https://siddhi.io/redirect/docs.html">Siddhi Documentation</a>. Latest API Docs is <a target="_blank" href="https://siddhi-io.github.io/siddhi/api/5.1.30">5.1.30</a>. You can reachout through Slack channel, Google mail group and etc. Please refer the community contribution for more information.
Project: RBAC Manager (Provisioning / Security & Compliance)
File: guide.md

Issues, whether bugs, tasks, or feature requests are essential for keeping rbac-manager great. We believe it should be as easy as possible to contribute changes that get things working in your environment. There are a few guidelines that we need contributors to follow so that we can keep on top of things. This project adheres to a . Please review this document before contributing to this project. Before you can contribute, you will need to sign the . rbac-manager is a relatively simple cobra cli tool that looks up information about rbac in a cluster. The folder contains the flags and other cobra config. We label issues with the if we believe they'll be a good starting point for new contributors. If you're interested in working on an issue, please start a conversation on that issue, and we can help answer any questions as they come up. A properly configured Golang environment with Go 1.11 or higher Access to a cluster via a properly configured KUBECONFIG Install the project with `go get github.com/fairwindsops/rbac-manager` Change into the rbac-manager directory which is installed at `$GOPATH/src/github.com/fairwindsops/rbac-manager` Run tests with `make test` If you've encountered an issue that is not already reported, please create an issue that contains the following: Clear description of the issue Steps to reproduce it Appropriate labels Each new pull request should: Reference any related issues Add tests that show the issues have been solved Pass existing tests and linting Contain a clear indication of if they're ready for review or a work in progress Be up to date and/or rebased on the master branch Push a new annotated tag. This tag should contain a changelog of pertinent changes. Currently github releases are manual; go into the UI and create a release with the changelog as the text. In the future, it would be nice to implement Goreleaser.
Project: OpenYurt (Provisioning / Automation & Configuration)
File: question.md

name: Question about: Question about OpenYurt. title: "[Question]" labels: kind/question <!-- Please use this template to ask question. Thanks!--> What happened: What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: OpenYurt version: Kubernetes version (use `kubectl version`): OS (e.g: `cat /etc/os-release`): Kernel (e.g. `uname -a`): Install tools: Others: others /kind question
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_class_list.md

title: kbcli class list List classes ``` kbcli class list [flags] ``` ``` kbcli class list --cluster-definition apecloud-mysql ``` ``` --cluster-definition string Specify cluster definition, run "kbcli clusterdefinition list" to show all available cluster definition -h, --help help for list ``` ``` --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 ``` - Manage classes
Project: ArangoDB (App Definition and Development / Database)
File: set_has_error_is_errno.md

+++ title = "`static void sethas_exception(Impl &&, bool) noexcept`" description = "Sets whether the implementation's error code has a domain or category matching that of POSIX `errno`. Constexpr, never throws." categories = ["modifiers"] weight = 340 +++ Sets whether the implementation's error code has a domain or category matching that of POSIX `errno` by setting or clearing the relevant bit in the flags. Constexpr where possible. Requires: Always available. Complexity: Constant time. Guarantees: Never throws an exception.
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-ddl-declare-variable.md

layout: global title: DECLARE VARIABLE displayTitle: DECLARE VARIABLE 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. The `DECLARE VARIABLE` statement is used to create a temporary variable in Spark. Temporary variables are scoped at a session level. You can reference variables by their name everywhere constant expressions are allowed. Unless you qualify a variable with `session` or `system.session`, a variable is only resolved after Spark fails to resolve a name to a column or column alias. Temporary variables cannot be referenced in persisted objects such as persisted view, column default expressions, and generated column expressions. ```sql DECLARE [ OR REPLACE ] [ VARIABLE ] variablename [ datatype ] [ { DEFAULT | = } default_expr ] ``` OR REPLACE* If specified, a pre-existing temporary variable is replaced if it exists. variable_name* Specifies a name for the variable to be created. The variable name may be optionally qualified with a `system`.`session` or `session`. Syntax: `[ system . [ session .] ] variable_name` data_type* Optionally defines the data type of the variable. If it is not specified the type is derived from the default expression. default_expr* An optional expression used to initialize the value of the variable after declaration. The expression is re-evaluated whenever the variable is reset to `DEFAULT` using . If `datatype` is specified `defaultexpr` must be castable to the variable type. If `data_type` is not specified you must specify a default and its type will become the type of the variable. If no default expression is given, the variable is initialized with `NULL`. ```sql -- The dense form of declaring a variable with default DECLARE five = 5; -- STRING variable initialialized to `NULL` DECLARE some_var STRING; ```
Project: ThreatMapper (Provisioning / Security & Compliance)
File: automating-scans.md

title: Automating Scans Vulnerabilities may be introduced into your production platforms at any point. And change to application dependencies of infrastructure may introduce new vulnerabilities. Changes in the application topology, such as promoting a service from internal dev traffic to external Internet traffic, can change ThreatMapper's risk-of-exploit score for a vulnerability. Most significantly, new vulnerabilities can be discovered in existing components at any time. A component that passed all vulnerability scans when it was deployed may still contain issues that are discovered weeks, months or years afterwards. ThreatMapper can scan your production platforms periodically, using the most up-to-date threat feeds at each time. This enables ThreatMapper to catch changes in application components and topology, and to find recently-disclosed vulnerabilities in components that are already deployed. The results of automated scans are added to the Vulnerability Scans report, and can be raised through any configured method. ThreatMapper presents a series of APIs that you can use to enumerate nodes and run scans: ThreatMapper can be invoked during the build process for a workload, commonly referred to as CI (Continuous Integration). For more information, check out the (Scanning in the CI Pipeline)[Scan-CI] documentation. ThreatMapper can scan registries, looking for vulnerabilities in containers. Scans can be invoked manually, or can run periodically against the registry. For more information, check out the (Scanning Registries)[Scanning Registries] documentation. Schedule is set by default in ThreatMapper to scan all containers and hosts once a week. They can be enabled if needed. A good example for API-driven automation - you can create a script that enumerates your infrastructure and workloads, and then scans on-demand. You can use ThreatMapper to scan new nodes as they are added to the infrastructure, and can prevent these nodes from becoming active if they fail the scan: Instance is started by elastic platform e.g. AWS Instance contains ThreatMapper agent as a component When instance starts, agent self-registers with management console. Management console notices a new instance has been added and schedules a scan (using streaming API - details to be documented) Once the scan has completed, if it is deemed to have failed (admin defines pass or fail criteria), the management console can delete the new node (using preconfigured credentials)
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: CHANGES.md

Bump fsnotify to v1.6.0. Should fix some issues. Bump fsnotify to v1.5.1 fixes issue #28, hpcloud/tail#90. PR #27: "Add timeout to tests"by @kokes++. Also timeout on FreeBSD. PR #29: "Use temp directory for tests, instead of relative" by @ches++. Documentation updates. Small linter cleanups. Added example in test. Document the usage of Cleanup when re-reading a file (thanks to @lesovsky) for issue #18. Add example directories with example and tests for issues. Fix of checksum problem because of forced tag. No changes to the code. Incorporated PR 162 by by Mohammed902: "Simplify non-Windows build tag". Incorporated PR 9 by mschneider82: "Added seekinfo to Tail". Incorporated PR 7: "Fix deadlock when stopping on non-empty file/buffer", fixes upstream issue 93. Incorporated changes of unmerged upstream PR 149 by mezzi: "added line num to Line struct". Incorporated changes of unmerged upstream PR 128 by jadekler: "Compile-able code in readme". Incorporated changes of unmerged upstream PR 130 by fgeller: "small change to comment wording". Incorporated changes of unmerged upstream PR 133 by sm3142: "removed spurious newlines from log messages". Incorporated changes of unmerged upstream PR 126 by Code-Hex: "Solved the problem for never return the last line if it's not followed by a newline". Incorporated changes of unmerged upstream PR 131 by StoicPerlman: "Remove deprecated os.SEEK consts". The changes bumped the minimal supported Go release to 1.9. migration to go modules. release of master branch of the dormant upstream, because it contains fixes and improvement no present in the tagged release.
Project: YugabyteDB (App Definition and Development / Database)
File: rbac-model-ycql.md

title: Role-based access control (RBAC) model in YCQL linkTitle: Overview headerTitle: Role-based access overview description: Overview of the role-based access control (RBAC) model in YCQL. headcontent: How role-based access control works menu: v2.18: identifier: rbac-model-ycql parent: authorization weight: 716 type: docs <ul class="nav nav-tabs-alt nav-tabs-yb"> <li > <a href="../rbac-model/" class="nav-link"> <i class="icon-postgres" aria-hidden="true"></i> YSQL </a> </li> <li > <a href="../rbac-model-ycql/" class="nav-link active"> <i class="icon-cassandra" aria-hidden="true"></i> YCQL </a> </li> </ul> The role-based access control (RBAC) model in YCQL is a collection of permissions on resources given to roles. Thus, the entire RBAC model is built around roles, resources, and permissions. It is essential to understand these concepts in order to understand the RBAC model. Roles in YCQL can represent individual users or a group of users. They encapsulate a set of permissions that can be assigned to other roles (or users). Roles are essential to implementing and administering access control on a YugabyteDB cluster. Below are some important points about roles: Roles which have login permission are users. Hence, all users are roles but all roles are not users. Roles can be granted to other roles, making it possible to organize roles into a hierarchy. Roles inherit the permissions of all other roles granted to them. YCQL defines a number of specific resources, that represent underlying database objects. A resource can denote one object or a collection of objects. YCQL resources are hierarchical as described below: Keyspaces and tables follow the hierarchy: `ALL KEYSPACES` > `KEYSPACE` > `TABLE` ROLES are hierarchical (they can be assigned to other roles). They follow the hierarchy: `ALL ROLES` > `ROLE #1` > `ROLE #2` ... The table below lists out the various resources. Resource | Description | -|-| `KEYSPACE` | Denotes one keyspace. Typically includes all the tables and indexes defined in that keyspace. | `TABLE` | Denotes one table. Includes all the indexes defined on that table. | `ROLE` | Denotes one role. | `ALL KEYSPACES` | Collection of all keyspaces in the database. | `ALL ROLES` | Collection of all roles in the database. | Permissions are necessary to execute operations on database objects. Permissions can be granted at any level of the database hierarchy and are inherited downwards. The set of permissions include: Permission | Objects | Operations | ||-| `ALTER` | keyspace, table, role | ALTER | `AUTHORIZE` | keyspace, table, role | GRANT PERMISSION, REVOKE PERMISSION | `CREATE` | keyspace, table, role, index | CREATE | `DROP` | keyspace, table, role, index | DROP | `MODIFY` | keyspace, table | INSERT, UPDATE, DELETE, TRUNCATE | `SELECT` | keyspace, table | SELECT | `DESCRIBE` (not implemented) | role | LIST ROLES | {{< note title="Note" >}} The `ALTER` permission on the base table is required in order to CREATE or DROP indexes on it. {{< /note >}} Read more about .
Project: StarRocks (App Definition and Development / Database)
File: CREATE_INDEX.md

displayed_sidebar: "English" This statement is used to create indexes. You can use this statement to create oly Bitmap indexes. For usage notes and scenarios of Bitmap indexes, see . :::tip This operation requires the ALTER privilege on the target table. You can follow the instructions in to grant this privilege. ::: ```sql CREATE INDEX indexname ON tablename (column [, ...],) [USING BITMAP] [COMMENT 'balabala'] ``` Note: For the naming conventions of indexes, see . One column can have only one BITMAP index. If a column already has an index, you cannot create one more index on it. Create bitmap index for `siteid` on `table1`. ```sql CREATE INDEX index_name ON table1 (siteid) USING BITMAP COMMENT 'balabala'; ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.163.md

layout: release date: 2023-10-24 tag: v0.6.163 Add new component text-box @aabidsofi19 (#9167) [bug] fetch namespace GraphQL Query @theBeginner86 (#9144) [mesheryctl] fixed meshery start command bug with adapter components @zakisk (#9160) mesheryctl mesh tests @Philip-21 (#9063) [Meshery Performance] fixed one small bug @captain-Akshay (#9163) [UI] Converted MesheryPerformanceComponent from class-based to functional component @captain-Akshay (#9075) [UI] Dashboard workload chart @aabidsofi19 (#9159) [UI] Disable credential in settings @Yashsharma1911 (#9152) [docs/bug] Update index.md @theBeginner86 (#9164) [Docs] discuss integration reinstatement @leecalcote (#9174) Component genrator @Jougan-0 (#9153) Component generator @Jougan-0 (#9151) Standaridization of gke installation docs @aboobakersiddiqr63 (#9177) Minor typo and format changes in Supported docs @aboobakersiddiqr63 (#9176) [Docs] discuss integration reinstatement @leecalcote (#9174) [Docs] Mesheryctl page: Eliminate cycical redirection / flicker @leecalcote (#9171) Updated aks.md and added helm.md @aboobakersiddiqr63 (#9141) Updated minikube.md @aboobakersiddiqr63 (#9140) [Docs]: Add section describing the use of children and grandchildren @coder12git (#9168) [chore] Support for Visibility in Content APIs | CU-85ztrgw1z @theBeginner86 (#9157) [docs/bug] Update index.md @theBeginner86 (#9164) [DOCS] added sending events section in docs @zakisk (#9064) Fix Meshery Docs search @coder12git (#9148) [WIP] Add docs for connection states @MUzairS15 (#9065) [Docs] Restructure, Menu and TOC massage @leecalcote (#9147) [MeshSync] Expose MeshSync Discovered Resources @theBeginner86 (#9143) Added contents in FAQ.md. @Zubiii333 (#9126) [Docs] Rewrite of Quick Start Guide @leecalcote (#9139) Thank you to our contributors for making this release possible: @Jougan-0, @MUzairS15, @Philip-21, @Yashsharma1911, @Zubiii333, @aabidsofi19, @aboobakersiddiqr63, @captain-Akshay, @coder12git, @l5io, @leecalcote, @theBeginner86, @zakisk and l5io