cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: 71397b34-1d50-4ee1-97cb-c96c34676f74.md

title: Lambda Functions Without X-Ray Tracing hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 71397b34-1d50-4ee1-97cb-c96c34676f74 Query name: Lambda Functions Without X-Ray Tracing Platform: Ansible Severity: <span style="color:#edd57e">Low</span> Category: Observability URL: AWS Lambda functions should have TracingConfig enabled. For this, property 'tracing_mode' should have the value 'Active'<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="2 37" name: looped creation community.aws.lambda: name: '{{ item.name }}' state: present zipfile: '{{ item.zipfile }}' runtime: 'python2.7' role: 'arn:aws:iam::987654321012:role/lambdabasicexecution' handler: 'hellopython.myhandler' vpcsubnetids: subnet-123abcde subnet-edcba321 vpcsecuritygroup_ids: sg-123abcde sg-edcba321 environmentvariables: '{{ item.envvars }}' tags: key1: 'value1' loop: name: HelloWorld zip_file: hello-code.zip env_vars: key1: "first" key2: "second" name: ByeBye zip_file: bye-code.zip env_vars: key1: "1" key2: "2" name: looped creation V2 community.aws.lambda: name: '{{ item.name }}' state: present zipfile: '{{ item.zipfile }}' runtime: 'python2.7' role: 'arn:aws:iam::987654321012:role/lambdabasicexecution' handler: 'hellopython.myhandler' tracing_mode: "PassThrough" vpcsubnetids: subnet-123abcde subnet-edcba321 vpcsecuritygroup_ids: sg-123abcde sg-edcba321 environmentvariables: '{{ item.envvars }}' tags: key1: 'value1' loop: name: HelloWorld zip_file: hello-code.zip env_vars: key1: "first" key2: "second" name: ByeBye zip_file: bye-code.zip env_vars: key1: "1" key2: "2" ``` ```yaml title="Negative test num. 1 - yaml file" name: looped creation V3 community.aws.lambda: name: '{{ item.name }}' state: present zipfile: '{{ item.zipfile }}' runtime: python2.7 role: arn:aws:iam::987654321012:role/lambdabasicexecution handler: hellopython.myhandler tracing_mode: Active vpcsubnetids: subnet-123abcde subnet-edcba321 vpcsecuritygroup_ids: sg-123abcde sg-edcba321 environmentvariables: '{{ item.envvars }}' tags: key1: value1 loop: name: HelloWorld zip_file: hello-code.zip env_vars: key1: first key2: second name: ByeBye zip_file: bye-code.zip env_vars: key1: '1' key2: '2' ```
Project: YDB (App Definition and Development / Database)
File: union_all_rules.md

The resulting table includes all columns that were found in at least one of the input tables. If a column wasn't present in all the input tables, then it's automatically assigned the (that can accept `NULL`). If a column in different input tables had different types, then the shared type (the broadest one) is output. If a column in different input tables had a heterogeneous type, for example, string and numeric, an error is raised.
Project: NomsDB (App Definition and Development / Database)
File: HACKING.md

Mac or Linux (Noms isn't currently supported on Windows) ``` git clone https://github.com/attic-labs/noms ``` ``` cd noms go build ./cmd/noms ``` ``` cd noms go test ./go/... go test ./cmd/... ``` Travis automatically creates releases for tagged versions, so the following should do it: ``` git tag latest -f git push origin latest ```
Project: Meshery (Provisioning / Automation & Configuration)
File: 10-27-2023-00-09-10_0ba626af.md

timestamp: "2023-10-27 00:08:55 UTC Fri" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "*name" k8s-distro: minikube k8s-version: "v1.25.2" service-mesh: Consul service-mesh-version: "v1.2.2" tests: consul-client: null consul-server: null overall-status: "failing"
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-registry-publish.md

