cwielenb/CNCF-Dataset huggingface dataset:
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_core.Util.md

/ / Util .Util absolute(`filepath`): `string` Notes: path.resolve() turns /kui/x into c:\kui\x. We just want to absolute-ify a local filepath if it isn't already so. this only works for local filepaths; if we wanted this to work for all kui VFS, we would need to use `vfs ls`, which is asynchronous. | Name | Type | | : | :- | | `filepath` | `string` | `string` An absolute path for the given `path`, only if it is not already absolute base64PlusGzip(`plaintext`, `compress?`): `string` | Name | Type | Default value | | :- | :-- | : | | `plaintext` | `string` | `undefined` | | `compress` | `boolean` | `true` | `string` a base64-encoded and gzip-compressed version of the given `plaintext` `Const` cwd(): `string` `string` decodeBase64PlusGzip(`data`, `compressed?`): `Buffer` | Name | Type | Default value | | :-- | :-- | : | | `data` | `string` | `undefined` | | `compressed` | `boolean` | `true` | `Buffer` the reverse of `base64PlusGzip` `Const` expandHomeDir(`path`): `string` | Name | Type | | :-- | :- | | `path` | `string` | `string` fallbackCWD(`cwd?`): `string` In case of error, e.g. removed CWD, this is our fallback plan | Name | Type | | :-- | :- | | `cwd?` | `string` | `string` flatten<`T`\>(`arrays`): `T`[] flatten an array of arrays | Name | | : | | `T` | | Name | Type | | :- | : | | `arrays` | `T` | `T`[] isHTML(`message`): message is HTMLElement | Name | Type | | :-- | :-- | | `message` | `Node` \| `Entity`<`void`, , <`void`\>\> \| `MessageWithUsageModel` | message is HTMLElement isPromise<`T`, `U`\>(`content`): content is Promise<T\> | Name | | : | | `T` | | `U` | | Name | Type | | :-- | : | | `content` | `U` \| `Promise`<`T`\> | content is Promise<T\> prettyPrintBytes(`_bytes`): `string` | Name | Type | | :- | :- | | `_bytes` | `string` \| `number` | `string` pretty-printed bytes `Const` prettyPrintTime(`timestamp`, `fmt?`, `previousTimestamp?`, `execOptions?`): `HTMLElement` Pretty print a timestamp | Name | Type | Default value | | :- | :-- | : | | `timestamp` | `string` \| `number` \| `Date` | `undefined` | | `fmt` | `"delta"` \| `"long"` \| `"short"` \| `"narrow"` | `'long'` | | `previousTimestamp?` | `string` \| `number` \| `Date` | `undefined` | | `execOptions` | `LanguageBearing` | `undefined` | `HTMLElement` promiseEach<`T`, `R`\>(`arr`, `fn`): `Promise`<`R`[]\> Map a asynchronous function to an array sequentially from front to back. | Name | | : | | `T` | | `R` | | Name | Type | | :- | :- | | `arr` | `T`[] | | `fn` | (`t`: `T`, `idx`: `number`) => `R` \| `Promise`<`R`\> | `Promise`<`R`[]\>
Project: YDB (App Definition and Development / Database)
File: max_min.md

Returns the minimum or maximum among N arguments. Those functions let you replace the SQL standard statement `CASE WHEN a < b THEN a ELSE b END` that would be too sophisticated for N more than two. The argument types must be mutually castable and accept `NULL`. `GREATEST` is a synonym for `MAXOF` and `LEAST` is a synonym for `MINOF`. Examples ```yql SELECT MIN_OF(1, 2, 3); ```
Project: KICS (Provisioning / Security & Compliance)
File: 1e749bc9-fde8-471c-af0c-8254efd2dee5.md

