cwielenb/CNCF-Dataset huggingface dataset:
Project: YugabyteDB (App Definition and Development / Database)
File: cr-cr-copy-from-csv-scripts-sql.md

title: Create function crcopyfrom_scripts() linkTitle: Create crcopyfrom_scripts() headerTitle: Create the function crcopyfrom_scripts() description: Creates a function that writes the chosen one of three \COPY command invocations. menu: v2.18: identifier: cr-cr-copy-from-csv-scripts-sql parent: ingest-scripts weight: 20 type: docs This procedure makes use of the Window function to enable a single invocation of the function to choose the first, the second, or the third `.csv` file with respect to the alphabetical order of their filenames. Save this script as "cr-cr-copy-from-csv-scripts.sql" ```plpgsql drop function if exists crcopyfrom_scripts(int) cascade; create function crcopyfrom_scripts(which in int) returns text language plpgsql as $body$ <<b>>declare copyfromcsv constant text := $$\copy ?1 from '?2' with (format 'csv', header true);$$; csv_file text not null := ''; staging_table text not null := ''; begin with a as ( select rownumber() over (order by s.csvfile) as r, s.csv_file, s.staging_table from covidcast_names as s) select a.csvfile, a.stagingtable into b.csvfile, b.stagingtable from a where a.r = which; return replace(replace( copyfromcsv, '?1', staging_table), '?2', csv_file); end b; $body$; ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: neo4j.md

title: "Neo4j" icon: /images/logos/powered-by/neo4j.png hasNav: true hasLink: "https://www.youtube.com/watch?v=a5rx0_c4RXQ&list=PL4dEBWmGSIU9OkXQU2OAXmITPLhiMSPRp&index=31" <!-- Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -->
Project: YDB (App Definition and Development / Database)
File: topic-consumer-offset-commit.md

Each topic consumer has a . You can use the `topic consumer offset commit` command to save the consumer offset for the consumer that you . General format of the command: ```bash {{ ydb-cli }} [global options...] topic consumer offset commit [options...] <topic-path> ``` `global options`: . `options`: . `topic-path`: Topic path. Viewing the command description: ```bash {{ ydb-cli }} topic consumer offset commit --help ``` | Name | Description | | | `--consumer <value>` | Consumer name. | | `--partition <value>` | Partition number. | | `--offset <value>` | Offset value that you want to set. | {% include %} For `my-consumer`, set the offset of 123456789 in `my-topic` and partition `1`: ```bash {{ ydb-cli }} -p db1 topic consumer offset commit \ --consumer my-consumer \ --partition 1 \ --offset 123456789 \ my-topic ```
Project: RBAC Lookup (Provisioning / Security & Compliance)
File: guide.md

Issues, whether bugs, tasks, or feature requests are essential for keeping rbac-lookup great. We believe it should be as easy as possible to contribute changes that get things working in your environment. There are a few guidelines that we need contributors to follow so that we can keep on top of things. This project adheres to a . Please review this document before contributing to this project. Before you can contribute, you will need to sign the . rbac-lookup is a relatively simple cobra cli tool that looks up information about rbac in a cluster. The folder contains the flags and other cobra config, while the folder has the code for looking up rbac information a cluster. There is additinal code that allows the user to see GKE IAM information as well, since GKE IAM is so closely tied to rbac. We label issues with the if we believe they'll be a good starting point for new contributors. If you're interested in working on an issue, please start a conversation on that issue, and we can help answer any questions as they come up. A properly configured Golang environment with Go 1.17 or higher Access to a cluster via a properly configured KUBECONFIG Install the project with `go get github.com/fairwindsops/rbac-lookup` Change into the rbac-lookup directory which is installed at `$GOPATH/src/github.com/fairwindsops/rbac-lookup` Use `make build` to build the binary locally. Use `make test` to run the tests and generate a coverage report. Use `make lint` to run (requires golangci-lint installed) If you've encountered an issue that is not already reported, please create an issue that contains the following: Clear description of the issue Steps to reproduce it Appropriate labels Each new pull request should: Reference any related issues Add tests that show the issues have been solved Pass existing tests and linting Contain a clear indication of if they're ready for review or a work in progress Be up to date and/or rebased on the master branch Push a new annotated tag. This tag should contain a changelog of pertinent changes. Goreleaser will take care of the rest.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.69.md

layout: release date: 2021-11-03 tag: v0.5.69 [CI] Set Node version to LTS for docker builds @sudo-NithishKarthik (#4551) Manifest Pattern Transposition and Dry Run @utkarsh-pro (#4529) [mesheryctl] Fetching latest relase tag via web-scraping. @piyushsingariya (#4473) Create docs for configuration management with patterns, filters and applications @navendu-pottekkat (#4550) Thank you to our contributors for making this release possible: @leecalcote, @navendu-pottekkat, @piyushsingariya, @sudo-NithishKarthik and @utkarsh-pro
Project: KICS (Provisioning / Security & Compliance)
File: e24e18d9-4c2b-4649-b3d0-18c088145e24.md

title: CloudWatch Without Retention Period Specified hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: e24e18d9-4c2b-4649-b3d0-18c088145e24 Query name: CloudWatch Without Retention Period Specified Platform: Ansible Severity: <span style="color:#5bc0de">Info</span> Category: Observability URL: AWS CloudWatch should have CloudWatch Logs enabled in order to monitor, store, and access log events<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="2 7" name: example ec2 group community.aws.cloudwatchlogsloggroup: loggroupname: test-log-group name: example2 ec2 group community.aws.cloudwatchlogsloggroup: loggroupname: test-log-group retention: 111111 ``` ```yaml title="Negative test num. 1 - yaml file" name: example3 ec2 group community.aws.cloudwatchlogsloggroup: loggroupname: test-log-group retention: 5 ```
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: CHANGELOG-v2023.11.2.md

