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

+++ title = "postgresidentconf resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "postgresidentconf" identifier = "inspec/resources/os/postgresidentconf.md postgresidentconf resource" parent = "inspec/resources/os" +++ Use the `postgresidentconf` Chef InSpec audit resource to test the client authentication data defined in the pg_ident.conf file. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.31.0 of InSpec. An `postgresidentconf` Chef InSpec audit resource block declares client authentication data that should be tested: describe postgresidentconf.where { pgusername == 'filtervalue' } do its('attribute') { should eq ['value'] } end where `'attribute'` is a attribute in the pg ident configuration file `'filter_value'` is the value that is to be filtered for `'value'` is the value that is to be matched expected `map_name` returns a an array of strings that matches the where condition of the filter table describe postgresidentconf.where { pg_username == 'name' } do its('map_name') { should eq ['value'] } end `pg_username` returns a an array of strings that matches the where condition of the filter table describe postgresidentconf.where { pg_username == 'name' } do its('pg_username') { should eq ['value'] } end `system_username` returns a an array of strings that matches the where condition of the filter table describe postgresidentconf.where { pg_username == 'name' } do its('system_username') { should eq ['value'] } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}}
Project: GreptimeDB (App Definition and Development / Database)
File: 2023-08-13-metadata-txn.md

Feature Name: Update Metadata in single transaction Tracking Issue: https://github.com/GreptimeTeam/greptimedb/issues/1715 Date: 2023-08-13 Author: "Feng Yangsen <fengys1996@gmail.com>, Xu Wenkang <wenymedia@gmail.com>" Update Metadata in single transaction. Currently, multiple transactions are involved during the procedure. This implementation is inefficient, and it's hard to make data consistent. Therefore, We can update multiple metadata in a single transaction. Now we have the following table metadata keys: TableInfo ```rust // tableinfo/{tableid} pub struct TableInfoKey { table_id: TableId, } pub struct TableInfoValue { pub table_info: RawTableInfo, version: u64, } ``` TableRoute ```rust // tableroute/{tableid} pub struct NextTableRouteKey { table_id: TableId, } pub struct TableRoute { pub region_routes: Vec<RegionRoute>, } ``` DatanodeTable ```rust // tableroute/{datanodeid}/{table_id} pub struct DatanodeTableKey { datanode_id: DatanodeId, table_id: TableId, } pub struct DatanodeTableValue { pub table_id: TableId, pub regions: Vec<RegionNumber>, version: u64, } ``` TableNameKey ```rust // table_name/{CatalogName}/{SchemaName}/{TableName} pub struct TableNameKey<'a> { pub catalog: &'a str, pub schema: &'a str, pub table: &'a str, } pub struct TableNameValue { table_id: TableId, } ``` These table metadata only updates in the following operations. It needs to update `TableRoute` key and `DatanodeTable` keys. If the `TableRoute` equals the Snapshot of `TableRoute` submitting the Failover task, then we can safely update these keys. After submitting Failover tasks to acquire locks for execution, the `TableRoute` may be updated by another task. After acquiring the lock, we can get the latest `TableRoute` again and then execute it if needed. Creates all of the above keys. `TableRoute`, `TableInfo`, should be empty. The TableNameKey's lock will be held by the procedure framework. `TableInfoKey` and `NextTableRouteKey` will be added with `removed-` prefix, and the other above keys will be deleted. The transaction will not compare any keys. Rename table, updates `TableInfo` and `TableName`. Compares `TableInfo`, and the new `TableNameKey` should be empty, and TableInfo should equal the Snapshot when submitting DDL. The old and new TableNameKey's lock will be held by the procedure framework. Alter table, updates `TableInfo`. `TableInfo` should equal the Snapshot when submitting DDL.
Project: NeuVector (Provisioning / Security & Compliance)
File: SECURITY.md

Join the [kubernetes-security-announce] group for security and vulnerability announcements. You can also subscribe to an RSS feed of the above using . Instructions for reporting a vulnerability can be found on the [Kubernetes Security and Disclosure Information] page. Information about supported Kubernetes versions can be found on the [Kubernetes version and version skew support policy] page on the Kubernetes website.
Project: LinuxKit (Provisioning / Automation & Configuration)
File: 2017-06-25.md

