cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: dee21308-2a7a-49de-8ff7-c9b87e188575.md

title: SSH Access Is Not Restricted hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: dee21308-2a7a-49de-8ff7-c9b87e188575 Query name: SSH Access Is Not Restricted Platform: GoogleDeploymentManager Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: Google Firewall should not allow SSH access (port 22) from the Internet (public CIDR block) to ensure the principle of least privileges<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="10" resources: name: firewall type: compute.v1.firewall properties: name: my-firewall sourceRanges: "0.0.0.0/0" allowed: IPProtocol: icmp ports: "80" "8080" "1000-2000" "22" ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="10" resources: name: firewall type: compute.v1.firewall properties: name: my-firewall sourceRanges: "0.0.0.0/0" allowed: IPProtocol: icmp ports: "80" "8080" "1000-2000" "21-3390" ``` ```yaml title="Positive test num. 3 - yaml file" hl_lines="4" resources: name: firewall type: compute.v1.firewall properties: name: my-firewall sourceRanges: "0.0.0.0/0" allowed: IPProtocol: all ``` ```yaml title="Negative test num. 1 - yaml file" resources: name: firewall type: compute.v1.firewall properties: name: my-firewall allowed: IPProtocol: icmp ports: "80" "8080" "1000-2000" ```
Project: YugabyteDB (App Definition and Development / Database)
File: perf_execute.md

title: EXECUTE statement [YSQL] headerTitle: EXECUTE linkTitle: EXECUTE description: Use the EXECUTE statement to execute a previously prepared statement. menu: v2.18: identifier: perf_execute parent: statements type: docs Use the `EXECUTE` statement to execute a previously prepared statement. This separation is a performance optimization because a prepared statement would be executed many times with different values while the syntax and semantics analysis and rewriting are done only once during `PREPARE` processing. {{%ebnf%}} execute_statement {{%/ebnf%}} Specify the name of the prepared statement to execute. Specify the expression. Each expression in `EXECUTE` must match with the corresponding data type from `PREPARE`. Create a sample table. ```plpgsql yugabyte=# CREATE TABLE sample(k1 int, k2 int, v1 int, v2 text, PRIMARY KEY (k1, k2)); ``` Prepare a simple insert. ```plpgsql yugabyte=# PREPARE ins (bigint, double precision, int, text) AS INSERT INTO sample(k1, k2, v1, v2) VALUES ($1, $2, $3, $4); ``` Execute the insert twice (with different parameters). ```plpgsql yugabyte=# EXECUTE ins(1, 2.0, 3, 'a'); ``` ```plpgsql yugabyte=# EXECUTE ins(2, 3.0, 4, 'b'); ``` Check the results. ```plpgsql yugabyte=# SELECT * FROM sample ORDER BY k1; ``` ``` k1 | k2 | v1 | v2 -+-+-+- 1 | 2 | 3 | a 2 | 3 | 4 | b (2 rows) ```
Project: KubeMQ (App Definition and Development / Streaming & Messaging)
File: kubemq_queues.md

Execute Kubemq 'queues' commands Execute Kubemq 'queues' commands ``` kubemq queues [flags] ``` ``` kubemq queues send kubemq queues attach kubemq queues receive kubemq queues list kubemq queues peek kubemq queues ack kubemq queues stream ``` ``` -h, --help help for queues ``` - - Queues ack all messages in a 'queues' channel - Queues attach to 'queues' channels command - Queues list of 'queues' channels - Queues peek a messages from a queue channel command - Queues receive a messages from a queue channel command - Queues send a message to a queue channel command - Queues stream a message from a queue command
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: pipeline.md

The `Pipeline` represents a data processing job. The most important concept in Numaflow, it defines: A list of , which define the data processing tasks; A list of `edges`, which are used to describe the relationship between the vertices. Note an edge may go from a vertex to multiple vertices, and as of v0.10, an edge may also go from multiple vertices to a vertex. This many-to-one relationship is possible via The `Pipeline` is abstracted as a . A `Pipeline` spec looks like below. ```yaml apiVersion: numaflow.numaproj.io/v1alpha1 kind: Pipeline metadata: name: simple-pipeline spec: vertices: name: in source: generator: rpu: 5 duration: 1s name: cat udf: builtin: name: cat name: out sink: log: {} edges: from: in to: cat from: cat to: out ``` To query `Pipeline` objects with `kubectl`: ```sh kubectl get pipeline # or "pl" as a short name ```
Project: StarRocks (App Definition and Development / Database)
File: cos_similarity_norm.md

