cwielenb/CNCF-Dataset huggingface dataset:
Project: Apache StreamPipes (App Definition and Development / Streaming & Messaging)
File: expected.documentation.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. ~ --> <p align="center"> <img src="icon.png" width="150px;"/> </p> Numerical Filter Description Add a detailed description here Describe the configuration parameters here
Project: ClickHouse (App Definition and Development / Database)
File: quantile.md

slug: /en/sql-reference/aggregate-functions/reference/quantile sidebar_position: 200 Computes an approximate of a numeric data sequence. This function applies with a reservoir size up to 8192 and a random number generator for sampling. The result is non-deterministic. To get an exact quantile, use the function. 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. Note that for an empty numeric sequence, `quantile` will return NaN, but its `quantile*` variants will return either NaN or a default value for the sequence type, depending on the variant. Syntax ``` sql quantile(level)(expr) ``` Alias: `median`. 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` Expression over the column values resulting in numeric , or . Returned value Approximate quantile of the specified level. Type: for numeric data type input. if input values have the `Date` type. if input values have the `DateTime` type. Example Input table: ``` text val 1 1 2 3 ``` Query: ``` sql SELECT quantile(val) FROM t ``` Result: ``` text quantile(val) 1.5 ``` See Also
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_exec_redis.md

title: Kubectl-Dba Exec Redis menu: docs_{{ .version }}: identifier: kubectl-dba-exec-redis name: Kubectl-Dba Exec Redis parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Execute SQL commands to a redis resource Use this cmd to execute redis commands to a redis object's primary pod. Examples: kubectl dba exec rd rd-demo -n demo -f demo.lua kubectl dba exec rd rd-demo -n demo -f demo.lua -k "key1" -a "arg1" kubectl dba exec rd rd-demo -c 'set x y' ``` kubectl-dba exec redis [flags] ``` ``` -a, --argv stringArray args to pass to the lua script, used in script as ARGV[*] and the flag can be specified multiple times with different args. -c, --command string single command to execute -f, --file string path to lua script file -h, --help help for redis -k, --keys stringArray keys to pass to the lua script, used in script as KEYS[*] and the flag can be specified multiple times with different keys. ``` ``` --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/runner/.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 --default-seccomp-profile-type string Default seccomp profile --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 --password string Password for basic authentication to the API server --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 --username string Username for basic authentication to the API server ``` - Execute script or command to a database.
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_list_profiles.md

title: "Command - devspace list profiles" sidebar_label: devspace list profiles Lists all DevSpace profiles ``` devspace list profiles [flags] ``` ``` Lists all DevSpace configurations for this project ``` ``` -h, --help help for profiles ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --disable-profile-activation If true will ignore all profile activations --inactivity-timeout int Minutes the current user is inactive (no mouse or keyboard interaction) until DevSpace will exit automatically. 0 to disable. Only supported on windows and mac operating systems (default 180) --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile strings The DevSpace profiles to apply. Multiple profiles are applied in the order they are specified --profile-parent strings One or more profiles that should be applied before the specified profile (e.g. devspace dev --profile-parent=base1 --profile-parent=base2 --profile=my-profile) --profile-refresh If true will pull and re-download profile parent sources --restore-vars If true will restore the variables from kubernetes before loading the config --save-vars If true will save the variables to kubernetes after loading the config --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context DEPRECATED: Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) --vars-secret string The secret to restore/save the variables from/to, if --restore-vars or --save-vars is enabled (default "devspace-vars") ```
Project: OpenYurt (Provisioning / Automation & Configuration)
File: RELEASE-PROCESS.md

The release process of a new version of OpenYurt involves the following: (Currently only the are eligible to release a new version) Look at in the releases page: For example, at the time of writing, it was v1.2.1 The next version will thus be v1.3.0 Add a new section in for the new version that is being released along with the new features, patches and deprecations it introduces. It should not include every single change but solely what matters to our customers, for example issue template that has changed is not important. Publish documentation for new version on . Fork , create a version from current using `yarn run docusaurus docs:version <VERSION>`. Creating a new release in the will trigger a GitHub workflow which will create a new image with the latest code and tagged with the next version (in this example v1.2.0). Every release should use the template provided below to create the GitHub release. Here's the template: ``` Thank you to everyone who contributed to this release! ``` Before we can release our new Helm chart version, we need to prepare it: Create a new chart version with the updated version and appVersion in . Update the CRDs & Kubernetes resources based on the release artifact (YAML) As per our , we need to create a new shipping cycle in our project settings with a target date in 2 to 3 months after the last cycle. Lastly, a new should be created to maintain the changes of next release. Announce the new release in Slack channel, DingTalk and WeChat groups.
Project: ClickHouse (App Definition and Development / Database)
File: metric_log.md

slug: /en/operations/system-tables/metric_log Contains history of metrics values from tables `system.metrics` and `system.events`, periodically flushed to disk. Columns: `hostname` () Hostname of the server executing the query. `event_date` () Event date. `event_time` () Event time. `eventtimemicroseconds` () Event time with microseconds resolution. Example ``` sql SELECT * FROM system.metric_log LIMIT 1 FORMAT Vertical; ``` ``` text Row 1: hostname: clickhouse.eu-central1.internal event_date: 2020-09-05 event_time: 2020-09-05 16:22:33 eventtimemicroseconds: 2020-09-05 16:22:33.196807 milliseconds: 196 ProfileEvent_Query: 0 ProfileEvent_SelectQuery: 0 ProfileEvent_InsertQuery: 0 ProfileEvent_FailedQuery: 0 ProfileEvent_FailedSelectQuery: 0 ... ... CurrentMetric_Revision: 54439 CurrentMetric_VersionInteger: 20009001 CurrentMetric_RWLockWaitingReaders: 0 CurrentMetric_RWLockWaitingWriters: 0 CurrentMetric_RWLockActiveReaders: 0 CurrentMetric_RWLockActiveWriters: 0 CurrentMetric_GlobalThread: 74 CurrentMetric_GlobalThreadActive: 26 CurrentMetric_LocalThread: 0 CurrentMetric_LocalThreadActive: 0 CurrentMetric_DistributedFilesToInsert: 0 ``` See also Enabling and disabling the setting. Contains periodically calculated metrics. Contains a number of events that occurred. Contains instantly calculated metrics. Base concepts of ClickHouse monitoring.
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: iptables.md

title: IPTables labels: layer: network category: linux software: linux tutorials: https://github.com/open-policy-agent/contrib/blob/master/opa-iptables/docs/tutorial.md code: https://github.com/open-policy-agent/contrib/tree/master/opa-iptables inventors: gsoc cisco styra IPTables is a useful tool available to Linux kernel for filtering network packets. OPA makes it possible to manage IPTables rules using context-aware policy.
Project: ClickHouse (App Definition and Development / Database)
File: v21.11.7.9-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Quota limit was not reached, but the limit was exceeded. This PR fixes . (). Backported in : Fix failures in queries that are trying to use skipping indices, which are not materialized yet. Fixes and . (). Backported in : Fix crash in `JoinCommon::removeColumnNullability`, close . (). Backported in : Fix surprisingly bad code in function `file`. (). Backported in : Fix possible crash (or incorrect result) in case of `LowCardinality` arguments of window function. Fixes . (). Fix arraySlice with null args. (). Fix crash in case of MATERIALIZE COLUMN with no default expression. (). Fix queries with hasColumnInTable constant condition and non existing column ().
Project: KICS (Provisioning / Security & Compliance)
File: a187ac47-8163-42ce-8a63-c115236be6fb.md

title: Azure Container Registry With No Locks hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: a187ac47-8163-42ce-8a63-c115236be6fb Query name: Azure Container Registry With No Locks Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Insecure Configurations URL: Azurerm Container Registry should contain associated locks, which means 'azurermmanagementlock.scope' should be associated with 'azurermcontainerregistry'<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "azurermcontainerregistry" "acr" { name = "containerRegistry1" resourcegroupname = azurermresourcegroup.rg.name location = azurermresourcegroup.rg.location sku = "Standard" admin_enabled = false } resource "azurermmanagementlock" "public-ip" { name = "resource-ip" scope = azurermcontainerregistry.acr1.id lock_level = "CanNotDelete" notes = "Locked because it's needed by a third-party" } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermcontainerregistry" "acr" { name = "containerRegistry1" resourcegroupname = azurermresourcegroup.rg.name location = azurermresourcegroup.rg.location sku = "Standard" admin_enabled = false } resource "azurermmanagementlock" "public-ip" { name = "resource-ip" scope = azurermcontainerregistry.acr.id lock_level = "CanNotDelete" notes = "Locked because it's needed by a third-party" } ```
Project: YugabyteDB (App Definition and Development / Database)
File: yba_storage-config_s3_update.md