This report covers weekly developments in the / [#2090] [#2033] [@mgoelzer] [@justincormack]). Kernel GPG verification:* The kernel compilation containers now verify the GPG and SHA256 checksums before building the binaries. ([#2062] [#2083] [@mscribe] [@justincormack] [@rn] [@riyazdf]). The base Alpine build image now includes `gnupg` to support this feature ([#2091] [@riyazdf] [@rn]). Security SIG on Landlock:* The third Moby Security SIG focussed on the security module that provides unprivileged fine-grained sandboxing to applications. There are as well as videos and forum links ([#2087] [#2089] [#2073] [@riyazdf]). Networking drivers now modules:* The kernels have been updated to 4.11.6/4.9.33/4.4.73, and many drivers are now loaded as modules to speed up boot-time ([#2095] [#2061] [@rn] [@justincormack] [@tych0]) Whaley important update: The ASCII logo was updated and we fondly wave goodbye to the waves. ([#2084] [@thaJeztah] [@rn]) Containerised getty and sshd: The login services now run in their own mount namespace, which was confusing people since they were expecting it to be on the host filesystem. This is now being addressed via a reminder in the `motd` upon login ([#2078] [#2097] [@deitch] [@ijc] [@justincormack] [@riyazdf] [@rn]) Hardened user copying: The RFC on ensuring that we use a hardened kernel/userspace copying system was closed, as it is enabled by default on all our modern kernels and a regression test is included by default ([#2086] [@fntlnz] [@riyazdf]). Vultr provider: There is an ongoing effort to add a metadata provider for ([#2101] [@furious-luke] [@justincormack]). Simplified Makefiles for packages ([#2080] [@justincormack] [@rn]) The MirageOS SDK is integrating many upstream changes from dependent libraries, for the DHCP client ([#2070] [#2072] [@samoht] [@talex5] [@avsm]). A comprehensive test suite for containerd is now integrated into LinuxKit tests ([#2062] [@AkihiroSuda] [@justincormack] [@rn]) Fix documentation links ([#2074] [@ndauten] [@justincormack]) Update RTF version ([#2077] [@justincormack]) tests: add build test for Docker for Mac blueprint ([#2093] [@riyazdf] [@MagnusS]) Disable Qemu EFI ISO test for now ([#2100] [@justincormack]) The CI whitelists and ACLs were updated ([linuxkit-ci#11] [linuxkit-ci#15] [linuxkit/linuxkit-ci#10] [@rn] [@justincormack]) Fix spelling errors ([#2079] [@ndauten]) Fix typo in dev report ([#2094] [@justincormack]) Fix dead Link to VMWare File ([#2082] [@davefreitag]) Other reports in this series can be browsed directly in the repository at .
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: deployment.md

sidebar_position: 1 import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; Before you getting start the local run, you need to make sure you already have installed the following software which SeaTunnel required: (Java 8 or 11, other versions greater than Java 8 can theoretically work as well) installed and `JAVA_HOME` set. Enter the and download the latest version of distribute package `seatunnel-<version>-bin.tar.gz` Or you can download it by terminal ```shell export version="2.3.5" wget "https://archive.apache.org/dist/seatunnel/${version}/apache-seatunnel-${version}-bin.tar.gz" tar -xzvf "apache-seatunnel-${version}-bin.tar.gz" ``` <!-- TODO: We should add example module as quick start which is no need for install Spark or Flink --> Since 2.2.0-beta, the binary package does not provide connector dependencies by default, so when using it for the first time, you need to execute the following command to install the connector: (Of course, you can also manually download the connector from to download, then manually move to the `connectors/seatunnel` directory). ```bash sh bin/install-plugin.sh 2.3.5 ``` If you need to specify the version of the connector, take 2.3.5 as an example, you need to execute ```bash sh bin/install-plugin.sh 2.3.5 ``` Usually you don't need all the connector plugins, so you can specify the plugins you need by configuring `config/plugin_config`, for example, you only need the `connector-console` plugin, then you can modify plugin.properties as ```plugin_config --seatunnel-connectors-- connector-console --end-- ``` If you'd like to make a sample application to work properly, you need to add the following plugins ```plugin_config --seatunnel-connectors-- connector-fake connector-console --end-- ``` You can find out all supported connectors and corresponding pluginconfig configuration names under `${SEATUNNELHOME}/connectors/plugins-mapping.properties`. :::tip If you'd like to install the connector plugin by manually downloading the connector, you need to pay special attention to the following The connectors directory contains the following subdirectories, if they do not exist, you need to create them manually ``` flink flink-sql seatunnel spark ``` If you'd like to install the V2 connector plugin manually, you only need to download the V2 connector plugin you need and put them in the seatunnel directory ::: For now, you are already deployment SeaTunnel complete. You can follow to configure and run a data synchronization job.
Project: MongoDB (App Definition and Development / Database)
File: test_coverage.md

|Component|Sub-component|Existing tests| |||| |Checkpoint|| |Component|Sub-component|Existing tests| |||| |Aggregated Time Windows|| |Backup|| |Backup|Cursors|, |Checkpoint|| |Checkpoint|Checkpoint Cleanup| |Checkpoint|History Store| |Checkpoint|Metadata| |Checkpoint|Obsolete Data| |Checkpoint|Recovery| |Compression||, , , |Config Api||, |Connection Api|| |Connection Api|Reconfigure|, |Connection Api|Turtle File| |Connection Api|Wiredtiger Open| |Cursors|Prepare| |Cursors|Reconfigure| |Cursors|Search| |Cursors|Search Near| |Cursors|Statistics| |Encryption|| |Eviction|Prepare| |History Store|| |History Store|Eviction Checkpoint Interaction| |Indexes|| |Indexes|Search Near| |Prepare|| |Reconciliation|Overflow Keys| |Recovery|| |Recovery|Log Files| |Rollback To Stable||, , |Salvage|Prepare| |Schema Api|| |Session Api|Reconfigure| |Session Api|Verify| |Statistics|| |Tiered Storage|Checkpoint| |Tiered Storage|Flush Tier| |Transactions|| |Truncate|| |Truncate|Prepare| |Verify|Prepare|, |Wt Util||, , , , ,
Project: Trivy (Provisioning / Security & Compliance)
File: ubuntu.md

Trivy supports these scanners for OS packages. | Scanner | Supported | | :--: | :-: | | SBOM | | | Vulnerability | | | License | | Please see for supported versions. The following table provides an outline of the features Trivy offers. | Feature | Supported | |::|::| | Detect unfixed vulnerabilities | | | | | Same as . Ubuntu offers its own security advisories, and these are utilized when scanning Ubuntu for vulnerabilities. See . When looking at fixed versions, it's crucial to consider the patches supplied by Ubuntu. As an illustration, for CVE-2023-3269, the fixed version for Ubuntu 23.04 (lunar) is listed as `6.2.0-26.26` in . It's essential to recognize that this differs from the upstream fixed version, which stands at `6.5`. Typically, only the upstream information gets listed on , so it's important not to get confused. Trivy calculates the severity of an issue based on the 'Priority' metric found in the Security Tracker. If 'Priority' isn't provided by Ubuntu, the severity from the NVD is taken into account. Using CVE-2019-15052 as an example, while it is rated as , Ubuntu has marked its "Priority" as . As a result, Trivy will display it as "Medium". Trivy supports the following [vulnerability statuses] for Ubuntu. | Status | Supported | | :--: | :-: | | Fixed | | | Affected | | | Under Investigation | | | Will Not Fix | | | Fix Deferred | | | End of Life | | Same as .
Project: Checkov (Provisioning / Security & Compliance)
File: Contribute New Gitlab Policies.md

layout: default published: true title: Contribute New Gitlab configuration policy nav_order: 5 In this example, we'll add support for a new Gitlab configuration check. We are going to add a new check that will examine how merge requests protection rules are configured and validate we enforce at least 2 approvers. First, we will validate if the Gitlab API call that GETs the branch protection current state exists in `checkov/gitlab/dal.py`. If not it can be added to that file like the following example: ```python class Gitlab(BaseVCSDAL): ... ... def getprojectapprovals(self): if self.project_id: projectapprovals = self.request( endpoint=f"projects/{self.project_id}/approvals") return project_approvals return None def persistprojectapprovals(self): projectapprovals = self.getproject_approvals() if project_approvals: BaseVCSDAL.persist(path=self.gitlabprojectapprovalsfilepath, conf=project_approvals) def persistallconfs(self): if strtobool(os.getenv("CKVGITLABCONFIGFETCHDATA", "True")): self.persistprojectapprovals() self.persist_groups() ``` Go to `checkov/gitlab/checks` and add `enforcebranchprotectiononadmins.py`: ```python class MergeRequestRequiresApproval(BaseGitlabCheck): def init(self): name = "Merge requests should require at least 2 approvals" id = "CKVGITLAB1" categories = [CheckCategories.SUPPLY_CHAIN] super().init( name=name, id=id, categories=categories, supported_entities=["*"], block_type=BlockType.DOCUMENT ) def scanentityconf(self, conf): if projectaprovalsschema.validate(conf): if conf.get("approvalsbeforemerge", 0) < 2: return CheckResult.FAILED, conf return CheckResult.PASSED, conf check = MergeRequestRequiresApproval() ``` And also add the JSON schema to validate the Gitlab API response `/checkov/gitlab/schemas/project_approvals.py`: ```python from checkov.common.vcs.vcs_schema import VCSSchema class ProjectApprovalsSchema(VCSSchema): def init(self): schema = { "$schema": "http://json-schema.org/draft-04/schema#", "type": "object", "properties": { "approvalsbeforemerge": { "type": "integer" }, "resetapprovalson_push": { "type": "boolean" }, "disableoverridingapproverspermerge_request": { "type": "boolean" }, "mergerequestsauthor_approval": { "type": "boolean" }, "mergerequestsdisablecommittersapproval": { "type": "boolean" }, "requirepasswordto_approve": { "type": "boolean" } }, "required": [ "approvalsbeforemerge", "resetapprovalson_push", "disableoverridingapproverspermerge_request", "mergerequestsauthor_approval", "mergerequestsdisablecommittersapproval", "requirepasswordto_approve" ] } super().init(schema=schema) schema = ProjectApprovalsSchema() ``` follow the examples in `tests/gitlab/test_runner.py` and add a test to the new check So there you have it! A new check will be scanned once your contribution is merged!
Project: ORY Hydra (Provisioning / Key Management)
File: TokenPaginationResponseHeaders.md

Name | Type | Description | Notes | - | - | - Link | Pointer to string | The Link HTTP Header The &#x60;Link&#x60; header contains a comma-delimited list of links to the following pages: first: The first page of results. next: The next page of results. prev: The previous page of results. last: The last page of results. Pages are omitted if they do not exist. For example, if there is no next page, the &#x60;next&#x60; link is omitted. Examples: &lt;/clients?pagesize&#x3D;5&amp;pagetoken&#x3D;0&gt;; rel&#x3D;\&quot;first\&quot;,&lt;/clients?pagesize&#x3D;5&amp;pagetoken&#x3D;15&gt;; rel&#x3D;\&quot;next\&quot;,&lt;/clients?pagesize&#x3D;5&amp;pagetoken&#x3D;5&gt;; rel&#x3D;\&quot;prev\&quot;,&lt;/clients?pagesize&#x3D;5&amp;pagetoken&#x3D;20&gt;; rel&#x3D;\&quot;last\&quot; | [optional] XTotalCount | Pointer to int64 | The X-Total-Count HTTP Header The &#x60;X-Total-Count&#x60; header contains the total number of items in the collection. | [optional] `func NewTokenPaginationResponseHeaders() *TokenPaginationResponseHeaders` NewTokenPaginationResponseHeaders instantiates a new TokenPaginationResponseHeaders object This constructor will assign default values to properties that have it defined, and makes sure properties required by API are set, but the set of arguments will change when the set of required properties is changed `func NewTokenPaginationResponseHeadersWithDefaults() *TokenPaginationResponseHeaders` NewTokenPaginationResponseHeadersWithDefaults instantiates a new TokenPaginationResponseHeaders object This constructor will only assign default values to properties that have it defined, but it doesn't guarantee that properties required by API are set `func (o *TokenPaginationResponseHeaders) GetLink() string` GetLink returns the Link field if non-nil, zero value otherwise. `func (o TokenPaginationResponseHeaders) GetLinkOk() (string, bool)` GetLinkOk returns a tuple with the Link field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *TokenPaginationResponseHeaders) SetLink(v string)` SetLink sets Link field to given value. `func (o *TokenPaginationResponseHeaders) HasLink() bool` HasLink returns a boolean if a field has been set. `func (o *TokenPaginationResponseHeaders) GetXTotalCount() int64` GetXTotalCount returns the XTotalCount field if non-nil, zero value otherwise. `func (o TokenPaginationResponseHeaders) GetXTotalCountOk() (int64, bool)` GetXTotalCountOk returns a tuple with the XTotalCount field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *TokenPaginationResponseHeaders) SetXTotalCount(v int64)` SetXTotalCount sets XTotalCount field to given value. `func (o *TokenPaginationResponseHeaders) HasXTotalCount() bool` HasXTotalCount returns a boolean if a field has been set.
Project: YDB (App Definition and Development / Database)
File: nanvl.md

Replaces the values of `NaN` (not a number) in expressions like `Float`, `Double`, or . Arguments: The expression where you want to make a replacement. The value to replace `NaN`. If one of the arguments is `Double`, the result is`Double`, otherwise, it's `Float`. If one of the arguments is `Optional`, then the result is `Optional`. Examples ```yql SELECT NANVL(double_column, 0.0) FROM my_table; ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: groupintobatches.md

title: "GroupIntoBatches" <!-- 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. --> {{< localstorage language language-py >}} {{< button-pydoc path="apache_beam.transforms.util" class="GroupIntoBatches" >}} Batches the input into desired batch size. In the following example, we create a pipeline with a `PCollection` of produce by season. We use `GroupIntoBatches` to get fixed-sized batches for every key, which outputs a list of elements for every key. {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHON_GroupIntoBatches" show="groupintobatches" >}} {{< /playground >}} <!-- TODO(BEAM-10889): Create a page for BatchElements and link to it here. //--> For unkeyed data and dynamic batch sizes, one may want to use . {{< button-pydoc path="apache_beam.transforms.util" class="GroupIntoBatches" >}}
Project: CloudEvents (App Definition and Development / Streaming & Messaging)
File: sequence.md

This extension defines an attribute that can be included within a CloudEvent to describe the position of an event in the ordered sequence of events produced by a unique event source. The `sequence` attribute represents the value of this event's order in the stream of events. This specification does not define the meaning or set of valid value of this attribute, rather it only mandates that the value be a string that can be lexicographically compared to other `sequence` values to determine which one comes first. The `sequence` with a lower lexicographical value comes first. Produces and consumers are free to define an out-of-band agreement on the semantic meaning, or valid values, for the attribute. As with the main , the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in . However, the scope of these key words is limited to when this extension is used. For example, an attribute being marked as "REQUIRED" does not mean it needs to be in all CloudEvents, rather it needs to be included only when this extension is being used. Type: `String` Description: Value expressing the relative order of the event. This enables interpretation of data supercedence. Constraints REQUIRED MUST be a non-empty lexicographically-orderable string RECOMMENDED as monotonically increasing and contiguous The entity creating the CloudEvent MUST ensure that the `sequence` values used are formatted such that across the entire set of values used a receiver can determine the order of the events via a simple string-compare type of operation. This means that it might be necessary for the value to include some kind of padding (e.g. leading zeros in the case of the value being the string representation of an integer).
Project: StarRocks (App Definition and Development / Database)
File: coalesce.md

displayed_sidebar: "English" Returns the first non-NULL expression among the input parameters. Returns NULL if non-NULL expressions cannot be found. ```Haskell coalesce(expr1,...); ``` `expr1`: the input expressions, which must evaluate to compatible data types. The return value has the same type as `expr1`. ```Plain Text mysql> select coalesce(3,NULL,1,1); +-+ | coalesce(3, NULL, 1, 1) | +-+ | 3 | +-+ 1 row in set (0.00 sec) ```