cwielenb/CNCF-Dataset huggingface dataset:
Project: Hazelcast IMDG (App Definition and Development / Database)
File: SECURITY.md

Hazelcast is committed to providing our users with secure software they can rely on. We promptly investigate all reports of security vulnerabilities affecting Hazelcast products. If you believe you have found a security vulnerability, we strongly encourage you to report it to us immediately, and we ask your help in working with our team before disclosure in a public forum. This allows us to address the issue most effectively for the benefit and protection of all users. Its easy to submit a vulnerability report: If youre a Hazelcast customer, open a support ticket and provide us with as much detail as youre able. If you are not a Hazelcast customer, please email security@hazelcast.com*. Note: This email address is only for reporting security vulnerabilities, not inquiries about security-related topics. Please reach out to us via one of our community channels for general security questions. Using either method, your report will be received promptly by Hazelcast staff. Our standard process is: Upon receiving your private report, Hazelcast will route it to the appropriate team for investigation. If we need additional information, we will directly and privately reach out to the person who sent the vulnerability report. We will verify the vulnerability and its fix. The security fix will be included in a new release. We greatly appreciate your partnership in helping us provide the strongest security posture for all users. Thank you. To find out which Hazelcast versions are currently being supported please visit our page.
Project: ClickHouse (App Definition and Development / Database)
File: v21.3.18.4-lts.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Use separate `clickhouse-bridge` group and user for bridge processes. Set oomscoreadj so the bridges will be first subjects for OOM killer. Set set maximum RSS to 1 GiB. Closes . (). Backported in : Update zoneinfo files to 2021c. (). Backported in : Fix shutdown of `AccessControlManager`. Now there can't be reloading of the configuration after AccessControlManager has been destroyed. This PR fixes the flaky test .html). (). Backported in : Fix invalid constant type conversion when nullable or lowcardinality primary key is used. (). Backported in : Fix the number of threads used in `GLOBAL IN` subquery (it was executed in single threads since bugfix). (). Backported in : Fix segfault while inserting into column with type LowCardinality(Nullable) in Avro input format. (). Backported in : Fix possible `Table columns structure in ZooKeeper is different from local table structure` exception while recreating or creating new replicas of `ReplicatedMergeTree`, when one of table columns have default expressions with case-insensitive functions. (). Backported in : Fix connection timeouts (`sendtimeout`/`receivetimeout`). (). Backported in : Condition in filter predicate could be lost after push-down optimisation. (). Backported in : Fix concurrent access to `LowCardinality` during `GROUP BY` (leads to SIGSEGV). (). Backported in : Fix crash of sample by `tuple()`, closes . (). Backported in : Allow identifiers staring with numbers in multiple joins. (). Backported in : fix replaceRegexpAll bug. (). Do not add const group by key for query with only having. (). Merging (). May be fix s3 tests (). Fix ca-bundle.crt in kerberized_hadoop/Dockerfile ().
Project: Druid (App Definition and Development / Database)
File: druid-aws-rds.md

id: druid-aws-rds title: "Druid AWS RDS Module" <!-- ~ 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. --> is a managed service to operate relation databases such as PostgreSQL, Mysql etc. These databases could be accessed using static db password mechanism or via temporary tokens. This module provides AWS RDS token implementation to be used with or when mysql/postgresql is operated using AWS RDS. ```json { "type": "aws-rds-token", "user": "USER", "host": "HOST", "port": PORT, "region": "AWS_REGION" } ``` Before using this password provider, please make sure that you have connected all dots for db user to connect using token. See . To use this extension, make sure you it in your config file along with other extensions e.g. ``` druid.extensions.loadList=["druid-aws-rds-extensions", "postgresql-metadata-storage", ...] ```
Project: ClickHouse (App Definition and Development / Database)
File: v20.10.3.30-stable.md

