cwielenb/CNCF-Dataset huggingface dataset:
Project: Meshery (Provisioning / Automation & Configuration)
File: SECURITY.md

We are very grateful to the security researchers and users that report back Meshery security vulnerabilities. We investigate every report thoroughly. To make a report, send an email to the private mailing list with the vulnerability details. For normal product bugs unrelated to latent security vulnerabilities, please head to the appropriate repository and submit a . Send us a report whenever you: Think Meshery has a potential security vulnerability. Are unsure whether or how a vulnerability affects Meshery. Think a vulnerability is present in another project that Meshery depends on (Docker for example). Don't send a vulnerability report if: You need help tuning Meshery components for security. You need help applying security related updates. Your issue is not security related. The Meshery team acknowledges and analyzes each vulnerability report within 10 working days. Any vulnerability information you share with the Meshery team stays within the Meshery project. We don't disseminate the information to other projects. We only share the information as needed to fix the issue. We keep the reporter updated as the status of the security issue is addressed. Once a security vulnerability has been fully characterized, a fix is developed by the Meshery team. The development and testing for the fix happens in a private GitHub repository in order to prevent premature disclosure of the vulnerability. The Meshery project maintains a mailing list for private early disclosure of security vulnerabilities. The list is used to provide actionable information to close Meshery partners. The list is not intended for individuals to find out about security issues. On the day chosen for public disclosure, a sequence of activities takes place as quickly as possible: Changes are merged from the private GitHub repository holding the fix into the appropriate set of public branches. Meshery team ensures all necessary binaries are promptly built and published. Once the binaries are available, an announcement is sent out on the following channels: The The The #announcements channel on Slack As much as possible this announcement will be actionable, and include any mitigating steps customers can take prior to upgrading to a fixed version.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: feat-12785.en.md

Add `timestamp_format` config to log handers. We've added a new configuration option `timestamp_format` to the log handlers. This new config supports the following values: `auto`: Automatically determines the timestamp format based on the log formatter being used. Utilizes `rfc3339` format for text formatters, and `epoch` format for JSON formatters. `epoch`: Represents timestamps in microseconds precision Unix epoch format. `rfc3339`: Uses RFC3339 compliant format for date-time strings. For example: `2024-03-26T11:52:19.777087+00:00`.
Project: Meshery (Provisioning / Automation & Configuration)
File: 09-29-2022-16-04-09_8c17f987.md

timestamp: "2022-09-29 16:04:00 UTC Thu" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "v0.6.9" k8s-distro: minikube k8s-version: "v1.21.5" service-mesh: Consul service-mesh-version: "v0.48.0" tests: consul-client: null consul-server: null overall-status: "failing"
Project: Druid (App Definition and Development / Database)
File: schema-changes.md

id: schema-changes title: "Schema changes" <!-- ~ 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. --> Apache Druid allows you to provide a new schema for new data without the need to update the schema of any existing data. It is sufficient to update your supervisor spec, if using , or to provide the new schema the next time you do a . This is made possible by the fact that each , at the time it is created, stores a copy of its own schema. Druid reconciles all of these individual segment schemas automatically at query time. Schema changes are sometimes necessary for existing data. For example, you may want to change the type of a column in previously-ingested data, or drop a column entirely. Druid handles this using , the same method it uses to handle updates of existing data. Reindexing involves rewriting all affected segments and can be a time-consuming operation.
Project: Harbor (Provisioning / Container Registry)
File: 7-07-Trigger-scheduled.md

Test 7-07 - Scheduled trigger ======= To verify the scheduled replication rule can work as expected. User guide This test requires that at least two Harbor instances are running and available. Create a new replication rule whose triggering condition is set to scheduled and no filter is configured. Need at least one image is pushed to the project that the rule is applied to Login UI as admin user. Go to `Administration->Replications` page. In step 2, a few jobs should be started when the time configured in schedule trigger comes. All the images under the project should be replicated to the remote registry. None
Project: SPIRE (Provisioning / Key Management)
File: plugin_agent_nodeattestor_aws_iid.md

