cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: 819d50fd-1cdf-45c3-9936-be408aaad93e.md

title: Security Center Pricing Tier Is Not Standard hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 819d50fd-1cdf-45c3-9936-be408aaad93e Query name: Security Center Pricing Tier Is Not Standard Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Make sure that the 'Standard' pricing tiers were selected.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="2" resource "azurermsecuritycentersubscriptionpricing" "positive1" { tier = "Free" } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermsecuritycentersubscriptionpricing" "negative1" { tier = "Standard" } ```
Project: StarRocks (App Definition and Development / Database)
File: hll_empty.md

displayed_sidebar: "English" Generates an empty HLL column to supplement the default values when inserting or loading data. ```Haskell HLL_EMPTY() ``` Returns an empty HLL. Supplement the default values when inserting data. ```plain text insert into hllDemo(k1,v1) values(10,hll_empty()); ``` Supplement the default values when loading data. ```plain text curl --location-trusted -u <username>:<password> \ -H "columns: temp1, temp2, col1=hllhash(temp1), col2=hllempty()" \ -T example7.csv -XPUT \ http://<fehost>:<fehttpport>/api/testdb/table7/streamload ```
Project: Shifu (Provisioning / Automation & Configuration)
File: develop-on-mac.md

Welcome developers! This guide will help you on setting up development environment for `Shifu` on `Mac OS` ``` MacBook Pro (14-inch, 2021) ``` Please submit an to GitHub if you are having issue following this guide/you have noticed anything wrong with this guide. From , install ```homebrew``` with the following command: ``` /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" ``` *(Optional)* If you need to proxy connections from your terminal: ``` export http_proxy='http://[proxyServerAddr]:[port]' export https_proxy='http://[proxyServerAddr]:[port]' export ALL_PROXY='http://[proxyServerAddr]:[port]' ``` Use the following command to clone *Shifu*: ```sh git clone https://github.com/Edgenesis/shifu.git ``` Follow the official from Docker official website. the installation dmg and install. After installation, use "File --> Open Folder" to open *Shifu* directory: A prompt should show up automatically to open this project in remote container: Click on that, VSCode should open your project in remote container. Your development environment is ready! *Note*: If you use `Visual Studio Code` with `Dev Container` you can skip all below environment setup steps. Depending on your Mac's CPU architecture, you can download one of the following packagaes: For Intel(amd64) Macs: ``` https://go.dev/dl/go1.22.0.darwin-amd64.pkg ``` For M1(arm64) Macs: ``` https://go.dev/dl/go1.22.0.darwin-arm64.pkg ``` from , install with: ```sh brew install kind ``` from , install with: ```sh brew install kubectl ``` from , install with: ```sh curl -L -o kubebuilder https://go.kubebuilder.io/dl/latest/$(go env GOOS)/$(go env GOARCH) chmod +x kubebuilder && mv kubebuilder /usr/local/bin/ ``` Navigate to `shifu`'s directory, issue: ```sh GO111MODULE=on go mod download ``` *(Optional)* If you are having issue download dependencies, add a proxy by using: ```sh GOPROXY=https://goproxy.cn,direct GO111MODULE=on go mod download ``` Follow our and start building `Shifu`.
Project: Meshery (Provisioning / Automation & Configuration)
File: aws-target-group-binding.md

layout: integration title: AWS Target Group Binding subtitle: Collaborative and visual infrastructure as code for AWS Target Group Binding image: /assets/img/integrations/aws-target-group-binding/icons/color/aws-target-group-binding-color.svg permalink: extensibility/integrations/aws-target-group-binding docURL: https://docs.meshery.io/extensibility/integrations/aws-target-group-binding description: integrations-category: Cloud Native Network integrations-subcategory: Service Proxy registrant: Artifact Hub components: name: target-group-binding colorIcon: assets/img/integrations/aws-target-group-binding/components/target-group-binding/icons/color/target-group-binding-color.svg whiteIcon: assets/img/integrations/aws-target-group-binding/components/target-group-binding/icons/white/target-group-binding-white.svg description: featureList: [ "Expose your pods using an existing ALB TargetGroup or NLB TargetGroup.", "Allows you to provision the load balancer infrastructure completely outside of Kubernetes.", "Used by AWS LoadBalancer controller internally to support the functionality for Ingress and Service resource as well." ] 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: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_plugin_s3.MinioConfig.md

