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

+++ title = "google_user resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "google_user" identifier = "inspec/resources/gcp/googleuser.md googleuser resource" parent = "inspec/resources/gcp" +++ Use the `google_user` InSpec audit resource to test properties of a single GCP user. A `google_user` resource block declares the tests for a single GCP user by principal email address or immutable ID. describe googleuser(userkey: 'principalemailaddress@domain.com') do it { should exist } end The following examples show how to use this InSpec audit resource. describe googleuser(userkey: '110491234567894702010') do it { should exist } end describe googleuser(userkey: '110491234567894702010') do its('name.full_name') { should eq "Bill S. Preston Esq." } end describe googleuser(userkey: 'theodoretedlogan@excellentadventure.com') do it { should havemfaenabled } end describe googleuser(userkey: 'theodoretedlogan@excellentadventure.com') do it { shouldnot besuspended } end `agreedtoterms`, `archived`, `changepasswordatnextlogin`, `creationtime`, `customerid`, `emails`, `etag`, `id`, `includeinglobaladdresslist`, `ipwhitelisted`, `isadmin`, `isdelegatedadmin`, `isenforcedin2sv`, `isenrolledin2sv`, `ismailboxsetup`, `kind`, `lastlogintime`, `name`, `noneditablealiases`, `orgunitpath`, `primary_email`, `suspended` Ensure the G Suite Admin SDK is enabled and you have sufficient privileges to list users.
Project: ClickHouse (App Definition and Development / Database)
File: apply-deleted-mask.md

slug: /en/sql-reference/statements/alter/apply-deleted-mask sidebar_position: 46 sidebar_label: APPLY DELETED MASK ``` sql ALTER TABLE [db].name [ON CLUSTER cluster] APPLY DELETED MASK [IN PARTITION partition_id] ``` The command applies mask created by and forcefully removes rows marked as deleted from disk. This command is a heavyweight mutation, and it semantically equals to query ```ALTER TABLE [db].name DELETE WHERE rowexists = 0```. :::note It only works for tables in the family (including tables). ::: See also
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_clusterdefinition_list.md

title: kbcli clusterdefinition list List ClusterDefinitions. ``` kbcli clusterdefinition list [flags] ``` ``` kbcli clusterdefinition list ``` ``` -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 ``` - ClusterDefinition command.
Project: Meshery (Provisioning / Automation & Configuration)
File: awx-operator.md

layout: integration title: AWX Operator subtitle: Collaborative and visual infrastructure as code for AWX Operator image: /assets/img/integrations/awx-operator/icons/color/awx-operator-color.svg permalink: extensibility/integrations/awx-operator docURL: https://docs.meshery.io/extensibility/integrations/awx-operator description: integrations-category: Orchestration & Management integrations-subcategory: Automation & Configuration registrant: Artifact Hub components: name: awx-backup colorIcon: assets/img/integrations/awx-operator/components/awx-backup/icons/color/awx-backup-color.svg whiteIcon: assets/img/integrations/awx-operator/components/awx-backup/icons/white/awx-backup-white.svg description: name: awx-restore colorIcon: assets/img/integrations/awx-operator/components/awx-restore/icons/color/awx-restore-color.svg whiteIcon: assets/img/integrations/awx-operator/components/awx-restore/icons/white/awx-restore-white.svg description: name: awx colorIcon: assets/img/integrations/awx-operator/components/awx/icons/color/awx-color.svg whiteIcon: assets/img/integrations/awx-operator/components/awx/icons/white/awx-white.svg description: name: awx-mesh-ingress colorIcon: assets/img/integrations/awx-operator/components/awx-mesh-ingress/icons/color/awx-mesh-ingress-color.svg whiteIcon: assets/img/integrations/awx-operator/components/awx-mesh-ingress/icons/white/awx-mesh-ingress-white.svg description: featureList: [ "Keep revision history and audit trail of all configuration changes", "Use MeshMap&lsquo;s visual designer to explore your App Mesh configuration", "Deploy Meshery on your EKS clusters for App Mesh management" ] 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: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: rego-cheat-sheet.md

