cwielenb/CNCF-Dataset huggingface dataset:
Project: ORY Hydra (Provisioning / Key Management)
File: TokenPaginationRequestParameters.md

Name | Type | Description | Notes | - | - | - PageSize | Pointer to int64 | Items per Page This is the number of items per page to return. For details on pagination please head over to the . | [optional] [default to 250] PageToken | Pointer to string | Next Page Token The next page token. For details on pagination please head over to the . | [optional] [default to "1"] `func NewTokenPaginationRequestParameters() *TokenPaginationRequestParameters` NewTokenPaginationRequestParameters instantiates a new TokenPaginationRequestParameters 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 NewTokenPaginationRequestParametersWithDefaults() *TokenPaginationRequestParameters` NewTokenPaginationRequestParametersWithDefaults instantiates a new TokenPaginationRequestParameters 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 *TokenPaginationRequestParameters) GetPageSize() int64` GetPageSize returns the PageSize field if non-nil, zero value otherwise. `func (o TokenPaginationRequestParameters) GetPageSizeOk() (int64, bool)` GetPageSizeOk returns a tuple with the PageSize field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *TokenPaginationRequestParameters) SetPageSize(v int64)` SetPageSize sets PageSize field to given value. `func (o *TokenPaginationRequestParameters) HasPageSize() bool` HasPageSize returns a boolean if a field has been set. `func (o *TokenPaginationRequestParameters) GetPageToken() string` GetPageToken returns the PageToken field if non-nil, zero value otherwise. `func (o TokenPaginationRequestParameters) GetPageTokenOk() (string, bool)` GetPageTokenOk returns a tuple with the PageToken field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *TokenPaginationRequestParameters) SetPageToken(v string)` SetPageToken sets PageToken field to given value. `func (o *TokenPaginationRequestParameters) HasPageToken() bool` HasPageToken returns a boolean if a field has been set.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_service_account_key.md

+++ title = "googleserviceaccount_key resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleserviceaccount_key" identifier = "inspec/resources/gcp/googleserviceaccountkey.md googleserviceaccountkey resource" parent = "inspec/resources/gcp" +++ A `googleserviceaccount_key` is used to test a Google ServiceAccountKey resource ```ruby googleserviceaccountkeys(project: 'chef-gcp-inspec', serviceaccount: "display-name@project-id.iam.gserviceaccount.com").keynames.each do |sakey_name| describe googleserviceaccountkey(project: 'chef-gcp-inspec', serviceaccount: "display-name@project-id.iam.gserviceaccount.com", name: sakeyname.split('/').last) do it { should exist } its('keytype') { shouldnot cmp 'USER_MANAGED' } end end ``` describe googleserviceaccount_key(name: "projects/sample-project/serviceAccounts/test-sa@sample-project.iam.gserviceaccount.com/keys/c6bd986da9fac6d71178db41d1741cbe751a5080" ) do its('keyalgorithm') { should eq "KEYALGRSA2048" } end Properties that can be accessed from the `googleserviceaccount_key` resource: `name` : The name of the key. `privatekeytype` : Output format for the service account key. Possible values: TYPE_UNSPECIFIED TYPEPKCS12FILE TYPEGOOGLECREDENTIALS_FILE `key_algorithm` : Specifies the algorithm for the key. Possible values: KEYALGUNSPECIFIED KEYALGRSA_1024 KEYALGRSA_2048 `privatekeydata` : Private key data. Base-64 encoded. `publickeydata` : Public key data. Base-64 encoded. `validaftertime` : Key can only be used after this time. `validbeforetime` : Key can only be used before this time. `key_type` : Specifies the type of the key. Possible values: KEYTYPEUNSPECIFIED USER_MANAGED SYSTEM_MANAGED `service_account` : The name of the serviceAccount. `path` : The full name of the file that will hold the service account private key. The management of this file will depend on the value of sync_file parameter. File path must be absolute. Ensure the is enabled for the current project.
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-error-conditions.md

