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

+++ title = "azurermkeyvaults resource" draft = false gh_repo = "inspec" platform = "azure" [menu] [menu.inspec] title = "azurermkeyvaults" identifier = "inspec/resources/azure/azurermkeyvaults.md azurermkeyvaults resource" parent = "inspec/resources/azure" +++ {{< inspec/azurermdeprecated resource="azurekey_vaults" >}} Use the `azurermkeyvaults` InSpec audit resource to test properties and configuration of Azure Key Vaults. This resource interacts with version `2016-10-01` of the Azure Management API. For more information see the . At the moment, there doesn't appear to be a way to select the version of the Azure API docs. If you notice a newer version being referenced in the official documentation please open an issue or submit a pull request using the updated version. This resource is available in the `inspec-azure` [resource pack](/inspec/glossary/#resource-pack). To use it, add the following to your `inspec.yml` in your top-level profile: depends: name: inspec-azure git: https://github.com/inspec/inspec-azure.git You'll also need to setup your Azure credentials; see the resource pack . This resource first became available in 1.2.0 of the inspec-azure resource pack. An `azurermkeyvaults` resource block returns all Azure Key Vaults within a Resource Group. describe azurermkeyvaults(resource_group: 'my-rg') do ... end The following examples show how to use this InSpec audit resource. describe azurermkeyvaults(resource_group: 'my-rg') do it { should exist } its('names') { should include 'vault-101' } end Filters the results to include only those vaults which match the given name. This is a string value. describe azurermkeyvaults(resource_group: 'my-rg').where{ name.eql?('vault-101') } do it { should exist } end Filters the results to include only those vaults which reside in a given location. This is a string value. describe azurermkeyvaults(resource_group: 'my-rg').where{ location.eql?('eastus') } do it { should exist } end `id` `name` `location` `type` `tags` `properties` Azure resource ID. Key Vault name, e.g. `vault-101`. its('names') { should include 'vault-101' } Resource location, e.g. `eastus`. its('locations') { should_not include 'eastus' } The type of Resource, typically `Microsoft.KeyVault/vaults`. Resource tags applied to the Key Vault. A collection of additional configuration properties related to the Key Vault, e.g. `vaultUri`. {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The control will pass if the filter returns at least one result. Use `should_not` if you expect zero matches. describe azurermkeyvaults(resource_group: 'my-rg') do it { should exist } end Your [Service Principal](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal) must be setup with a `contributor` role on the subscription you wish to test.
Project: DevStream (Provisioning / Automation & Configuration)
File: SECURITY.md

Version: v0.12 (2023-04-24) As a tool manager, some of the tools need to be installed in a production environment. Thus, some of DevStream's plugins need to have production access, which makes security an important topic. The DevStream team takes security as job zero and improves it continuously. We currently support the most recent release (`N`, e.g. `0.2`) and the release previous to the most recent one (`N-1`, e.g. `0.1`). With the release of `N+1`, `N-1` drops out of support and `N` becomes `N-1`. We regularly perform patch releases (e.g. `0.1.1` and `0.2.1`) for supported versions, which will contain fixes for security vulnerabilities. Prior releases might receive critical security fixes on a best effort basis, however, it cannot be guaranteed that security fixes get back-ported to these unsupported versions. In some cases, where a security fix needs complex re-design of a feature or is otherwise very intrusive, and there's a workaround available, we may decide to provide a forward-fix only, e.g. to be released the next minor release, instead of releasing it within a patch branch for the currently supported releases. Please report vulnerabilities by e-mail to the following address: tao.hu@merico.dev If you find a security-related bug in DevStream, we kindly ask you to disclose responsibly and give us appropriate time to react to mitigate the vulnerability. We do our best to react quickly. Sometimes, it might take a little longer (e.g. out-of-office conditions); please bear with us in these cases. We publish security advisories using the feature to keep our community well informed, and will credit you for your findings (unless you prefer to stay anonymous, of course).
Project: Chef InSpec (Provisioning / Security & Compliance)
File: etc_hosts_allow.md

+++ title = "etchostsallow resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "etchostsallow" identifier = "inspec/resources/os/etchostsallow.md etchostsallow resource" parent = "inspec/resources/os" +++ Use the `etchostsallow` Chef InSpec audit resource to test rules defined for accepting daemon and client traffic in the `'/etc/hosts.allow'` file. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.39.1 of InSpec. An etc/hosts.allow rule specifies one or more daemons mapped to one or more clients, with zero or more options for accepting traffic when found. Use the where clause to match a property to one or more rules in the `hosts.allow` file. describe etchostsallow.where { daemon == 'value' } do its ('client_list') { should include ['values'] } its ('options') { should include ['values'] }p end Use the optional constructor parameter to give an alternative path to `hosts.allow` file. describe etchostsallow(hosts_path).where { daemon == 'value' } do its ('client_list') { should include ['values'] } its ('options') { should include ['values'] } end where `daemon` is a filter that will be allowed to pass traffic in. `client_list`, `options` are the valid resource properties that test the list of clients who will be allowed to pass traffic in, and a list of tasks that are to be done with the rule when traffic is found respectively. The `daemon` property returns a string containing the daemon that is allowed in the rule. describe etchostsallow.where { client_list == ['127.0.1.154', '[:fff:fAb0::]'] } do its('daemon') { should eq ['vsftpd', 'sshd'] } end The `client_list` property returns a 2d string array where each entry contains the clients specified for the rule. describe etchostsallow.where { daemon == 'sshd' } do its('client_list') { should include ['192.168.0.0/16', '[abcd::0000:1234]'] } end The `options` property returns a 2d string array where each entry contains any options specified for the rule. describe etchostsallow.where { daemon == 'sshd' } do its('options') { should include ['deny', 'echo "REJECTED"'] } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}}
Project: KICS (Provisioning / Security & Compliance)
File: 98295b32-ec09-4b5b-89a9-39853197f914.md

title: Schema JSON Reference Does Not Exists (v2) hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 98295b32-ec09-4b5b-89a9-39853197f914 Query name: Schema JSON Reference Does Not Exists (v2) Platform: OpenAPI Severity: <span style="color:#5bc0de">Info</span> Category: Structure and Semantics URL: Schema reference should exists on definitions field<br> ```json title="Positive test num. 1 - json file" hl_lines="15" { "swagger": "2.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "schema": { "$ref": "#/definitions/Use" } } }, "parameters": [ { "$ref": "#/parameters/limitParam" } ] } } }, "parameters": { "limitParam": { "name": "limit", "in": "body", "description": "max records to return", "required": true, "schema": { "type": "integer" } } }, "definitions": { "User": { "type": "object", "required": [ "id", "name" ], "properties": { "id": { "type": "integer", "format": "int64" }, "name": { "type": "string" } } } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="14" swagger: '2.0' info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '200': schema: "$ref": "#/definitions/Use" parameters: "$ref": "#/parameters/limitParam" parameters: limitParam: name: limit in: body description: max records to return required: true schema: type: integer definitions: User: type: object required: id name properties: id: type: integer format: int64 name: type: string ``` ```json title="Negative test num. 1 - json file" { "swagger": "2.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "schema": { "$ref": "#/definitions/User" } } }, "parameters": [ { "$ref": "#/parameters/limitParam" } ] } } }, "parameters": { "limitParam": { "name": "limit", "in": "body", "description": "max records to return", "required": true, "schema": { "type": "integer" } } }, "definitions": { "User": { "type": "object", "required": [ "id", "name" ], "properties": { "id": { "type": "integer", "format": "int64" }, "name": { "type": "string" } } } } } ``` ```yaml title="Negative test num. 2 - yaml file" swagger: '2.0' info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '200': schema: "$ref": "#/definitions/User" parameters: "$ref": "#/parameters/limitParam" parameters: limitParam: name: limit in: body description: max records to return required: true schema: type: integer definitions: User: type: object required: id name properties: id: type: integer format: int64 name: type: string ```
Project: YugabyteDB (App Definition and Development / Database)
File: reset_stmt.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="193" height="65" viewbox="0 0 193 65"><path class="connector" d="M0 22h15m59 0h30m54 0h20m-89 0q5 0 5 5v20q0 5 5 5h5m42 0h17q5 0 5-5v-20q0-5 5-5m5 0h15"/><polygon points="0,29 5,22 0,15" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="5" width="59" height="25" rx="7"/><text class="text" x="25" y="22">RESET</text><a xlink:href="../../../syntaxresources/grammardiagrams#name"><rect class="rule" x="104" y="5" width="54" height="25"/><text class="text" x="114" y="22">name</text></a><rect class="literal" x="104" y="35" width="42" height="25" rx="7"/><text class="text" x="114" y="52">ALL</text><polygon points="189,29 193,29 193,15 189,15" style="fill:black;stroke-width:0"/></svg>
Project: YDB (App Definition and Development / Database)
File: table_path_name_recindex.md

Access to the current table name, which might be needed when you use , , and other related functions. No arguments. Returns a string with the full path or an empty string and warning when used in an unsupported context (for example, when working with a subquery or a range of 1000+ tables). {% note info %} The , , and functions don't support temporary and anonymous tables (they return an empty string or 0 for ). These functions are calculated when projections in `SELECT`, and by that time the current table may already be temporary. To avoid such a situation, create a subquery for calculating these functions, as shown in the second example below. {% endnote %} Examples ```yql SELECT TablePath() FROM CONCAT(tablea, tableb); ``` ```yql SELECT key, tpath AS path FROM (SELECT a.*, TablePath() AS tpath FROM RANGE(`my_folder`) AS a) WHERE key IN $subquery; ``` Get the table name based on the table path. You can obtain the path using the function or as the `Path` column when using the table function . Optional arguments: Path to the table, `TablePath()` is used by default (see also its limitations). Specifying the system ("yt") whose rules are used to determine the table name. You need to specify the system only if doesn't specify the current cluster. Examples ```yql USE hahn; SELECT TableName() FROM CONCAT(tablea, tableb); ``` ```yql SELECT TableName(Path, "yt") FROM hahn.FOLDER(folder_name); ``` Access to the current sequence number of a row in the physical source table, starting from 1 (depends on the storage implementation). No arguments. When used in combination with , and other similar mechanisms, numbering restarts for each input table. If used in an incorrect context, it returns 0. Example ```yql SELECT TableRecordIndex() FROM my_table; ```
Project: ClickHouse (App Definition and Development / Database)
File: v22.9.7.34-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Updated normaliser to clone the alias ast. resolves Implementation: Updated QueryNormalizer to clone alias ast, when its replaced. Previously just assigning the same leads to exception in LogicalExpressinsOptimizer as it would be the same parent being inserted again. * This bug is not seen with new analyser (allowexperimentalanalyzer), so no changes for it. I added a test for the same. (). Backported in : Bring sha512 sums back to the building step. (). Backported in : Fix bad inefficiency of `remotefilesystemread_method=read` with filesystem cache. Closes . (). Backported in : Fix incorrect UserTimeMicroseconds/SystemTimeMicroseconds accounting. (). Backported in : Fix rare possible hung on query cancellation. (). Backported in : An issue with the following exception has been reported while trying to read a Parquet file from S3 into ClickHouse:. (). Backported in : Fix sumMap() for Nullable(Decimal()). (). Backported in : Fixed `ALTER ... RESET SETTING` with `ON CLUSTER`. It could be applied to one replica only. Fixes . (). Backported in : Fix undefined behavior in the `quantiles` function, which might lead to uninitialized memory. Found by fuzzer. This closes . (). NO CL ENTRY: 'Fix multipart upload for large S3 object, backport to 22.9'. (). Yet another fix for AggregateFunctionMinMaxAny (). Use only PRs to our repository in pr_info on push (). Fix tags workflow (). Assign release PRs (). Fix another bug in AggregateFunctionMinMaxAny ().
Project: ClickHouse (App Definition and Development / Database)
File: corr.md

slug: /en/sql-reference/aggregate-functions/reference/corr sidebar_position: 107 Syntax: `corr(x, y)` Calculates the Pearson correlation coefficient: `((x - x)(y - y)) / sqrt(((x - x)^2) * ((y - y)^2))`. :::note This function uses a numerically unstable algorithm. If you need in calculations, use the `corrStable` function. It works slower but provides a lower computational error. :::
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.6.12.md

RabbitMQ `3.6.12` is a maintenance release. See the for general documentation on upgrades. This release has no other known incompatibilities with versions 3.6.7 through 3.6.11. See the upgrade and compatibility sections in the if upgrading from an earlier release. Process responsible for running the autoheal partition handling strategy could run into a deadlock with its peers, preventing autoheal from completing. GitHub issue: Garbage collection of mirrored queue metrics on nodes that did not host a leader or mirror for a queue affected delivery and acknowledgement rates. This could result in rates being 0 or negative when they should not be. GitHub issue: Stats emission could prevent queue mirrors from performing garbage collection and consume memory even when they were empty. GitHub issue: (continuation to ) `RABBITMQSCHEDULERBINDTYPE` and `RABBITMQDISTRIBUTIONBUFFERSIZE` now can be set via `rabbitmq-env.conf`. GitHub issue: Passwords in source and destination URIs are now redacted out. GitHub issue: Passwords in upstream URIs are now redacted out. 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 . 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-3.6.12.tar.gz`.
Project: Druid (App Definition and Development / Database)
File: sorting-orders.md

id: sorting-orders title: "String comparators" <!-- ~ 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. --> :::info Apache Druid supports two query languages: and . This document describes the native language. For information about functions available in SQL, refer to the . ::: These sorting orders are used by the , , GroupByQuery's , and . Sorts values by converting Strings to their UTF-8 byte array representations and comparing lexicographically, byte-by-byte. Suitable for strings with both numeric and non-numeric content, e.g.: "file12 sorts after file2" See https://github.com/amjjd/java-alphanum for more details on how this ordering sorts values. This ordering is not suitable for numbers with decimal points or negative numbers. For example, "1.3" precedes "1.15" in this ordering because "15" has more significant digits than "3". Negative numbers are sorted after positive numbers (because numeric characters precede the "-" in the negative numbers). Sorts values as numbers, supports integers and floating point values. Negative values are supported. This sorting order will try to parse all string values as numbers. Unparseable values are treated as nulls, and nulls precede numbers. When comparing two unparseable values (e.g., "hello" and "world"), this ordering will sort by comparing the unparsed strings lexicographically. Sorts values by their string lengths. When there is a tie, this comparator falls back to using the String compareTo method. Sorts values as versions, e.g.: "10.0 sorts after 9.0", "1.0.0-SNAPSHOT sorts after 1.0.0". See https://maven.apache.org/ref/3.6.0/maven-artifact/apidocs/org/apache/maven/artifact/versioning/ComparableVersion.html for more details on how this ordering sorts values.
Project: Carvel (App Definition and Development / Application Definition & Image Build)
File: README_SQS.md

The following is a sample class and Lambda function that receives Amazon SQS event message data as input, writes some of the message data to CloudWatch Logs, and responds with a 200 status and the same body as the request. (Note that anything written to stdout or stderr will be logged as CloudWatch Logs events.) ```go package main import ( "context" "fmt" "github.com/aws/aws-lambda-go/events" "github.com/aws/aws-lambda-go/lambda" ) func handler(ctx context.Context, sqsEvent events.SQSEvent) error { for _, message := range sqsEvent.Records { fmt.Printf("The message %s for event source %s = %s \n", message.MessageId, message.EventSource, message.Body) } return nil } func main() { lambda.Start(handler) } ```
Project: KICS (Provisioning / Security & Compliance)
File: b05bb927-2df5-43cc-8d7b-6825c0e71625.md

title: Components Example Definition Is Unused hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b05bb927-2df5-43cc-8d7b-6825c0e71625 Query name: Components Example Definition Is Unused Platform: OpenAPI Severity: <span style="color:#5bc0de">Info</span> Category: Best Practices URL: Components examples definitions should be referenced or removed from Open API definition<br> ```json title="Positive test num. 1 - json file" hl_lines="42" { "openapi": "3.0.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "Success", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/MyObject" } } } } } } } }, "components": { "schemas": { "MyObject": { "type": "object", "properties": { "id": { "type": "string" }, "name": { "type": "string" } } } }, "examples": { "objectExample": { "value": { "id": "1", "name": "new object" }, "summary": "A sample object" } } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="27" openapi: 3.0.0 info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '200': description: Success content: application/json: schema: "$ref": "#/components/schemas/MyObject" components: schemas: MyObject: type: object properties: id: type: string name: type: string examples: objectExample: value: id: '1' name: new object summary: A sample object ``` ```json title="Negative test num. 1 - json file" { "openapi": "3.0.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "Success", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/MyObject" }, "examples": { "objectExample": { "$ref": "#/components/examples/objectExample" } } } } } } } } }, "components": { "schemas": { "MyObject": { "type": "object", "properties": { "id": { "type": "string" }, "name": { "type": "string" } } } }, "examples": { "objectExample": { "value": { "id": "1", "name": "new object" }, "summary": "A sample object" } } } } ``` ```yaml title="Negative test num. 2 - yaml file" openapi: 3.0.0 info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '200': description: Success content: application/json: schema: "$ref": "#/components/schemas/MyObject" examples: objectExample: "$ref": "#/components/examples/objectExample" components: schemas: MyObject: type: object properties: id: type: string name: type: string examples: objectExample: value: id: '1' name: new object summary: A sample object ```
Project: ArangoDB (App Definition and Development / Database)
File: implicit_failure_error_copy_constructor.md

+++ title = "`basicoutcome(const failuretype<EC> &)`" description = "Implicit error-from-failure-type-sugar copy constructor. Available if `predicate::enablecompatibleconversion<void, EC, void, void>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "implicit-constructors", "tagged-constructors"] weight = 520 +++ Implicit error-from-failure-type-sugar copy constructor used to disambiguate the construction of the error type. Calls {{% api "void onoutcomecopyconstruction(T *, U &&) noexcept" %}} with `this` and `const failuretype<EC> &`. Requires: `predicate::enablecompatibleconversion<void, EC, void, void>` is true. Complexity: Same as for the `error_type` constructor which accepts `EC`. Constexpr, triviality and noexcept of underlying operations is propagated.