Update an S3 YugabyteDB Anywhere storage configuration Update an S3 storage configuration in YugabyteDB Anywhere ``` yba storage-config s3 update [flags] ``` ``` --update-credentials [Optional] Update credentials of the storage configuration. (default false) If set to true, provide either (access-key-id,secret-access-key) pair or set use-iam-instance-profile. --access-key-id string S3 Access Key ID. Required for non IAM role based storage configurations. Can also be set using environment variable AWSACCESSKEY_ID. --secret-access-key string S3 Secret Access Key. Required for non IAM role based storage configurations. Can also be set using environment variable AWSSECRETACCESS_KEY. --new-name string [Optional] Update name of the storage configuration. --use-iam-instance-profile [Optional] Use IAM Role from the YugabyteDB Anywhere Host. Configuration creation will fail on insufficient permissions on the host. (default false) -h, --help help for update ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -n, --name string [Optional] The name of the storage configuration for the operation. Required for create, delete, describe, update. -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage a YugabyteDB Anywhere S3 storage configuration
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: v1.12.0.md

id: v1.12.0 title: v1.12.0 description: Backstage Release v1.12.0 These are the release notes for the v1.12.0 release of . A huge thanks to the whole team of maintainers and contributors as well as the amazing Backstage Community for the hard work in getting this release developed and done. This release mostly contains a bunch of smaller additions and bug fixes, but on top of that, theres also some quality of life improvements and features as listed below. Enjoy! As a convenience, it is now possible to define your action inputs and outputs as `zod` schemas. This tends to be more convenient than writing JSON schema by hand, and gives you instant type feedback in your editor. Added by in The catalog has a new backend endpoint and corresponding client method, for fetching entities with proper cursor based pagination and server side filtering and ordering. This will be used to target performance hot-spots in the frontend and elsewhere. Added by in As we settle the new backend system bit by bit, we have renamed a number of exports from individual plugins, to match the new . If you are already leveraging the new backend system, you may find that you need to update some imports. For example, `githubEntityProviderCatalogModule` was renamed to `catalogModuleGithubEntityProvider`. These were considered non-breaking since they are still in alpha. More details can be found in and . Added a `catalogModulePuppetDbEntityProvider` alpha export for the new backend system. Contributed by in deployment plugin. Contributed by in Integration with . Contributed by in This release does not contain any security fixes. We recommend that you keep your Backstage project up to date with this latest release. For more guidance on how to upgrade, check out the documentation for . Below you can find a list of links and references to help you learn about and start using this new release. , , and Backstage's for discussions and support Backstage , , and Sign up for our if you want to be informed about what is happening in the world of Backstage.
Project: SPIRE (Provisioning / Key Management)
File: plugin_server_notifier_gcs_bundle.md

The `gcs_bundle` plugin responds to bundle loaded/updated events by fetching and pushing the latest root CA certificates from the trust bundle to an object in Google Cloud Storage. The certificates in the object can be used to bootstrap SPIRE agents. The plugin accepts the following configuration options: | Configuration | Description | Default | ||-|| | `bucket` | The bucket containing the object | | | `object_path` | The path to the object within the bucket | | | `serviceaccountfile` | Path to the service account credentials file | | The plugin authenticates with Google Cloud Storage using the mechanisms described in the Google Cloud . Specifically, service account credentials are obtained using a file path configured via `serviceaccountfile`, or the plugin uses Application Default Credentials available in the environment the SPIRE server is running in. The following configuration uploads bundle contents to the `spire-bundle.pem` object in the `my-bucket` bucket. The bundle is uploaded using Application Default Credentials available in the environment SPIRE server is running in. ```hcl Notifier "gcs_bundle" { plugin_data { bucket = "my-bucket" object_path = "spire-bundle.pem" } } ``` The following configuration uploads bundle contents to the `spire-bundle.pem` object in the `my-bucket` bucket. The bundle is uploaded using Service Account credentials found in the `/path/to/service/account/file` file. ```hcl Notifier "gcs_bundle" { plugin_data { bucket = "my-bucket" object_path = "spire-bundle.pem" serviceaccountfile = "/path/to/service/account/file" } } ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_sourcerepo_repositories.md

