cwielenb/CNCF-Dataset huggingface dataset:
Project: Beam (App Definition and Development / Streaming & Messaging)
File: ml-resources.md

title: "New Resources Available for Beam ML" date: 2022-11-09 00:00:01 -0800 categories: blog python authors: damccorm <!-- 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. --> If you've been paying attention, over the past year you've noticed that Beam has released a number of features designed to make Machine Learning easy. Ranging from things like the introduction of the `RunInference` transform to the continued refining of `Beam Dataframes`, this has been an area where we've seen Beam make huge strides. While development has advanced quickly, however, until recently there has been a lack of resources to help people discover and use these new features. Over the past several months, we've been hard at work building out documentation and notebooks to make it easier to use these new features and to show how Beam can be used to solve common Machine Learning problems. We're now happy to present this new and improved Beam ML experience! To get started, we encourage you to visit Beam's new . We've got plenty of content on things like , , , and much more. <img class="center-block" src="/images/blog/ml-landing.png" alt="ML landing page"> We've also introduced a number of example showing how to use built in beam transforms like `RunInference` and `Beam Dataframes`. <img class="center-block" src="/images/blog/ensemble-model-notebook.png" alt="Example ensemble notebook with RunInference"> Adding more examples and notebooks will be a point of emphasis going forward. For our next round of improvements, we are planning on adding examples of using RunInference with >30GB models, with multi-language pipelines, with common Beam concepts, and with TensorRT. We will also add examples showing other pieces of the Machine Learning lifecycle like model evaluation with TFMA, per-entity training, and more online training. We hope you find this useful! As always, if you see any areas for improvement, please or a !
Project: Terraform (Provisioning / Automation & Configuration)
File: sample.md