layout: global title: Error Conditions displayTitle: Error Conditions license: | 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. {% comment %} Don't discuss error classes (e.g. `42`) or sub-classes (e.g. `K01`) with users. It's not helpful. Keep this documentation focused on error states (e.g. `58002`) and conditions (e.g. `AMBIGUOUSCOLUMNREFERENCE`), which is what users see and what they will typically be searching for when they encounter an error. To update this information, edit `error-conditions.json`. The table below will be automatically derived from that file via `docs/util/build-error-docs.py`. Also note that this is a Jekyll comment and not an HTML comment so that this comment does not show up in the generated HTML to end users. :-) {% endcomment %} This is a list of error states and conditions that may be returned by Spark SQL. {% includeapigen _generated/error-conditions.html %}
Project: YugabyteDB (App Definition and Development / Database)
File: savepoint_release.md

title: RELEASE SAVEPOINT statement [YSQL] headerTitle: RELEASE SAVEPOINT linkTitle: RELEASE SAVEPOINT description: Use the `RELEASE SAVEPOINT` statement to release a savepoint. menu: v2.18: identifier: savepoint_release parent: statements type: docs Use the `RELEASE SAVEPOINT` statement to release the server-side state associated with tracking a savepoint and make the named savepoint no longer accessible to . {{%ebnf%}} savepoint_release {{%/ebnf%}} ```plpgsql RELEASE [ SAVEPOINT ] name ``` The name of the savepoint you wish to release. Begin a transaction and create a savepoint. ```plpgsql BEGIN TRANSACTION; SAVEPOINT test; ``` Once you are done with it, release the savepoint: ```plpgsql RELEASE test; ``` If at this point, you attempt to rollback to `test`, it will be an error: ```plpgsql ROLLBACK TO test; ``` ```output ERROR: savepoint "test" does not exist ```
Project: SuperEdge (Provisioning / Automation & Configuration)
File: CONTRIBUTOR.md

The outstanding contributors of SuperEdge are given in the list below, in no particular order | Maintainer | GitHub ID | Email | | :--: | :: | :-: | | Xiaodong Luo | @ | 15622358376@163.com | | Yingzhe Ru | @ | yingzheru@tencent.com | | Navy | @ | arenas@aliyun.com | | Shaw Ho | @ | tossmilestone@gmail.com | | Galen Peng | @ | kyoiora@gmail.com | | Jiawei Cheng | @ | | | Peimin Min | @ | peiminmin@yeah.net | | Hongqiao Lian | @ | 2471035068@qq.com | | Whisper | @ | 2510932399@qq.com |
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-system-connection.1.md

% podman-system-connection 1 podman\-system\-connection - Manage the destination(s) for Podman service(s) podman system connection subcommand Manage the destination(s) for Podman service(s). The user is prompted for the ssh login password or key file passphrase as required. The `ssh-agent` is supported if it is running. Podman manages the system connection by writing and reading the `podman-connections.json` file located under `$XDGCONFIGHOME/containers` or if the env is not set it defaults to `$HOME/.config/containers`. Or the `PODMANCONNECTIONSCONF` environment variable can be set to a full file path which podman will use instead. This file is managed by the podman commands and should never be edited by users directly. To manually configure the connections use `service_destinations` in containers.conf. If the ReadWrite column in the podman system connection list output is set to true the connection is stored in the `podman-connections.json` file otherwise it is stored in containers.conf and can therefore not be edited with the podman system connection commands. | Command | Man Page | Description | | -- | -- | - | | add | | Record destination for the Podman service | | default | | Set named destination as default for the Podman service | | list | | List the destination for the Podman service(s) | | remove | | Delete named destination | | rename | | Rename the destination for Podman service | List system connections: ``` $ podman system connection list Name URI Identity Default ReadWrite devl ssh://root@example.com/run/podman/podman.sock ~/.ssh/id_rsa true true ``` , June 2020, Originally compiled by Jhon Honce (jhonce at redhat dot com)
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_core.Cell.md

