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

title: kbcli addon Addon command. ``` -h, --help help for addon ``` ``` --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 ``` - Describe an addon specification. - Disable an addon. - Enable an addon. - List addons.
Project: Harbor (Provisioning / Container Registry)
File: 3-21-DB-admin-role-user-manage-project-members.md

Test 3-21 - Admin Role User Manages Project Members (DB Mode) ======= To verify that a user with system admin role can add members of various roles to a project. Users are managed locally by Harbor (DB mode). User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against a local database. ( auth_mode is set to db_auth* .) The user data is stored in a local database. A linux host with Docker CLI installed (Docker client). At least three non-admin users are in Harbor. At least one project that admin user is not a member of. NOTE: The below non-admin user M should NOT be the same as the non-admin user in Test 3-11. Assign an non-admin user M with system admin role and act as an admin user. Repeat all steps in Test 3-11. A user with system admin role can perform all operations the same as the admin user. Same as Test 3-11. None
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.70.md

layout: release date: 2021-11-03 tag: v0.5.70 [mesheryctl] minor changes to installation script @hexxdump (#4544) [CI] Golang deps: bump up apiserver version @leecalcote (#4555) [CI] Golang deps: pinning openapi deps @leecalcote (#4554) [CI] Golang deps: pinning openapi deps @leecalcote (#4554) Thank you to our contributors for making this release possible: @hexxdump and @leecalcote
Project: ClickHouse (App Definition and Development / Database)
File: quantiletiming.md

slug: /en/sql-reference/aggregate-functions/reference/quantiletiming sidebar_position: 204 With the determined precision computes the of a numeric data sequence. The result is deterministic (it does not depend on the query processing order). The function is optimized for working with sequences which describe distributions like loading web pages times or backend response times. When using multiple `quantile*` functions with different levels in a query, the internal states are not combined (that is, the query works less efficiently than it could). In this case, use the function. Syntax ``` sql quantileTiming(level)(expr) ``` Alias: `medianTiming`. Arguments `level` Level of quantile. Optional parameter. Constant floating-point number from 0 to 1. We recommend using a `level` value in the range of `. `expr` over a column values returning a -type number. If negative values are passed to the function, the behavior is undefined. If the value is greater than 30,000 (a page loading time of more than 30 seconds), it is assumed to be 30,000. Accuracy The calculation is accurate if: Total number of values does not exceed 5670. Total number of values exceeds 5670, but the page loading time is less than 1024ms. Otherwise, the result of the calculation is rounded to the nearest multiple of 16 ms. :::note For calculating page loading time quantiles, this function is more effective and accurate than . ::: Returned value Quantile of the specified level. Type: `Float32`. :::note If no values are passed to the function (when using `quantileTimingIf`), is returned. The purpose of this is to differentiate these cases from cases that result in zero. See for notes on sorting `NaN` values. ::: Example Input table: ``` text response_time 72 112 126 145 104 242 313 168 108 ``` Query: ``` sql SELECT quantileTiming(response_time) FROM t ``` Result: ``` text quantileTiming(response_time) 126 ``` See Also
Project: SPIRE (Provisioning / Key Management)
File: plugin_agent_svidstore_gcp_secretmanager.md

The `gcp_secretmanager` plugin stores in the resulting X509-SVIDs of the entries that the agent is entitled to. The format that is used to store in a secret the issued identity is the following: ```json { "spiffeId": "spiffe://example.org", "x509Svid": "X509CERTCHAIN_PEM", "x509SvidKey": "PRIVATEKEYPEM", "bundle": "X509BUNDLEPEM", "federatedBundles": { "spiffe://federated.org": "X509FEDERATEDBUNDLE_PEM" } } ``` This plugin requires the following IAM permissions in order to function: ```text secretmanager.secrets.create secretmanager.secrets.delete secretmanager.secrets.get secretmanager.secrets.update secretmanager.versions.add ``` Please note that this plugin does not require permission to read secret payloads stored on secret version. | Configuration | Description | DEFAULT | |-|-|-| | serviceaccountfile | (Optional) Path to the service account file used to authenticate with the Google Compute Engine API. By default credentials are retrieved from environment. | Value of `GOOGLEAPPLICATIONCREDENTIALS` environment variable | A sample configuration: ```hcl SVIDStore "gcp_secretmanager" { plugin_data { serviceaccountfile = "/opt/token" } } ``` It is possible to add an IAM Policy when creating a new secret. This is done using the `role` and `serviceaccount` selectors, which must be configured together. The secret will have the inherited IAM Policy together with the new policy, with a single Binding created. The Binding will use the provided role together with service account as unique member. In case that a role/serviceaccount is not set, the secret will use inherited policies from Secret Manager. ```yaml bindings: members: serviceAccount:test-secret@project-id.iam.gserviceaccount.com role: roles/secretmanager.viewer ``` Selectors are used on `storable` entries to describe metadata that is needed by `gcp_secretmanager` in order to store secrets in Google Cloud Secret manager. In case that a `required` selector is not provided, the plugin will return an error at execution time. | Selector | Example | Required | Description | ||-|-|-| | `gcpsecretmanager:name` | `gcpsecretmanager:secretname:some-name` | x | The secret name where SVID will be stored | | `gcpsecretmanager:projectid` | `gcpsecretmanager:projectid:some-project` | x | The Google Cloud project ID which the plugin will use Secret Manager | | `gcpsecretmanager:role` | `gcpsecretmanager:role:roles/secretmanager.viewer` | - | The Google Cloud role id for IAM policy (serviceaccount required when set) | | `gcpsecretmanager:serviceaccount` | `gcpsecretmanager:serviceaccount:test-secret@test-proj.iam.gserviceaccount.com` | - | The Google Cloud Service account for IAM policy (role required when set) |
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_plugin_s3.UnsupportedS3ProviderError.md

/ / UnsupportedS3ProviderError .UnsupportedS3ProviderError `Error` `UnsupportedS3ProviderError` new UnsupportedS3ProviderError(`message?`) | Name | Type | | : | :- | | `message?` | `string` | Error.constructor node_modules/typescript/lib/lib.es5.d.ts:1028 message: `string` Error.message node_modules/typescript/lib/lib.es5.d.ts:1023 name: `string` Error.name node_modules/typescript/lib/lib.es5.d.ts:1022 `Optional` stack: `string` Error.stack node_modules/typescript/lib/lib.es5.d.ts:1024 `Static` stackTraceLimit: `number` Error.stackTraceLimit node_modules/@types/node/globals.d.ts:142 `Static` captureStackTrace(`targetObject`, `constructorOpt?`): `void` Create .stack property on a target object | Name | Type | | :- | : | | `targetObject` | `Object` | | `constructorOpt?` | `Function` | `void` Error.captureStackTrace node_modules/@types/node/globals.d.ts:133 `Static` `Optional` prepareStackTrace(`err`, `stackTraces`): `any` Optional override for formatting stack traces `see` https://github.com/v8/v8/wiki/Stack%20Trace%20API#customizing-stack-traces | Name | Type | | : | :-- | | `err` | `Error` | | `stackTraces` | `CallSite`[] | `any` Error.prepareStackTrace node_modules/@types/node/globals.d.ts:140
Project: Druid (App Definition and Development / Database)
File: next-steps.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. --> The present version establishes the new IT framework. Work completed to date includes: Restructure the Docker images to use the Druid produced from the Maven build. Use "official" images for dependencies. Restructure the Docker compose files. Create the cluster configuration mechanisms. Convert one "test group" to a sub-module: "high-availability". Create the `pom.xml`, scripts and other knick-knacks needed to tie everything together. Create the initial test without using security settings to aid debugging. However, much work remains: Convert remaining tests. Decide when we need full security. Convert the many certificate setup scripts. Support cluster types other than Docker. The following detail items are open: Disable a test if the `disabled` type is set in the test configuration file. Apply it to disable the HA tests for all but Docker. Handle missing config files: generate a "dummy" that is disabled. When launching a container build or test run from Maven, write environment variables to a `target/env.sh` file so that the user doesn't have to find them manually to run the helper scripts. There is some redundancy in each test group project. Figure out solutions: The `cluster.sh` script Boilerplate in the `pom.xml` file. Move test data from `/resources` to `/shared/data`. Build up the data directory from multiple sources during cluster launch. Sort out which data and spec files are actually used. Remove those which are not used. Sort the files by test-specific and shared across tests by moving them into different directories. The "public" and "integration test" versions of the Docker images have diverged significantly, which makes it harder to "test what we ship." Differences include: Different base image Different ways to set up dependencies. Different paths within the container. Different launch scripts. The test images place Druid in `/usr/local`, the public images in `/opt`. The tests do want to do things beyond what the "public" image does. However, this should not require a fork of the builds. To address this issue: Extend this project to create a base common to the "public" and integration test images. Extend the integration test image to build on top of the public image.
Project: OrientDB (App Definition and Development / Database)
File: README.md

orientdb-lucene =============== Lucene indexes for OrientDB Lucene is a high-performance, full-featured text search engine library written entirely in Java. It is a technology suitable for nearly any application that requires full-text and spatial search, especially cross-platform. For Lucene documentation visit please . This project aims to bring the power of Lucene index into . OrientDB does provide its own index engine for classic indexes like unique, notunique and dictionary. This goal of ths project is not replacing OrientDB internal indexing system, but rather extending it throught Lucene to support Full-Text and Spatial. Two types of indexes are supported: Full text index Spatial Index Jump to the to learn how to use orientdb-lucene!
Project: Beam (App Definition and Development / Streaming & Messaging)
File: runinference-sklearn.md

title: "RunInference with Sklearn" <!-- 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. --> <table> <tr> <td> <a> {{< button-pydoc path="apache_beam.ml.inference" class="RunInference" >}} </a> </td> </tr> </table> The following examples demonstrate how to to create pipelines that use the Beam RunInference API and Sklearn. In this example, we create a pipeline that uses an SKlearn RunInference transform on unkeyed data. {{< highlight language="py" file="sdks/python/apachebeam/examples/snippets/transforms/elementwise/runinferencesklearnunkeyedmodel_handler.py" class="notebook-skip" >}} {{< codesample "sdks/python/apachebeam/examples/snippets/transforms/elementwise/runinferencesklearnunkeyedmodelhandler.py" sklearnunkeyedmodel_handler >}} {{</ highlight >}} {{< paragraph class="notebook-skip" >}} Output: {{< /paragraph >}} {{< highlight class="notebook-skip" >}} {{< codesample "sdks/python/apachebeam/examples/snippets/transforms/elementwise/runinferencetest.py" sklearnunkeyedmodelhandler >}} {{< /highlight >}} In this example, we create a pipeline that uses an SKlearn RunInference transform on keyed data. {{< highlight language="py" file="sdks/python/apachebeam/examples/snippets/transforms/elementwise/runinferencesklearnkeyedmodel_handler.py" class="notebook-skip" >}} {{< codesample "sdks/python/apachebeam/examples/snippets/transforms/elementwise/runinferencesklearnkeyedmodelhandler.py" sklearnkeyedmodel_handler >}} {{</ highlight >}} {{< paragraph class="notebook-skip" >}} Output: {{< /paragraph >}} {{< highlight class="notebook-skip" >}} {{< codesample "sdks/python/apachebeam/examples/snippets/transforms/elementwise/runinferencetest.py" sklearnkeyedmodelhandler >}} {{< /highlight >}}
Project: RBAC Lookup (Provisioning / Security & Compliance)
File: README.md

<div align="center"> <img src="img/logo.svg" height="200" alt="RBAC Lookup" style="padding-bottom: 20px" /> <br> <a href="https://github.com/FairwindsOps/rbac-lookup/releases"> <img src="https://img.shields.io/github/v/release/FairwindsOps/rbac-lookup"> </a> <a href="https://goreportcard.com/report/github.com/FairwindsOps/rbac-lookup"> <img src="https://goreportcard.com/badge/github.com/FairwindsOps/rbac-lookup"> </a> <a href="https://join.slack.com/t/fairwindscommunity/shared_invite/zt-e3c6vj4l-3lIH6dvKqzWII5fSSFDi1g"> <img src="https://img.shields.io/static/v1?label=Slack&message=Join+our+Community&color=4a154b&logo=slack"> </a> </div> RBAC Lookup is a CLI that allows you to easily find Kubernetes roles and cluster roles bound to any user, service account, or group name. Binaries are generated with goreleaser for each release for simple installation. Check out the ``` brew install FairwindsOps/tap/rbac-lookup ``` ``` asdf plugin add rbac-lookup asdf install rbac-lookup latest asdf global rbac-lookup latest ``` While RBAC Lookup helps provide visibility into Kubernetes auth, RBAC Manager helps make auth simpler to manage. This is a Kubernetes operator that enables more concise RBAC configuration that is easier to scale and automate. For more information, see . <!-- Begin boilerplate --> The goal of the Fairwinds Community is to exchange ideas, influence the open source roadmap, and network with fellow Kubernetes users. or to get involved! <a href="https://insights.fairwinds.com/auth/register/"> <img src="https://www.fairwinds.com/hubfs/DocBanners/FairwindsOSSUserGroup740x125v6.png" alt="Love Fairwinds Open Source? Automate Fairwinds Open Source for free with Fairwinds Insights. Click to learn more" /> </a> Enjoying rbac-lookup? Check out some of our other projects: - Audit, enforce, and build policies for Kubernetes resources, including over 20 built-in checks for best practices - Right-size your Kubernetes Deployments by compare your memory and CPU settings against actual usage - Detect Kubernetes resources that have been deprecated or removed in future versions - Check to see if any of your Helm charts have updates available - Simplify the management of RBAC in your Kubernetes clusters Or
Project: ArangoDB (App Definition and Development / Database)
File: boost_result.md

+++ title = "`boostresult<T, E = boost::system::errorcode, NoValuePolicy = policy::default_policy<T, E, void>>`" description = "A type alias to a `basicresult` configured with `boost::system::errorcode` and `policy::default_policy`." +++ A type alias to a {{% api "basicresult<T, E, NoValuePolicy>" %}} configured with `boost::system::errorcode` and `policy::`{{% api "default_policy" %}}. This type alias always references the `boost` edition of things, unlike {{% api "result<T, E = varies, NoValuePolicy = policy::defaultpolicy<T, E, void>>" %}} which references either this alias or {{% api "stdresult<T, E = std::errorcode, NoValuePolicy = policy::defaultpolicy<T, E, void>>" %}}. Namespace: `BOOSTOUTCOMEV2_NAMESPACE` Header: `<boost/outcome/boost_result.hpp>`
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.99.md

layout: release date: 2023-06-28 tag: v0.6.99 [MeshModel] Update relationship schema @MUzairS15 (#7966) Added tabs component to storybook @senali-d (#7860) [Filters] Change filter file download endpoint @MUzairS15 (#7964) [Remote Provider] Support for pagesize and count @abdullah1308 (#7892) Update WASMFilter.json @MUzairS15 (#7959) [MeshModel] Add WASM Filter component @MUzairS15 (#7955) [MeshModel] Add `WASM Filter` as a core component. @MUzairS15 (#7929) Resource endpoints audit @abdullah1308 (#7917) Parsing the relative path correctly @suhail34 (#7951) Resource endpoints audit @abdullah1308 (#7917) Bump relay-compiler from 14.1.0 to 15.0.0 in /ui @dependabot (#7945) Fix dropdown input border color in dark mode @HarshDobariya79 (#7923) Bump @cypress/code-coverage from 3.10.1 to 3.10.7 in /ui @dependabot (#7935) Bump cypress from 12.9.0 to 12.15.0 in /provider-ui @dependabot (#7941) Bump @emotion/server from 11.10.0 to 11.11.0 in /provider-ui @dependabot (#7936) Bump webpack-cli from 5.0.1 to 5.1.4 in /ui @dependabot (#7937) Bump next from 13.3.4 to 13.4.7 in /provider-ui @dependabot (#7938) Bump eslint-plugin-cypress from 2.13.2 to 2.13.3 in /provider-ui @dependabot (#7944) Bump eslint from 8.39.0 to 8.43.0 in /provider-ui @dependabot (#7934) Bump relay-compiler from 14.1.0 to 15.0.0 in /ui @dependabot (#7945) Bump @cypress/code-coverage from 3.10.1 to 3.10.7 in /ui @dependabot (#7935) Bump cypress from 12.9.0 to 12.15.0 in /provider-ui @dependabot (#7941) Updated redocly workflow to update swagger files @abdullah1308 (#7957) Bump @emotion/server from 11.10.0 to 11.11.0 in /provider-ui @dependabot (#7936) Bump webpack-cli from 5.0.1 to 5.1.4 in /ui @dependabot (#7937) Bump github.com/spf13/viper from 1.15.0 to 1.16.0 @dependabot (#7940) Bump next from 13.3.4 to 13.4.7 in /provider-ui @dependabot (#7938) Bump eslint-plugin-cypress from 2.13.2 to 2.13.3 in /provider-ui @dependabot (#7944) Bump golang.org/x/oauth2 from 0.0.0-20221014153046-6fdb5e3db783 to 0.9.0 in /scripts/component_generation @dependabot (#7947) Bump eslint from 8.39.0 to 8.43.0 in /provider-ui @dependabot (#7934) Bump google.golang.org/api from 0.103.0 to 0.128.0 in /scripts/component_generation @dependabot (#7948) Bump github.com/layer5io/meshkit from 0.6.37 to 0.6.46 in /scripts/component_generation @dependabot (#7949) Bump github.com/layer5io/meshkit from 0.6.38 to 0.6.46 in /scripts/component_updation @dependabot (#7946) Change ruby version and Adapter Documentation @Boombag0607 (#7933) Resource endpoints audit @abdullah1308 (#7917) Change ruby version and Adapter Documentation @Boombag0607 (#7933) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Boombag0607, @Chadha93, @HarshDobariya79, @MUzairS15, @abdullah1308, @dependabot, @dependabot[bot], @l5io, @leecalcote, @nebula-aac, @senali-d, @suhail34 and @theBeginner86
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: pipeline-operations.md

You might want to make some changes to an existing pipeline, for example, updating request CPU, or changing the minimal replicas for a vertex. Updating a pipeline is as simple as applying the new pipeline spec to the existing one. But there are some scenarios that you'd better not update the pipeline, instead, you should delete and recreate it. The scenarios include but are not limited to: Topology changes such as adding or removing vertices, or updating the edges between vertices. Updating the for a reduce vertex. Updating the user-defined container image for a vertex, while the new image can not properly handle the unprocessed data in its backlog. To summarize, if there are unprocessed messages in the pipeline, and the new pipeline spec will change the way how the messages are processed, then you should delete and recreate the pipeline. To pause a pipeline, use the command below, it will bring the pipeline to `Paused` status, and terminate all the running vertex pods. ```bash kubectl patch pl my-pipeline --type=merge --patch '{"spec": {"lifecycle": {"desiredPhase": "Paused"}}}' ``` Pausing a pipeline will not cause data loss. It does not clean up the unprocessed data in the pipeline, but just terminates the running pods. When the pipeline is resumed, the pods will be restarted and continue processing the unprocessed data. When pausing a pipeline, it will shutdown the source vertex pods first, and then wait for the other vertices to finish the backlog before terminating them. However, it will not wait forever and will terminate the pods after `pauseGracePeriodSeconds`. This is default set to 30 and can be customized by setting `spec.lifecycle.pauseGracePeriodSeconds`. If there's a vertex in the pipeline, please make sure it uses for storage, otherwise the data will be lost. The command below will bring the pipeline back to `Running` status. ```bash kubectl patch pl my-pipeline --type=merge --patch '{"spec": {"lifecycle": {"desiredPhase": "Running"}}}' ``` When deleting a pipeline, before terminating all the pods, it will try to wait for all the backlog messages that have already been ingested into the pipeline to be processed. However, it will not wait forever, if the backlog is too large, it will terminate the pods after `terminationGracePeriodSeconds`, which defaults to 30, and can be customized by setting `spec.lifecycle.terminationGracePeriodSeconds`.