cwielenb/CNCF-Dataset huggingface dataset:
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-pattern-import.md

layout: default title: mesheryctl-pattern-import permalink: reference/mesheryctl/pattern/import redirect_from: reference/mesheryctl/pattern/import/ type: reference display-title: "false" language: en command: pattern subcommand: import Import a Meshery design Import Helm Charts, Kubernetes Manifest, Docker Compose or Meshery designs by passing remote URL or local file system path to the file. Source type must be provided. YAML and TGZ (with helm only) format of file is accepted, if you are importing Meshery Design OCI file format is also supported If you are providing remote URL, it should be a direct URL to a downloadable file. For example, if the file is stored on GitHub, the URL should be 'https://raw.githubusercontent.com/path-to-file'. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl pattern import [flags] </div> </pre> Import pattern manifest <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl pattern import -f [file/URL] -s [source-type] -n [name] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -f, --file string Path/URL to pattern file -h, --help help for import -n, --name string Name for the pattern file -s, --source-type string Type of source file (ex. manifest / compose / helm / design) </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -t, --token string Path to token file default from current context -v, --verbose verbose output </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.67.md

layout: release date: 2023-03-23 tag: v0.6.67 update components from stylesheet with new style overrides @Abhishek-kumar09 (#7384) [API] Docs: Improve Relationships description @leecalcote (#7375) [Mesheryctl] Chore: change casing of "default" token in unit tests @leecalcote (#7381) [Mesheryctl] Chore: change casing of "default" token in unit tests @leecalcote (#7381) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Aisuko, @Revolyssup, @alphaX86, @l5io and @leecalcote
Project: Goldilocks (Provisioning / Security & Compliance)
File: installation.md

meta: name: description content: "Installation instructions, requirements, and troubleshooting for Goldilocks." kubectl configured in the cluster some workloads with pods (Goldilocks will monitor any workload controller that includes a PodSpec template (`spec.template.spec.containers[]` to be specific). This includes `Deployments`, `DaemonSets`, and `StatefulSets` among others.) metrics-server (a requirement of vpa) golang 1.17+ There are multiple ways to install VPA for use with Goldilocks: Install using the `hack/vpa-up.sh` script from the Install using the The full VPA install includes the updater and the admission webhook for VPA. Goldilocks only requires the recommender. An admission webhook can introduce unexpected results in a cluster if not planned for properly. If installing VPA using the goldilocks chart and the vpa sub-chart, only the VPA recommender will be installed. See the and the Goldilocks for more information. does not require the use of prometheus, but it is supported. The use of prometheus may provide more accurate results. is enabled by default in Autopilot clusters, but you must . You can enable it like so: ``` gcloud container clusters update [CLUSTER-NAME] --enable-vertical-pod-autoscaling {--region [REGION-NAME] | --zone [ZONE-NAME]} ``` NOTE: This does not support using prometheus as a data backend. First, make sure you satisfy the requirements above. ``` helm repo add fairwinds-stable https://charts.fairwinds.com/stable kubectl create namespace goldilocks Helm v2: helm install --name goldilocks --namespace goldilocks fairwinds-stable/goldilocks Helm v3: helm install goldilocks --namespace goldilocks fairwinds-stable/goldilocks ``` The directory contains collections of Kubernetes YAML definitions for installing the controller and dashboard components in cluster. ``` git clone https://github.com/FairwindsOps/goldilocks.git cd goldilocks kubectl create namespace goldilocks kubectl -n goldilocks apply -f hack/manifests/controller kubectl -n goldilocks apply -f hack/manifests/dashboard ``` Pick an application namespace and label it like so in order to see some data: ``` kubectl label ns goldilocks goldilocks.fairwinds.com/enabled=true ``` After that you should start to see VPA objects in that namespace. The default installation creates a ClusterIP service for the dashboard. You can access via port forward: ``` kubectl -n goldilocks port-forward svc/goldilocks-dashboard 8080:80 ``` Then open your browser to
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: user-mode-networking.md

Indicates that this machine relays traffic from the guest through a user-space process running on the host. In some VPN configurations the VPN may drop traffic from alternate network interfaces, including VM network devices. By enabling user-mode networking (a setting of `true`), VPNs observe all podman machine traffic as coming from the host, bypassing the problem. When the qemu backend is used (Linux, Mac), user-mode networking is mandatory and the only allowed value is `true`. In contrast, The Windows/WSL backend defaults to `false`, and follows the standard WSL network setup. Changing this setting to `true` on Windows/WSL informs Podman to replace the WSL networking setup on start of this machine instance with a user-mode networking distribution. Since WSL shares the same kernel across distributions, all other running distributions reuses this network. Likewise, when the last machine instance with a `true` setting stops, the original networking setup is restored.
Project: Daytona (App Definition and Development / Application Definition & Image Build)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: '' labels: enhancement 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: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: sql.md

SQL transform plugin Use SQL to transform given input row. SQL transform use memory SQL engine, we can via SQL functions and ability of SQL engine to implement the transform task. | name | type | required | default value | |-|--|-|| | sourcetablename | string | yes | - | | resulttablename | string | yes | - | | query | string | yes | - | The source table name, the query SQL table name must match this field. The query SQL, it's a simple SQL supported base function and criteria filter operation. But the complex SQL unsupported yet, include: multi source table/rows JOIN and AGGREGATE operation and the like. the query expression can be `select [tablename.]columna` to query the column that named `column_a`. and the table name is optional. or `select crow.cinnerrow.columnb` to query the inline struct column that named `columnb` within `crow` column and `cinnerrow` column. In this query expression, can't have table name. The data read from source is a table like this: | id | name | age | |-|-|--| | 1 | Joy Ding | 20 | | 2 | May Ding | 21 | | 3 | Kin Dom | 24 | | 4 | Joy Dom | 22 | We use SQL query to transform the source data like this: ``` transform { Sql { sourcetablename = "fake" resulttablename = "fake1" query = "select id, concat(name, '_') as name, age+1 as age from fake where id>0" } } ``` Then the data in result table `fake1` will update to | id | name | age | |-|--|--| | 1 | Joy Ding_ | 21 | | 2 | May Ding_ | 22 | | 3 | Kin Dom_ | 25 | | 4 | Joy Dom_ | 23 | if your upstream data schema is like this: ```hacon source { FakeSource { resulttablename = "fake" row.num = 100 string.template = ["innerQuery"] schema = { fields { name = "string" c_date = "date" c_row = { cinnerrow = { cinnerint = "int" cinnerstring = "string" cinnertimestamp = "timestamp" cmap1 = "map<string, string>" cmap2 = "map<string, map<string,string>>" } c_string = "string" } } } } } ``` Those query all are valid: ```sql select name, c_date, c_row, crow.cinner_row, crow.cstring, crow.cinnerrow.cinner_int, crow.cinnerrow.cinner_string, crow.cinnerrow.cinner_timestamp, crow.cinnerrow.cmap_1, crow.cinnerrow.cmap1.somekey ``` But this query are not valid: ```sql select crow.cinnerrow.cmap2.somekey.innermapkey ``` The map must be the latest struct, can't query the nesting map. ``` env { job.mode = "BATCH" } source { FakeSource { resulttablename = "fake" row.num = 100 schema = { fields { id = "int" name = "string" age = "int" } } } } transform { Sql { sourcetablename = "fake" resulttablename = "fake1" query = "select id, concat(name, '_') as name, age+1 as age from fake where id>0" } } sink { Console { sourcetablename = "fake1" } } ``` Support struct query Add SQL Transform Connector
Project: secureCodeBox (Provisioning / Security & Compliance)
File: 08_concepts.md

title: "Cross-cutting Concepts" sidebar_label: "Cross-cutting Concepts" sidebar_position: 8 This section describes the cross-cutting concepts of secureCodeBox. These are concepts which affect all components. Instead of concepts only affecting a single or some components. They are described here particularly because they are not easy exchangeable with something differently. In fact, they are strong coupled dependencies, and therefore must be chosen carefully. :::note Not documented yet. ::: <!-- TODO: https://github.com/secureCodeBox/documentation/issues/236 -->
Project: Chef InSpec (Provisioning / Security & Compliance)
File: security_policy.md

+++ title = "security_policy resource" draft = false gh_repo = "inspec" platform = "windows" [menu] [menu.inspec] title = "security_policy" identifier = "inspec/resources/os/securitypolicy.md securitypolicy resource" parent = "inspec/resources/os" +++ Use the `security_policy` Chef InSpec audit resource to test security policies on the Windows platform. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.0.0 of InSpec. A `security_policy` resource block declares the name of a security policy and the value to be tested: describe security_policy do its('policy_name') { should eq 'value' } end describe securitypolicy(translatesid: true) do its('policyname') { should include 'sidname' } end where `'policy_name'` must specify a security policy `{ should eq 'value' }` tests the value of `policy_name` against the value declared in the test `translate_sid` converts the security identifier (SID) into a human readable SID name if `true`. Default value is `false`. This resource supports any of the security policy name as properties for e.g. `SeNetworkLogonRigth`, `SeRemoteInteractiveLogonRight` etc. its('SeNetworkLogonRight') { should eq '*S-1-5-11' } The following examples show how to use this Chef InSpec audit resource. describe security_policy do its('SeRemoteInteractiveLogonRight') { should eq '*S-1-5-32-544' } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}}
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: configuration-recommendations-for-production-environments.md

