cwielenb/CNCF-Dataset huggingface dataset:
Project: ShardingSphere (App Definition and Development / Database)
File: mask.en.md

+++ title = "Data Masking" weight = 6 +++ The YAML configuration approach to data masking is highly readable, with the YAML format enabling a quick understanding of dependencies between mask rules. Based on the YAML configuration, ShardingSphere automatically completes the creation of `ShardingSphereDataSource` objects, reducing unnecessary coding efforts for users. ```yaml rules: !MASK tables: <table_name> (+): # Mask table name columns: <column_name> (+): # Mask logic column name maskAlgorithm: # Mask algorithm name maskAlgorithms: <maskalgorithmname> (+): # Mask algorithm name type: # Mask algorithm type props: # Mask algorithm properties ``` Please refer to for more details about type of algorithm. Configure data masking rules in the YAML file, including data sources, mask rules, global attributes, and other configuration items. Using the `createDataSource` of calling the `YamlShardingSphereDataSourceFactory` object to create `ShardingSphereDataSource` based on the configuration information in the YAML file. The data masking YAML configurations are as follows: ```yaml dataSources: unique_ds: dataSourceClassName: com.zaxxer.hikari.HikariDataSource driverClassName: com.mysql.jdbc.Driver jdbcUrl: jdbc:mysql://localhost:3306/demo_ds?serverTimezone=UTC&useSSL=false&useUnicode=true&characterEncoding=UTF-8 username: root password: rules: !MASK tables: t_user: columns: password: maskAlgorithm: md5_mask email: maskAlgorithm: maskbeforespecialcharsmask telephone: maskAlgorithm: keepfirstnlastm_mask maskAlgorithms: md5_mask: type: MD5 maskbeforespecialcharsmask: type: MASKBEFORESPECIAL_CHARS props: special-chars: '@' replace-char: '*' keepfirstnlastm_mask: type: KEEPFIRSTNLASTM props: first-n: 3 last-m: 4 replace-char: '*' ``` Read the YAML configuration to create a data source according to the `createDataSource` method of `YamlShardingSphereDataSourceFactory`. ```java YamlShardingSphereDataSourceFactory.createDataSource(getFile()); ```
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: projects.md

<em>Note: Please follow this guide to install Monokle Desktop </em> Launch Monokle Desktop and, on the welcome screen, there are three options to start working with projects: Select an exisiting folder. Create an empty project. Start from a template. Click Select an existing folder and navigate to an existing project folder containing K8 resources. After a project is opened in Monokle Desktop, the project selector at the top of the screen will denote the project that is being displayed in the IDE. Select the Monokle icon at the tof left of the screen to switch between projects: Easily switch in between projects to more efficiently work with multiple projects at the same time.
Project: ClickHouse (App Definition and Development / Database)
File: mutations.md

slug: /en/operations/system-tables/mutations The table contains information about of tables and their progress. Each mutation command is represented by a single row. `database` () The name of the database to which the mutation was applied. `table` () The name of the table to which the mutation was applied. `mutationid` () The ID of the mutation. For replicated tables these IDs correspond to znode names in the `<tablepathinclickhouse_keeper>/mutations/` directory in ClickHouse Keeper. For non-replicated tables the IDs correspond to file names in the data directory of the table. `command` () The mutation command string (the part of the query after `ALTER TABLE [db.]table`). `create_time` () Date and time when the mutation command was submitted for execution. `blocknumbers.partitionid` (()) For mutations of replicated tables, the array contains the partitions' IDs (one record for each partition). For mutations of non-replicated tables the array is empty. `block_numbers.number` (()) For mutations of replicated tables, the array contains one record for each partition, with the block number that was acquired by the mutation. Only parts that contain blocks with numbers less than this number will be mutated in the partition. In non-replicated tables, block numbers in all partitions form a single sequence. This means that for mutations of non-replicated tables, the column will contain one record with a single block number acquired by the mutation. `partstodo_names` (()) An array of names of data parts that need to be mutated for the mutation to complete. `partstodo` () The number of data parts that need to be mutated for the mutation to complete. `is_done` () The flag whether the mutation is done or not. Possible values: `1` if the mutation is completed, `0` if the mutation is still in process. :::note Even if `partstodo = 0` it is possible that a mutation of a replicated table is not completed yet because of a long-running `INSERT` query, that will create a new data part needed to be mutated. ::: If there were problems with mutating some data parts, the following columns contain additional information: `latestfailedpart` () The name of the most recent part that could not be mutated. `latestfailtime` () The date and time of the most recent part mutation failure. `latestfailreason` () The exception message that caused the most recent part mutation failure. To track the progress on the system.mutations table, use a query like the following - this requires read permissions on the system.* tables: ``` sql SELECT * FROM clusterAllReplicas('cluster_name', 'db', system.mutations) WHERE is_done=0 AND table='tmp'; ``` :::tip replace `tmp` in `table='tmp'` with the name of the table that you are checking mutations on. ::: See Also table engine family
Project: Kraken (Provisioning / Container Registry)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: '' labels: '' 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 [...] 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: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_cluster_diff-config.md