/ / Cell .Cell new Cell(`cell`) | Name | Type | | :-- | :- | | `cell` | | `Optional` className: `string` `Optional` css: `string` `Optional` drilldownTo: `"side-split"` \| `"this-split"` \| `"new-window"` `Optional` fontawesome: `string` \| `string`[] `Optional` innerClassName: `string` `Optional` key: `string` `Optional` onclick: `any` `Optional` outerCSS: `string` `Optional` tag: `string` `Optional` tagClass: `string` value: `string` `Optional` valueDom: `ReactElement`<`any`, `string` \| `JSXElementConstructor`<`any`\>\>
Project: YugabyteDB (App Definition and Development / Database)
File: security-checklist.md

title: Security checklist headerTitle: Security checklist linkTitle: Security checklist description: Review security measures for your YugabyteDB installation. menu: v2.18: identifier: security-checklist parent: secure weight: 710 type: docs There is a number of security measures that you can implement to protect your YugabyteDB installation. Authentication requires that all clients provide valid credentials before they can connect to a YugabyteDB cluster. YugabyteDB stores authentication credentials internally in the YB-Master system tables. The authentication mechanisms available to clients depend on what is supported and exposed by the YSQL, YCQL, and YEDIS APIs. For more information, see . Roles can be modified to grant users or applications only the essential privileges based on the operations they need to perform against the database. Typically, an administrator role is created first. The administrator then creates additional roles for users. For more information, see . Run the YB-Master and YB-TServer services with a dedicated operating system user account. Ensure that this dedicated user account has permissions to access the data drives, but no unnecessary permissions. Ensure that YugabyteDB runs in a trusted network environment, such that: Servers running YugabyteDB services are directly accessible only by the servers running the application and database administrators. Only servers running applications can connect to YugabyteDB services on the RPC ports. Access to the should be denied to everybody else. Limit the interfaces on which YugabyteDB instances listen for incoming connections. Specify just the required interfaces when starting `yb-master` and `yb-tserver` by using the `--rpcbindaddresses` option. Do not bind to the loopback address. Refer to the for more information on using these options. Do not assign a public IP address to the nodes running YugabyteDB, if possible. Applications can connect to YugabyteDB over private IP addresses. In Amazon Web Services (AWS), run the YugabyteDB cluster in a separate VPC () and peer this only with VPCs from which database access is required, for example from those VPCs where the application will run. Make the security groups assigned to the database servers very restrictive. Ensure that they can communicate with each other on the necessary ports, and expose only the client accessible ports to just the required set of servers. See the . ensures that network communication between servers is secure. You can configure YugabyteDB to use TLS to encrypt intra-cluster and client to server network communication. You should enable encryption in transit in YugabyteDB clusters and clients to ensure privacy and integrity of data transferred over the network. For more information, see . ensures that data at rest, stored on disk, is protected. You can configure YugabyteDB with a self-generated symmetric key to perform cluster-wide encryption. For more information, see .
Project: KICS (Provisioning / Security & Compliance)
File: 59029ddf-e651-412b-ae7b-ff6d403184bc.md