title: Rego Cheat Sheet subtitle: Quick reference for learning Rego labels: category: learning inventors: styra code: https://github.com/StyraInc/rego-cheat-sheet tutorials: https://docs.styra.com/opa/rego-cheat-sheet docs_features: learning-rego: note: | The was designed as a language reference, featuring common contact points, with Rego learners in mind. The has been designed to be a reference for Rego learners and users documenting the common contact points with the language. There is also a for those looking for a printable reference.
Project: ShardingSphere (App Definition and Development / Database)
File: drop-sharding-algorithm.en.md

+++ title = "DROP SHARDING ALGORITHM" weight = 11 +++ The `DROP SHARDING ALGORITHM` syntax is used to drop sharding algorithm for specified database. {{< tabs >}} {{% tab name="Grammar" %}} ```sql DropShardingAlgorithm ::= 'DROP' 'SHARDING' 'ALGORITHM' algorithmName ifExists? ('FROM' databaseName)? ifExists ::= 'IF' 'EXISTS' algorithmName ::= identifier databaseName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} When `databaseName` is not specified, the default is the currently used `DATABASE`. If `DATABASE` is not used, `No database selected` will be prompted; `ifExists` clause used for avoid `Sharding algorithm not exists` error. Drop sharding algorithm for specified database ```sql DROP SHARDING ALGORITHM torderhashmod FROM shardingdb; ``` Drop sharding algorithm for current database ```sql DROP SHARDING ALGORITHM torderhash_mod; ``` Drop sharding algorithm with `ifExists` clause ```sql DROP SHARDING ALGORITHM IF EXISTS torderhash_mod; ``` `DROP`, `SHARDING`, `ALGORITHM`, `FROM`
Project: Pulumi (Provisioning / Automation & Configuration)
File: overview.md

Broadly speaking, Pulumi is composed of five components: These components interact to provide the feature set exposed by the Pulumi CLI and SDKs, including desired-state deployments using standard programming languages, remote state storage and secret encryption, and the ability to bridge the gap between existing and Pulumi-managed infrastructure. These components are composed like so: In most cases, the language plugin, CLI, and resource providers will all live in separate processes, and each instance of a resource provider will live in its own process.
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: common-options.md

Common parameters of source connectors | name | type | required | default value | |-|--|-|| | resulttablename | string | no | - | | sourcetablename | string | no | - | When `sourcetablename` is not specified, the current plug-in processes the data set `(dataset)` output by the previous plug-in in the configuration file; When `sourcetablename` is specified, the current plugin is processing the data set corresponding to this parameter. When `resulttablename` is not specified, the data processed by this plugin will not be registered as a data set that can be directly accessed by other plugins, or called a temporary table `(table)`; When `resulttablename` is specified, the data processed by this plugin will be registered as a data set `(dataset)` that can be directly accessed by other plugins, or called a temporary table `(table)` . The dataset registered here can be directly accessed by other plugins by specifying `sourcetablename` .
Project: KICS (Provisioning / Security & Compliance)
File: c62746cf-92d5-4649-9acf-7d48d086f2ee.md

title: Storage Account Not Using Latest TLS Encryption Version hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: c62746cf-92d5-4649-9acf-7d48d086f2ee Query name: Storage Account Not Using Latest TLS Encryption Version Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: Ensure Storage Account is using the latest version of TLS encryption<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="8 12" name: Create an account with kind of FileStorage azurermstorageaccount: resource_group: myResourceGroup name: c1h0002 type: Premium_LRS kind: FileStorage minimumtlsversion: TLS1_0 tags: testing: testing name: Create a second account with kind of FileStorage azurermstorageaccount: resource_group: myResourceGroup name: clh0003 type: Premium_LRS kind: FileStorage ``` ```yaml title="Negative test num. 1 - yaml file" name: Create an account with kind of FileStorage azurermstorageaccount: resource_group: myResourceGroup name: c1h0002 type: Premium_LRS kind: FileStorage minimumtlsversion: TLS1_2 tags: testing: testing ```
Project: YugabyteDB (App Definition and Development / Database)
File: include-security-settings.md