/ / MinioConfig .MinioConfig aliases: `Record`<`string`, { `accessKey`: `string` ; `api`: `string` ; `path`: `"auto"` \| `"dns"` ; `secretKey`: `string` ; `subdir`: `string` ; `url`: `string` }\> version: `string`
Project: MongoDB (App Definition and Development / Database)
File: zstdgrep.1.md

zstdgrep(1) -- print lines matching a pattern in zstandard-compressed files ============================================================================ SYNOPSIS -- `zstdgrep` [<grep-flags>] [--] <pattern> [<files> ...] DESCRIPTION -- `zstdgrep` runs `grep`(1) on files, or `stdin` if no files argument is given, after decompressing them with `zstdcat`(1). The <grep-flags> and <pattern> arguments are passed on to `grep`(1). If an `-e` flag is found in the <grep-flags>, `zstdgrep` will not look for a <pattern> argument. Note that modern `grep` alternatives such as `ripgrep` (`rg`(1)) support `zstd`-compressed files out of the box, and can prove better alternatives than `zstdgrep` notably for unsupported complex pattern searches. Note though that such alternatives may also feature some minor command line differences. EXIT STATUS -- In case of missing arguments or missing pattern, 1 will be returned, otherwise 0. SEE ALSO -- `zstd`(1) AUTHORS Thomas Klausner <wiz@NetBSD.org>
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: local-development-environments.md

Even though Lagoon has only a hard dependency on Docker and \(which is mostly shipped with Docker\) there are some things which are nice for local development that are not included in Docker: An HTTP reverse proxy for nice URLs and HTTPS offloading. A DNS system so we don't have to remember IP addresses. SSH agents to use SSH keys within containers. A system that receives and displays mail locally. ???+ warning You do not need to install Lagoon locally to use it locally! That sounds confusing but follow the documentation. Lagoon is the system that deploys your local development environment to your production environment, it's not the environment itself. Lagoon has traditionally worked best with `pygmy` , which is the amazee.io flavored system of the above tools and works out of the box with Lagoon. It lives at `pygmy` is written in Golang, so to install it, run: ```bash title="Install with HomeBrew" brew tap pygmystack/pygmy && brew install pygmy ``` For detailed usage or installation info on pygmy, see its . Lagoon is well-integrated with Lando! For more information, please see the documentation at to get yourself up and running. Lando's workflow for Lagoon will be familiar to users of Lando, and will also be the easiest way for Lagoon newcomers to get up and running. Pygmy presents a closer integration with Docker, which will lend itself better to more complex scenarios and use cases but will also require a deeper understanding. Lagoon is also supported on DDEV! Check out their documentation to get started: . We have previously evaluated adding support for other systems like and , and while we may add support for these in the future, our current focus is on supporting our current tools.
Project: KICS (Provisioning / Security & Compliance)
File: 63ae3638-a38c-4ff4-b616-6e1f72a31a6a.md

title: Cloud Storage Anonymous or Publicly Accessible hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 63ae3638-a38c-4ff4-b616-6e1f72a31a6a Query name: Cloud Storage Anonymous or Publicly Accessible Platform: GoogleDeploymentManager Severity: <span style="color:#ff0000">Critical</span> Category: Access Control URL: Cloud Storage Buckets must not be anonymously or publicly accessible, which means the subattribute 'entity' from attributes 'acl' and 'defaultObjectAcl' must not be 'allUsers' or 'allAuthenticatedUsers'<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4" resources: name: storage-bucket type: storage.v1.bucket properties: name: my-bucket ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="4 7" resources: name: storage-bucket type: storage.v1.bucket properties: name: my-bucket defaultObjectAcl: entity: allAuthenticatedUsers ``` ```yaml title="Positive test num. 3 - yaml file" hl_lines="10 7" resources: name: storage-bucket type: storage.v1.bucket properties: name: my-bucket acl: entity: allUsers entity: user-liz@example.com defaultObjectAcl: entity: allAuthenticatedUsers entity: user-liz@example.com ``` ```yaml title="Negative test num. 1 - yaml file" resources: name: storage-bucket type: storage.v1.bucket properties: name: my-bucket acl: entity: user-liz@example.com defaultObjectAcl: entity: user-liz@example.com ```
Project: CloudMatos (Provisioning / Security & Compliance)
File: COMMUNITY.md