title: Logging of Sensitive Data hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 59029ddf-e651-412b-ae7b-ff6d403184bc Query name: Logging of Sensitive Data Platform: Ansible Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: To keep sensitive values out of logs, tasks that expose them need to be marked defining 'no_log' and setting to True<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="14" name: Positive Playbook hosts: localhost tasks: name: bar ansible.builtin.user: name: john_doe comment: John Doe uid: 1040 group: admin password: "{{ item }}" with_items: wow no_log: false ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="5" name: Positive Playbook hosts: localhost tasks: name: bar ansible.builtin.user: name: john_doe comment: John Doe uid: 1040 group: admin password: "{{ item }}" with_items: wow ``` ```yaml title="Negative test num. 1 - yaml file" name: Negative playbook hosts: localhost tasks: name: foo ansible.builtin.user: name: john_doe comment: John Doe uid: 1040 group: admin password: "{{ item }}" with_items: wow no_log: true name: Negative Playbook 2 hosts: localhost tasks: name: bar ansible.builtin.user: name: john_doe comment: John Doe uid: 1040 group: admin with_items: wow no_log: false name: Negative Playbook 3 hosts: localhost tasks: name: bar ansible.builtin.user: name: john_doe comment: John Doe uid: 1040 group: admin with_items: wow ```
Project: ClickHouse (App Definition and Development / Database)
File: v20.12.5.14-stable.md

Backported in : Fix error when query `MODIFY COLUMN ... REMOVE TTL` doesn't actually remove column TTL. (). Backported in : Fix possible crashes in aggregate functions with combinator `Distinct`, while using two-level aggregation. Fixes . (). Backported in : Fix filling table `system.settingsprofileelements`. This PR fixes . (). Backported in : Restrict merges from wide to compact parts. In case of vertical merge it led to broken result part. (). Backported in : Fixed `value is too short` error when executing `toType(...)` functions (`toDate`, `toUInt32`, etc) with argument of type `Nullable(String)`. Now such functions return `NULL` on parsing errors instead of throwing exception. Fixes . (). Backported in : Proper support for 12AM in `parseDateTimeBestEffort` function. This fixes . (). Backported in : Disable write with AIO during merges because it can lead to extremely rare data corruption of primary key columns during merge. (). Backported in : Update timezones info to 2020e. ().
Project: KICS (Provisioning / Security & Compliance)
File: 704fcc44-a58f-4af5-82e2-93f2a58ef918.md

title: User with IAM Role hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 704fcc44-a58f-4af5-82e2-93f2a58ef918 Query name: User with IAM Role Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Access Control URL: As a best practice, it is better to assign an IAM Role to a group than to a user<br> ```tf title="Positive test num. 1 - tf file" hl_lines="3" data "googleiampolicy" "positive" { binding { role = "roles/apigee.runtimeAgent" members = [ "user:jane@example.com", ] } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="18 3" resource "googleprojectiam_binding" "positive2" { project = "your-project-id" role = "roles/container.admin" members = [ "user:jane@example.com", ] condition { title = "expiresafter20191231" description = "Expiring at midnight of 2019-12-31" expression = "request.time < timestamp(\"2020-01-01T00:00:00Z\")" } } resource "googleprojectiam_member" "positive3" { project = "your-project-id" role = "roles/editor" member = "user:jane@example.com" } ``` ```tf title="Negative test num. 1 - tf file" data "googleiampolicy" "negative" { binding { role = "roles/apigee.runtimeAgent" members = [ "group:jane@example.com", ] } } ```
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.0.2-zh.md

Delete edgedevice from the name field of all virtual devices / profiles by @xiaoyu0803 in https://github.com/Edgenesis/shifu/pull/136 Custom Metadata support in EdgeDevice CRD by @tomqin93 in https://github.com/Edgenesis/shifu/pull/143 Refactor deviceShifu build and push in Makefile by @tomqin93 in https://github.com/Edgenesis/shifu/pull/144 Development Guide for Mac and Windows by @tomqin93 in https://github.com/Edgenesis/shifu/pull/121 v0.0.1 Changelog by @tomqin93 in https://github.com/Edgenesis/shifu/pull/131 Update contact information in README.md by @saiyan86 in https://github.com/Edgenesis/shifu/pull/132 [Issue #129] Fix some documentation errors by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/134 deviceShifu doc by @saiyan86 in https://github.com/Edgenesis/shifu/pull/137 [Issue #145] fix the wrong go version in document by @13316272689 in https://github.com/Edgenesis/shifu/pull/146 Bump github.com/gopcua/opcua from 0.3.4 to 0.3.5 by @dependabot in https://github.com/Edgenesis/shifu/pull/135 Bump k8s.io/apimachinery from 0.24.1 to 0.24.2 in /deviceshifu/pkg/mockdevice/mockdevice by @dependabot in https://github.com/Edgenesis/shifu/pull/140 Bump k8s.io/client-go from 0.24.1 to 0.24.2 by @dependabot in https://github.com/Edgenesis/shifu/pull/139 [Issue #123] Update devcontainer by @tomqin93 in https://github.com/Edgenesis/shifu/pull/147 Bump sigs.k8s.io/controller-runtime from 0.12.1 to 0.12.2 in /k8s/crd by @dependabot in https://github.com/Edgenesis/shifu/pull/150 Bump up Kustomize, controller-gen and kube-rbac-proxy versions by @tomqin93 in https://github.com/Edgenesis/shifu/pull/151 @MrLeea-13155bc made their first contribution in https://github.com/Edgenesis/shifu/pull/134 @13316272689 made their first contribution in https://github.com/Edgenesis/shifu/pull/146 : https://github.com/Edgenesis/shifu/compare/v0.0.1...v0.0.2
Project: KICS (Provisioning / Security & Compliance)
File: 92e4464a-4139-4d57-8742-b5acc0347680.md

title: KMS Admin and CryptoKey Roles In Use hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 92e4464a-4139-4d57-8742-b5acc0347680 Query name: KMS Admin and CryptoKey Roles In Use Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Google Project IAM Policy should not assign a KMS admin role and CryptoKey role to the same member<br> ```tf title="Positive test num. 1 - tf file" hl_lines="3" resource "googleprojectiam_policy" "positive1" { project = "your-project-id" policydata = data.googleiampolicy.positive1.policydata } data "googleiampolicy" "positive1" { binding { role = "roles/cloudkms.admin" members = [ "user:jane@example.com", ] } binding { role = "roles/cloudkms.cryptoKeyDecrypter" members = [ "user:jane@example.com", ] } } ``` ```tf title="Negative test num. 1 - tf file" resource "googleprojectiam_policy" "negative1" { project = "your-project-id" policydata = data.googleiampolicy.negative1.policydata } data "googleiampolicy" "negative1" { binding { role = "roles/cloudkms.admin" members = [ "user:jane@example.com", ] } binding { role = "roles/cloudkms.cryptoKeyDecrypter" members = [ "user:jane2@example.com", ] } } ```
Project: Nocalhost (App Definition and Development / Application Definition & Image Build)
File: MAINTAINERS.md

This page lists all active maintainers of this repository. If you were a maintainer and would like to add your name to the Emeritus list, please send us a PR. See for governance guidelines and how to become a maintainer. See for general contribution guidelines. , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: ml-ann.md

layout: global title: Multilayer perceptron classifier displayTitle: Multilayer perceptron classifier license: | 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. > This section has been moved into the .
Project: KICS (Provisioning / Security & Compliance)
File: 9bf57c23-fbab-4222-85f3-3f207a53c6a8.md

title: Nifcloud RDB Has Common Private Network hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 9bf57c23-fbab-4222-85f3-3f207a53c6a8 Query name: Nifcloud RDB Has Common Private Network Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Networking and Firewall URL: The rdb has common private network<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "nifclouddbinstance" "positive" { identifier = "example" instance_class = "db.large8" networkid = "net-COMMONPRIVATE" } ``` ```tf title="Negative test num. 1 - tf file" resource "nifclouddbinstance" "negative" { identifier = "example" instance_class = "db.large8" networkid = nifcloudprivate_lan.main.id } ```
Project: KICS (Provisioning / Security & Compliance)
File: bc20bbc6-0697-4568-9a73-85af1dd97bdd.md

title: VM With Full Cloud Access hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: bc20bbc6-0697-4568-9a73-85af1dd97bdd Query name: VM With Full Cloud Access Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: A VM instance is configured to use the default service account with full access to all Cloud APIs<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="7" name: create a instance google.cloud.gcpcomputeinstance: name: test_object zone: us-central1-a project: test_project auth_kind: serviceaccount service_accounts: scopes: cloud-platform state: present ``` ```yaml title="Negative test num. 1 - yaml file" name: create a instance google.cloud.gcpcomputeinstance: name: test_object zone: us-central1-a project: test_project auth_kind: serviceaccount state: present ```