<!-- +++ private = true +++ --> In addition to the volume encryption that YugabyteDB Managed uses to encrypt your data, you can enable YugabyteDB (EAR) for clusters. When enabled, your YugabyteDB cluster (including backups) is encrypted using a customer managed key (CMK) residing in a cloud provider Key Management Service (KMS). <!--You can also enable EAR for a cluster after the cluster is created.--> To use a CMK to encrypt your cluster, make sure you have configured the CMK in AWS KMS, Azure Key Vault, or Google Cloud KMS. Refer to . To use a CMK, select the Enable cluster encryption at rest option and set the following options: KMS provider: AWS, Azure, or GCP. For AWS: Customer managed key (CMK): Enter the Amazon Resource Name (ARN) of the CMK to use to encrypt the cluster. Access key: Provide an access key of an with permissions for the CMK. An access key consists of an access key ID and the secret access key. For Azure: The Azure , the vault URI (for example, `https://myvault.vault.azure.net`), and the name of the key. The client ID and secret for an application with permission to encrypt and decrypt using the CMK. For GCP: Resource ID: Enter the resource ID of the key ring where the CMK is stored. Service Account Credentials: Click Add Key to select the credentials JSON file you downloaded when creating credentials for the service account that has permissions to encrypt and decrypt using the CMK.
Project: Akri (Provisioning / Automation & Configuration)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: '' labels: feature assignees: '' Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Is your feature request related to a way you would like Akri extended? Please describe. A clear and concise description of what cool feature Akri lacks. Ex. I'd love Akri to support discovery of Bluetooth devices. Describe the solution you'd like A clear and concise description of what you want to happen. Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. Additional context Add any other context or screenshots about the feature request here.
Project: YugabyteDB (App Definition and Development / Database)
File: hexists.md

title: HEXISTS linkTitle: HEXISTS description: HEXISTS menu: preview: parent: api-yedis weight: 2110 aliases: /preview/api/redis/hexists /preview/api/yedis/hexists type: docs `HEXISTS key field This is a predicate to check whether or not the given `field` exists in the hash that is specified by the given `key`. If the given `key` and `field` exist, 1 is returned. If the given `key` or `field` does not exist, 0 is returned. If the given `key` is associated with non-hash data, an error is raised. Returns existence status as integer, either 1 or 0. ```sh $ HSET yugahash area1 "America" ``` ``` 1 ``` ```sh $ HEXISTS yugahash area1 ``` ``` 1 ``` ```sh $ HEXISTS yugahash area_none ``` ``` 0 ``` , , , , , , , , , ,
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-context-delete.md

layout: default title: mesheryctl-system-context-delete permalink: reference/mesheryctl/system/context/delete redirect_from: reference/mesheryctl/system/context/delete/ type: reference display-title: "false" language: en command: system subcommand: context Delete context Delete an existing context (a named Meshery deployment) from Meshery config file <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system context delete [context-name] [flags] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system context delete [context name] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for delete -s, --set string New context to deploy Meshery </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -c, --context string (optional) temporarily change the current context. -v, --verbose verbose output -y, --yes (optional) assume yes for user interactive prompts. </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: FOSSA (Provisioning / Security & Compliance)
File: conda.md

While originally created for Python programs, Conda can package and distribute software for any language. It provides a full list of all dependencies installed in the environment, without providing a dependency graph. A conda project is discovered if the project directory contains an `environment.yml` file. Run `conda env create --json --file environment.yml --dry-run --force` to get a complete list of packages that would be installed by `conda env create -f environment.yml`. Using the `--dry-run` option means that `fossa-cli` does not actually modify any local environments. This process can take some time since `conda` may need to refresh its package data in order to run the command. In our tests we have seen it take up to 3 minutes, for very large conda environments it could be longer. If the `conda list --json` operation does not succeed, we fall back to parsing the `environment.yml`, and getting the list of dependencies from the `dependencies` section of this file.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.11.10.md

RabbitMQ `3.11.10` is a maintenance release in the `3.11.x` . Please refer to the upgrade section from if upgrading from a version prior to 3.11.0. This release requires Erlang 25. has more details on Erlang version requirements for RabbitMQ. As of 3.11.0, RabbitMQ requires Erlang 25. Nodes will fail to start on older Erlang releases. Erlang 25 as our new baseline means much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation available to all RabbitMQ 3.11 users. Release notes can be found on GitHub at . Tag changes could result in a loop of internal events in certain plugins. GitHub issue: Key classic mirrored queue (a deprecated feature) settings now can be overridden with operator policies. Contributed by @SimonUnge (AWS). GitHub issue: Individual virtual host page failed to render. GitHub issue: Individual exchange page failed to render. GitHub issue: The plugin now supports authentication with JWT tokens (the OAuth 2 authentication backend). GitHub issues: , The `authoauth2.preferredusername_claims` key in `rabbitmq.conf` now accepts a list of values. GitHub issue: `ra` was upgraded To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.10.tar.xz` instead of the source tarball produced by GitHub.
Project: OpenYurt (Provisioning / Automation & Configuration)
File: 20220526-install-openyurt-components-using-helm.md

