cwielenb/CNCF-Dataset huggingface dataset:
Project: YugabyteDB (App Definition and Development / Database)
File: ysql_hba_conf-configuration.md

title: Configure client authentication in YSQL headerTitle: Configure client authentication in YSQL linkTitle: Configure client authentication description: Use the ysqlhbaconf_csv flag to configure client authentication in YSQL. menu: v2.18: identifier: ysqlhbaconf-configuration parent: enable-authentication weight: 730 type: docs <ul class="nav nav-tabs-alt nav-tabs-yb"> <li > <a href="../ysqlhbaconf-configuration/" class="nav-link active"> <i class="icon-postgres" aria-hidden="true"></i> YSQL </a> </li> </ul> YugabyteDB client authentication for YSQL is managed by the YB-TServer configuration flag, which works similarly to the file in PostgreSQL. The values include records that specify allowed connection types, users, client IP addresses, and the authentication method. Records in the YugabyteDB `ysqlhba.conf` file are auto generated based on the values included in the `--ysqlhbaconfcsv` flag. For example, starting a YB-TServer with the following `--ysqlhbaconf_csv` flag enables trust authentication for all users: ```sh --ysqlhbaconf_csv='host all all 0.0.0.0/0 trust, host all all ::0/0 trust' ``` To display the current values in the `ysql_hba.conf` file, run the following `SHOW` statement to get the file location: ```sql yugabyte=# SHOW hba_file; ``` ```output hba_file /Users/yugabyte/yugabyte-data/node-1/disk-1/pgdata/ysqlhba.conf (1 row) ``` and then view the file. Here is an example of `ysql_hba.conf` file contents. ```output host all all 0.0.0.0/0 trust host all all ::0/0 trust ``` For more information, refer to .
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.6.15.md