title: Resource description description: Kafka resource description keywords: [kafka, java heap, hardware resource] sidebar_position: 3 sidebar_label: Resource description Kafka Server's JVM Heap configuration, production environment can refer to the : ```bash -Xmx6g -Xms6g -XX:MetaspaceSize=96m -XX:+UseG1GC -XX:MaxGCPauseMillis=20 -XX:InitiatingHeapOccupancyPercent=35 -XX:G1HeapRegionSize=16M -XX:MinMetaspaceFreeRatio=50 -XX:MaxMetaspaceFreeRatio=80 -XX:+ExplicitGCInvokesConcurrent ``` Combined mode When creating a Kafka Cluster, specify the `--broker-heap` parameter. Separated mode When creating a Kafka Cluster, specify the component parameters with the `--broker-heap`; specify controller with the `--controller-heap` parameter. :::note When modifying the Java Heap configuration, attention should be paid to the resources allocated to the Cluster at the same time. For example, `--memory=1Gi`, but `-Xms` in `--broker-heap` is specified as `6g`, the broker service will not start normally due to insufficient memory. ::: It is recommended to use the following hardware resource in a production environment: `-cpu` >= 16 cores `-memory` >= 64Gi Since Kafka uses a large amount of Page Cache to improve read and write speed, memory resources outside the heap memory allocated can improve overall performance. `-storage` configure it according to the specific situations The default compression algorithm for Kafka Cluster is `compression.type=producer`, which is specified by the Producer end. Refer to the average message size of the Topic, compression ratio, number of Topic replicas, and data retention time to perform a comprehensive evaluation.
Project: ArangoDB (App Definition and Development / Database)
File: value_lvalue_const.md