title: kbcli cluster diff-config Show the difference in parameters between the two submitted OpsRequest. ``` kbcli cluster diff-config [flags] ``` ``` kbcli cluster diff-config opsrequest1 opsrequest2 ``` ``` -h, --help help for diff-config ``` ``` --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 ``` - Cluster command.
Project: Meshery (Provisioning / Automation & Configuration)
File: appmesh-controller.md

layout: integration title: AWS App Mesh subtitle: Collaborative and visual infrastructure as code for AWS App Mesh image: /assets/img/integrations/appmesh-controller/icons/color/appmesh-controller-color.svg permalink: extensibility/integrations/appmesh-controller docURL: https://docs.meshery.io/extensibility/integrations/appmesh-controller description: integrations-category: Cloud Native Network integrations-subcategory: Service Mesh registrant: Artifact Hub components: name: backend-group colorIcon: assets/img/integrations/appmesh-controller/components/backend-group/icons/color/backend-group-color.svg whiteIcon: assets/img/integrations/appmesh-controller/components/backend-group/icons/white/backend-group-white.svg description: name: gateway-route colorIcon: assets/img/integrations/appmesh-controller/components/gateway-route/icons/color/gateway-route-color.svg whiteIcon: assets/img/integrations/appmesh-controller/components/gateway-route/icons/white/gateway-route-white.svg description: name: mesh colorIcon: assets/img/integrations/appmesh-controller/components/mesh/icons/color/mesh-color.svg whiteIcon: assets/img/integrations/appmesh-controller/components/mesh/icons/white/mesh-white.svg description: name: virtual-gateway colorIcon: assets/img/integrations/appmesh-controller/components/virtual-gateway/icons/color/virtual-gateway-color.svg whiteIcon: assets/img/integrations/appmesh-controller/components/virtual-gateway/icons/white/virtual-gateway-white.svg description: name: virtual-node colorIcon: assets/img/integrations/appmesh-controller/components/virtual-node/icons/color/virtual-node-color.svg whiteIcon: assets/img/integrations/appmesh-controller/components/virtual-node/icons/white/virtual-node-white.svg description: name: virtual-router colorIcon: assets/img/integrations/appmesh-controller/components/virtual-router/icons/color/virtual-router-color.svg whiteIcon: assets/img/integrations/appmesh-controller/components/virtual-router/icons/white/virtual-router-white.svg description: name: virtual-service colorIcon: assets/img/integrations/appmesh-controller/components/virtual-service/icons/color/virtual-service-color.svg whiteIcon: assets/img/integrations/appmesh-controller/components/virtual-service/icons/white/virtual-service-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: ArangoDB (App Definition and Development / Database)
File: set_spare_storage.md