layout: default title: mesheryctl-registry-publish permalink: reference/mesheryctl/registry/publish redirect_from: reference/mesheryctl/registry/publish/ type: reference display-title: "false" language: en command: registry subcommand: publish Publish Meshery Models to Websites, Remote Provider, Meshery Server Publishes metadata about Meshery Models to Websites, Remote Provider, or Meshery Server, including model and component icons by reading from a Google Spreadsheet and outputing to markdown or json format. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl registry publish [system] [google-sheet-credential] [sheet-id] [models-output-path] [imgs-output-path] [flags] </div> </pre> Publish To System <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl registry publish [system] [google-sheet-credential] [sheet-id] [models-output-path] [imgs-output-path] -o [output-format] </div> </pre> Publish To Meshery <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl registry publish meshery GoogleCredential GoogleSheetID [repo]/server/meshmodel </div> </pre> Publish To Remote Provider <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl registry publish remote-provider GoogleCredential GoogleSheetID [repo]/meshmodels/models [repo]/ui/public/img/meshmodels </div> </pre> Publish To Website <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl registry publish website GoogleCredential GoogleSheetID [repo]/integrations [repo]/ui/public/img/meshmodels </div> </pre> Publishing to meshery docs <pre class='codeblock-pre'> <div class='codeblock'> cd docs; </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl registry publish website $CRED 1DZHnzxYWOlJ69Oguz4LkRVTFM79kC2tuvdwizOJmeMw docs/pages/integrations docs/assets/img/integrations -o md </div> </pre> Publishing to mesheryio site <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl registry publish website $CRED 1DZHnzxYWOlJ69Oguz4LkRVTFM79kC2tuvdwizOJmeMw meshery.io/integrations meshery.io/assets/images/integration -o js </div> </pre> Publishing to layer5 site <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl registry publish website $CRED 1DZHnzxYWOlJ69Oguz4LkRVTFM79kC2tuvdwizOJmeMw layer5/src/collections/integrations layer5/src/collections/integrations -o mdx </div> </pre> Publishing to any website <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl registry publish website $CRED 1DZHnzxYWOlJ69Oguz4LkRVTFM79kC2tuvdwizOJmeMw path/to/models path/to/icons -o mdx </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for publish -o, --output-format string output format [md | mdx | js] </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.
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: bug_report.md

name: Bug report about: Report a bug in Dapr title: '' labels: kind/bug assignees: '' <!-- If you need to report a security issue please visit https://docs.dapr.io/operations/support/support-security-issues --> <!-- Remove the '> ' to select --> /area runtime /area operator /area placement /area docs /area test-and-release <!-- Delete all but your choice --> 1.1.x 1.0.x edge: output of `git describe --dirty` <!-- Briefly describe what you expect to happen --> <!-- Briefly describe what is actually happening --> <!-- How can a maintainer reproduce this issue (be detailed) --> <!-- How should the fix for this issue be communicated in our release notes? It can be populated later. --> <!-- Keep it as a single line. Examples: --> <!-- RELEASE NOTE: ADD New feature in Dapr. --> <!-- RELEASE NOTE: FIX Bug in runtime. --> <!-- RELEASE NOTE: UPDATE Runtime dependency. --> RELEASE NOTE:
Project: Cloud Custodian (Provisioning / Automation & Configuration)
File: ADOPTERS.md

Below is a list of adopters of Cloud Custodian in production environments that have publicly shared the details of their usage as well as the benefits provided by Cloud Custodian that their business relies on. There are some unreferenceable users that are leveraging Cloud Custodian that are not yet able to share details of their usage publicly at this time. There are many additional adopters of Cloud Custodian in the evaluating phase that will be added to this list as they transition to production deployments. Avalara Capital One Code 42 CyberArk Databricks Grupo HBO Max Intuit JP Morgan Chase & Co Premise Data Sage Siemens Zapier
Project: ShardingSphere (App Definition and Development / Database)
File: set-default-single-table-storage-unit.en.md