+++ title = "`const value_type &value() const &`" description = "Wide contract const lvalue reference observer of any value present. Constexpr propagating." categories = ["observers"] weight = 650 +++ Wide contract const lvalue reference observer of any value present. `NoValuePolicy::widevaluecheck()` is first invoked, then the reference to the value is returned. Note that if `value_type` is `void`, only a `const` overload returning `void` is present. Requires: Always available. Complexity: Depends on `NoValuePolicy::widevaluecheck()`. Guarantees: None.
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: playground.md

title: Guidebook Playground layout: 1: position: default maximized: true 2: position: default maximized: true === "Sequence of Choices" ```bash execute: now maximize: true outputOnly: true commentary --send guidebook-playground -f /kui/madwizard/playground/two-choices.md ``` === "Multi-select" ```bash execute: now maximize: true outputOnly: true commentary --send guidebook-playground -f /kui/madwizard/playground/multi.md ``` === "Form" ```bash execute: now maximize: true outputOnly: true commentary --send guidebook-playground -f /kui/madwizard/playground/form.md ``` === "Graphical Wizard" ```bash execute: now outputOnly: true maximize: true madwizard playground guidebook-playground ``` === "Textual Wizard" ```bash execute: now outputOnly: true maximize: true madwizard playground guidebook-playground --ui=text ```
Project: Rundeck (Provisioning / Automation & Configuration)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: '' assignees: '' Note: Bug Reports not following this template may be closed without feedback. Getting Help Please use this issue template for reporting identified or suspected bugs only. For support on configuration or troubleshooting please see for the appropriate channels. Describe the bug A clear and concise description of what the bug is. My Rundeck detail Rundeck version: [ e.g. 3.3.10] install type: [choose: rpm,deb,war,docker] OS Name/version: [e.g. ubuntu 20.04] DB Type/version: [choose: mysql, postgres, mssql, oracle, ... ] To Reproduce Steps to reproduce the behavior: Go to '...' Click on '....' Scroll down to '....' See error Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Desktop (please complete the following information): OS: [e.g. iOS] Browser [e.g. chrome, safari] Version [e.g. 22] Additional context Add any other context about the problem here.
Project: KICS (Provisioning / Security & Compliance)
File: 737a0dd9-0aaa-4145-8118-f01778262b8a.md