title: Install openyurt components using helm authors: "@cndoit18" "@zhangzhenyuyu" reviewers: "@rambohe-ch" "@huiwq1990" creation-date: 2022-05-26 last-updated: 2022-05-26 status: provisional - - - - - Refer to the . In order to deploy and use OpenYurt, OpenYurt provides users with 5 deployment methods. From a beginner's point of view, there are too many installation methods, which can easily confuse end users. Maybe we need to reduce some installation methods, and we need to define specific scenarios for each installation method. In order to simplify the installation process, in this proposal, we would like to provide a way of helm installation. We will write OpenYurt's chart package, which can enable OpenYurt to support installation using helm, and use the OpenYurt-helm repository to manage the chart package. In addition, we will design Github-action to synchronize the released chart package with the gh-pages branch. The entire release process is fully automated and requires no human intervention. In order to deploy and use OpenYurt, OpenYurt provides users with a total of 5 deployment methods. There are too many installation methods, which can easily confuse users. In addition, using OpenYurt may often have to copy yaml files between different projects, which is cumbersome. This proposal seeks to address the above issues. Provide the chart package of openyurt and openyurt components, and provide the way of helm installation. Automate the chart package publishing process without manual intervention. As a developer of edge computing, I want to install openyurt-related components when deploying a k8s cluster for rapid development and testing. As an end user, I would like to try out the features of OpenYurt. Which components need to organize the chart package: yurt-controller-manager yurt-app-manager yurt-tunnel-server/agent yurt-edgex-manager yurt-dashboard Take the openyurt repo as an example: Add a new chart package to the openyurt repository, and write the related chart package implementation. Introduce openyurt-helm as an aggregate repo (existing), which references the chart package path just now. Provide support for helm repo in openyurt-helm, and add a reusable pipeline. When triggered, scan the path of the corresponding component to generate the corresponding chart package, and synchronize the released chart package to the gh-pages branch. Optional: In the release process of each component, add a pipeline, and the pipeline of openyurt-helm will be called during release.
Project: Trivy (Provisioning / Security & Compliance)
File: kubernetes.md

When scanning a Kubernetes cluster, Trivy differentiates between the following: Cluster infrastructure (e.g api-server, kubelet, addons) Cluster configuration (e.g Roles, ClusterRoles). Application workloads (e.g nginx, postgresql). Whenever Trivy scans either of these Kubernetes resources, the container image is scanned separately to the Kubernetes resource definition (the YAML manifest) that defines the resource. When scanning any of the above, the container image is scanned separately to the Kubernetes resource definition (the YAML manifest) that defines the resource. Container image is scanned for: Vulnerabilities Misconfigurations Exposed secrets Kubernetes resource definition is scanned for: Vulnerabilities - partially supported through Misconfigurations Exposed secrets To learn more, please see the .
Project: ThreatMapper (Provisioning / Security & Compliance)
File: scanning-tags.md

title: Vulnerability Scanning using Tags Users can tag individual nodes and run vulnerability scans on a subset of nodes using these user-defined tags as explained below. Users can go to table view and click on the User Defined Tags column to tag a node as shown in the following picture. It is possible to assign multiple tags to a node. While running vulnerability scans, users can select user defined tags to run the scan on a subset of nodes corresponding to the selected tags as shown in the following picture.
Project: StarRocks (App Definition and Development / Database)
File: hll_raw_agg.md

displayed_sidebar: "English" This function is an aggregate function that is used to aggregate HLL fields. It returns an HLL value. ```Haskell hllrawagg(hll) ``` `hll`: the HLL column that is generated by other columns or based on the loaded data. Returns a value of the HLL type. ```Plain mysql> select k1, hllcardinality(hllraw_agg(v1)) from tbl group by k1; ++-+ | k1 | hllcardinality(hllraw_agg(`v1`)) | ++-+ | 2 | 4 | | 1 | 3 | ++-+ ```