cwielenb/CNCF-Dataset huggingface dataset:
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_data_verify_mysql.md

title: Kubectl-Dba Data Verify Mysql menu: docs_{{ .version }}: identifier: kubectl-dba-data-verify-mysql name: Kubectl-Dba Data Verify Mysql parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Verify rows to a mysql resource Use this cmd to verify data in a mysql object ``` kubectl-dba data verify mysql [flags] ``` ``` kubectl dba data verify mysql -n demo sample-mysql --rows 1000 ``` ``` -h, --help help for mysql -r, --rows int number of rows to verify (default 100) ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "/home/runner/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --default-seccomp-profile-type string Default seccomp profile --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --password string Password for basic authentication to the API server --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use --username string Username for basic authentication to the API server ``` - Verify data in a database
Project: KICS (Provisioning / Security & Compliance)
File: be96849c-3df6-49c2-bc16-778a7be2519c.md

title: Secure Ciphers Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: be96849c-3df6-49c2-bc16-778a7be2519c Query name: Secure Ciphers Disabled Platform: CloudFormation Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: Check if secure ciphers aren't used in CloudFront<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="26" AWSTemplateFormatVersion: "2010-09-09" Resources: cloudfrontdistribution: Type: AWS::CloudFront::Distribution Properties: DistributionConfig: CacheBehaviors: LambdaFunctionAssociations: EventType: viewer-request LambdaFunctionARN: examp DefaultCacheBehavior: LambdaFunctionAssociations: EventType: viewer-request LambdaFunctionARN: examp IPV6Enabled: true Origins: CustomOriginConfig: OriginKeepaliveTimeout: 60 OriginReadTimeout: 30 Tags: Key: name Value: example ViewerCertificate: CloudFrontDefaultCertificate: false MinimumProtocolVersion: SSLv3 ``` ```json title="Positive test num. 2 - json file" hl_lines="44" { "AWSTemplateFormatVersion": "2010-09-09", "Resources": { "cloudfrontdistribution": { "Type": "AWS::CloudFront::Distribution", "Properties": { "DistributionConfig": { "Origins": [ { "CustomOriginConfig": { "OriginKeepaliveTimeout": 60, "OriginReadTimeout": 30 } } ], "CacheBehaviors": [ { "LambdaFunctionAssociations": [ { "EventType": "viewer-request", "LambdaFunctionARN": "examp" } ] } ], "DefaultCacheBehavior": { "LambdaFunctionAssociations": [ { "EventType": "viewer-request", "LambdaFunctionARN": "examp" } ] }, "IPV6Enabled": true }, "Tags": [ { "Key": "name", "Value": "example" } ], "ViewerCertificate": { "CloudFrontDefaultCertificate": false, "MinimumProtocolVersion": "SSLv3" } } } } } ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: "2010-09-09" Resources: cloudfrontdistribution: Type: AWS::CloudFront::Distribution Properties: DistributionConfig: CacheBehaviors: LambdaFunctionAssociations: EventType: viewer-request LambdaFunctionARN: examp DefaultCacheBehavior: LambdaFunctionAssociations: EventType: viewer-request LambdaFunctionARN: examp IPV6Enabled: true Origins: CustomOriginConfig: OriginKeepaliveTimeout: 60 OriginReadTimeout: 30 Tags: Key: name Value: example ViewerCertificate: CloudFrontDefaultCertificate: true ``` ```json title="Negative test num. 2 - json file" { "AWSTemplateFormatVersion": "2010-09-09", "Resources": { "cloudfrontdistribution": { "Type": "AWS::CloudFront::Distribution", "Properties": { "DistributionConfig": { "CacheBehaviors": [ { "LambdaFunctionAssociations": [ { "EventType": "viewer-request", "LambdaFunctionARN": "examp" } ] } ], "DefaultCacheBehavior": { "LambdaFunctionAssociations": [ { "LambdaFunctionARN": "examp", "EventType": "viewer-request" } ] }, "IPV6Enabled": true, "Origins": [ { "CustomOriginConfig": { "OriginKeepaliveTimeout": 60, "OriginReadTimeout": 30 } } ] }, "Tags": [ { "Key": "name", "Value": "example" } ], "ViewerCertificate": { "CloudFrontDefaultCertificate": true } } } } } ```
Project: Timescale (App Definition and Development / Database)
File: BuildSource.md