title: Role Binding To Default Service Account hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 1e749bc9-fde8-471c-af0c-8254efd2dee5 Query name: Role Binding To Default Service Account Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Defaults URL: No role nor cluster role should bind to a default service account<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="11" apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: read-pods namespace: default subjects: kind: User name: jane apiGroup: rbac.authorization.k8s.io kind: ServiceAccount name: default namespace: kube-system roleRef: kind: Role name: pod-reader apiGroup: rbac.authorization.k8s.io ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: read-pods namespace: default subjects: kind: User name: jane apiGroup: rbac.authorization.k8s.io roleRef: kind: Role name: pod-reader apiGroup: rbac.authorization.k8s.io ```
Project: LinuxKit (Provisioning / Automation & Configuration)
File: platform-vbox.md

LinuxKit can run using Oracle VirtualBox. This should work on OSX, Linux and Windows. The standard install should be sufficient. NB: Windows support is not currently working but should be fixed soon. The Virtualbox backend currently supports booting from disks or ISOs. It should work with either BIOS (default) or EFI (with `linuxkit run vbox --uefi ...`). With `linuxkit run vbox` the serial console is redirected to stdio, providing interactive access to the VM. The Virtualbox backend support configuring a persistent disk using the standard `linuxkit` `-disk` syntax. Multiple disks are supported and can be created in `raw` format; other formats that VirtualBox supports can be attached. Note that additional drives are attached to the SATA Controller, unlike the VM disk which is on the IDE Controller. You can select the networking mode, which defaults to the standard `nat`, by using the `-networking` command-line option. Some networking modes (`hostonly`, `bridge`) will require the additional `adapter` parameter to the `-networking` option: ~~~ -networking hostonly,adapter=vboxnet0 ~~~ You can specify more than one `-networking` option to setup multiple adapters. It is recommended to setup the first adapter as `nat`.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_kms_crypto_key_iam_bindings.md

+++ title = "googlekmscryptokeyiam_bindings resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlekmscryptokeyiam_bindings" identifier = "inspec/resources/gcp/googlekmscryptokeyiambindings.md googlekmscryptokeyiambindings resource" parent = "inspec/resources/gcp" +++ This resource is deprecated. Please use google_kms_crypto_key_iam_policy instead Use the `googlekmscryptokeyiam_bindings` InSpec audit resource to test properties of all, or a filtered group of, GCP KMS Crypto Key IAM Bindings. A `googlekmscryptokeyiam_bindings` resource block collects GCP KMS Crypto Key IAM Bindings then tests that group. describe googlekmscryptokeyiambindings(cryptokey_url: 'projects/project/locations/europe-west2/keyRings/key-ring/cryptoKeys/key-name') do it { should exist } end Use this InSpec resource to enumerate roles then test in-depth using `googlekmskeyringiam_binding`. googlekmscryptokeyiambindings(cryptokeyurl: 'projects/project/locations/europe-west2/keyRings/key-ring/cryptoKeys/key-name').iambindingroles.each do |iambinding_role| describe googlekmscryptokeyiambinding(cryptokey_url: 'projects/project/locations/europe-west2/keyRings/key-ring/cryptoKeys/key-name', role: "roles/owner") do it { should exist } its('members') {should include 'user:someuser@domain.com' } end end The following examples show how to use this InSpec audit resource. describe googlekmscryptokeyiambindings(cryptokey_url: 'projects/project/locations/europe-west2/keyRings/key-ring/cryptoKeys/key-name') do its('count') { should be <= 100} end describe googlekmscryptokeyiambindings(cryptokey_url: 'projects/project/locations/europe-west2/keyRings/key-ring/cryptoKeys/key-name') do its('iambindingroles') { should include "roles/storage.admin" } end describe googlekmscryptokeyiambindings(cryptokeyurl: 'projects/project/locations/europe-west2/keyRings/key-ring/cryptoKeys/key-name').where(iambinding_role: "roles/iam.securityReviewer") do it { should_not exist } end This resource supports the following filter criteria: `iambindingrole`. This may be used with `where`, as a block or as a method. `iambindingroles` - an array of googlekmscryptokeyiam_binding role strings e.g. `["roles/compute.admin", "roles/owner"]` Ensure the is enabled for the project where the resource is located.s
Project: Chef InSpec (Provisioning / Security & Compliance)
File: windows_firewall.md

+++ title = "windows_firewall resource" draft = false gh_repo = "inspec" platform = "windows" [menu] [menu.inspec] title = "windows_firewall" identifier = "inspec/resources/os/windowsfirewall.md windowsfirewall resource" parent = "inspec/resources/os" +++ Use the `windows_firewall` Chef InSpec audit resource to test if a firewall profile is correctly configured on a Windows system. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} A `windows_firewall` resource block specifies which profile to validate: describe windows_firewall('name') do it { should be_enabled } end where `('name')` must specify the name of a firewall profile, such as `'Public'`, `'Private'` or `'Domain'` `be_enabled` is a valid matcher for this resource The following example shows how to use this Chef InSpec audit resource. describe windows_firewall('Public') do it { should be_enabled } it { should havedefaultinbound_allowed } its('num_rules') { should eq 219 } end The resource compiles the following list of firewall profile properties: `description` `defaultinboundaction` `defaultoutboundaction` `allowinboundrules` `allowlocalfirewall_rules` `allowlocalipsec_rules` `allowuserapps` `allowuserports` `allowunicastresponsetomulticast` `notifyonlisten` `enablestealthmodeforipsec` `logmaxsize_kilobytes` `log_allowed` `log_blocked` `log_ignored` `num_rules` Each of these properties can be used in two distinct ways: its('defaultinboundaction') { should cmp 'Allow' } or via matcher: it { should havedefaultinbound_action 'Allow' } Shortcuts are defined for: `havedefaultinbound_allow?` `havedefaultoutbound_allow?` {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The `be_enabled` matcher tests if the Profile is enabled: it { should be_enabled }
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: apply-once.eg.md

It's generally used in scenario. ```yaml apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: apply-once-app spec: components: name: hello-world type: webservice properties: image: oamdev/hello-world traits: type: scaler properties: replicas: 1 policies: name: apply-once type: apply-once properties: enable: true ```
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_connect_mysql.md

title: Kubectl-Dba Connect Mysql menu: docs_{{ .version }}: identifier: kubectl-dba-connect-mysql name: Kubectl-Dba Connect Mysql parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Connect to a mysql object Use this cmd to exec into a mysql object's primary pod. ``` kubectl-dba connect mysql [flags] ``` ``` -h, --help help for mysql ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "/home/runner/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --default-seccomp-profile-type string Default seccomp profile --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --password string Password for basic authentication to the API server --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use --username string Username for basic authentication to the API server ``` - Connect to a database.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: beam-2.49.0.md