+++ title = "`void setsparestorage(basicresult|basicoutcome *, uint16_t) noexcept`" description = "Sets the sixteen bits of spare storage in the specified result or outcome." +++ Sets the sixteen bits of spare storage in the specified result or outcome. You can retrieve these bits later using {{% api "uint16t sparestorage(const basicresult|basicoutcome *) noexcept" %}}. Overridable: Not overridable. Requires: Nothing. Namespace: `BOOSTOUTCOMEV2_NAMESPACE::hooks` Header: `<boost/outcome/basic_result.hpp>`
Project: secureCodeBox (Provisioning / Security & Compliance)
File: 2020-10-15-sundown-and-eol-of-version-1.md

title: Sundown and EOL of Version 1 author: Sven Strittmatter author_title: Core Developer author_url: https://github.com/Weltraumschaf authorimageurl: https://www.gravatar.com/avatar/3fe213284598b5cb69009665902c77a1 tags: eol sundown v1 description: Sundown and end of live of secureCodeBox version 1. image: /img/blog/2020-10-15-sundown.jpg (Photo by on ) Sad news but the secureCodeBox version 1 will soon reach its end of life. So here we announce its sundown phase beginning from now on until the end of the year. <!--truncate--> From today we announce the sundown phase of secureCodeBox version 1. This means that we will not implement any new features nor update any dependencies in this version! We will only patch critical security issues or bugs. Of course, you can submit pull requests or ask kindly for a bug fix. We may do it if we have the resources. But don't be annoyed if we won't. If you need urgently a patch you may pay us for doing it. But also don't be annoyed if we decline. We won't put any more effort into the secureCodeBox version 1 as necessary and we want to focus on the work for secureCodeBox version 2. The sundown phase will last until 31. December 2020. After that date, we will archive all the repositories belonging only to version 1 and won't do any updates or accept pull requests for version 1. If you need patches after this date you must pay us or fork the sources and do it by yourself. Is there a migration tool or guide from version 1 to version 2? Short answer: No! Version 1 and version 2 are so different that you can't migrate the installation automatically. It is necessary to knock down your version 1 installation and setup a fresh version 2. It may be possible to migrate the data collected by version 1 in Elastic. But at the moment we do not provide tools to migrate this data. Maybe we will provide such a tool in the future. It depends on the demand. We don't want to put effort into something nobody needs. We dropped our data from version 1 and started from scratch. So you may face a major fuckup now. We understand that such a move is almost always quite a bit annoying. That's why we ask you for sorry and hope we won't lose you as a secureCodeBox user. If you need help moving to secureCodeBox version 2 don't hesitate to ask us for help! You can reach us at , (Channel `#project-securecodebox`), E-Mail (securecodebox [at] iteratec [dot] com) or just file an issue at GitHub. Finally to cheer you up a little cute kitten: (Photo by on )
Project: Datree (Provisioning / Security & Compliance)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: '' labels: enhancement 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 [...] 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: Sonobuoy (Provisioning / Security & Compliance)
File: sonobuoy_images_download.md

Saves downloaded images from local docker client to a tar file ``` sonobuoy images download [flags] ``` ``` --context string Context in the kubeconfig to use. --dry-run If true, only print the image operations that would be performed. --e2e-repo string Specify a registry for KUBETESTREPO, overriding registries for test images. --e2e-repo-config string Specify a yaml file acting as KUBETESTREPO_LIST, overriding registries for test images. -h, --help help for download --kubeconfig Kubeconfig Path to explicit kubeconfig file. --kubernetes-version string Use default E2E image, but override the version. Default is 'auto', which will be set to your cluster's version if detected, erroring otherwise. 'ignore' will try version resolution but ignore errors. 'latest' will find the latest dev image/version upstream. -p, --plugin strings Describe which plugin's images to interact with (Valid plugins are 'e2e', 'systemd-logs'). (default [e2e,systemd-logs]) ``` ``` --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) ``` - Manage images used in a plugin to facilitate running them in airgapped (or similar) environments. Supported plugins are: 'e2e'
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_core.BadgeSpec.md