RabbitMQ 3.6.15 is a maintenance release. See the ["Upgrading clusters" section of the documentation](https://www.rabbitmq.com/upgrade.html) for general documentation on upgrades. This release has no known incompatibilities with versions 3.6.7 through 3.6.14. See the upgrade and compatibility sections in the [3.6.7 release notes](https://github.com/rabbitmq/rabbitmq-server/releases/tag/rabbitmqv36_7) if upgrading from an earlier release. Please read this node on [RabbitMQ 3.6.x series support timeline](https://groups.google.com/forum/#!msg/rabbitmq-users/kXkI-f3pgEw/UFowJIK4BQAJ). Avoid infinite loop when dropping entries in the GM. GitHub issue: Various changes to the OCF scripts. GitHub issues: , , will now prohibit logins with a blank passwords. Such attempts are usually made by mistake because a passwordless user that was meant to authenticate using was not configured to use the correct [authentication mechanism](https://www.rabbitmq.com/authentication.html). Note that the same behavior can already be achieved using a , so this is just an extra safety measure. GitHub issue: Multi-input forms (such as message properties) again submit all fields. GitHub issues: User update form now successfully updates tags for passwordless users (or if the password is cleared at the same time). GitHub issue: `Content-Type` header was returned twice in API responses. GitHub issue: Avoid duplicated event handlers in the UI. GitHub issue: Use `auto` width to make option values fully visible. GitHub issue: Concurrently registering consumers could fail with a "Key exists" exception in the log. GitHub issue: Disabling policy (or plugin) now cleans up all internal exchanges and queues used by federation links. GitHub issue: Standalone MacOS package now ships with Erlang/OTP 20.1 which is compatible with High Sierra. GitHub issue: Make adm the group owner for RabbitMQ log directories. GitHub issue: `https/web-mqtt` listener displayed incorrect port in management UI. GitHub issue: Fix node and row selectors after jQuery upgrade to 1.12. GitHub issue: Enable hostname verification for OTP 19. GitHub issue: To upgrade a non-clustered RabbitMQ simply install the new version. All configuration and persistent message data are retained. When upgrading using definitions export/import from versions earlier than 3.6.0, see http://rabbitmq.com/passwords.html. To upgrade a RabbitMQ cluster, follow the instructions [in RabbitMQ documentation](https://www.rabbitmq.com/clustering.html#upgrading). Warning: The source code archive provided by GitHub only contains the source of the broker, not the plugins or the client libraries. Please download the archive named `rabbitmq-server-3.6.15.tar.xz`.
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-context-create.md

layout: default title: mesheryctl-system-context-create permalink: reference/mesheryctl/system/context/create redirect_from: reference/mesheryctl/system/context/create/ type: reference display-title: "false" language: en command: system subcommand: context Create a new context (a named Meshery deployment) Add a new context to Meshery config.yaml file <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system context create context-name [flags] </div> </pre> Create new context <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system context create [context-name] </div> </pre> Create new context and provide list of components, platform & URL <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system context create context-name --components meshery-nsm --platform docker --url http://localhost:9081 --set --yes </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -a, --components stringArray List of components -h, --help help for create -p, --platform string Platform to deploy Meshery --provider string Provider to use with the Meshery server -s, --set Set as current context -u, --url string Meshery Server URL with Port </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> Usage of mesheryctl context create Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: KICS (Provisioning / Security & Compliance)
File: integrations_pre_commit.md

To use `kics` with add the following hook to your local repo's `.pre-commit-config.yaml` file. ```yaml repo: https://github.com/Checkmarx/kics rev: "" # change to correct tag or sha hooks: id: kics-scan ``` You can provide arguments to `kics` by providing the pre-commit `args` . The following example will print the `kics scan` output, but will not block regardless of success/failure. ```yaml repos: repo: https://github.com/Checkmarx/kics rev: "" # change to correct tag or sha hooks: id: kics-scan verbose: true args: [--ignore-on-exit, "all"] ``` You can create your own local pre-commit hook using the language. This is a more lightweight way to configure `kics` as a pre-commit hook. ```yaml repos: repo: local hooks: id: kics-scan-local name: Kics scan language: docker_image entry: checkmarx/kics scan -p /src --no-progress verbose: true ```
Project: Vald (App Definition and Development / Database)
File: CODE_OF_CONDUCT.md

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at i.can.feel.gravity@gmail.com. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. This Code of Conduct is adapted from the , version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq
Project: KICS (Provisioning / Security & Compliance)
File: 74a18d1a-cf02-4a31-8791-ed0967ad7fdc.md

title: Cognito UserPool Without MFA hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 74a18d1a-cf02-4a31-8791-ed0967ad7fdc Query name: Cognito UserPool Without MFA Platform: CloudFormation Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: AWS Cognito UserPool should have MFA (Multi-Factor Authentication) defined to users<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="8 14" Resources: UserPool2: Type: "AWS::Cognito::UserPool" Properties: UserPoolName: !Sub ${AuthName}-user-pool AutoVerifiedAttributes: phone_number MfaConfiguration: "OFF" SmsConfiguration: ExternalId: !Sub ${AuthName}-external SnsCallerArn: !GetAtt SNSRole.Arn UserPool4: Type: "AWS::Cognito::UserPool" Properties: UserPoolName: !Sub ${AuthName}-user-pool AutoVerifiedAttributes: phone_number SmsConfiguration: ExternalId: !Sub ${AuthName}-external SnsCallerArn: !GetAtt SNSRole.Arn ``` ```json title="Positive test num. 2 - json file" hl_lines="10 19" { "Resources": { "UserPool2": { "Type": "AWS::Cognito::UserPool", "Properties": { "UserPoolName": "${AuthName}-user-pool", "AutoVerifiedAttributes": [ "phone_number" ], "MfaConfiguration": "OFF", "SmsConfiguration": { "ExternalId": "${AuthName}-external", "SnsCallerArn": "SNSRole.Arn" } } }, "UserPool4": { "Type": "AWS::Cognito::UserPool", "Properties": { "SmsConfiguration": { "ExternalId": "${AuthName}-external", "SnsCallerArn": "SNSRole.Arn" }, "UserPoolName": "${AuthName}-user-pool", "AutoVerifiedAttributes": [ "phone_number" ] } } } } ``` ```yaml title="Negative test num. 1 - yaml file" Resources: UserPool: Type: "AWS::Cognito::UserPool" Properties: UserPoolName: !Sub ${AuthName}-user-pool AutoVerifiedAttributes: phone_number MfaConfiguration: "ON" SmsConfiguration: ExternalId: !Sub ${AuthName}-external SnsCallerArn: !GetAtt SNSRole.Arn UserPool2: Type: "AWS::Cognito::UserPool" Properties: UserPoolName: !Sub ${AuthName}-user-pool AutoVerifiedAttributes: phone_number MfaConfiguration: "OPTIONAL" SmsConfiguration: ExternalId: !Sub ${AuthName}-external SnsCallerArn: !GetAtt SNSRole.Arn ``` ```json title="Negative test num. 2 - json file" { "Resources": { "UserPool": { "Type": "AWS::Cognito::UserPool", "Properties": { "UserPoolName": "${AuthName}-user-pool", "AutoVerifiedAttributes": [ "phone_number" ], "MfaConfiguration": "ON", "SmsConfiguration": { "ExternalId": "${AuthName}-external", "SnsCallerArn": "SNSRole.Arn" } } }, "UserPool2": { "Type": "AWS::Cognito::UserPool", "Properties": { "UserPoolName": "${AuthName}-user-pool", "AutoVerifiedAttributes": [ "phone_number" ], "MfaConfiguration": "OPTIONAL", "SmsConfiguration": { "ExternalId": "${AuthName}-external", "SnsCallerArn": "SNSRole.Arn" } } } } } ```
Project: secureCodeBox (Provisioning / Security & Compliance)
File: 04_solution_strategy.md

title: "Solution Strategy" sidebar_label: "Solution Strategy" sidebar_position: 4 This chapter describes the main technical concepts used as solution strategy to implement secureCodeBox. First lets narrow down the core responsibility of secureCodeBox. The whole system's responsibility is: to orchestrate various security scanners, and process and persist the findings from these scanner's results. In version 1 we achieved this with an own application based on a business process engine. More about this topic and its drawbacks are described in the blog post . Due to these drawbacks we and make an own implementation for this aspect of the system obsolete. More details about this decision is described in the previously linked ADR. The move to as implementation of our orchestration has the consequence that we do not have the SQL persistence available as in typical Java based application stacks. So, we . More details about this decision is described in the previously linked ADR.
Project: StarRocks (App Definition and Development / Database)
File: unnest_bitmap.md

displayed_sidebar: "English" unnest_bitmap is a table function that takes a bitmap and converts elements in that bitmap into multiple rows of a table. StarRocks' can be used in conjunction with the unnest_bitmap function to implement common column-to-row logic. This function can be used to replace `unnest(bitmaptoarray(bitmap))`. It has better performance, takes up less memory resources, and is not limited by the length of the array. This function is supported from v3.1. ```Haskell unnest_bitmap(bitmap) ``` `bitmap`: the bitmap you want to convert. Returns multiple rows converted from the bitmap. The type of return value is BIGINT. `c2` is a bitmap column in table `t1`. ```SQL -- Use the bitmaptostring function to convert values in the c2 column into a string. mysql> select c1, bitmaptostring(c2) from t1; ++-+ | c1 | bitmaptostring(c2) | ++-+ | 1 | 1,2,3,4,5,6,7,8,9,10 | ++-+ -- Use the unnest_bitmap function to expand the bitmap column into multiple rows. mysql> select c1, unnestbitmap from t1, unnestbitmap(c2); +++ | c1 | unnest_bitmap | +++ | 1 | 1 | | 1 | 2 | | 1 | 3 | | 1 | 4 | | 1 | 5 | | 1 | 6 | | 1 | 7 | | 1 | 8 | | 1 | 9 | | 1 | 10 | +++ ```
Project: YugabyteDB (App Definition and Development / Database)
File: row-to-json.md

title: rowtojson() headerTitle: rowtojson() linkTitle: rowtojson() description: Create a JSON object from a SQL record. menu: v2.18: identifier: row-to-json parent: json-functions-operators weight: 270 type: docs Purpose: Create a JSON object from a SQL record. Signature: ``` input value: record pretty: boolean (optional) return value: json ``` Notes: This has only the `json` variant. The first (mandatory) formal parameter is any SQL `record` whose fields might be compound values. The second formal parameter is optional. When it is true, line feeds are added between fields. Use this `ysqlsh` script to create the required type "t" and then to execute the `ASSERT`. ```plpgsql create type t as (a int, b text); do $body$ declare row constant t := (42, 'dog'); jfalse constant json := rowto_json(row, false); jtrue constant json := rowto_json(row, true); expectedjfalse constant json := '{"a":42,"b":"dog"}'; expectedjtrue constant json := '{"a":42, "b":"dog"}'; begin assert (jfalse::text = expectedj_false::text) and (jtrue::text = expectedj_true::text), 'unexpected'; end; $body$; ``` The `rowtojson()` function has no practical advantage over or and is restricted because it explicitly handles a SQL `record` and cannot handle a SQL array (at top level). If you want to pretty-print the text representation of the JSON value result, you can use the `::text` typecast or .
Project: StarRocks (App Definition and Development / Database)
File: bitmap_intersect.md

displayed_sidebar: "English" Aggregation function, used to calculate the bitmap intersection after grouping. Common usage scenarios, such as calculating user retention rate. ```Haskell BITMAP BITMAP_INTERSECT(BITMAP value) ``` Enter a set of bitmap values, find the intersection of this set of bitmap values, and return the result. Table structure ```yml KeysType: AGG_KEY Columns: tag varchar, date datetime, userid bitmap bitmapunion ``` ```SQL -- Calculate users retention under different tags today and yesterday. select tag, bitmapintersect(userid) from ( select tag, date, bitmapunion(userid) user_id from table where date in ('2020-05-18', '2020-05-19') group by tag, date) a group by tag; ``` Use with bitmaptostring function to obtain the specific data of the intersection. ```SQL --Find out users retained under different tags today and yesterday. select tag, bitmaptostring(bitmapintersect(userid)) from ( select tag, date, bitmapunion(userid) user_id from table where date in ('2020-05-18', '2020-05-19') group by tag, date) a group by tag; ``` BITMAP_INTERSECT, BITMAP
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_plugin_client_common.TextWithIconWidgetProps.md

/ / TextWithIconWidgetProps .TextWithIconWidgetProps Component-specific Options `TextWithIconWidgetProps` `Optional` className: `string` . `Optional` iconIsNarrow: `boolean` `Optional` iconOnclick: `string` \| () => `void` `Optional` id: `string` `Optional` popover: `Pick`<`Props`, `"headerContent"` \| `"bodyContent"`\> & `Partial`<`Props`\> popover properties specified by client `Optional` position: `"bottom"` \| `"top-end"` \| `"top"` \| `"top-start"` \| `"left"` \| `"right"` \| `"auto"` popover position override specified by container (not client)? . text: `string` `Optional` textOnclick: `string` \| () => `void` `Optional` title: `string` viewLevel:
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: hotkeys.md

Monokle Desktop currently supports the following keyboard shortcuts: Connect to Cluster: Ctrl/Cmd I Settings: Ctrl/Cmd , (Comma) Exit Preview: ESC Browse Folder: Ctrl/Cmd O Refresh Folder: Ctrl/Cmd F5 Toggle Left Pane: Ctrl/Cmd B Toggle Right Pane: Ctrl/Cmd ALT B Save (in editors): Ctrl/Cmd S Navigate Back (Selection History): ALT ArrowLeft Navigate Forward (Selection History): ALT ArrowRight Open New Resource Wizard: Ctrl/Cmd N Apply Resource or File to cluster: Ctrl/Cmd ALT S Diff Resource: Ctrl/Cmd ALT D Open File Explorer Tab: Ctrl/Cmd Shift E Open Cluster Tab: Ctrl/Cmd Shift C Open Kustomization Tab: Ctrl/Cmd Shift K Open Helm Tab: Ctrl/Cmd Shift H Open Validation Tab: Ctrl/Cmd Shift V Open Terminal Pane: Ctrl/Cmd ` (Backtick) Reset Resource Filters: Ctrl/Cmd ALT R Open Quick Search: Ctrl/Cmd SHIFT P Zoom In: Ctrl/Cmd = Zoom Out: Ctrl/Cmd - Open Shortcuts: Ctrl/Cmd / Reload Preview: Ctrl/Cmd R Scale Deployment: Ctrl/Cmd Shift S
Project: TiDB (App Definition and Development / Database)
File: CONTRIBUTING.md

This document outlines some of the conventions on development workflow, commit message formatting, contact points and other resources to make it easier to get your contribution accepted. Fork the repository on GitHub. Read the README.md for build instructions. Play with the project, submit bugs, submit patches! Developing BR requires: An internet connection to download the dependencies Navigate to the tidb directory ```sh cd ../tidb ``` run `make build_br` to build the program. ```sh make build_br ``` After all these, you will find `br` in `tidb/bin` directory This project contains unit tests and integration tests with coverage collection. See for how to execute and add tests. BR uses to manage dependencies. To add or update a dependency: use the `go mod edit` command to change the dependency. This is a rough outline of what a contributor's workflow looks like: Create a topic branch from where you want to base your work. This is usually `master`. Make commits of logical units and add test case if the change fixes a bug or adds new functionality. Run tests and make sure all the tests are passed. Make sure your commit messages are in the proper format (see below). Push your changes to a topic branch in your fork of the repository. Submit a pull request. Your PR must receive LGTMs from two maintainers. Thanks for your contributions! The coding style suggested by the Golang community is used in BR. See the for details. Please follow this style to make BR easy to review, maintain and develop. We follow a rough convention for commit messages that is designed to answer two questions: what changed and why. The subject line should feature the what and the body of the commit should describe the why. ``` restore: add comment for variable declaration Improve documentation. ``` The format can be described more formally as follows: ``` <subsystem>: <what changed> <BLANK LINE> <why this change was made> <BLANK LINE> <footer>(optional) ``` The first line is the subject and should be no longer than 70 characters, the second line is always blank, and other lines should be wrapped at 80 characters. This allows the message to be easier to read on GitHub as well as in various git tools. If the change affects more than one subsystem, you can use comma to separate them like `backup,restore:`. If the change affects many subsystems, you can use `````` instead, like ```:```. For the why part, if no specific reason for the change, you can use one of some generic reasons like "Improve documentation.", "Improve performance.", "Improve robustness.", "Improve test coverage."