This is the starting point for joining and contributing to the . Improve docs, codebase, unit and integration tests Extend support to more cloud platforms and Services Augment observability data for enhanced detection Suggest and discuss new features, updates, use cases Report Become a Maintainer[MatosMaintainers] Follow the to setup and get started. For all collaboration and communication going on in Matos Project, please read and follow our . We have dedicated workspace. We are happy to talk to you! Chat with other people about Matos Connect to other Matos developers and maintainers Get help and answers from Matos community Do not report bugs or issues @here, report at Newsletters FAQ's Meetings Tutorials
Project: SPIFFE (Provisioning / Key Management)
File: ERIC_LEE.md

Nomination submitted by @anvega: Eric Lee is Staff Software Engineer and previously Site Reliability Engineer at GitHub. In his role, he is responsible for making SPIFFE and SPIRE available to engineers at GitHub. Eric understands the ins and outs of going from idea to production, as well as deep understanding of the challenges of making SPIFFE available to multiple teams once in production. As such, he has a good grasp on the pains and needs of prospective adopters and end users alike. Additionally, he has been a long time supporter and evangelist of the projects. His personal style is characterized for his pragmatism - he is a great asset whenever dealing with problems or tough conversations that require decision making. Eric has answered the following questions in support of his nomination. What makes you a good fit for the SPIFFE Steering Committee? I am a good fit for the steering committee because I bring the perspective of a SPIFFE project user and operator at an organization with a diverse set of infrastructures and workloads: Cloud, On-premise, containerized, and not. I have been a member of the community from the first Scytale in-person community days and have presented my team's work at community events. I am familiar with the problem space and the organizational and non-technical perspective of framing the value proposition to users across Security, Operations, and Product as well as the regulatory concerns of building high assurance software for regulated environments. What aspects of SSC participation are you most excited about? I am most excited about making SPIFFE more approachable and turn-key for the uninitiated user. The problem space of issuing cryptographic identity to workloads is challenging and a high-risk change for organizations. While introducing SPIFFE to my organization I have always found the existing community welcoming, responsive and thoughtful in its assistance to me and my teams. There is context as an operator of the system I would like to see incorporated into the project's priorities from an operability and debugability standpoint, by bringing these challenges to light or popularizing existing community solutions. I think we've only seen the beginning of SPIFFE's utility to the software world. Is there anything else you'd like to say as part of your nomination? Should I not be elected I would welcome the opportunity to continue contributing to the community and elected SSC members by sharing whatever context I can. GitHub Handle: @elee Email Address: elee@github.com LinkedIn Profile: https://www.linkedin.com/in/elee1/ Current Affiliation: GitHub
Project: KICS (Provisioning / Security & Compliance)
File: b1d51728-7270-4991-ac2f-fc26e2695b38.md

title: Disk Encryption Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b1d51728-7270-4991-ac2f-fc26e2695b38 Query name: Disk Encryption Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: VM disks for critical VMs must be encrypted with Customer Supplied Encryption Keys (CSEK) or with Customer-managed encryption keys (CMEK), which means the attribute 'diskencryptionkey' must be defined and its sub attributes 'rawkey' or 'kmskeyselflink' must also be defined<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1 22" resource "googlecomputedisk" "positive1" { name = "test-disk" type = "pd-ssd" zone = "us-central1-a" image = "debian-9-stretch-v20200805" labels = { environment = "dev" } physicalblocksize_bytes = 4096 } resource "googlecomputedisk" "positive2" { name = "test-disk" type = "pd-ssd" zone = "us-central1-a" image = "debian-9-stretch-v20200805" labels = { environment = "dev" } physicalblocksize_bytes = 4096 diskencryptionkey { sha256 = "A" } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="12" resource "googlecomputedisk" "positive3" { name = "test-disk" type = "pd-ssd" zone = "us-central1-a" image = "debian-9-stretch-v20200805" labels = { environment = "dev" } physicalblocksize_bytes = 4096 diskencryptionkey { raw_key = "" sha256 = "A" } } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="12" resource "googlecomputedisk" "positive4" { name = "test-disk" type = "pd-ssd" zone = "us-central1-a" image = "debian-9-stretch-v20200805" labels = { environment = "dev" } physicalblocksize_bytes = 4096 diskencryptionkey { kmskeyself_link = "" sha256 = "A" } } ``` ```tf title="Negative test num. 1 - tf file" resource "googlecomputedisk" "negative1" { name = "test-disk" type = "pd-ssd" zone = "us-central1-a" image = "debian-9-stretch-v20200805" labels = { environment = "dev" } physicalblocksize_bytes = 4096 diskencryptionkey { raw_key = "SGVsbG8gZnJvbSBHb29nbGUgQ2xvdWQgUGxhdGZvcm0=" sha256 = "A" } } ``` ```tf title="Negative test num. 2 - tf file" resource "googlecomputedisk" "negative1" { name = "test-disk" type = "pd-ssd" zone = "us-central1-a" image = "debian-9-stretch-v20200805" labels = { environment = "dev" } physicalblocksize_bytes = 4096 diskencryptionkey { kmskeyself_link = "disk-crypto-key" sha256 = "A" } } ```
Project: ThreatMapper (Provisioning / Security & Compliance)
File: demo.md