+++ title = "SET DEFAULT SINGLE TABLE STORAGE UNIT" weight = 3 +++ The `SET DEFAULT SINGLE TABLE STORAGE UNIT` syntax is used to set default single table storage unit. {{< tabs >}} {{% tab name="Grammar" %}} ```sql SetDefaultSingleTableStorageUnit ::= 'SET' 'DEFAULT' 'SINGLE' 'TABLE' 'STORAGE' 'UNIT' singleTableDefinition singleTableDefinition ::= '=' (storageUnitName | 'RANDOM') storageUnitName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} `STORAGE UNIT` needs to use storage unit managed by RDL. The `RANDOM` keyword stands for random storage. Set a default single table storage unit ```sql SET DEFAULT SINGLE TABLE STORAGE UNIT = ds_0; ``` Set the default single table storage unit to random storage ```sql SET DEFAULT SINGLE TABLE STORAGE UNIT = RANDOM; ``` `SET`, `DEFAULT`, `SINGLE`, `TABLE`, `STORAGE`, `UNIT`, `RANDOM`
Project: Checkov (Provisioning / Security & Compliance)
File: Git History.md

layout: default published: false title: Git History nav_order: 20 Checkov supports scanning of secrets in git history to identify and flag secrets, that might not be in the head commit of the branch but are still visible by accessing the git history of the repo. Checkov fetches all the available commits and uses same scan as the Checkov 'secrets' checkov framework to search for secrets in the diff available from git history. Each secret found can be traced to the first commit in which it appeared and the last commit that contained the secret if it was removed. Git history scan uses the same signatures and models as a regular secrets scan. The only difference is that the root directory is the path to either the root git directory or the bare git repo. Using the `--scan-secrets-history` flag will scan git history for secrets only. This will not scan for other issues such as IaC misconfiguration. Use `--secrets-history-timeout` to set how long the secrets scan will run on history before stopping. If the timeout was not enough to finish the run, no results will be returned. The default is `12h`. A run with a timeout of `12h` by default: ```bash checkov -d <git dir> --scan-secrets-history --bc-api-key <yourapikey> ``` A run with a timeout of `1h`: ```bash checkov -d <git dir> --scan-secrets-history --secrets-history-timeout 1h --bc-api-key <yourapikey> ``` on https://github.com/bridgecrewio/detect-secrets repo: ```bash _| | _ | | / | '_ \ / _ \/ | |/ / _ \ \ / / | (| | | | / (| < (_) \ V / \_|_| |_|\|\|_|\_\/ \/ By Prisma Cloud | version: 2.3.172 secrets scan results: Passed checks: 0, Failed checks: 320, Skipped checks: 0 Check: CKVSECRET6: "Base64 High Entropy String" FAILED for resource: 732a8470a9623e89355d477688afd7f8f4d55e03 Severity: LOW File: /tests/plugins/azurestoragekey_test.py:12-13; Commit Added: 018c9d1ee2a152a82c612ee82c0cd952a4f3eae4 Guide: https://docs.prismacloud.io/en/enterprise-edition/policy-reference/secrets-policies/secrets-policy-index/git-secrets-6 12 | 'Accoun*', # noqa: E501 Check: CKVSECRET6: "Base64 High Entropy String" FAILED for resource: b57a3ad258d7674d2005a53aaa67460e25791f71 Severity: LOW File: /tests/plugins/keyword_test.py:22-23; Commit Added: 01cde918f5f471cb0e03964db37f905e5bcdd1cf; Commit Removed: e01d818ad118b0b1fccb1cc9b406e7aa1539e242 Guide: https://docs.prismacloud.io/en/enterprise-edition/policy-reference/secrets-policies/secrets-policy-index/git-secrets-6 22 | 'PASSWORD = "ve"' Check: CKVSECRET2: "AWS Access Key" FAILED for resource: d70eab08607a4d05faa2d0d6647206599e9abc65 Severity: LOW File: /testdiff/testdata/add_sample.diff:10-11; Commit Added: 07d52374f6d1ccc8709069be43139a6ba7ae544b Guide: https://docs.prismacloud.io/en/enterprise-edition/policy-reference/secrets-policies/secrets-policy-index/git-secrets-2 ... ```
Project: Meshery (Provisioning / Automation & Configuration)
File: superedge.md

layout: integration title: Superedge subtitle: Collaborative and visual infrastructure as code for Superedge image: /assets/img/integrations/superedge/icons/color/superedge-color.svg permalink: extensibility/integrations/superedge docURL: https://docs.meshery.io/extensibility/integrations/superedge description: integrations-category: Provisioning integrations-subcategory: Automation & Configuration registrant: Artifact Hub components: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "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: StarRocks (App Definition and Development / Database)
File: SET_PROPERTY.md