Backported in : Add allownondeterministicoptimizeskipunused_shards (to allow non deterministic like rand() or dictGet() in sharding key). (). Backported in : Decrement the `ReadonlyReplica` metric when detaching read-only tables. This fixes . (). Backported in : Possibility to move part to another disk/volume if the first attempt was failed. (). Backported in : Fixed `DROP TABLE IF EXISTS` failure with `Table ... doesn't exist` error when table is concurrently renamed (for Atomic database engine). Fixed rare deadlock when concurrently executing some DDL queries with multiple tables (like `DROP DATABASE` and `RENAME TABLE`) Fixed `DROP/DETACH DATABASE` failure with `Table ... doesn't exist` when concurrently executing `DROP/DETACH TABLE`. (). Backported in : Fix collate name & charset name parser and support `length = 0` for string type. (). Backported in : Fix dictGet in sharding_key (and similar places, i.e. when the function context is stored permanently). (). Backported in : Fix the case when memory can be overallocated regardless to the limit. This closes . (). Backported in : Fix a possible memory leak during `GROUP BY` with string keys, caused by an error in `TwoLevelStringHashTable` implementation. (). Backported in : Fix async Distributed INSERT w/ preferlocalhostreplica=0 and internal_replication. (). Backported in : Fix group by with totals/rollup/cube modifers and min/max functions over group by keys. Fixes . (). Backported in : Fix double free in case of exception in function `dictGet`. It could have happened if dictionary was loaded with error. ().
Project: Vault (Provisioning / Key Management)
File: routing.md

<!-- START doctoc generated TOC please keep comment here to allow auto update --> <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE --> - <!-- END doctoc generated TOC please keep comment here to allow auto update --> Parent route typically serves to group related child resources Parent index route typically displays empty state placeholder with call to action or redirects to default child resource Child resource names are pluralized Child index route represents list view. Child singularized name + /details is the read view. Avoid extending routes. This can lead to unnecessary inheritance which gets messy quickly. For , consider a decorator. The file structure can be leveraged to simplify CRUD actions and passing data. The singular resource route should live at the same level as its folder, this automatically passes its model to any route nested within the folder. Below, `details.js` and `edit.js` will automatically receive the model returned by the model hook in `resource-foo.js`. Alternately, if defining a custom model hook in those routes, we can use methods like `this.modelFor` instead of re-querying records. ``` routes/vault/cluster/access parent/ index.js resource-foos / resource-foo.js create.js index.js resource-foo/ details.js edit.js ``` For example, route structure : ``` routes/vault/cluster/access oidc/ index.js clients/ client.js create.js index.js client/ details.js edit.js providers.js <- utilizes the modelFor method to get id about parent's clientId ``` To guide users, we sometimes have a call to action that depends on a resource's state. For example, if a secret engine hasn't been configured routing to the first step to do so, and otherwise navigating to its overview page. Instead of extending route classes to share this `isConfigured` state, consider a decorator! is a great example. Renders `window.confirm()` alert that a user has unsaved changes if navigaing away from route with the decorator Unloads or rolls back Ember data model record <!-- TODO add withConfig() if we refactor for more general use --> <!-- ### We sometimes have a call to action guiding users that depends on a resource's state. For example, if a secret engine hasn't been configured the UI renders an empty state linking to the first configuration step. Otherwise, it routes to the overview page of that engine. Sample use: ```js import { withConfig } from '../decorators/fetch-config'; @withConfig() export default class SomeRouter extends Route { model() { // in case of any error other than 404 we want to display that to the user if (this.configError) { throw this.configError; } return { config: this.configModel, // configuration data to determine UI state }; } } ``` -->
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.10.12.md