displayed_sidebar: "English" Measures the similarity of two normalized vectors by calculating the cosine of the angle between them. The angle is formed by the direction of the vectors while the difference in their magnitude is ignored. This function assumes that the input vectors have been normalized. If you need to normalize vectors before calculating the cosine similarity, use . The similarity is between -1 and 1. Smaller angles between vectors indicate greater cosine similarity. If two vectors have the same direction, they have a 0-degree angle and the cosine similarity is 1. Perpendicular vectors have a 90-degree angle and a cosine similarity of 0. Opposite vectors have a 180-degree angle and a cosine similarity of -1. ```Haskell cosinesimilaritynorm(a, b) ``` `a` and `b` are the vectors to compare. They must have the same dimension. The supported data type is `Array<float>`. The two arrays must have the same number of elements. Otherwise, an error is returned. Returns a FLOAT value within the range of [-1, 1]. If any input parameter is null or invalid, an error is reported. Create a table to store vectors and insert data into this table. ```SQL CREATE TABLE t1_similarity (id int, data array<float>) DISTRIBUTED BY HASH(id); INSERT INTO t1_similarity VALUES (1, array<float>[0.1, 0.2, 0.3]), (2, array<float>[0.2, 0.1, 0.3]), (3, array<float>[0.3, 0.2, 0.1]); ``` Calculate the similarity of each row in the `data` column compared to the array `[0.1, 0.2, 0.3]` and list the result in descending order. ```Plain SELECT id, data, cosinesimilaritynorm([0.1, 0.2, 0.3], data) as dist FROM t1_similarity ORDER BY dist DESC; ++++ | id | data | dist | ++++ | 1 | [0.1,0.2,0.3] | 0.14000002 | | 2 | [0.2,0.1,0.3] | 0.13000001 | | 3 | [0.3,0.2,0.1] | 0.10000001 | ++++ ```
Project: Apollo (Provisioning / Automation & Configuration)
File: nodejs-sdks-user-guide.md

Project address: Thanks for providing support for the NodeJS Apollo client Project address: Thanks for providing support for the NodeJS Apollo client Project address: Thanks for providing support for the NodeJS Apollo client Project address: Thanks for providing support for the NodeJS Apollo client Project address: Thanks for providing support for the NodeJS Apollo client Project address: Thanks for providing support for the NodeJS Apollo client Project address: Thanks for providing support for the NodeJS Apollo client
Project: Meshery (Provisioning / Automation & Configuration)
File: mpi-operator.md

layout: integration title: Kubeflow MPI Operator subtitle: Collaborative and visual infrastructure as code for Mongodb Operator image: /assets/img/integrations/mpi-operator/icons/color/mpi-operator-color.svg permalink: extensibility/integrations/mpi-operator docURL: https://docs.meshery.io/extensibility/integrations/mpi-operator description: integrations-category: Machine Learning integrations-subcategory: Machine Learning registrant: Artifact Hub components: name: mpi-job colorIcon: assets/img/integrations/mpi-operator/components/mpi-job/icons/color/mpi-job-color.svg whiteIcon: assets/img/integrations/mpi-operator/components/mpi-job/icons/white/mpi-job-white.svg description: featureList: [ "Easily run synchronized, allreduce-style distributed training on Kubernetes.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: ArangoDB (App Definition and Development / Database)
File: implicit_failure_exception_copy_constructor.md

+++ title = "`basicoutcome(const failuretype<EP> &)`" description = "Implicit exception-from-failure-type-sugar copy constructor. Available if `predicate::enablecompatibleconversion<void, void, EP, void>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "implicit-constructors", "tagged-constructors"] weight = 534 +++ Implicit exception-from-failure-type-sugar copy constructor used to disambiguate the construction of the exception type. Calls {{% api "void onoutcomecopyconstruction(T *, U &&) noexcept" %}} with `this` and `const failuretype<EP> &`. Requires: `predicate::enablecompatibleconversion<void, void, EP, void>` is true. Complexity: Same as for the `exception_type` constructor which accepts `EP`. Constexpr, triviality and noexcept of underlying operations is propagated.
Project: Percona Server for MySQL (App Definition and Development / Database)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: bug assignees: PJK Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior. If possible, please attach a runnable code snippet. Expected behavior A clear and concise description of what you expected to happen. Environment libcbor version and build configuration flags (or source package version if using a package manager).
Project: YDB (App Definition and Development / Database)
File: datatypes_primitive_datetime.md