+++ title = "googlesourcereporepositories resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlesourcereporepositories" identifier = "inspec/resources/gcp/googlesourcereporepositories.md googlesourcereporepositories resource" parent = "inspec/resources/gcp" +++ A `googlesourcereporepositories` is used to test a Google Repository resource ```ruby repo_name = 'inspec-gcp-repository' describe.one do googlesourcereporepositories(project: 'chef-gcp-inspec').names.each do |name| describe name do it { should match /\/repos\/#{repo_name}$/ } end end end ``` Properties that can be accessed from the `googlesourcereporepositories` resource: See the resource for more information. `names` : an array of `googlesourcereporepository` name `urls` : an array of `googlesourcereporepository` url `sizes` : an array of `googlesourcereporepository` size `pubsub_configs` : an array of `googlesourcereporepository` pubsub_configs 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: Meshery (Provisioning / Automation & Configuration)
File: devfile.md

layout: integration title: Devfile subtitle: Collaborative and visual infrastructure as code for Devfile image: /assets/img/integrations/devfile/icons/color/devfile-color.svg permalink: extensibility/integrations/devfile docURL: https://docs.meshery.io/extensibility/integrations/devfile description: integrations-category: App Definition and Development integrations-subcategory: Application Definition & Image Build registrant: Artifact Hub components: featureList: [ "Development environments are quick to create, can be thrown away at will, and can be easily re-created when needed.", "Mechanism for teams to share configurations across projects, and provide a single source of truth throughout the application lifecycle.", "Central location management so updates can be applied once and be properly aligned across development teams." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: Meshery (Provisioning / Automation & Configuration)
File: pulsar-operator.md