RabbitMQ `3.10.12` is a maintenance release in the `3.10.x` . Please refer to the upgrade section from if upgrading from a version prior to 3.10.0. This release requires Erlang 24.2 and supports Erlang 25. has more details on Erlang version requirements for RabbitMQ. Erlang 23 support has reached its . This release of RabbitMQ requires Erlang 24.2 or later versions. Nodes will fail to start on older Erlang releases. Erlang 25 is recommended: it offers much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation. Release notes can be found on GitHub at . Quorum queues are now more resilient to WAL log growth with workloads that involve clients that register a consumer and then close the channel or connection without ever consuming any deliveries or cancelling the consumer. GitHub issue: When a node encouters an invalid `definitions.local.file` on boot, it will refuse to start instead of ignoring the file. GitHub issue: Fixed a type analyzer definition. Contributed by @illotum (AWS). GitHub issue: Queue info keys now support more inclusive property names related to (deprecated) classic mirrored queues. For example, `mirror_pids` can now be used instead of `slave_pids`. Contributed by @illotum (AWS). GitHub issue: `rabbitmq-diagnostics memory_breakdown` now executes significantly faster in environments with a large number (say, tens or hundreds of thousands) of quorum queues. Two orders of magnitude faster, in fact. GitHub issue: Definition export in JSON failed on nodes that used `definitions.skipifunchanged`. GitHub issue: Using quorum queue-specific commands on streams now results in clearer error messages. Contributed by @gomoripeti (CloudAMQP). GitHub issue: LDAP server password could end up in the logs in certain types of exceptions. Contributed by @SimonUnge (AWS). GitHub issue: `x-max-age` now can be set by STOMP clients via a header. GitHub issue: To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.10.12.tar.xz` instead of the source tarball produced by GitHub.
Project: StarRocks (App Definition and Development / Database)
File: log2.md

displayed_sidebar: "English" Calculates the base 2 logarithm of a number. ```SQL log2(arg) ``` `arg`: The value whose logarithm you want to calculate. Only DOUBLE data type is supported. NOTE StarRocks returns NULL if `arg` is specified as a negative or 0. Returns a value of the DOUBLE data type. Example 1: Calculate the base 2 logarithm of 8. ```Plain mysql> select log2(8); ++ | log2(8) | ++ | 3 | ++ 1 row in set (0.00 sec) ```
Project: Kyverno (Provisioning / Security & Compliance)
File: kyverno_json.md

Runs tests against any json compatible payloads/policies. Runs tests against any json compatible payloads/policies. NOTE: This is an experimental command, use `KYVERNO_EXPERIMENTAL=true` to enable it. ``` kyverno json [flags] ``` ``` -h, --help help for json ``` ``` --adddirheader If true, adds the file directory to the header of the log messages --alsologtostderr log to standard error as well as files (no effect when -logtostderr=true) --logbacktraceat traceLocation when logging hits line file:N, emit a stack trace (default :0) --log_dir string If non-empty, write log files in this directory (no effect when -logtostderr=true) --log_file string If non-empty, use this log file (no effect when -logtostderr=true) --logfilemax_size uint Defines the maximum size a log file can grow to (no effect when -logtostderr=true). Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800) --logtostderr log to standard error instead of files (default true) --one_output If true, only write logs to their native severity level (vs also writing to each lower severity level; no effect when -logtostderr=true) --skip_headers If true, avoid header prefixes in the log messages --skiplogheaders If true, avoid headers when opening log files (no effect when -logtostderr=true) --stderrthreshold severity logs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or -alsologtostderr=true) (default 2) -v, --v Level number for the log level verbosity --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging ``` - Kubernetes Native Policy Management. - Runs tests against any json compatible payloads/policies.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: os_env.md

+++ title = "os_env resource" draft = false gh_repo = "inspec" platform = "os" [menu] [menu.inspec] title = "os_env" identifier = "inspec/resources/os/osenv.md osenv resource" parent = "inspec/resources/os" +++ Use the `os_env` Chef InSpec audit resource to test the environment variables for the platform on which the system is running. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.0.0 of InSpec. A `os_env` resource block declares an environment variable, and then declares its value: describe os_env('VARIABLE') do its('property') { should eq 1 } end where `('VARIABLE')` must specify an environment variable, such as `PATH` `matcher` is a valid matcher for this resource The following examples show how to use this Chef InSpec audit resource. describe os_env('PATH') do its('split') { should_not include('') } its('split') { should_not include('.') } end On windows a User's environment variable may obscure the local machine (system) environment variable. The correct environment variable may be tested as follows: describe os_env('PATH', 'target') do its('split') { should_not include('') } its('split') { should_not include('.') } end where `'target'` may be either `system` or `user` Chef Habitat uses the `os_env` resource to test environment variables. The environment variables are first defined in a whitespace array, after which each environment variable is tested: habenvvars = %w(HABAUTHTOKEN HABCACHEKEY_PATH HABDEPOTURL HAB_ORG HAB_ORIGIN HABORIGINKEYS HAB_RING HABRINGKEY HABSTUDIOSHOME HABSTUDIOROOT HAB_USER) habenvvars.each do |e| describe os_env(e) do its('content') { should eq nil } end end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The `content` matcher return the value of the environment variable: its('content') { should eq '/usr/local/bin:/usr/local/sbin:/usr/sbin:/usr/bin:/sbin' } The `split` matcher splits the value of the environment variable with the `:` deliminator (use the `;` deliminator if Windows): its('split') { should include ('/usr/bin') } Note: the `split` matcher returns an array including `""` for cases where there is a trailing colon (`:`), such as `dir1::dir2:`
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.79.md

layout: release date: 2023-04-13 tag: v0.6.79 perform remote provider logout @MUzairS15 (#7540) [Server] Credential crud @Azanul (#7513) Fixed alignment of MeshMap access popup @Nikhil-Ladha (#7538) Add job to perform a Meshery rollout for CNCF playground on release @Revolyssup (#7539) Thank you to our contributors for making this release possible: @Azanul, @MUzairS15, @Nikhil-Ladha, @Revolyssup, @leecalcote, @theBeginner86 and MUzairS15
Project: ko (App Definition and Development / Application Definition & Image Build)
File: CONTRIBUTING.md

We'd love to accept your patches and contributions to this project. There are just a few small guidelines you need to follow. Contributions to this project must be accompanied by a Contributor License Agreement. You (or your employer) retain the copyright to your contribution; this simply gives us permission to use and redistribute your contributions as part of the project. Head over to <https://cla.developers.google.com/> to see your current agreements on file or to sign a new one. You generally only need to submit a CLA once, so if you've already submitted one (even if it was for a different project), you probably don't need to do it again. All submissions, including submissions by project members, require review. We use GitHub pull requests for this purpose. Consult for more information on using pull requests. Ensure the following passes: ``` ./hack/presubmit.sh ``` and commit any resultant changes to `go.mod` and `go.sum`. To update any docs after client changes, run: ``` ./hack/update-codegen.sh ```
Project: YugabyteDB (App Definition and Development / Database)
File: dcl_drop_owned.md

title: DROP OWNED statement [YSQL] headerTitle: DROP OWNED linkTitle: DROP OWNED description: Use the DROP OWNED statement to drop all database objects within the current database that are owned by one of the specified roles. menu: v2.18: identifier: dcldropowned parent: statements type: docs Use the `DROP OWNED` statement to drop all database objects within the current database that are owned by one of the specified roles. Any privileges granted to the given roles on objects in the current database or on shared objects will also be revoked. {{%ebnf%}} drop_owned, role_specification {{%/ebnf%}} CASCADE Automatically drop objects that depend on the affected objects. RESTRICT This is the default mode and will raise an error if there are other database objects that depend on the dropped objects. Drop all objects owned by `john`. ```plpgsql yugabyte=# drop owned by john; ```
Project: ClickHouse (App Definition and Development / Database)
File: build-cross-arm.md