| Type | Description | Notes | | -- | -- | -- | | `Date` | Date, precision to the day | Range of values for all time types except `Interval`: From 00:00 01.01.1970 to 00:00 01.01.2106. Internal `Date` representation: Unsigned 16-bit integer | | `Datetime` | Date/time, precision to the second | Internal representation: Unsigned 32-bit integer | | `Timestamp` | Date/time, precision to the microsecond | Internal representation: Unsigned 64-bit integer | | `Interval` | Time interval (signed), precision to microseconds | Value range: From -136 years to +136 years. Internal representation: Signed 64-bit integer. {% if featuremaptables %}Can't be used in the primary key{% endif %} | | `TzDate` | Date with time zone label, precision to the day | Not supported in table columns | | `TzDateTime` | Date/time with time zone label, precision to the second | Not supported in table columns | | `TzTimestamp` | Date/time with time zone label, precision to the microsecond | Not supported in table columns |
Project: Salt Project (Provisioning / Automation & Configuration)
File: 3006.1.md

(release-3006.1)= <! Do not edit this file. This is auto generated. Edit the templates in doc/topics/releases/templates/ for a given release. --> <!-- Add release specific details below --> <!-- Do not edit the changelog below. This is auto generated. --> Check that the return data from the cloud create function is a dictionary before attempting to pull values out. Ensure NamedLoaderContext's have their value() used if passing to other modules add documentation note about reactor state ids. Added support for ``test=True`` to the ``file.cached`` state module Updated `sourcehash` documentation and added a log warning when `sourcehash` is used with a source other than `http`, `https` and `ftp`. Fixed clear pillar cache on every highstate and added cleanpillarcache=False to saltutil functions. Fix dmsetup device names with hyphen being picked up. Update all the scheduler functions to include a fire_event argument which will determine whether to fire the completion event onto the event bus. This event is only used when these functions are called via the schedule execution modules. Update all the calls to the schedule related functions in the deltaproxy proxy minion to include fire_event=False, as the event bus is not available when these functions are called. , Default to a 0 timeout if none is given for the terraform roster to avoid `-o ConnectTimeout=None` when using `salt-ssh` Disable class level caching of the file client on `SaltCacheLoader` and properly use context managers to take care of initialization and termination of the file client. Fixed several file client uses which were not properly terminating it by switching to using it as a context manager whenever possible or making sure `.destroy()` was called when using a context manager was not possible. Fix running setup.py when passing in --salt-config-dir and --salt-cache-dir arguments. Moved /etc/salt/proxy and /lib/systemd/system/salt-proxy@.service to the salt-minion DEB package Stop passing `kwargs` and be explicit about the keyword arguments to pass, namely, to `cp.cache_file` call in `salt.states.pkg` lgporeg.setvalue now returns ``True`` on success instead of ``None`` Make salt user's home /opt/saltstack/salt Fix cmd.run doesn't output changes in test mode Move salt user and group creation to common package Fixed issue in salt-cloud so that multiple masters specified in the cloud are written to the minion config properly Make sure the `salt-ssh` CLI calls it's `fsclient.destroy()` method when done. Stop using the deprecated `salt.transport.client` imports. Add a `.pth` to the Salt onedir env to ensure packages in extras are importable. Bump relenv to 0.12.3. Fix ``lgpo_reg`` state to work with User policy Cloud deployment directories are owned by salt user and group ``lgpo_reg`` state now enforces and reports changes to the registry
Project: Apollo (Provisioning / Automation & Configuration)
File: CODE_OF_CONDUCT.md

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at apollo-config@googlegroups.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. This Code of Conduct is adapted from the , version 1.4, available at
Project: Meshery (Provisioning / Automation & Configuration)
File: meshery-extensions_feature.md

name: Meshery Extensions Feature Request about: Request an enhancement in Meshery Extensions title: '[Extensions]' labels: kind/enhancement, component/extensions assignees: '' <!-- A brief description of what the problem is. (e.g. I need to be able to...) --> <!-- A brief description of the enhancement. --> <!-- Specifics on the approach to fulfilling the feature request. --> <!-- Stipulations of functional behavior or non-functional items that must be in-place in order for the issue to be closed. --> <!-- Any visual diagrams of the desired user interface. --> UI Design For Meshery Extensions in Figma Questions: and
Project: ArangoDB (App Definition and Development / Database)
File: exception_ptr_rethrow_outcome.md

+++ title = "`exceptionptrrethrow<T, EC, EP>`" description = "Policy class defining that the ADL discovered free function `rethrowexception()` should be called on incorrect wide value observation. Inherits publicly from `base`. Can only be used with `basicoutcome`." +++ Note: This policy class specialisation can only be used with `basicoutcome`, not `basicresult`. Use {{% api "exceptionptrrethrow<T, EC, void>" %}} with `basic_result`. Policy class defining that the ADL discovered free function `rethrowexception(impl.assumeexception())` if possible, followed by `rethrowexception(impl.assumeerror())` should be called on incorrect wide value observation. Generally this will ADL discover {{% api "std::rethrowexception()" %}} or `boost::rethrowexception()` depending on the `EC` type. Incorrect wide error observation performs: ```c++ BOOSTOUTCOMETHROWEXCEPTION(badoutcome_access("no error")); ``` Incorrect wide exception observation performs: ```c++ BOOSTOUTCOMETHROWEXCEPTION(badoutcome_access("no exception")); ``` Inherits publicly from {{% api "base" %}}, and its narrow value, error and exception observer policies are inherited from there. Requires: Nothing. Namespace: `BOOSTOUTCOMEV2_NAMESPACE::policy` Header: `<boost/outcome/policy/outcomeexceptionptr_rethrow.hpp>`
Project: YDB (App Definition and Development / Database)
File: flatten_type_by.md