displayed_sidebar: "English" Sets user properties. Currently, only the number of user connections (`maxuserconnections`) can be set using this command. :::tip The user properties mean the properties of users, not user_identity. For example, if two users, 'jack'@'%' and 'jack'@'192.%', are created using CREATE USER, the SET PROPERTY statement works only on user `jack``, not 'jack'@'%' or 'jack'@'192.%'. Only users with the `user_admin` role can perform this operation. ::: ```SQL SET PROPERTY [FOR 'user'] 'key' = 'value' [, 'key' = 'value'] ``` Modify the maximum number of connections to `1000` for user `jack`. ```SQL SET PROPERTY FOR 'jack' 'maxuserconnections' = '1000'; ``` <!-- Modify cpu_share to 1000 for the user jack ```SQL SET PROPERTY FOR 'jack' 'resource.cpu_share' = '1000'; ``` Modify the weight of the normal level for the user jack ```SQL SET PROPERTY FOR 'jack' 'quota.normal' = '400'; ``` -->
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.1.0.2.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Major | Make streaming to handle non-utf8 byte array* Streaming allows binary (or other non-UTF8) streams. | Major | Allow more aggressive action on detection of the jetty issue* added new configuration variables to control when TT aborts if it sees a certain number of exceptions: // Percent of shuffle exceptions (out of sample size) seen before it's // fatal - acceptable values are from 0 to 1.0, 0 disables the check. // ie. 0.3 = 30% of the last X number of requests matched the exception, // so abort. conf.getFloat( "mapreduce.reduce.shuffle.catch.exception.percent.limit.fatal", 0); // The number of trailing requests we track, used for the fatal // limit calculation conf.getInt("mapreduce.reduce.shuffle.catch.exception.sample.size", 1000);
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: writing-tests-for-actions.md

id: writing-tests-for-actions title: Writing Tests For Actions description: How to write tests for actions Once you created a new action, your own custom one, or you would like to contribute new actions, you have to cover it with Unit tests to be sure that your actions do what they suppose to do. Make sure that you cover the most of scenario's, which could happen with the action. One of indispensable part of the test is to supply the context to a handler of action for the execution. We encourage you to use a utility method for that, so your tests are immune to structural changes of context. What is inevitably going to happen during the time. Example how to use it: ```typescript import { createMockActionContext } from '@backstage/plugin-scaffolder-node-test-utils'; const mockContext = createMockActionContext({ input: { repoUrl: 'dev.azure.com?repo=repo&owner=owner&organization=org' }, }); await action.handler(mockContext); expect(mockContext.output).toHaveBeenCalledWith( 'remoteUrl', 'https://dev.azure.com/organization/project/_git/repo', ); ``` One thing to be aware about: if you would like to call `createMockActionContext` inside `it`, you have to provide a `workspacePath`. By default, `createMockActionContext` uses `import { createMockDirectory } from '@backstage/backend-test-utils';` to create it for you. This implementation contains a hook inside which creates this limitation. So in this case you can do then: ```typescript describe('github:autolinks:create', async () => { const workspacePath = createMockDirectory().resolve('workspace'); // ... it('should call the githubApis for creating alphanumeric autolink reference', async () => { // ... await action.handler( createMockActionContext({ input: { repoUrl: 'github.com?repo=repo&owner=owner', keyPrefix: 'TICKET-', urlTemplate: 'https://example.com/TICKET?query=<num>', }, workspacePath, }), ); //... }); }); ```
Project: YugabyteDB (App Definition and Development / Database)
File: tsrem.md

title: TSREM linkTitle: TSREM description: TSREM menu: preview: parent: api-yedis weight: 2450 aliases: /preview/api/redis/tsrem /preview/api/yedis/tsrem type: docs `TSREM key timestamp [timestamp ...]` This command removes one or more specified timestamps from the time series that is associated with the given `key`. If the `key` exists, but is not of time series type, an error is raised. If the given `timestamp` is not a valid signed 64 bit integer, an error is raised. If the provided timestamps don't exist, TSREM still returns "OK". As a result, TSREM just ensures the provided timestamps no longer exist, but doesn't provide any information about whether they existed before the command was run. Returns the appropriate status string. The timestamp can be arbitrary integers used just for sorting values in a certain order. ```sh TSADD ts_key 1 one 2 two 3 three 4 four 5 five 6 six ``` ``` "OK" ``` ```sh TSGET ts_key 2 ``` ``` "two" ``` ```sh TSGET ts_key 3 ``` ``` "three" ``` ```sh TSRANGEBYTIME ts_key 1 4 ``` ``` 1) "1" 2) "one" 3) "2" 4) "two" 5) "3" 6) "three" 7) "4" 8) "four" ``` ```sh TSREM ts_key 2 3 ``` ``` "OK" ``` ```sh TSRANGEBYTIME ts_key 1 4 ``` ``` 1) "1" 2) "one" 3) "4" 4) "four" ``` ```sh TSGET ts_key 2 ``` ``` (nil) ``` ```sh TSGET ts_key 3 ``` ``` (nil) ``` , , , , ,
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-data-sources.md

layout: global title: Data Sources displayTitle: Data Sources 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. Spark SQL supports operating on a variety of data sources through the DataFrame interface. A DataFrame can be operated on using relational transformations and can also be used to create a temporary view. Registering a DataFrame as a temporary view allows you to run SQL queries over its data. This section describes the general methods for loading and saving data using the Spark Data Sources and then goes into specific options that are available for the built-in data sources. * * * * * * * * * * * * * * * *
Project: Puppet (Provisioning / Automation & Configuration)
File: windows.md

If you'd like to run Puppet from source on Windows platforms, follow the to using bundler and installing the necessary gems on Windows. You will need to install Ruby on Windows from or from . C:\> cd C:\work\puppet C:\work\puppet> gem install bundler C:\work\puppet> bundle install --path .bundle C:\work\puppet> bundle exec puppet --version 4.7.1 When writing a test that cannot possibly run on Windows, e.g. there is no mount type on windows, do the following: describe Puppet::MyClass, :unless => Puppet::Util::Platform.windows? do .. end If the test doesn't currently pass on Windows, e.g. due to on going porting, then use an rspec conditional pending block: pending("porting to Windows", :if => Puppet::Util::Platform.windows?) do <example1> end pending("porting to Windows", :if => Puppet::Util::Platform.windows?) do <example2> end Then run the test as: C:\work\puppet> bundle exec rspec spec/path/to/test.rb Don't assume file paths start with '/', as that is not a valid path on Windows. Use Puppet::Util.absolute\_path? to validate that a path is fully qualified. Use File.expand\_path('/tmp') in tests to generate a fully qualified path that is valid on POSIX and Windows. In the latter case, the current working directory will be used to expand the path. Always use binary mode when performing file I/O, unless you explicitly want Ruby to translate between unix and dos line endings. For example, opening an executable file in text mode will almost certainly corrupt the resulting stream, as will occur when using: IO.open(path, 'r') { |f| ... } IO.read(path) If in doubt, specify binary mode explicitly: IO.open(path, 'rb') Don't assume file paths are separated by ':'. Use `File::PATH_SEPARATOR` instead, which is ':' on POSIX and ';' on Windows. On Windows, `File::SEPARATOR` is '/', and `File::ALT_SEPARATOR` is '\'. On POSIX systems, `File::ALT_SEPARATOR` is nil. In general, use '/' as the separator as most Windows APIs, e.g. CreateFile, accept both types of separators. Don't use waitpid/waitpid2 if you need the child process' exit code, as the child process may exit before it has a chance to open the child's HANDLE and retrieve its exit code. Use Puppet::Util::Execution.execute. Don't assume 'C' drive. Use environment variables to look these up: "#{ENV['windir']}/system32/netsh.exe"
Project: ClickHouse (App Definition and Development / Database)
File: settings_changes.md

slug: /en/operations/system-tables/settings_changes Contains information about setting changes in previous ClickHouse versions. Columns: `version` () The ClickHouse version in which settings were changed `changes` ( of ) A description of the setting changes: (setting name, previous value, new value, reason for the change) Example ``` sql SELECT * FROM system.settings_changes WHERE version = '23.5' FORMAT Vertical ``` ``` text Row 1: version: 23.5 changes: [('inputformatparquetpreserveorder','1','0','Allow Parquet reader to reorder rows for better parallelism.'),('parallelizeoutputfromstorages','0','1','Allow parallelism when executing queries that read from file/url/s3/etc. This may reorder rows.'),('usewithfillbysortingprefix','0','1','Columns preceding WITH FILL columns in ORDER BY clause form sorting prefix. Rows with different values in sorting prefix are filled independently'),('outputformatparquetcompliantnested_types','0','1','Change an internal field name in output Parquet file schema.')] ``` See also