slug: /en/development/build-cross-arm sidebar_position: 67 title: How to Build ClickHouse on Linux for AARCH64 (ARM64) Architecture sidebar_label: Build on Linux for AARCH64 (ARM64) If you use AArch64 machine and want to build ClickHouse for AArch64, build as usual. If you use x8664 machine and want cross-compile for AArch64, add the following flag to `cmake`: `-DCMAKETOOLCHAIN_FILE=cmake/linux/toolchain-aarch64.cmake`
Project: Clair (Provisioning / Security & Compliance)
File: clairctl.md

`clairctl` is a command line tool for working with Clair. This CLI is capable of generating manifests from most public registries (dockerhub, quay.io, Red Hat Container Catalog) and submitting them for analysis to a running Clair. Note that if the Clair instance has authentication configured, the value provided to the `issuer` flag must be on the list accepted by the server. ``` NAME: clairctl - interact with a clair API USAGE: clairctl [global options] command [command options] [arguments...] VERSION: 0.1.0 DESCRIPTION: A command-line tool for clair v4. COMMANDS: manifest print a clair manifest for the named container report request vulnerability reports for the named containers export-updaters run updaters and export results import-updaters import updates help, h Shows a list of commands or help for one command GLOBAL OPTIONS: -D print debugging logs (default: false) --config value, -c value clair configuration file (default: "config.yaml") [$CLAIR_CONF] --issuer value, --iss value jwt "issuer" to use when making authenticated requests (default: "clairctl") --help, -h show help (default: false) --version, -v print the version (default: false) ``` ``` NAME: clairctl manifest - print a clair manifest for the named container USAGE: clairctl manifest [arguments...] DESCRIPTION: print a clair manifest for the named container ``` ``` NAME: clairctl report - request vulnerability reports for the named containers USAGE: clairctl report [command options] container... DESCRIPTION: Request and print a Clair vulnerability report for the named container(s). OPTIONS: --host value URL for the clairv4 v1 API. (default: "http://localhost:6060/") [$CLAIR_API] --out value, -o value output format: text, json, xml (default: text) ``` ``` NAME: clairctl export-updaters - run updaters and export results USAGE: clairctl export-updaters [command options] [out] DESCRIPTION: Run configured exporters and export to a file. A configuration file is needed to run this command, see 'clairctl help' for how to specify one. OPTIONS: --strict Return non-zero exit when updaters report errors. (default: false) ``` ``` NAME: clairctl import-updaters - import updates USAGE: clairctl import-updaters input... DESCRIPTION: Import updates from files or HTTP URIs. A configuration file is needed to run this command, see 'clairctl help' for how to specify one. ```
Project: KICS (Provisioning / Security & Compliance)
File: ac5a0bc0-a54c-45aa-90c3-15f7703b9132.md

title: Configuration Aggregator to All Regions Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ac5a0bc0-a54c-45aa-90c3-15f7703b9132 Query name: Configuration Aggregator to All Regions Disabled Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Observability URL: AWS Config Configuration Aggregator All Regions must be set to True<br> ```tf title="Positive test num. 1 - tf file" hl_lines="16 4" resource "awsconfigconfiguration_aggregator" "positive1" { name = "example" accountaggregationsource { account_ids = ["123456789012"] regions = ["us-east-2", "us-east-1", "us-west-1", "us-west-2"] } } resource "awsconfigconfiguration_aggregator" "positive2" { dependson = [awsiamrolepolicy_attachment.organization] name = "example" # Required organizationaggregationsource { all_regions = false rolearn = awsiam_role.organization.arn } } ``` ```tf title="Negative test num. 1 - tf file" resource "awsconfigconfiguration_aggregator" "negative1" { name = "example" accountaggregationsource { all_regions = true } } resource "awsconfigconfiguration_aggregator" "negative2" { dependson = [awsiamrolepolicy_attachment.organization] name = "example" # Required organizationaggregationsource { all_regions = true rolearn = awsiam_role.organization.arn } } ```