title: Changelog | KubeDB description: Changelog menu: docs_{{.version}}: identifier: changelog-kubedb-v2023.11.2 name: Changelog-v2023.11.2 parent: welcome weight: 20231102 product_name: kubedb menuname: docs{{.version}} sectionmenuid: welcome url: /docs/{{.version}}/welcome/changelog-v2023.11.2/ aliases: /docs/{{.version}}/CHANGELOG-v2023.11.2/ Update deps Bring back GetRequestType() (#1064) Remove spec.upgrade field and Upgrade ops type (#1063) Prepare for release v0.22.0 (#157) Prepare for release v0.37.0 (#729) Prepare for release v0.13.0 (#83) Prepare for release v0.37.0 (#675) Prepare for release v0.8.0 (#41) Disable stash installation Prepare for release v0.21.0 (#231) Prepare for release v0.17.0 (#91) Prepare for release v0.30.0 (#404) Prepare for release v0.30.0 (#574) Prepare for release v0.30.0 (#569) Prepare for release v0.15.0 (#88) Prepare for release v0.24.0 (#484) Remove spec.upgrade field and Upgrade ops type (#482) Reprovision opsReq will progress even if DB is in Provisioning state (#480) Prepare for release v0.24.0 (#330) Prepare for release v0.10.0 (#48) Prepare for release v0.21.0 (#135) Prepare for release v0.24.0 (#295) Prepare for release v0.37.0 (#676) Prepare for release v0.37.0 (#58) Prepare for release v0.24.0 (#312) Prepare for release v0.30.0 (#493) Prepare for release v0.16.0 (#79) Prepare for release v0.24.0 (#243) Prepare for release v0.13.0 (#84) Prepare for release v0.22.0 (#265) Minimize mongo test areas; Increase timeout (#264) Add Redis Autoscaler tests (#255) Update mysql remote replica (#263) Prepare for release v0.13.0 (#93) Prepare for release v0.13.0 (#69)
Project: Carvel (App Definition and Development / Application Definition & Image Build)
File: README_Cognito_UserPools_PreAuthentication.md

The following is a sample Lambda function that receives Amazon Cognito User Pools pre-authentication event as an input and writes some of the record data to CloudWatch Logs. (Note that anything written to stdout or stderr will be logged as CloudWatch Logs events.) Please see instructions for setting up the Cognito triggers at https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html . ```go package main import ( "fmt" "github.com/aws/aws-lambda-go/lambda" "github.com/aws/aws-lambda-go/events" ) func handler(event events.CognitoEventUserPoolsPreAuthentication) (events.CognitoEventUserPoolsPreAuthentication, error) { fmt.Printf("PreAuthentication of user: %s\n", event.UserName) return event, nil } func main() { lambda.Start(handler) } ```
Project: Druid (App Definition and Development / Database)
File: use-cases.md

title: Use Cases canonical: 'https://druid.apache.org/use-cases' <!-- 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. --> Edit this page in the repo. To see your changes, navigate to them from the .
Project: Beam (App Definition and Development / Streaming & Messaging)
File: tfx.md

title: "TensorFlow Extended (TFX)" icon: /images/logos/powered-by/tfx.png hasNav: true hasLink: "https://www.youtube.com/watch?v=TURQ1O8fn0k" cardDescription: "TensorFlow Extended (TFX) is an end-to-end platform for deploying production ML pipelines based on Apache Beam." <!-- Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> : TensorFlow Extended (TFX) is an end-to-end platform for deploying production ML pipelines based on Apache Beam.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.6.1.en.md

Do not save invalid uploaded backup files. Rename `messagequeuetoolong` error reason to `mailboxoverflow` `mailboxoverflow` is consistent with the corresponding config parameter: `forceshutdown.maxmailboxsize`. Upgrade HTTP client libraries. The HTTP client library (`gun-1.3`) incorrectly appends a `:portnumber` suffix to the `Host` header for standard ports (`http` on port 80, `https` on port 443). This could cause compatibility issues with servers or gateways performing strict `Host` header checks (e.g., AWS Lambda, Alibaba Cloud HTTP gateways), leading to errors such as `InvalidCustomDomain.NotFound` or "The specified CustomDomain does not exist." Improve cluster discovery behaviour when a node is manually removed from a cluster using 'emqx ctl cluster leave' command. Previously, if the configured cluster 'discovery_strategy' was not 'manual', the left node might re-discover and re-join the same cluster shortly after it left (unless it was stopped). After this change, 'cluster leave' command disables automatic cluster_discovery, so that the left node won't re-join the same cluster again. Cluster discovery can be re-enabled by running 'emqx ctl discovery enable` or by restarting the left node. Handle several errors in `/clients/{clientid}/mqueuemessages` and `/clients/{clientid}/inflightmessages` APIs: Internal timeout, which means that EMQX failed to get the list of Inflight/Mqueue messages within the default timeout of 5 s. This error may occur when the system is under a heavy load. The API will return 500 `{"code":"INTERNAL_ERROR","message":"timeout"}` response and log additional details. Client shutdown. The error may occur if the client connection is shutdown during the API call. The API will return 404 `{"code": "CLIENT_SHUTDOWN", "message": "Client connection has been shutdown"}` response in this case. Make sure stats `'subscribers.count'` `'subscribers.max'` countains shared-subscribers. It only contains non-shared subscribers previously. Fixed an issue that prevented importing source data integrations and retained messages. Before the fix: source data integrations are ignored from the backup file importing the `mnesia` table for retained messages are not supported Fixed `clusterrpccommit` transaction ID cleanup procedure after `cluster leave` on replicant nodes. Previously, the transaction id of the core node would be deleted prematurely, blocking configuration updates on the core node. Fixed an issue when users were not able to see the "Retained Messages" under the "Monitoring" menu in the admin dashboard. "Retained messages" backend API uses `qlc`, and `qlc` uses `file_sorter` that puts temporary files in the working directory by default, which is not writable by emqx user since 58d0f04. This patch fixes this by making `/opt/emqx` directory owned by `emqx:emqx`.
Project: Devfile (App Definition and Development / Application Definition & Image Build)
File: PULL_REQUEST_TEMPLATE.md

<!-- Summarize the changes --> <!-- Link to github issue(s) --> Testing and documentation do not need to be complete in order for this PR to be approved. We just need to ensure tracking issues are opened. Open new test/doc issues under the repo Check each criteria if: There is a separate tracking issue. Add the issue link under the criteria or test/doc updates are made as part of this PR If unchecked, explain why it's not needed [ ] Unit/Functional tests <!-- These are run as part of the PR workflow, ensure they are updated --> <!-- Do we need to verify integration with ODO and Openshift console? --> [ ] Documentation <!-- This includes product docs and READMEs. --> [ ] Client Impact <!-- Do we have anything that can break our clients? If so, open a notifying issue -->
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: event-time-extractor.md

A `eventTimeExtractor` built-in transformer extracts event time from the payload of the message, based on a user-provided `expression` and an optional `format` specification. `expression` is used to compile the payload to a string representation of the event time. `format` is used to convert the event time in string format to a `time.Time` object. Event Time Extractor expression is implemented with `expr` and `sprig` libraries. These function can be accessed directly in expression. `payload` keyword represents the message object. It will be the root element to represent the message object 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.trim(string(json(payload).timestamp))` # Remove spaces from either side of the value of field `timestamp` Depending on whether a `format` is specified, Event Time Extractor uses different approaches to convert the event time string to a `time.Time` object. When `format` is specified, the native library is used to make the conversion. In this process, the `format` parameter is passed as the layout input to the time.Parse() function, while the event time string is passed as the value parameter. When `format` is not specified, the extractor uses to parse the event time string without knowing the format in advance. Please refer to . When encountering parsing errors, event time extractor skips the extraction and passes on the message without modifying the original input message event time. Errors can occur for a variety of reasons, including: `format` is specified but the event time string can't parse to the specified format. `format` is not specified but dataparse can't convert the event time string to a `time.Time` object. Event time strings can be ambiguous when it comes to date format, such as MM/DD/YYYY versus DD/MM/YYYY. When using such format, you're required to explicitly specify `format`, to avoid confusion. If no format is provided, event time extractor treats ambiguous event time strings as an error scenario. If the event time string in your message payload is in epoch format, you can skip specifying a `format`. You can rely on `dateparse` to recognize a wide range of epoch timestamp formats, including Unix seconds, milliseconds, microseconds, and nanoseconds. ```yaml spec: vertices: name: in source: http: {} transformer: builtin: name: eventTimeExtractor kwargs: expression: sprig.trim(string(json(payload).timestamp)) format: 2006-01-02T15:04:05Z07:00 ```
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-components-list.md

layout: default title: mesheryctl-components-list permalink: reference/mesheryctl/components/list redirect_from: reference/mesheryctl/components/list/ type: reference display-title: "false" language: en command: components subcommand: list List registered components List all components registered in Meshery Server <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl components list [flags] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> // View list of components </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl exp components list </div> </pre> View list of components with specified page number (25 components per page) <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl exp components list --page 2 </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for list -p, --page int (optional) List next set of models with --page (default = 1) (default 1) </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: ClickHouse (App Definition and Development / Database)
File: v23.8.5.16-lts.md

sidebar_position: 1 sidebar_label: 2023 Backported in : Check sha512 for tgz; use a proper repository for keeper; write only filenames to TGZ.sha512 files for tarball packages. Prerequisite for . (). Fix storage Iceberg files retrieval (). Try to fix possible segfault in Native ORC input format (). Fix window functions in case of sparse columns. (). Use `--filter` to reduce checkout time (). One final leftover in diff_urls of PRInfo (). Bring relevant commits from backport/23.8/55336 to 23.8 ().
Project: Chef InSpec (Provisioning / Security & Compliance)
File: azurerm_locks.md

+++ title = "azurerm_locks resource" draft = false gh_repo = "inspec" platform = "azure" [menu] [menu.inspec] title = "azurerm_locks" identifier = "inspec/resources/azure/azurermlocks.md azurermlocks resource" parent = "inspec/resources/azure" +++ {{< inspec/azurermdeprecated resource="azurelocks" >}} Use the `azurerm_locks` InSpec audit resource to test properties of some or all Azure Resource Locks. This resource interacts with version `2016-09-01` of the Azure Management API. For more information see the . At the moment, there doesn't appear to be a way to select the version of the Azure API docs. If you notice a newer version being referenced in the official documentation please open an issue or submit a pull request using the updated version. This resource is available in the `inspec-azure` [resource pack](/inspec/glossary/#resource-pack). To use it, add the following to your `inspec.yml` in your top-level profile: depends: name: inspec-azure git: https://github.com/inspec/inspec-azure.git You'll also need to setup your Azure credentials; see the resource pack . This resource first became available in 1.3.8 of the inspec-azure resource pack. An `azurerm_locks` resource block returns all Locks on a given Resource. describe azurermlocks(resourcegroup: 'rg', resourcename: 'my-vm', resourcetype: 'Microsoft.Compute/virtualMachines') do ... end The following examples show how to use this InSpec audit resource. describe azurermlocks(resourcegroup: 'my-rg', resourcename: 'my-vm', resourcetype: 'Microsoft.Compute/virtualMachines') do it { should exist } end `ids` `names` `properties` {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The control will pass if the filter returns at least one result. Use `should_not` if you expect zero matches. Your [Service Principal](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal) must be setup with a `contributor` role on the subscription you wish to test.
Project: FOSSA (Provisioning / Security & Compliance)
File: golang.md

Historically, the Go buildtool ecosystem has been very fragmented: many tools like dep, Glide, Govendor, etc have tried to address issues around build reproducibility, versioning and vendoring of dependencies. As of Go 1.11, we have first-class support for "modules", which solves issues previously seen around versioning and build reproducibility. Because modules address those issues so well, the other tooling has largely gone into maintenance mode, with the notable exception of dep. As such, Go analysis in fossa-cli primarily targets Go 1.11+ modules and dep. Support for Glide is also included, because it's still commonly used. | Strategy | Direct Deps | Transitive Deps | Edges | Container Scanning | | - | | | | | | | :whitecheckmark: | :whitecheckmark: | :warning: | :x: | | | :whitecheckmark: | :x: | :warning: | :x: | | | :whitecheckmark: | :whitecheckmark: | :warning: | :x: | | | :whitecheckmark: | :warning: | :warning: | :x: | | | :whitecheckmark: | :whitecheckmark: | :x: | :whitecheckmark: | Most strategies (except for gomod, where it would be redundant -- golist supersedes gomod) use `go list -json all` to hydrate edges and transitive dependencies. Package imports are recursively traversed, ignoring `Standard` (system) packages. `go list` behaves slightly differently depending on the context: in a gomodules project, packages can contain a `Module` field that contains a pinned `Version`. The version will otherwise be unspecified `go list` includes vendored packages in both gomodules and non-gomodules projects.