/ / BadgeSpec .BadgeSpec This is the most complete form of a badge specification, allowing the caller to provide a title, an onclick handler, and an optional fontawesome icon representation. `Optional` css: `string` `Optional` fontawesome: `string` `Optional` image: `HTMLImageElement` \| `SVGElement` title: `string` `Optional` onclick(): `void` `void`
Project: YugabyteDB (App Definition and Development / Database)
File: 05-limit.md

title: "LIMIT" In this exercise we'll query the products table and return just the first 12 rows. ``` SELECT product_id, product_name, unit_price FROM products LIMIT 12; ``` This query should return 12 rows. In this exercise we'll query the products table and skip the first 4 rows before selecting the next 12. ``` SELECT product_id, product_name, unit_price FROM products LIMIT 12 OFFSET 4; ``` This query should return 12 rows. In this exercise we'll query the products table, order the results in a descending order by product\id_ and limit the rows returned to 12. ``` SELECT product_id, product_name, unit_price FROM products ORDER BY product_id DESC LIMIT 12; ``` This query should return 12 rows.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: passert.md

title: "PAssert" <!-- 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. --> See for updates.
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: opensearch.md

is a community-driven, Apache 2.0-licensed open source search and analytics suite that makes it easy to ingest, search, visualize, and analyze data. from 2 - `uselagoon/opensearch-2` Some options are configurable via [environment variables](../concepts-advanced/environment-variables.md). | Environment Variable | Default | Description | | :- | :- | :- | | OPENSEARCHJAVAOPTS | -Xms512m -Xmx512m | Sets the memory usage of the OpenSearch container. Both values need be the same value or OpenSearch will not start cleanly. | On Linux-based systems, the start of the OpenSearch container may fail due to a low `vm.maxmapcount` setting. ```bash title="Error" opensearch_1 | ERROR: [1] bootstrap checks failed opensearch1 | [1]: max virtual memory areas vm.maxmap_count [65530] is too low, increase to at least [262144] ``` .
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: dex.md

Numaflow comes with a Server for authentication integration. Currently, the supported identity provider is Github. SSO configuration of Numaflow UI will require editing some configuration detailed below. In Github, register a new OAuth application. The callback address should be the homepage of your Numaflow UI + `/dex/callback`. After registering this application, you will be given a client ID. You will need this value and also generate a new client secret. First we need to configure `server.disable.auth` to `false` in the ConfigMap `numaflow-cmd-params-config`. This will enable authentication and authorization for the UX server. ```yaml apiVersion: v1 kind: ConfigMap metadata: name: numaflow-cmd-params-config data: server.disable.auth: "false" ``` Next we need to configure the `numaflow-dex-server-config` ConfigMap. Change `<ORG_NAME>` to your organization you created the application under and include the correct teams. This file will be read by the init container of the Dex server and generate the config it will server. ```yaml kind: ConfigMap apiVersion: v1 metadata: name: numaflow-dex-server-config data: config.yaml: | connectors: type: github id: github name: GitHub config: clientID: $GITHUBCLIENTID clientSecret: $GITHUBCLIENTSECRET orgs: name: <ORG_NAME> teams: admin readonly ``` Finally we will need to create/update the `numaflow-dex-secrets` Secret. You will need to add the client ID and secret you created earlier for the application here. ```yaml apiVersion: v1 kind: Secret metadata: name: numaflow-dex-secrets stringData: dex-github-client-id: <GITHUBCLIENTID> dex-github-client-secret: <GITHUBCLIENTSECRET> ``` If you are enabling/disabling authorization and authentication for the Numaflow server, it will need to be restarted. Any changes or additions to the connectors in the `numaflow-dex-server-config` ConfigMap will need to be read and generated again requiring a restart as well.
Project: Ansible (Provisioning / Automation & Configuration)
File: Bug fix.md

<! Describe the change below, including rationale and design decisions --> <! HINT: Include "Fixes #nnn" if you are fixing an existing issue --> Bugfix Pull Request <! Include additional information to help people understand the change here --> <! A step-by-step reproduction of the problem is helpful if there is no related issue --> <! Paste verbatim command output below, e.g. before and after your change --> ```paste below ```