title: Default Service Account In Use hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 737a0dd9-0aaa-4145-8118-f01778262b8a Query name: Default Service Account In Use Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Insecure Configurations URL: Default service accounts should not be actively used<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1 12" resource "kubernetesserviceaccount" "example" { metadata { name = "default" } } resource "kubernetesserviceaccount" "example2" { metadata { name = "default" } automountserviceaccount_token = true } ``` ```tf title="Negative test num. 1 - tf file" resource "kubernetesserviceaccount" "example3" { metadata { name = "default" } automountserviceaccount_token = false } ```
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: v0.11.2.md

Fixed remote actor invocation timeout error on Kubernetes with mTLS enabled (https://github.com/dapr/dapr/issues/2195) fixed in the 0.11.2 release had a bug that caused actors to not work on Kubernetes clusters with mTLS enabled. The root cause was the result of changes made to how Dapr uses server names when doing mutual authentication in sidecar to sidecar gRPC calls. The server name format changed from `cluster.local` to `<app-id>.<namespace>.cluster.local`, and the actors runtime did not pass the namespace to the server name. That led to an authentication error that was reported to the user as a gRPC timeout deadline exceeded error. The issue was fixed with . As an immediate step, we checked why our actor e2e tests did not catch this, as this was supposed to be covered in the test. Further investigation showed that our e2e test for actors did not use Kubernetes pod to pod invocation, which did not create a gRPC connection with the wrong server name. An issue to fix the e2e test was and later .
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_core.Themes.md

/ / Themes .Themes Theme: & { `apiVersion?`: `ThemeApiVersion` ; `attrs?`: `string`[] ; `css`: `string` \| `string`[] ; `description?`: `string` ; `lightweight?`: `boolean` ; `name`: `string` ; `style`: `"light"` \| `"dark"` } findThemeByName(`name`): `Promise`<{ `plugin`: `string` ; `theme`: }\> | Name | Type | | :-- | :- | | `name` | `string` | `Promise`<{ `plugin`: `string` ; `theme`: }\> the Theme model associated with the given theme name getDefaultTheme(): `Promise`<`string`\> `Promise`<`string`\> the name of the default theme `Const` getPersistedThemeChoice(): `Promise`<`string`\> Return the previously selected (and persisted) choice of theme `Promise`<`string`\> `Const` resetToDefaultTheme(): `Promise`<`boolean`\> Reset to the default theme `Promise`<`boolean`\> `Const` switchToTheme(`theme`, `saveNotNeeded?`): `Promise`<`void`\> Internal logic to switch themes | Name | Type | Default value | | :-- | :-- | : | | `theme` | `string` | `undefined` | | `saveNotNeeded` | `boolean` | `false` | `Promise`<`void`\>
Project: YDB (App Definition and Development / Database)
File: load-actors-key-value.md

Loads a key-value tablet. {% include notitle %} ```proto message TKeyValueLoad { message TWorkerConfig { optional string KeyPrefix = 1; optional uint32 MaxInFlight = 2; optional uint32 Size = 11; // data size, bytes optional bool IsInline = 9 [default = false]; optional uint32 LoopAtKeyCount = 10 [default = 0]; // 0 means "do not loop" } optional uint64 Tag = 1; optional uint64 TargetTabletId = 2; optional uint32 DurationSeconds = 5; repeated TWorkerConfig Workers = 7; } ```
Project: ClickHouse (App Definition and Development / Database)
File: update.md

slug: /en/sql-reference/statements/alter/update sidebar_position: 40 sidebar_label: UPDATE ``` sql ALTER TABLE [db.]table [ON CLUSTER cluster] UPDATE column1 = expr1 [, ...] [IN PARTITION partitionid] WHERE filterexpr ``` Manipulates data matching the specified filtering expression. Implemented as a . :::note The `ALTER TABLE` prefix makes this syntax different from most other systems supporting SQL. It is intended to signify that unlike similar queries in OLTP databases this is a heavy operation not designed for frequent use. ::: The `filterexpr` must be of type `UInt8`. This query updates values of specified columns to the values of corresponding expressions in rows for which the `filterexpr` takes a non-zero value. Values are casted to the column type using the `CAST` operator. Updating columns that are used in the calculation of the primary or the partition key is not supported. One query can contain several commands separated by commas. The synchronicity of the query processing is defined by the setting. By default, it is asynchronous. See also setting Blog:
Project: KICS (Provisioning / Security & Compliance)
File: ad296c0d-8131-4d6b-b030-1b0e73a99ad3.md

title: Group With Privilege Escalation By Actions 'iam:UpdateLoginProfile' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ad296c0d-8131-4d6b-b030-1b0e73a99ad3 Query name: Group With Privilege Escalation By Actions 'iam:UpdateLoginProfile' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Group with privilege escalation by actions 'iam:UpdateLoginProfile' and Resource set to '*'. For more information see https://rhinosecuritylabs.com/aws/aws-privilege-escalation-methods-mitigation/.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsiamgroup" "cosmic" { name = "cosmic" } resource "awsiamgrouppolicy" "testinline_policy" { name = "testinlinepolicy" group = awsiamgroup.cosmic.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "iam:UpdateLoginProfile", ] Effect = "Allow" Resource = "*" }, ] }) } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamuser" "cosmic2" { name = "cosmic2" } resource "awsiamuserpolicy" "inlinepolicyruninstances2" { name = "inlinepolicyrun_instances" user = awsiamuser.cosmic2.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "ec2:Describe*", ] Effect = "Allow" Resource = "*" }, ] }) } ```
Project: ArangoDB (App Definition and Development / Database)
File: assume_value_rvalue_const.md

+++ title = "`const valuetype &&assumevalue() const && noexcept`" description = "Narrow contract const rvalue reference observer of any value present. Constexpr propagating, never throws." categories = ["observers"] weight = 630 +++ Narrow contract const rvalue reference observer of any value present. `NoValuePolicy::narrowvaluecheck()` is first invoked, then the reference to the value is returned. The convention is that hard undefined behaviour occurs if no value is actually present, however `NoValuePolicy::narrowvaluecheck()` can do something to avoid that. Note that if `value_type` is `void`, only a `const` overload returning `void` is present. Requires: Always available. Complexity: Depends on `NoValuePolicy::narrowvaluecheck()`. Guarantees: An exception is never thrown.