title: Quickstart Demo To get a quick overview of the ThreatMapper UI and operational processes, you can access the Demo sandbox: URL: https://threatmapper.deepfence.show/ Username: `community@deepfence.io` Password: `mzHAmWa!89zRD$KMIZ@ot4SiO` The credentials provide read-only access to a live ThreatMapper instance. You can explore the application topology, initiate vulnerability and other scans, review results and inspect the configuration for scanning registries and configuring notifications.
Project: Salt Project (Provisioning / Automation & Configuration)
File: CustomAction01.md

* 2016-11.15 mkr If I set TargetFrameworkVersion to v4.0, in order to access the 32bit registry from 64bit Windows 0) The code static RegistryKey wrGetKey(string k, bool sw32) { return RegistryKey.OpenBaseKey(RegistryHive.LocalMachine, sw32 ? RegistryView.Registry32 : RegistryView.Registry64).OpenSubKey(k); } 1) I get a warning that make no sense C:\windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(983,5): warning MSB3644: The reference assemblies for framework ". NETFramework,Version=v4.0" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your a pplication to a version of the framework for which you have the SDK or Targeting Pack installed. Note that assemblies will be resolved from the Global Assembly Cache (GAC) and will be used in place of reference assemblies. Therefore your assembly may not be correctly targeted f or the framework you intend. [C:\git\salt-windows-msi\wix\MinionConfigurationExtension\MinionConfigurationExtension.csproj] whereas the log contains SFXCA: Binding to CLR version v4.0.30319 2) This program finds the 32 bit NSIS in the 64 bit registry. This is no good. I postpone to understand this and do not change TargetFrameworkVersion (leaving it at v2.0). Archive for the attempt to read settings from conf/minion into a ini file. Idea was 1) read simple keys from the config file into a ini file 2) read properties from ini file. Idea failed because reading ini files (in Appsearch) always preceeds reading a config file in Customaction before="Appsearch". The ini file Search path is c:\windows The ini file is read by WiX IniFileSearch in product.wxs List<string> iniContent = new List<string>(); iniContent.Add("[Backup]"); What should be the "known location" to store settings after uninstall? string iniFilePath32 = @"C:\windows\system32\config\systemprofile\Local\SaltStack\Salt\"; string iniFilePath64 = @"C:\windows\SysWOW64\config\systemprofile\Local\SaltStack\Salt\"; string iniFile = iniFilePath32 + @"MinionConfigBackup.ini"; System.IO.Directory.CreateDirectory(iniFilePath32); write_this(iniFile, iniContent.ToArray()); private static void write_this(string thefile, string[] thecontent) { using (var fs = new FileStream(thefile, FileMode.OpenOrCreate, FileAccess.ReadWrite)) { using (var fw = new StreamWriter(fs)) { foreach (string line in thecontent) { fw.Write(line); fw.Write(System.Environment.NewLine); }; fw.Flush(); // Added } fs.Flush(); } }
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: filter.md