title: "Apache Beam 2.49.0" date: 2023-07-17 09:00:00 -0400 categories: blog release authors: yhu <!-- 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. --> We are happy to present the new 2.49.0 release of Beam. This release includes both improvements and new functionality. See the for this release. <!--more--> For more information on changes in 2.49.0, check out the . Support for Bigtable Change Streams added in Java `BigtableIO.ReadChangeStream` (). Added Bigtable Read and Write cross-language transforms to Python SDK ((), ()). Allow prebuilding large images when using `--prebuildsdkcontainerengine=cloudbuild`, like images depending on `tensorflow` or `torch` (). Disabled `pip` cache when installing packages on the workers. This reduces the size of prebuilt Python container images (). Select dedicated avro datum reader and writer (Java) (). Timer API for the Go SDK (Go) (). Remove Python 3.7 support. () Fixed KinesisIO `NullPointerException` when a progress check is made before the reader is started (IO) () Long-running Python pipelines might experience a memory leak: . Python SDK's cross-language Bigtable sink mishandles records that don't have an explicit timestamp set: . To avoid this issue, set explicit timestamps for all records before writing to Bigtable. According to git shortlog, the following people contributed to the 2.49.0 release. Thank you to all contributors! Abzal Tuganbay AdalbertMemSQL Ahmed Abualsaud Ahmet Altay Alan Zhang Alexey Romanenko Anand Inguva Andrei Gurau Arwin Tio Bartosz Zablocki Bruno Volpato Burke Davison Byron Ellis Chamikara Jayalath Charles Rothrock Chris Gavin Claire McGinty Clay Johnson Damon Daniel Dopieraa Danny McCormick Darkhan Nausharipov David Cavazos Dip Patel Dmitry Repin Gavin McDonald Jack Dingilian Jack McCluskey James Fricker Jan Lukavsk Jasper Van den Bossche John Casey John Gill Joseph Crowley Kanishk Karanawat Katie Liu Kenneth Knowles Kyle Galloway Liam Miller-Cushon MakarkinSAkvelon Masato Nakamura Mattie Fu Michel Davit Naireen Hussain Nathaniel Young Nelson Osacky Nick Li Oleh Borysevych Pablo Estrada Reeba Qureshi Reuven Lax Ritesh Ghorse Robert Bradshaw Robert Burke Rouslan Saadat Su Sam Rohde Sam Whittle Sanil Jain Shunping Huang Smeet nagda Svetak Sundhar Timur Sultanov Udi Meiri Valentyn Tymofieiev Vlado Djerek WuA XQ Hu Xianhua Liu Xinyu Liu Yi Hu Zachary Houfek alexeyinkin bigduu bullet03 bzablocki jonathan-lemos jubebo magicgoody ruslan-ikhsan sultanalieva-s vitaly.terentyev
Project: Apache NiFi (App Definition and Development / Streaming & Messaging)
File: SECURITY.md