This directory contains a private key that is only used for signing the test data, along with the public key that the package uses to verfify the signing. Here are the steps to reproduce the test data, which would be necessary if the archive and checksum changes. Import the secret key `gpg --import sample.private.key` Sign the sample_release SHA256SUMS file using the sample key: `gpg -u 200BDA882C95B80A --output samplerelease/sample0.1.0SHA256SUMS.sig --detach-sig samplerelease/sample0.1.0SHA256SUMS` 0.1.0_SHA256SUMS`
Project: Chef InSpec (Provisioning / Security & Compliance)
File: azurerm_mysql_databases.md

+++ title = "azurermmysqldatabases resource" draft = false gh_repo = "inspec" platform = "azure" [menu] [menu.inspec] title = "azurermmysqldatabases" identifier = "inspec/resources/azure/azurermmysqldatabases.md azurermmysqldatabases resource" parent = "inspec/resources/azure" +++ {{< inspec/azurermdeprecated resource="azuremysql_databases" >}} Use the `azurermmysqldatabases` InSpec audit resource to test properties and configuration of Azure MySQL Databases. This resource interacts with version `2017-12-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: 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.6.0 of the inspec-azure resource pack. An `azurermmysqldatabases` resource block returns all MySQL Databases on a MySQL Server, within a resource group. describe azurermmysqldatabases(resourcegroup: ..., servername: ...) do ... end The following examples show how to use this InSpec audit resource. describe azurermmysqldatabases(resourcegroup: 'resource-group-1', servername: 'production') do it { should exist } its('names') { should include 'my-database-name' } end `azuremysqldatabases` resources are filterable on all available properties. Below are some examples. Filters the results to include only those databases that match the given name. This is a string value. describe azurermmysqldatabases(resourcegroup: 'rg', servername: 'server').where{ name.eql?('production-database') } do it { should exist } end Filters the results to include only those resource groups that reside in a given location. This is a string value. describe azurermmysqldatabases(resourcegroup: 'rg', servername: 'server').where{ location.eql?('eastus') } do it { should exist } end `id` `name` `type` `properties` Azure resource ID. SQL Database name, e.g. `my-sql-database`. its('names') { should include 'my-sql-database' } The type of Resource, typically `Microsoft.Sql/servers/databases`. A collection of additional configuration properties related to the MySQL Database, e.g. `collation`. {{< 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. describe azurermmysqldatabases do it { should exist } end 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: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: v1.33.0.md

title: v1.33.0 weight: 998967000 The transition from Golang v2 and v3 plugins to the new Golang v4 plugin introduces significant changes. To gain insights into the reasoning behind these changes, you can refer to the explanation provided at https://book.kubebuilder.io/migration/v3vsv4#tldr-of-the-new-gov4-plugin. For a comprehensive understanding of the migration process to the v4 plugin format, the Kubebuilder documentation outlines the necessary steps. Detailed instructions can be found at https://book.kubebuilder.io/migration/manuallymigrationguidegov3to_gov4. This migration is designed to enhance your project's functionality and compatibility, reflecting the evolving landscape of Golang development. See for more details. For more information on the kustomize/v2 plugin, please refer to the documentation at https://book.kubebuilder.io/plugins/kustomize-v2 See for more details.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.10.14.md

RabbitMQ `3.10.14` is a maintenance release in the `3.10.x` . Please refer to the upgrade section from if upgrading from a version prior to 3.10.0. This release requires Erlang 24.3 and supports Erlang 25. has more details on Erlang version requirements for RabbitMQ. Erlang 23 and 24 versions older than 24.3 have reached . This release of RabbitMQ requires Erlang 24.3 or later versions. Nodes will fail to start on older Erlang releases. Erlang 25 is recommended: it offers much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation. Release notes can be found on GitHub at . Dead-lettering of a large number of messages to a classic mirrored queues now has lower peak memory footprint. GitHub issue: Preserve additional information in the log message when heartbeat frame cannot be sent due to a TCP timeout. GitHub issue: `rabbitmqctl add_vhost` now coerces a single string value of `--tags` into an array. GitHub issue: Core server did not correctly translate empty stream message bodies to AMQP 0-9-1 when a stream was consumed by an AMQP 0-9-1 (as opposed to RabbitMQ Stream protocol) client. GitHub issue: `ERROR` frames delivery is now correctly delivered w.r.t. TCP connection closure for clients that run into certain types of exceptions. Contributed by @csicar. GitHub issue: `ra` was upgraded `prometheus.erl` was upgraded To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.10.14.tar.xz` instead of the source tarball produced by GitHub.
Project: StarRocks (App Definition and Development / Database)
File: instr.md

displayed_sidebar: "English" This function returns the position where str first appeared in substr (start counting from 1 and measured in characters). If str is not found in substr, then this function will return 0. ```Haskell INT instr(VARCHAR str, VARCHAR substr) ``` ```Plain Text MySQL > select instr("abc", "b"); +-+ | instr('abc', 'b') | +-+ | 2 | +-+ MySQL > select instr("abc", "d"); +-+ | instr('abc', 'd') | +-+ | 0 | +-+ ``` INSTR
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.4.0.md

<enhance>imeplementmqtttelemetry_service by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/327 N/A [Issue #321] Use gcr.io/distroless for all images by @tomqin93 in https://github.com/Edgenesis/shifu/pull/322 <enhance>add deviceshifu-socket ut by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/311 <feature> rebase from v0.3.0 by @tomqin93 in https://github.com/Edgenesis/shifu/pull/329 modify unit test code `strPointer .. ` using Paradigm type by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/332 TestCollectMQTTTelemetry by @Twpeak in https://github.com/Edgenesis/shifu/pull/334 TestCommandHandleMQTTFunc & mock Client and Server by @Twpeak in https://github.com/Edgenesis/shifu/pull/335 base unit test TestNew by @Twpeak in https://github.com/Edgenesis/shifu/pull/336 Mockdevice plc by @Twpeak in https://github.com/Edgenesis/shifu/pull/343 Mockdevice thermometer by @Twpeak in https://github.com/Edgenesis/shifu/pull/341 Mockdevice unit test agv by @Twpeak in https://github.com/Edgenesis/shifu/pull/345 Unit test mockdevice plate reader by @Twpeak in https://github.com/Edgenesis/shifu/pull/344 Skip mock device test by @kris21he in https://github.com/Edgenesis/shifu/pull/351 bump go 1.18/1.19 => 1.19.2 by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/349 english version revision by @rachelzhang0922 in https://github.com/Edgenesis/shifu/pull/304 Added design for telemetry_service to MQTT broker by @BtXin in https://github.com/Edgenesis/shifu/pull/310 <docs> fix readme typo by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/337 better doc structure by @Yang-Xijie in https://github.com/Edgenesis/shifu/pull/326 Added design for TDengine integration by @BtXin in https://github.com/Edgenesis/shifu/pull/339 [Issue #319] add Linux development guide by @tomqin93 in https://github.com/Edgenesis/shifu/pull/320 Bump github.com/onsi/gomega from 1.22.0 to 1.22.1 by @dependabot in https://github.com/Edgenesis/shifu/pull/315 Bump k8s.io/client-go from 0.25.2 to 0.25.3 by @dependabot in https://github.com/Edgenesis/shifu/pull/323 Bump github.com/stretchr/testify from 1.8.0 to 1.8.1 by @dependabot in https://github.com/Edgenesis/shifu/pull/348 @rachelzhang0922 made their first contribution in https://github.com/Edgenesis/shifu/pull/304 @Twpeak made their first contribution in https://github.com/Edgenesis/shifu/pull/334 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.3.0...v0.4.0
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.0-rc-1.md

layout: release date: 2021-02-22 tag: v0.5.0-rc-1 Update build-and-release.yml Update index.md Update main.css Update mesheryctl.md Update mesheryctl.md Update mesheryctl.md Update scoop.md Adding overflow :hidden Disable Nighthawk
Project: YugabyteDB (App Definition and Development / Database)
File: trust-authentication.md

title: Trust authentication headerTitle: Trust authentication linkTitle: Trust authentication description: Allow clients to connect using a database user name. menu: v2.18: identifier: trust-authentication parent: authentication weight: 734 type: docs <ul class="nav nav-tabs-alt nav-tabs-yb"> <li > <a href="../trust-authentication/" class="nav-link active"> <i class="icon-postgres" aria-hidden="true"></i> YSQL </a> </li> </ul> {{< warning title="Warning" >}} `trust` authentication is only suitable if you trust every user on every machine allowed to connect to the server by the ysql_hba.conf lines that specify trust. It is seldom reasonable to use trust for any TCP/IP connections other than those from localhost (127.0.0.1). {{< /warning >}} When `trust` authentication is specified, YugabyteDB assumes that any user trying to connect with the YB-TServer can access the database with the database user name they specify. This method is appropriate and very convenient for local connections to the YugabyteDB cluster. By default, YugabyteDB cluster uses `trust` authentication. One can explicitly specify `trust` authentication by setting the following flag: ```sh --ysqlhbaconf_csv='host all all 0.0.0.0/0 trust, host all all ::0/0 trust' ``` This enables `trust` authentication for all users.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: chocolatey_package.md

+++ title = "chocolatey_package resource" draft = false gh_repo = "inspec" platform = "windows" [menu] [menu.inspec] title = "chocolatey_package" identifier = "inspec/resources/os/chocolateypackage.md chocolateypackage resource" parent = "inspec/resources/os" +++ Use the `chocolatey_package` Chef InSpec audit resource to test if the named package and/or package version is installed on the system. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v2.1.30 of InSpec. A `chocolatey_package` resource block declares the name of a Chocolatey package to be tested: describe chocolatey_package('name') do it { should be_installed } end where `('name')` must specify the (case-sensitive) name of a package, such as `'nssm'` `be_installed` is a valid matcher for this resource The following examples show how to use this Chef InSpec audit resource describe chocolatey_package('nssm') do it { should be_installed } its('version') { should eq '2.1.0' } end For a full list of available matchers, please visit our . The `be_installed` matcher tests if the named package is installed at all. it { should be_installed } The `version` matcher tests if the named package version is on the system: its('version') { should eq '2.1.0' } You can also use the `cmp OPERATOR` matcher to perform comparisons using the version attribute: its('version') { should cmp >= '1.93.4-13debug84' } `cmp` understands version numbers using Gem::Version, and can use the operators `==, <, <=, >=, and >`. It will compare versions by each segment, not as a string - so '7.4' is smaller than '7.30', for example.
Project: KICS (Provisioning / Security & Compliance)
File: integrations_azurepipelines.md

You can integrate KICS into your Azure Pipelines CI/CD. This provides you the ability to run KICS scans in your Azure DevOps repositories and streamline vulnerabilities and misconfiguration checks to your infrastructure as code (IaC). ```yaml trigger: master pool: vmImage: "ubuntu-latest" container: checkmarx/kics:debian steps: script: | /app/bin/kics scan --ci -p ${PWD} -o ${PWD} cat results.json ``` When your pipeline executes, it will run this job. If KICS finds any issues, it will fail the build. <img src="https://raw.githubusercontent.com/Checkmarx/kics/master/docs/img/kicsazurepipelines_failure.png" width="850"> <img src="https://raw.githubusercontent.com/Checkmarx/kics/master/docs/img/kicsazurepipelines_success.png" width="850"> It's also possible to view KICS results by publishing the SARIF report as a build artifact and installing the Search for the SARIF Azure DevOps Extension in the . Install and give permissions to the plugin. Create a pipeline to scan IaC with KICS, configure the results output in the SARIF format, and publish it as a build artifact with artifact named as `CodeAnalysisLogs`: ```yaml trigger: master pool: vmImage: "ubuntu-latest" container: checkmarx/kics:debian steps: script: | /app/bin/kics scan --ci -p ${PWD} -o ${PWD} --report-formats json,sarif --ignore-on-exit results cat results.json task: PublishBuildArtifacts@1 inputs: pathToPublish: $(System.DefaultWorkingDirectory)/results.sarif artifactName: CodeAnalysisLogs ``` <img src="https://raw.githubusercontent.com/Checkmarx/kics/master/docs/img/azure-devops-build-status.png" width="850"> <img src="https://raw.githubusercontent.com/Checkmarx/kics/master/docs/img/azure-devops-sarif-plugin.png" width="850">
Project: Harbor (Provisioning / Container Registry)
File: 3-07-LDAP-usergroup-manage-project-groupmembers.md

Test 3-07 - LDAP usergroup manage project group members ======= To verify LDAP group can be assigned a role in project member User guide This test requires that a Harbor instance is running and available. An LDAP server is running and available, and enabled memberof overlay feature Harbor is set to authenticate against an LDAP or AD server. ( auth_mode is set to ldap_auth* .) The user data is stored in an LDAP or AD server. LDAP group config parameter are configured. ldapgroupbasedn ldapgroupfilter ldap_gid ldapgroupscope A linux host with Docker CLI installed (Docker client). Create group harborguest, harbordev, harbor_admin in LDAP. Create LDAP user guestuser, devuser, admin_user in LDAP. Assign add group following members harborguest guestuser, admin_user. harbordev devuser. harboradmin adminuser. Login as admin user, create private project projgrouptest Add following group with the roles to projgrouptest harborguest guest, add this member with LDAP Group DN directly: cn=harborguest,ou=groups,dc=example,dc=com. harbordev developer, create user group with LDAP group DN directly: cn=harbordeveloper,ou=groups,dc=example,dc=com Add a user group: group DN: cn=harboradmin,ou=groups,dc=example,dc=com, with name harboradmin, Add project member, select existing user group harbor_admin, assign role administrator. Login user guestuser, devuser, adminuser in web console. all of them can see the projgroup_test. All LDAP users guestuser, devuser, adminuser can login and see the projgroup_test in web console. guestuser has guest role in projgroup_test devuser has developer role in projgroup_test adminuser has administrator role in projgroup_test Login user guestuser, devuser, admin_user in command line. try to push pull images. All LDAP users can login to harbor in command line. guest_user -- can pull images dev_user -- can pull/push images admin_user -- can pull/push images Remove adminuser from LDAP group harboradmin, login again with adminuser. check the role in project projgroup_test After remove harboradmin membership, the adminuser should have guest role in project projgrouptest. Remove adminuser from LDAP group harborguest, login again with admin_user, check the role in project After remove harborguest membership, the adminuser can not see the project projgrouptest.
Project: ThreatMapper (Provisioning / Security & Compliance)
File: elasticsearch.md

title: Elasticsearch Forward Notifications to Elasticsearch Enter Elasticsearch endpoint url. (Example: http://10.108.0.2:9200) Enter Elasticsearch index name. Enter Elasticsearch doc type if version is 5.x. If version is 6 and above, enter `_doc` as doc type. If authentication is enabled for the Elasticsearch instance, set the auth header. If username is `demo` and password is `p@55w0rd`, then enter auth header value as `Basic ZGVtbzpwQDU1dzByZA==`. If authentication is not enabled, leave it empty. Choose the resource that has to be sent to Elasticsearch and click Subscribe button to save.
Project: KICS (Provisioning / Security & Compliance)
File: 934613fe-b12c-4e5a-95f5-c1dcdffac1ff.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: 934613fe-b12c-4e5a-95f5-c1dcdffac1ff Query name: CloudWatch Without Retention Period Specified Platform: Crossplane 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="9 38" apiVersion: cloudwatchlogs.aws.crossplane.io/v1alpha1 kind: LogGroup metadata: name: lg-3 spec: forProvider: logGroupName: /aws/eks/sample-cluster/cluster region: us-east-1 retentionInDays: 0 apiVersion: apiextensions.crossplane.io/v1 kind: Composition metadata: name: cluster-aws labels: provider: aws cluster: eks spec: compositeTypeRef: apiVersion: mydev.org/v1alpha1 kind: CompositeCluster writeConnectionSecretsToNamespace: crossplane-system patchSets: name: metadata patches: fromFieldPath: metadata.labels resources: name: sample-ec2 base: apiVersion: cloudwatchlogs.aws.crossplane.io/v1alpha1 kind: LogGroup metadata: name: lg-4 spec: forProvider: logGroupName: /aws/eks/sample-cluster/cluster region: us-east-1 retentionInDays: 0 ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="34 6" apiVersion: cloudwatchlogs.aws.crossplane.io/v1alpha1 kind: LogGroup metadata: name: lg-5 spec: forProvider: logGroupName: /aws/eks/sample-cluster/cluster region: us-east-1 apiVersion: apiextensions.crossplane.io/v1 kind: Composition metadata: name: cluster-aws labels: provider: aws cluster: eks spec: compositeTypeRef: apiVersion: mydev.org/v1alpha1 kind: CompositeCluster writeConnectionSecretsToNamespace: crossplane-system patchSets: name: metadata patches: fromFieldPath: metadata.labels resources: name: sample-ec2 base: apiVersion: cloudwatchlogs.aws.crossplane.io/v1alpha1 kind: LogGroup metadata: name: lg-6 spec: forProvider: logGroupName: /aws/eks/sample-cluster/cluster region: us-east-1 ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: cloudwatchlogs.aws.crossplane.io/v1alpha1 kind: LogGroup metadata: name: lg-1 spec: forProvider: logGroupName: /aws/eks/sample-cluster/cluster region: us-east-1 retentionInDays: 1 apiVersion: apiextensions.crossplane.io/v1 kind: Composition metadata: name: cluster-aws labels: provider: aws cluster: eks spec: compositeTypeRef: apiVersion: mydev.org/v1alpha1 kind: CompositeCluster writeConnectionSecretsToNamespace: crossplane-system patchSets: name: metadata patches: fromFieldPath: metadata.labels resources: name: sample-ec2 base: apiVersion: cloudwatchlogs.aws.crossplane.io/v1alpha1 kind: LogGroup metadata: name: lg-2 spec: forProvider: logGroupName: /aws/eks/sample-cluster/cluster region: us-east-1 retentionInDays: 1 ```
Project: ClickHouse (App Definition and Development / Database)
File: hudi.md

slug: /en/sql-reference/table-functions/hudi sidebar_position: 85 sidebar_label: hudi Provides a read-only table-like interface to Apache tables in Amazon S3. ``` sql hudi(url [,awsaccesskeyid, awssecretaccesskey] [,format] [,structure] [,compression]) ``` `url` Bucket url with the path to an existing Hudi table in S3. `awsaccesskeyid`, `awssecretaccesskey` - Long-term credentials for the account user. You can use these to authenticate your requests. These parameters are optional. If credentials are not specified, they are used from the ClickHouse configuration. For more information see . `format` The of the file. `structure` Structure of the table. Format `'column1name column1type, column2name column2type, ...'`. `compression` Parameter is optional. Supported values: `none`, `gzip/gz`, `brotli/br`, `xz/LZMA`, `zstd/zst`. By default, compression will be autodetected by the file extension. Returned value A table with the specified structure for reading data in the specified Hudi table in S3. See Also