A `filter` is a special-purpose built-in function. It is used to evaluate on each message in a pipeline and is often used to filter the number of messages that are passed to next vertices. Filter function supports comprehensive expression language which extend flexibility write complex expressions. `payload` will be root element to represent the message object in expression. Filter expression implemented with `expr` and `sprig` libraries. These function can be accessed directly in expression. `json` - Convert payload in JSON object. e.g: `json(payload)` `int` - Convert element/payload into `int` value. e.g: `int(json(payload).id)` `string` - Convert element/payload into `string` value. e.g: `string(json(payload).amount)` `Sprig` library has 70+ functions. `sprig` prefix need to be added to access the sprig functions. E.g: `sprig.contains('James', json(payload).name)` # `James` is contained in the value of `name`. `int(json(sprig.b64dec(payload)).id) < 100` ```yaml name: filter-vertex udf: builtin: name: filter kwargs: expression: int(json(payload).id) < 100 ```
Project: YugabyteDB (App Definition and Development / Database)
File: jsonb-object-agg.md

title: jsonbobjectagg() headerTitle: jsonbobjectagg() linkTitle: jsonbobjectagg() description: Aggregate a SETOF values into a JSON object. menu: v2.18: identifier: jsonb-object-agg parent: json-functions-operators weight: 155 type: docs Purpose: This is an aggregate function. (Aggregate functions compute a single result from a `SETOF` input values.) It creates a JSON object whose values are the JSON representations of the aggregated SQL values. It is most useful when these to-be-aggregated values are "row" type values with two fields. The first represents the key and the second represents the value of the intended JSON object's key-value pair. Signature: ``` input value: anyelement return value: jsonb ``` Notes: The syntax "order by... nulls first" within the parentheses of the aggregate function (a generic feature of aggregate functions) isn't useful here because the order of the key-value pairs of a JSON object has no semantic significance. (The `::text` typecast of a `jsonb` object uses the convention of ordering the pairs alphabetically by the key. ```plpgsql do $body$ declare object_agg jsonb not null := '"?"'; expectedobjectagg constant jsonb not null := '{"f1": 1, "f2": 2, "f3": null, "f4": 4}'::jsonb; begin with tab as ( values ('f4'::text, 4::int), ('f1'::text, 1::int), ('f3'::text, null::int), ('f2'::text, 2::int)) select jsonbobjectagg(column1, column2) into strict object_agg from tab; assert (objectagg = expectedobject_agg), 'unexpected'; end; $body$; ``` An object is a set of key-value pairs where each key is unique and the order is undefined and insignificant. (As explained earlier, when a JSON literal is This example emphasizes the property of a JSON object that keys are unique. (See the accounts of the functions.) This means that if a key-value pair is specified more than once, then the one that is most recently specified wins. You see the same rule at work here: ```plpgsql select ('{"f2": 42, "f7": 7, "f2": null}'::jsonb)::text; ``` It shows this: ``` text -- {"f2": null, "f7": 7} ``` The `DO` block specifies both the value for key "f2" and the value for key "f7" twice: ```plpgsql do $body$ declare object_agg jsonb not null := '"?"'; expectedobjectagg constant jsonb not null := '{"f2": null, "f7": 7}'::jsonb; begin with tab as ( values ('f2'::text, 4::int), ('f7'::text, 7::int), ('f2'::text, 1::int), ('f2'::text, null::int)) select jsonbobjectagg(column1, column2) into strict object_agg from tab; assert (objectagg = expectedobject_agg), 'unexpected'; end; $body$; ```
Project: ArangoDB (App Definition and Development / Database)
File: hook_outcome_in_place_construction.md

+++ title = "`void hookoutcomeinplaceconstruction(T *, inplacetype_t<U>, Args &&...) noexcept`" description = "(Until v2.2.0) ADL discovered free function hook invoked by the in-place constructors of `basic_outcome`." +++ Removed in Outcome v2.2.0, unless {{% api "BOOSTOUTCOMEENABLELEGACYSUPPORT_FOR" %}} is set to less than `220` to enable emulation. Use {{% api "onoutcomeinplaceconstruction(T *, inplacetype_t<U>, Args &&...) noexcept" %}} instead in new code. One of the constructor hooks for {{% api "basicoutcome<T, EC, EP, NoValuePolicy>" %}}, generally invoked by the in-place constructors of `basicoutcome`. See each constructor's documentation to see which specific hook it invokes. Overridable: By Argument Dependent Lookup. Requires: Nothing. Namespace: `BOOSTOUTCOMEV2_NAMESPACE::hooks` Header: `<boost/outcome/basic_outcome.hpp>`