<!-- 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. --> Apache NiFi welcomes the responsible reporting of security vulnerabilities. The NiFi team believes that working with skilled security researchers across the globe is crucial in identifying weaknesses in any technology. If you believe you've found a security issue in our product or service, we encourage you to notify us. We will work with you to resolve the issue promptly. Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue. Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party. Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder. While researching, we'd like to ask you to refrain from: Denial of service Spamming Social engineering (including phishing) of Apache NiFi staff or contractors Any physical attempts against Apache NiFi property or data centers NiFi Security Mailing List: Members of the monitor this private mailing list and respond to disclosures Apache NiFi follows the policy. Thus, any vulnerability is not disclosed by the project until a released version which mitigates the issue is available for download. Once this release is available, the issue is fully documented in the following locations: An email is sent to the same addresses as the release announcement (dev@nifi.apache.org, users@nifi.apache.org, announce@apache.org), security@nifi.apache.org, and oss-security@lists.openwall.com The The Thank you for helping keep Apache NiFi and our users safe!
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: crds-scope.md

title: CRD Scope linkTitle: CRD Scope weight: 60 This page details the various methods to control the scope of a CRD. See the for information on configuring operator scope, such as which namespaces to watch. Custom Resource Definitions (CRDs) contain a scope field that determines whether the resulting Custom Resource (CR) is cluster or namespace scoped. An operator author might use a namespaced-scoped CRD to restrict access to a CR to certain namespaces, or to have different versions of CRs accessible in different namespaces. Alternatively, an operator author might want a cluster-scoped CRD so all namespaces have visibility and access to CRs. The CRD manifests are generated by the `operator-sdk create api` command in `config/crd/bases`. A CRD's `spec.scope` field controls API scope; valid values are . For an Operator-sdk Go project, this value is determined by the `operator-sdk create api --namespaced` boolean flag, which edits the `types.go` file for the resource. For other operator types, the command edits `spec.scope` in the CRD's YAML manifest directly. When creating a new API, the `--namespaced` flag controls whether the resulting CRD will be cluster or namespace scoped. By default, `--namespaced` is set to `true` which sets the scope to `Namespaced`. An example command to create a cluster-scoped API would be: ```console $ operator-sdk create api --group cache --version v1alpha1 --kind Memcached --resource=true --controller=true --namespaced=false ``` You can also manually set the scope in the Go `types.go` file by adding or changing the to your resource. This file is usually located in `api/<version>/<kind>types.go` or `apis/<group>/<version>/<kind>types.go` if you are using the layout. Once this marker is set, the CRD files will be generated with the approriate scope. Here is an example API type with the marker set to cluster scope: ```golang //+kubebuilder:object:root=true //+kubebuilder:subresource:status //+kubebuilder:resource:scope=Cluster // Memcached is the Schema for the memcacheds API type Memcached struct { metav1.TypeMeta `json:",inline"` metav1.ObjectMeta `json:"metadata,omitempty"` Spec MemcachedSpec `json:"spec,omitempty"` Status MemcachedStatus `json:"status,omitempty"` } ``` To set the scope to namespaced, the marker would be set to `//+kubebuilder:resource:scope=Namespaced` instead. The scope can be manually set directly in the CRD's Kind YAML file, normally located in `config/crd/bases/<group>.<domain>_<kind>.yaml`. An example YAML file for a namespace-scoped CRD is shown below: ```YAML apiVersion: apiextensions.k8s.io/v1beta1 kind: CustomResourceDefinition metadata: annotations: controller-gen.kubebuilder.io/version: v0.2.5 creationTimestamp: null name: memcacheds.cache.example.com spec: group: cache.example.com names: kind: Memcached listKind: MemcachedList plural: memcacheds singular: memcached scope: Namespaced subresources: status: {} ... ```
Project: Shifu (Provisioning / Automation & Configuration)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: '' labels: '' assignees: '' Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Describe the solution you'd like A clear and concise description of what you want to happen. Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. Additional context Add any other context or screenshots about the feature request here.
Project: ClickHouse (App Definition and Development / Database)
File: v23.3.19.32-lts.md

sidebar_position: 1 sidebar_label: 2024 Backported in : Remove function `arrayFold` because it has a bug. This closes . This closes . (). Backported in : Fix transfer query to MySQL compatible query. Fixes . Fixes . Fixes . (). Backported in : Handle sigabrt case when getting PostgreSQl table structure with empty array. (). Backported in : Fix issue caught in https://github.com/docker-library/official-images/pull/15846. (). Prevent incompatible ALTER of projection columns (). Fix segfault after ALTER UPDATE with Nullable MATERIALIZED column (). Fix incorrect JOIN plan optimization with partially materialized normal projection (). MergeTree mutations reuse source part index granularity (). Fix invalid memory access in BLAKE3 (Rust) (). Normalize function names in CREATE INDEX (). Fix invalid preprocessing on Keeper (). Fix Integer overflow in Poco::UTF32Encoding (). Remove parallel parsing for JSONCompactEachRow (). Pin alpine version of integration tests helper container (). Fix docker image for integration tests (fixes CI) ().