Must be used in conjunction with the server-side aws_iid plugin The `aws_iid` plugin automatically attests instances using the AWS Instance Metadata API and the AWS Instance Identity document. It also allows an operator to use AWS Instance IDs when defining SPIFFE ID attestation policies. Generally no plugin data is needed in AWS, and this configuration should be used: ```hcl NodeAttestor "aws_iid" { plugin_data {} } ``` | Configuration | Description | |--|-| | ec2metadataendpoint | Endpoint for AWS SDK to retrieve instance metadata | For testing or non-standard AWS environments, you may need to specify the Metadata endpoint. For more information, see ```hcl NodeAttestor "aws_iid" { plugin_data { ec2metadataendpoint = "http://169.254.169.254/latest" } } ```
Project: Cyclops (App Definition and Development / Application Definition & Image Build)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: '' assignees: '' Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: Go to '...' Click on '....' Scroll down to '....' See error Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Desktop (please complete the following information): OS: [e.g. iOS] Browser [e.g. chrome, safari] Version [e.g. 22] Smartphone (please complete the following information): Device: [e.g. iPhone6] OS: [e.g. iOS8.1] Browser [e.g. stock browser, safari] Version [e.g. 22] Additional context Add any other context about the problem here.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.3.md

layout: release date: 2023-12-19 tag: v0.7.3 [bug] Fix Unnecessary re-rendering of Dashboard @theBeginner86 (#9684) Use rtk query in environments page @aabidsofi19 (#9679) fix connection status duplication and hide workspaces allocation @aabidsofi19 (#9678) update route for service-mesh @aabidsofi19 (#9675) Fix Lifecycle routing @aabidsofi19 (#9673) Add Postgres Autoscalar Icon @Akshun-01 (#9672) fix broken imports in environments @aabidsofi19 (#9671) [bug] Fix Unnecessary re-rendering of Dashboard @theBeginner86 (#9684) Thank you to our contributors for making this release possible: @Akshun-01, @aabidsofi19, @leecalcote and @theBeginner86
Project: Artifact Hub (App Definition and Development / Application Definition & Image Build)
File: tinkerbell_actions_repositories.md

Tinkerbell actions repositories are expected to be hosted in GitHub, GitLab or Bitbucket repos. When adding your repository to Artifact Hub, the url used must follow the following format: `https://github.com/user/repo[/path/to/packages]` `https://gitlab.com/user/repo[/path/to/packages]` `https://bitbucket.org/user/repo[/path/to/packages]` By default the `master` branch is used, but it's possible to specify a different one from the UI. Please NOTE that the repository URL used when adding the repository to Artifact Hub must NOT contain the git hosting platform specific parts, like tree/branch, just the path to your packages like it would show in the filesystem. The path to packages provided can contain one or more packages. Each package version must be on a separate folder, and it's up to you to decide if you want to publish one or multiple versions of your package. The structure of a repository with multiple actions packages and versions could look something like this: ```sh $ tree path/to/packages path/to/packages artifacthub-repo.yml package1 1.0.0 README.md artifacthub-pkg.yml 2.0.0 README.md artifacthub-pkg.yml package2 1.0.0 README.md artifacthub-pkg.yml ``` This structure is flexible, and in some cases it can be greatly simplified. In the case of a single package with a single version available at a time (the publisher doesn't want to make previous ones available, for example), the structure could look like this: ```sh $ tree path/to/packages path/to/packages artifacthub-repo.yml package1 artifacthub-pkg.yml ``` In the previous case, even the `package1` directory could be omitted. The reason is that both packages names and versions are read from the `artifacthub-pkg.yml` metadata file, so directories names are not used at all. Each package version needs an `artifacthub-pkg.yml` metadata file. Please see the file for more details. The repository metadata file shown above can be used to setup features like or . This file must be located at `/path/to/packages`. Once you have added your repository, you are all set up. As you add new versions of your actions packages or even new packages to your git repository, they'll be automatically indexed and listed in Artifact Hub. Actions source GitHub URL: Repository URL used in Artifact Hub: `https://github.com/tinkerbell/hub/actions` (please note how the tree/artifacthub-manifests part is not used)
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.13.0.md

add custom data processing before telemetryService by @cbgz121 in https://github.com/Edgenesis/shifu/pull/482 Add Changelog for v0.12.0 to main by @tomqin93 in https://github.com/Edgenesis/shifu/pull/506 add refactor telemetryService docs by @leepala in https://github.com/Edgenesis/shifu/pull/507 fix customized deviceshifu Content-Length Error by @leepala in https://github.com/Edgenesis/shifu/pull/511 remove write statusCode in response first by @leepala in https://github.com/Edgenesis/shifu/pull/513 Bump github.com/onsi/gomega from 1.26.0 to 1.27.1 by @dependabot in https://github.com/Edgenesis/shifu/pull/503 Bump github.com/minio/minio-go/v7 from 7.0.48 to 7.0.49 by @dependabot in https://github.com/Edgenesis/shifu/pull/509 Bump github.com/onsi/ginkgo/v2 from 2.8.1 to 2.8.3 by @dependabot in https://github.com/Edgenesis/shifu/pull/508 Bump github.com/stretchr/testify from 1.8.1 to 1.8.2 by @dependabot in https://github.com/Edgenesis/shifu/pull/514 Bump github.com/onsi/ginkgo/v2 from 2.8.3 to 2.8.4 by @dependabot in https://github.com/Edgenesis/shifu/pull/516 Bump github.com/briandowns/spinner from 1.21.0 to 1.22.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/515 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.12.0...v0.13.0
Project: KOTS (App Definition and Development / Application Definition & Image Build)
File: registry-instead-of-s3.md

KOTS requires an object store in order to store persistent versions of application version artifacts. KOTS also supports optionally providing a local OCI/Docker image repository to store application container images. This proposal removes the object store requirement in favor of the image repository. We could remove the requirement to have an object store (currently minio or rook) by using an image repository. This would be easier to support because there would be less third party components being used. If an image repository is provided for the application, KOTS will create a data image containing the application version manifests and store it in the remote image repository. For online installs to existing clusters, if a registry is not provided, KOTS will deploy a small, PVC backed image repository. KOTS will no longer deploy minio or create the object store in Rook by default. When an image repository is set in KOTS, the application manifests will be pushed to the registry instead of the object store. The code that downloads a version will be able to download a version from the image repository, instead. New CLI flags will be added to `kots install` and `kots pull` to provide a local registry to be used. When these flags are not provided, KOTS will install Docker Distribution statefulset and service using a ClusterIP. This will be an insecure registry. Application manifests are currently packaged as a `.tar.gz` file. KOTS will continue to do this, but use the to package these into an image. The image will be tagged as `registry.hostname` / `registry.namespace` / kots-application-{slug}:{sequence} For example, if the application slug is `my-app`, and the KOTS Admin Console user provided `registry.somebigbank.com/my-app` as the registry, the first version (sequence 0) will be an ORAS image pushed to `registry.somebigbank.com/my-app/kots-application-my-app:0`. There are no changes to any YAML schemas or APIs. Existing installations will be migrated when a version of KOTS with this functionality is started. kURL installations would work as-is (they already package docker distribution). In a future release, we could remove the rook object store manifest from kURL install scripts. Bring your own S3/Object Store, as proposed in https://github.com/replicatedhq/kots/pull/474 Application manifests may contain sensitive information (secrets).
Project: Dragonfly (Provisioning / Container Registry)
File: dfcache_delete.md

% DFCACHE(1) Version v2.1.0 | Frivolous "Dfcache" Documentation dfcache delete delete file from P2P cache system Delete file from P2P cache system. ```shell dfcache delete <-i cid> [flags] ``` ```shell -i, --cid string content or cache ID, e.g. sha256 digest of the content --config string the path of configuration file with yaml extension name, default is /etc/dragonfly/dfcache.yaml, it can also be set by env var: DFCACHE_CONFIG --console whether logger output records to the stdout --jaeger string jaeger endpoint url, like: http://localhost:14250/api/traces --logdir string Dfcache log directory --pprof-port int listen port for pprof, 0 represents random port (default -1) --service-name string name of the service for tracer (default "dragonfly-dfcache") -t, --tag string different tags for the same cid will be recognized as different files in P2P network --timeout duration Timeout for this cache operation, 0 is infinite --verbose whether logger use debug level --workhome string Dfcache working directory -h, --help help for delete ``` - the P2P cache client of dragonfly
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: dashboard1.md

title: Dashboard layout: 1: default 2: default 3: default 4: position: default placeholder: Click on entries in the tables, and output will show up here ```bash execute: now watch: /kubectl/config/change k get deploy --watch ``` ```bash execute: now watch: /kubectl/context/change k get pods --watch ``` ```bash execute: now watch: /kubectl/config/change k get events --sort-by='{.metadata.creationTimestamp}' --watch ```
Project: OpenAPI (App Definition and Development / Application Definition & Image Build)
File: alternative_schema_object.md

The following text is to be inserted after the XML Object section This object makes it possible to reference an external file that contains a schema that does not follow the OAS specification. If tooling does not support the type, tooling MUST consider the content valid but SHOULD provide a warning that the alternative schema was not processed. |Field Name | Type | Description | ||::|| |type | string | REQUIRED. The value MUST match one of the values identified in the alternative Schema Registry. | |location | url | REQUIRED. This is a absolute or relative reference to an external resource containing a schema of a known type. This reference may contain a fragment identifier to reference only a subset of an external document. | This object MAY be extended with Specification Extensions.
Project: ShardingSphere (App Definition and Development / Database)
File: broadcast.en.md

+++ title = "Broadcast Table" weight = 2 +++ Broadcast table YAML configuration is highly readable. The broadcast rules can be quickly understood thanks to the YAML format. ShardingSphere automatically creates the `ShardingSphereDataSource` object according to the YAML configuration, which reduces unnecessary coding for users. ```yaml rules: !BROADCAST tables: # Broadcast tables <table_name> <table_name> ``` Configure broadcast table list in the YAML file. Call the `createDataSource` method of the object `YamlShardingSphereDataSourceFactory`. Create ShardingSphereDataSource according to the configuration information in YAML files. The YAML configuration sample of the broadcast table is as follows: ```yaml dataSources: ds_0: dataSourceClassName: com.zaxxer.hikari.HikariDataSource driverClassName: com.mysql.jdbc.Driver jdbcUrl: jdbc:mysql://localhost:3306/demods0?serverTimezone=UTC&useSSL=false&useUnicode=true&characterEncoding=UTF-8 username: root password: ds_1: dataSourceClassName: com.zaxxer.hikari.HikariDataSource driverClassName: com.mysql.jdbc.Driver jdbcUrl: jdbc:mysql://localhost:3306/demods1?serverTimezone=UTC&useSSL=false&useUnicode=true&characterEncoding=UTF-8 username: root password: rules: !BROADCAST tables: t_address ``` Read the YAML configuration to create a data source according to the `createDataSource` method of `YamlShardingSphereDataSourceFactory`. ```java YamlShardingSphereDataSourceFactory.createDataSource(getFile("/META-INF/broadcast-databases-tables.yaml")); ```
Project: Meshery (Provisioning / Automation & Configuration)
File: kubeflow.md

layout: integration title: Kubeflow subtitle: Collaborative and visual infrastructure as code for Kubeflow image: /assets/img/integrations/kubeflow/icons/color/kubeflow-color.svg permalink: extensibility/integrations/kubeflow docURL: https://docs.meshery.io/extensibility/integrations/kubeflow description: integrations-category: Machine Learning integrations-subcategory: Machine Learning registrant: Artifact Hub components: name: scheduled-workflow colorIcon: assets/img/integrations/kubeflow/components/scheduled-workflow/icons/color/scheduled-workflow-color.svg whiteIcon: assets/img/integrations/kubeflow/components/scheduled-workflow/icons/white/scheduled-workflow-white.svg description: name: viewer colorIcon: assets/img/integrations/kubeflow/components/viewer/icons/color/viewer-color.svg whiteIcon: assets/img/integrations/kubeflow/components/viewer/icons/white/viewer-white.svg description: name: notebook colorIcon: assets/img/integrations/kubeflow/components/notebook/icons/color/notebook-color.svg whiteIcon: assets/img/integrations/kubeflow/components/notebook/icons/white/notebook-white.svg description: name: pod-default colorIcon: assets/img/integrations/kubeflow/components/pod-default/icons/color/pod-default-color.svg whiteIcon: assets/img/integrations/kubeflow/components/pod-default/icons/white/pod-default-white.svg description: name: profile colorIcon: assets/img/integrations/kubeflow/components/profile/icons/color/profile-color.svg whiteIcon: assets/img/integrations/kubeflow/components/profile/icons/white/profile-white.svg description: name: tensorboard colorIcon: assets/img/integrations/kubeflow/components/tensorboard/icons/color/tensorboard-color.svg whiteIcon: assets/img/integrations/kubeflow/components/tensorboard/icons/white/tensorboard-white.svg description: name: mpi-job colorIcon: assets/img/integrations/kubeflow/components/mpi-job/icons/color/mpi-job-color.svg whiteIcon: assets/img/integrations/kubeflow/components/mpi-job/icons/white/mpi-job-white.svg description: name: auth-code colorIcon: assets/img/integrations/kubeflow/components/auth-code/icons/color/auth-code-color.svg whiteIcon: assets/img/integrations/kubeflow/components/auth-code/icons/white/auth-code-white.svg description: featureList: [ "Make deployments of machine learning (ML) workflows on Kubernetes simple, portable and scalable. ", "Design and manage you the machine learning toolkit for Kubernetes", "Easy, repeatable, portable deployments on a diverse infrastructure (for example, experimenting on a laptop, then moving to an on-premises cluster or to the cloud)" ] 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: ShardingSphere (App Definition and Development / Database)
File: load-single-table.en.md

+++ title = "LOAD SINGLE TABLE" weight = 1 +++ The `LOAD SINGLE TABLE` syntax is used to load single table from storage unit. {{< tabs >}} {{% tab name="Grammar" %}} ```sql loadSingleTable ::= 'LOAD' 'SINGLE' 'TABLE' tableDefinition tableDefinition ::= tableIdentifier (',' tableIdentifier)* tableIdentifier ::= '.' | '..' | storageUnitName '.' | storageUnitName '..' | storageUnitName '.' schemaName '.*' | storageUnitName '.' tableName | storageUnitName '.' schemaName '.' tableName storageUnitName ::= identifier schemaName ::= identifier tableName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} support specifying schemaName in PostgreSQL and OpenGauss protocols Load specified single table ```sql LOAD SINGLE TABLE ds0.tsingle; ``` Load all single tables in the specified storage unit ```sql LOAD SINGLE TABLE ds_0.*; ``` Load all single tables ```sql LOAD SINGLE TABLE .; ``` `LOAD`, `SINGLE`, `TABLE`
Project: KICS (Provisioning / Security & Compliance)
File: c91d7ea0-d4d1-403b-8fe1-c9961ac082c5.md

title: Neptune Cluster With IAM Database Authentication Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: c91d7ea0-d4d1-403b-8fe1-c9961ac082c5 Query name: Neptune Cluster With IAM Database Authentication Disabled Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: Neptune Cluster should have IAM Database Authentication enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1 17" resource "awsneptunecluster" "positive1" { cluster_identifier = "neptune-cluster-demo" engine = "neptune" backupretentionperiod = 5 preferredbackupwindow = "07:00-09:00" skipfinalsnapshot = true apply_immediately = true storage_encrypted = true } resource "awsneptunecluster" "positive2" { cluster_identifier = "neptune-cluster-demo" engine = "neptune" backupretentionperiod = 5 preferredbackupwindow = "07:00-09:00" skipfinalsnapshot = true iamdatabaseauthentication_enabled = false apply_immediately = true storage_encrypted = true } ``` ```tf title="Negative test num. 1 - tf file" resource "awsneptunecluster" "negative1" { cluster_identifier = "neptune-cluster-demo" engine = "neptune" backupretentionperiod = 5 preferredbackupwindow = "07:00-09:00" skipfinalsnapshot = true iamdatabaseauthentication_enabled = true apply_immediately = true storage_encrypted = true } ```