To specify the type of container to convert to, you can use: `FLATTEN LIST BY` For `Optional<List<T>>`, `FLATTEN LIST BY` will unpack the list, treating `NULL` as an empty list. `FLATTEN DICT BY` For `Optional<Dict<T>>`, `FLATTEN DICT BY` will unpack the dictionary, interpreting `NULL` as an empty dictionary. `FLATTEN OPTIONAL BY` To filter the `NULL` values without serialization, specify the operation by using `FLATTEN OPTIONAL BY`. Examples ```sql SELECT t.item.0 AS key, t.item.1 AS value, t.dictcolumn AS originaldict, t.other_column AS other FROM my_table AS t FLATTEN DICT BY dict_column AS item; ``` ```sql SELECT * FROM ( SELECT AsList(1, 2, 3) AS a, AsList("x", "y", "z") AS b ) FLATTEN LIST BY (a, b); ``` ```yql SELECT * FROM ( SELECT "1;2;3" AS a, AsList("x", "y", "z") AS b ) FLATTEN LIST BY (String::SplitToList(a, ";") as a, b); ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: parse_config.md

+++ title = "parse_config resource" draft = false gh_repo = "inspec" platform = "os" [menu] [menu.inspec] title = "parse_config" identifier = "inspec/resources/os/parseconfig.md parseconfig resource" parent = "inspec/resources/os" +++ Use the `parse_config` Chef InSpec audit resource to test arbitrary configuration files. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.0.0 of InSpec. A `parse_config` resource block declares the location of the configuration setting to be tested, and then what value is to be tested. Because this resource relies on arbitrary configuration files, the test itself is often arbitrary and relies on custom Ruby code: output = command('some-command').stdout describe parseconfig(output, { dataconfig_option: value } ) do its('setting') { should eq 1 } end or: audit = command('/sbin/auditctl -l').stdout options = { assignment_regex: /^\s([^:]?)\s:\s(.?)\s$/, multiple_values: true } describe parse_config(audit, options) do its('setting') { should eq 1 } end where each test Must declare the location of the configuration file to be tested Must declare one (or more) settings to be tested May run a command to `stdout`, and then run the test against that output May use options to define how configuration data is to be parsed This resource supports multiple options to parse configuration data. Use the options in an `options` block stated outside of (and immediately before) the actual test. For example: options = { assignment_regex: /^\s([^:]?)\s:\s(.?)\s$/, multiple_values: true } output = command('some-command').stdout describe parse_config(output, options) do its('setting') { should eq 1 } end Use `assignment_regex` to test a key value using a regular expression: 'key = value' may be tested using the following regular expression, which determines assignment from key to value: assignment_regex: /^\s([^=]?)\s=\s(.?)\s$/ Use `comment_char` to test for comments in a configuration file: comment_char: '#' Use `key_values` to test how many values a key contains: key = a b c contains three values. To test that value to ensure it only contains one, use: key_values: 1 Use `multiple_values` if the source file uses the same key multiple times. All values will be aggregated in an array: params['key'] = ['a', 'b'] params['key2'] = ['c'] To use plain key value mapping, use `multiple_values: false`: params['key'] = 'b' params['key2'] = 'c' Use `standalone_comments` to parse comments as a line, otherwise inline comments are allowed: 'key = value # comment' params['key'] = 'value # comment' Use `standalone_comments: false`, to parse the following: 'key = value # comment' params['key'] = 'value' This resource is based on the `parseconfigfile` resource. See the resource for examples. {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}}
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-exp-workspace-list.md

layout: default title: mesheryctl-exp-workspace-list permalink: reference/mesheryctl/exp/workspace/list redirect_from: reference/mesheryctl/exp/workspace/list/ type: reference display-title: "false" language: en command: exp subcommand: workspace List registered workspaces List name of all registered workspaces <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl exp workspace list [flags] </div> </pre> List all registered workspace <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl exp workspace list --orgId [orgId] </div> </pre> Documentation for workspace can be found at: <pre class='codeblock-pre'> <div class='codeblock'> https://docs.layer5.io/cloud/spaces/workspaces/ </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for list -o, --orgId string Organization ID </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -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.