If you are building from source for non-development purposes (i.e., you want to run TimescaleDB, not submit a patch), you should always use a release-tagged commit and not build from `main`. See the Releases tab for the latest release. Prerequisites: A standard PostgreSQL 14, 15 or 16 installation with development environment (header files) (e.g., `postgresql-server-dev-16` package for Linux, Postgres.app for MacOS) C compiler (e.g., gcc or clang) version 3.4 or greater ```bash git clone git@github.com:timescale/timescaledb.git cd timescaledb git checkout 2.15.0 ./bootstrap cd build && make make install ``` Note, if you have multiple versions of PostgreSQL installed you can specify the path to `pg_config` that should be used by using `./bootstrap -DPGCONFIG=/path/to/pgconfig`. Please see our . If you are building from source for non-development purposes (i.e., you want to run TimescaleDB, not submit a patch), you should always use a release-tagged commit and not build from `main`. See the Releases tab for the latest release. Prerequisites: A standard OpenSSL for Windows Microsoft Visual Studio 2017 with CMake and Git components OR Visual Studio 2015/2016 with version 3.4 or greater and Git Make sure all relevant binaries are in your PATH: `pg_config` and `cmake` If using Visual Studio 2017 with the CMake and Git components, you should be able to simply clone the repo and open the folder in Visual Studio which will take care of the rest. If you are using an earlier version of Visual Studio, then it can be built in the following way: ```bash git clone git@github.com:timescale/timescaledb.git cd timescaledb git checkout 2.15.0 bootstrap.bat cmake --build ./build --config Release cmake --build ./build --config Release --target install ```
Project: Meshery (Provisioning / Automation & Configuration)
File: community.md

layout: default title: Meshery Community permalink: project/community abstract: Meshery's open source, cloud native community language: en type: project category: community list: include Meshery is a CNCF project maintained by engineers from Layer5, VMware, Red Hat, Rackspace, Citrix, Instabase, Microsoft, OpenGov, Computas AS, Rill Data, Quantex, Lumina Networks, API7, F5, Citi, Acquia, and HashiCorp. Meshery is an open source project that adheres to the . Meshery advance the state of the art surrounding cloud native management and enable adopters of Cloud Native technologies and techniques to do so with confidence. Our shared commitment to the open source spirit pushes Meshery forward. Meshery is one of a number of open source projects originated by the <a href="https://layer5.io/community">Layer5 community</a>. Get involved with Meshery and supporting projects. Start by reading through the , which provides details on how to participate. Seek out other community members, who will make sure you are not left out. We always have a role for everyone whether to be a code-writer, a community manager, user, advocate, or just to listen in. The Meshery community is always open and warmly welcomes you. If this is your first time making open source contribution, you are in the right place! Please see our for specific details about setting up your development environment and to start learning the innerworkings of a specific Meshery component. The Meshery project is community-built and welcomes collaboration! <a href="https://github.com/meshery/meshery"><i class="fab fa-github"></i> Fork Meshery</a> Join any of the . Watch and subscribe to the . Fill-in a <a href="https://layer5.io/newcomers">community member form</a> to gain access to community resources. Giving a talk or hosting a meetup about Meshery? Leverage existing slides or request swag to support your talk. <div class="wrapper"> <a href="https://forms.gle/1jqY7HWveSFKCdnD6"><div class="overview">Share your event</div></a> <a href="https://layer5.io/newcomers"><div class="overview">Access slides and resources</div></a> </div>
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-volume.1.md

% podman-volume 1 podman\-volume - Simple management tool for volumes podman volume subcommand podman volume is a set of subcommands that manage volumes. | Command | Man Page | Description | | - | | | | create | | Create a new volume. | | exists | | Check if the given volume exists. | | export | | Export volume to external tar. | | import | | Import tarball contents into an existing podman volume. | | inspect | | Get detailed information on one or more volumes. | | ls | | List all the available volumes. | | mount | | Mount a volume filesystem. | | prune | | Remove all unused volumes. | | reload | | Reload all volumes from volumes plugins. | | rm | | Remove one or more volumes. | | unmount | | Unmount a volume. | November 2018, Originally compiled by Urvashi Mohnani <umohnani@redhat.com>
Project: Packer (App Definition and Development / Application Definition & Image Build)
File: bug_report.md

name: Bug Report about: You're experiencing an issue with Packer that is different from the documented behavior. labels: bug <! Please keep this note for the community > Please vote on this issue by adding a to the original issue to help the community and maintainers prioritize this request Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request If you are interested in working on this issue or have submitted a pull request, please leave a comment <! Thank you for keeping this note for the community > When filing a bug, please include the following headings if possible. Any example text in this template can be deleted. A paragraph or two about the issue you're experiencing. Steps to reproduce this issue From `packer version` If the file is longer than a few dozen lines, please include the URL to the of the log or use the [Github detailed format](https://gist.github.com/ericclemmons/b146fe5da72ca1f706b2ef72a20ac39d) instead of posting it directly in the issue. OS, Architecture, and any other information you can provide about the environment. Include appropriate log fragments. If the log is longer than a few dozen lines, please include the URL to the of the log or use the instead of posting it directly in the issue. Set the env var `PACKER_LOG=1` for maximum log detail.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_fault_pod.md

title: kbcli fault pod Pod chaos. ``` -h, --help help for pod ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - Inject faults to pod. - failure pod - kill pod - kill containers
Project: YugabyteDB (App Definition and Development / Database)
File: yba_universe_describe.md

Describe a YugabyteDB Anywhere universe Describe a universe in YugabyteDB Anywhere ``` yba universe describe [flags] ``` ``` -n, --name string [Required] The name of the universe to be described. -h, --help help for describe ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage YugabyteDB Anywhere universes
Project: kaniko (App Definition and Development / Application Definition & Image Build)
File: MIGRATION_GUIDE.md

Starting from , the import path will be: "github.com/golang-jwt/jwt/v4" The `/v4` version will be backwards compatible with existing `v3.x.y` tags in this repo, as well as `github.com/dgrijalva/jwt-go`. For most users this should be a drop-in replacement, if you're having troubles migrating, please open an issue. You can replace all occurrences of `github.com/dgrijalva/jwt-go` or `github.com/golang-jwt/jwt` with `github.com/golang-jwt/jwt/v4`, either manually or by using tools such as `sed` or `gofmt`. And then you'd typically run: ``` go get github.com/golang-jwt/jwt/v4 go mod tidy ``` The original migration guide for older releases can be found at https://github.com/dgrijalva/jwt-go/blob/master/MIGRATION_GUIDE.md.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_project_iam_binding.md

+++ title = "googleprojectiam_binding resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleprojectiam_binding" identifier = "inspec/resources/gcp/googleprojectiambinding.md googleprojectiambinding resource" parent = "inspec/resources/gcp" +++ A `googleprojectiam_binding` is used to test a Google Project Iam Bindings ```ruby describe googleprojectiam_binding(project: "project", role: "roles/editor") do it { should exist } its('members') { should include 'user:testuser@example.com' } end ``` This resource supports . Specifying a `condition` in the constructor matches only bindings with that condition. `condition` has three possible fields, `title`, `expression` and `description`. If any of these fields are unspecified they will not be matched. ``` describe googleprojectiam_binding(project: "project", role: "roles/browser", condition: { title: "my title" }) do it { should exist } its('members.count'){ should cmp 1 } its('members') { should include 'user:testuser@example.com' } its('condition.title') {should cmp 'my title' } its('condition.expression') { should cmp "request.time < timestamp('2020-10-01T00:00:00.000Z')" } end ``` Properties that can be accessed from the `googleprojectiam_binding` resource: `role` : Role that is assigned to members. For example, roles/viewer, roles/editor, or roles/owner. `members` : Specifies the identities requesting access for a Cloud Platform resource. `condition` : Contains information about when this binding is to be applied. `expression` : Textual representation of an expression in Common Expression Language syntax. `title` : An optional title for the expression, i.e. a short string describing its purpose. `description` : An optional description of the expression. This is a longer text which describes the expression. Ensure the is enabled for the current project.
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: v1.12.3.md

This update includes bug fixes: In HTTP service invocation, in certain cases when a resiliency policy is applied (for example, one that includes timeouts), requests could be interrupted earlier with a "context deadline exceeded" error. Impacts users running Dapr 1.12.0-1.12.2 that use HTTP service invocation and who have resiliency policies applied When resiliency policies with timeouts are applied, due to a bug the incorrect context was used while sending the response to the client, and in certain situations it could have been terminated earlier than the request. We fixed the code that handles HTTP service invocation to make sure the timeout is applied to the entire response. Placement nodes acquire a lock, disseminate the tables, and release the lock in parallel. The Placement stream disconnects before the dissemination of tables. ``` Error invoke actor method: failed to invoke target x after 3 retries ``` Placement server logs: ``` level=error msg="Stream is disconnected before member is added ``` Impacts users running Dapr 1.12.0-1.12.2 Dissemination did not use a background context. The logic to acquire a lock, disseminate the tables, and release the lock were all occurring in parallel. Updated the Dapr Placement service to use a background context and follow a 3 step process to acquire a lock, disseminate the tables, and release the lock. When using a database with a case-sensitive collation, the SQL Server state store component did not work correctly. Certain operations, including those relied upon by the actor state store, were failing. Impacts users of Dapr 1.11.0-1.12.2 A stored procedure referenced a column named with the wrong case. This was causing errors on case-sensitive databases. We updated the stored procedure so it does use the correct case for column names. When using Dapr with Kafka for Pub/Sub and subscribing to multiple topics, users might see bottlenecks in Kafka message processing and long init times when the Dapr sidecar is starting up. Impacts users of Dapr 1.11.0-1.12.2 When new topic subscriptions were added, Dapr would close the consumer group and recreate it, leading to partition rebalance across the cluster. The Kafka consumer logic was changed to not recreate the consumer group every time a new topic subscription is added.
Project: OpenSCAP (Provisioning / Security & Compliance)
File: README.md

](https://github.com/OpenSCAP/openscap/actions/workflows/build.yml) ](https://gitter.im/OpenSCAP/openscap?utmsource=badge&utmmedium=badge&utmcampaign=pr-badge&utmcontent=badge) Open Source Security Compliance Solution The `oscap` program is a command line tool that allows users to load, scan, validate, edit, and export SCAP documents. Homepage of the project: User Manual: Compilation, testing and debugging: For new contributors: We welcome all contributions to the OpenSCAP project. If you would like to contribute, either by fixing existing issues or adding new features, please check out our to get started. If you would like to discuss anything, ask questions, or if you need additional help getting started, you can either send a message to our libera.chat IRC channel, #openscap, or to our . The Microsoft Windows support as of Febuary 1, 2022. The following example shows how to validate a given source data stream; all components within the data stream are validated (XCCDF, OVAL, OCIL, CPE, and possibly other components): ``` oscap ds sds-validate scap-ds.xml ``` To evaluate all definitions within the given OVAL Definition file, run the following command: ``` oscap oval eval --results oval-results.xml scap-oval.xml ``` where scap-oval.xml is the OVAL Definition file and oval-results.xml is the OVAL Result file. To evaluate all definitions from the OVAL component that are part of a particular data stream within a SCAP data stream collection, run the following command: ``` oscap oval eval --datastream-id ds.xml --oval-id xccdf.xml --results oval-results.xml scap-ds.xml ``` where ds.xml is the given data stream, xccdf.xml is an XCCDF file specifying the OVAL component, oval-results.xml is the OVAL Result file, and scap-ds.xml is a file representing the SCAP data stream collection. To evaluate a specific profile in an XCCDF file run this command: ``` oscap xccdf eval --profile Desktop --results xccdf-results.xml --cpe cpe-dictionary.xml scap-xccdf.xml ``` where scap-xccdf.xml is the XCCDF document, Desktop is the selected profile from the XCCDF document, xccdf-results.xml is a file storing the scan results, and cpe-dictionary.xml is the CPE dictionary. To evaluate a specific XCCDF benchmark that is part of a data stream within a SCAP data stream collection run the following command: ``` oscap xccdf eval --datastream-id ds.xml --xccdf-id xccdf.xml --results xccdf-results.xml scap-ds.xml ``` where scap-ds.xml is a file representing the SCAP data stream collection, ds.xml is the particular data stream, xccdf.xml is ID of the component-ref pointing to the desired XCCDF document, and xccdf-results.xml is a file containing the scan results. without XCCDF rules ``` oscap xccdf generate guide XCCDF-FILE > XCCDF-GUIDE-FILE ``` with XCCDF rules ``` oscap xccdf generate guide --profile PROFILE XCCDF-FILE > XCCDF-GUIDE-FILE ``` generate report from scanning ``` oscap xccdf generate report XCCDF-RESULT-FILE > XCCDF-REPORT-FILE ```