layout: integration title: Pulsar Operator subtitle: Collaborative and visual infrastructure as code for Pulsar Operator image: /assets/img/integrations/pulsar-operator/icons/color/pulsar-operator-color.svg permalink: extensibility/integrations/pulsar-operator docURL: https://docs.meshery.io/extensibility/integrations/pulsar-operator description: integrations-category: App Definition and Development integrations-subcategory: Streaming & Messaging registrant: Artifact Hub components: name: book-keeper-cluster colorIcon: assets/img/integrations/pulsar-operator/components/book-keeper-cluster/icons/color/book-keeper-cluster-color.svg whiteIcon: assets/img/integrations/pulsar-operator/components/book-keeper-cluster/icons/white/book-keeper-cluster-white.svg description: name: pulsar-broker colorIcon: assets/img/integrations/pulsar-operator/components/pulsar-broker/icons/color/pulsar-broker-color.svg whiteIcon: assets/img/integrations/pulsar-operator/components/pulsar-broker/icons/white/pulsar-broker-white.svg description: name: pulsar-proxy colorIcon: assets/img/integrations/pulsar-operator/components/pulsar-proxy/icons/color/pulsar-proxy-color.svg whiteIcon: assets/img/integrations/pulsar-operator/components/pulsar-proxy/icons/white/pulsar-proxy-white.svg description: name: zoo-keeper-cluster colorIcon: assets/img/integrations/pulsar-operator/components/zoo-keeper-cluster/icons/color/zoo-keeper-cluster-color.svg whiteIcon: assets/img/integrations/pulsar-operator/components/zoo-keeper-cluster/icons/white/zoo-keeper-cluster-white.svg description: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations