cwielenb/CNCF-Dataset huggingface dataset:
Project: SchemaHero (App Definition and Development / Database)
File: README.md

To generate the vault.yaml: helm template vault hashicorp/vault --namespace schemahero-vault --set server.dev.enabled=true are some predefined tables Applying a table.yaml Generating fixtures using schemahero Verifying that the generated fixtures are correct Ideally these tests should be executed from Go code for more reliability and easier to use. ed to run in a namespace named "schemahero-tutorial". The manifests here contain a postgresql 11.8.0 engine, and the SchemaHero database and table components. This directory does not contain the SchemaHero Operator; you'll have to install this yourself or already have it in the cluster. To install the PostgresQL 11.8.0 instance, run the following commands from this (examples/airline) directory: ```shell kubectl apply -f ./postgresql/postgresql-11.8.0.yaml ``` After the database engine has been deployed, the schema directory can be deployed and SchemaHero will create the tables. To start, deploy the database connection: ``` kubectl apply -f ./schema/airlinedb.yaml ``` Deplioy the tables: ``` kubectl apply -f ./schema ``` You can now connect to the database and explore the schema that was created: ```shell kubectl schemahero shell --namespace schemahero-tutorial airlinedb ``` The above command will start a new pod and connect your terminal to it. You'll be authenticated to the database, and the `airlinedb` will already be selected. Try viewing the schema of the reservation table: ``` \d reservation Table "public.reservation" Column | Type | Collation | Nullable | Default +--+--+-+ id | character(8) | | not null | created_at | timestamp without time zone | | not null | first_name | character varying(40) | | | last_name | character varying(40) | | | flight_number | character(4) | | | flight_date | timestamp without time zone | | not null | Indexes: "reservation_pkey" PRIMARY KEY, btree (id) ``` VAULT_TOKEN=root vault write auth/kubernetes/config \ tokenreviewerjwt="$(cat /var/run/secrets/kubernetes.io/serviceaccount/token)" \ kuberneteshost=https://${KUBERNETESPORT443TCP_ADDR}:443 \ kubernetescacert=@/var/run/secrets/kubernetes.io/serviceaccount/ca.crt' ``` Create the policy ``` tee -a /tmp/policy.hcl > /dev/null <<EOT path "database/creds/schemahero" { capabilities = ["read"] } path "database/config/airlinedb" { capabilities = ["read"] } EOT ``` ``` kubectl -n schemahero-vault cp /tmp/policy.hcl vault-0:/tmp/policy.hcl ``` ``` kubectl exec -n schemahero-vault -it vault-0 -- env VAULT_TOKEN=root vault policy write schemahero /tmp/policy.hcl ``` ``` kubectl exec -n schemahero-vault -it vault-0 -- env VAULT_TOKEN=root vault write auth/kubernetes/role/schemahero \ boundserviceaccount_names=schemahero \ boundserviceaccount_namespaces=schemahero-vault \ policies=schemahero \ ttl=1h ``` Deploy the serviceaccount: ``` kubectl apply -f ./vault/sa.yaml ```
Project: KICS (Provisioning / Security & Compliance)
File: e979fcbc-df6c-422d-9458-c33d65e71c45.md

title: ElasticSearch Without Slow Logs hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: e979fcbc-df6c-422d-9458-c33d65e71c45 Query name: ElasticSearch Without Slow Logs Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Observability URL: Ensure that AWS Elasticsearch enables support for slow logs<br> ```tf title="Positive test num. 1 - tf file" hl_lines="4" resource "awselasticsearchdomain" "positive1" { logpublishingoptions { cloudwatchloggrouparn = awscloudwatchloggroup.example.arn logtype = "ESAPPLICATION_LOGS" enabled = true } } ``` ```tf title="Negative test num. 1 - tf file" resource "awselasticsearchdomain" "negative1" { logpublishingoptions { cloudwatchloggrouparn = awscloudwatchloggroup.example.arn logtype = "INDEXSLOW_LOGS" enabled = true //for default its true } } ```
Project: Athenz (Provisioning / Key Management)
File: zts_api.md

The Authorization Token Service (ZTS) API This API has the following attributes: | Attribute | Value | | || | namespace | com.yahoo.athenz.zts | | version | 1 | All ZTS API commands require that the client use a TLS certificate issued by Athenz. Services can use their Athenz Issued Service Identity certificates when communicating with ZTS. Limited number of ZTS API endpoints are authorized against the configured policy data to verify that the principal has been given the rights to make the requested change. Each request description below gives the authorization command that includes the action and resource that the ZTS Server will run the authorization check against. For example, to delete an instance from the local database we have the following authorize statement: ``` sourceCode authorize("delete", "{domain}:instance.{instanceId}"); ``` This indicates that the principal requesting to delete instance id host001 from athenz.ci domain must have grant rights to action "delete" for resource called "instance.host001" in domain "athenz.ci". Please refer to the
Project: StarRocks (App Definition and Development / Database)
File: json_each.md

displayed_sidebar: "English" Expands the outermost elements of a JSON object into a set of key-value pairs held in two columns and returns a table that consists of one row for each element. ```Haskell jsoneach(jsonobject_expr) ``` `jsonobjectexpr`: the expression that represents the JSON object. The object can be a JSON column, or a JSON object that is produced by a JSON constructor function such as PARSE_JSON. Returns two columns: one named key and one named value. The key column stores VARCHAR values, and the value column stores JSON values. The jsoneach function is a table function that returns a table. The returned table is a result set that consists of multiple rows. Therefore, a lateral join must be used in the FROM clause to join the returned table to the original table. The lateral join is mandatory, but the LATERAL keyword is optional. The jsoneach function cannot be used in the SELECT clause. ```plaintext -- A table named tj is used as an example. In the tj table, the j column is a JSON object. mysql> SELECT * FROM tj; +++ | id | j | +++ | 1 | {"a": 1, "b": 2} | | 3 | {"a": 3} | +++ -- Expand the j column of the tj table into two columns by key and value to obtain a result set that consists of multiple rows. In this example, the LATERAL keyword is used to join the result set to the tj table. mysql> SELECT * FROM tj, LATERAL json_each(j); ++++-+ | id | j | key | value | ++++-+ | 1 | {"a": 1, "b": 2} | a | 1 | | 1 | {"a": 1, "b": 2} | b | 2 | | 3 | {"a": 3} | a | 3 | ++++-+ ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.11.20.md

RabbitMQ `3.11.20` is a maintenance release in the `3.11.x` . Please refer to the upgrade section from if upgrading from a version prior to 3.11.0. This release requires Erlang 25 and supports Erlang versions up to `25.3.x`. has more details on Erlang version requirements for RabbitMQ. As of 3.11.0, RabbitMQ requires Erlang 25. Nodes will fail to start on older Erlang releases. Erlang 25 as our new baseline means much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation available to all RabbitMQ 3.11 users. Release notes can be found on GitHub at . Fixed a potential resource leak in at-least-once dead lettering from quorum queues. GitHub issue: A new command, `rabbitmqctl deactivatefreediskspacemonitoring`, can be used to (temporarily or permanently) disable free disk space monitoring on a node. To re-activate it, use `rabbitmqctl activatefreediskspacemonitoring`. GitHub issue: AMQP 1.0 clients that try to publish in a way that results in the message not being routed anywhere are now notified with a more sensible settlement status. GitHub issue: Prometheus scraping API endpoints now support optional authentication. Contributed by @SimonUnge (AWS). GitHub issue: The plugin now filters out values that are `undefined` or `NaN`, simply excluding them from the API endpoint response. Previously, if a metric was not computed for any reason (e.g. free disk space monitor was disabled on the node), its value could end up being rendered as `undefined` or `NaN`, two values that Prometheus scrapers cannot handle (for numerical types such as gauges). GitHub issue: It was not possible to close a table column selection pane on screens that had little vertical space. Contributed by @Antsthebul. GitHub issue: `ra` was upgraded to To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.20.tar.xz` instead of the source tarball produced by GitHub.
Project: YugabyteDB (App Definition and Development / Database)
File: pexpireat.md

title: PEXPIREAT linkTitle: PEXPIREAT description: PEXPIREAT menu: preview: parent: api-yedis weight: 2234 aliases: /preview/api/redis/pexpireat /preview/api/yedis/pexpireat type: docs `PEXPIREAT key ttl-as-timestamp` PEXPIREAT has the same effect as EXPIREAT, but the Unix timestamp at which the key will expire is specified in milliseconds instead of seconds. Returns integer reply, specifically 1 if the timeout was set and 0 if key does not exist. ```sh $ SET yugakey "Yugabyte" ``` ``` "OK" ``` ```sh $ PEXPIREAT yugakey 1555555555005 ``` ``` (integer) 1 ``` ```sh $ PTTL yugakey ``` ``` (integer) 18674452994 ``` , , ,
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-pattern-offboard.md

layout: default title: mesheryctl-pattern-offboard permalink: reference/mesheryctl/pattern/offboard redirect_from: reference/mesheryctl/pattern/offboard/ type: reference display-title: "false" language: en command: pattern subcommand: offboard Offboard pattern Offboard pattern will trigger undeploy of pattern <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl pattern offboard [flags] </div> </pre> Offboard pattern by providing file path <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl pattern offboard -f [filepath] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -f, --file string Path to pattern file -h, --help help for offboard </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -t, --token string Path to token file default from current context -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: Rundeck (Provisioning / Automation & Configuration)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: '' labels: '' assignees: '' Getting Help Please use this template for feature requests only. For support on configuration or troubleshooting please see for the appropriate channels. Is your feature request related to a problem? Please describe. A clear and concise description of what the business problem is. Ex. I'm always frustrated when [...] / I am trying to [...] Describe the solution you'd like A clear and concise description of what you want to happen. Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. Additional context Add any other context or screenshots about the feature request here. Note: That feature requests will be closed after any clarification discussion to keep the open issues list low. Closed issues are still considered as part of feature request backlog. Since this is an Open Source project Pull Requests are welcome with enhancements.
Project: Teleport (Provisioning / Security & Compliance)
File: CODE_OF_CONDUCT.md

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at info@goteleport.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. This Code of Conduct is adapted from the , version 1.4, available at
Project: KICS (Provisioning / Security & Compliance)
File: 4fa66806-0dd9-4f8d-9480-3174d39c7c91.md

title: S3 Bucket Without Ignore Public ACL hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 4fa66806-0dd9-4f8d-9480-3174d39c7c91 Query name: S3 Bucket Without Ignore Public ACL Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: S3 bucket without ignore public ACL<br> ```tf title="Positive test num. 1 - tf file" hl_lines="10" resource "awss3bucket" "positive1" { bucket = "example" } resource "awss3bucketpublicaccess_block" "positive2" { bucket = awss3bucket.example.id blockpublicacls = true blockpublicpolicy = true ignorepublicacls = false } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="7" module "s3_bucket" { source = "terraform-aws-modules/s3-bucket/aws" version = "3.7.0" bucket = "my-s3-bucket" acl = "private" ignorepublicacls = false versioning = { enabled = true } } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="1" module "s3_bucket" { source = "terraform-aws-modules/s3-bucket/aws" version = "3.7.0" bucket = "my-s3-bucket" acl = "private" versioning = { enabled = true } } ``` <details><summary>Positive test num. 4 - tf file</summary> ```tf hl_lines="5" resource "awss3bucket" "positive1" { bucket = "example" } resource "awss3bucketpublicaccess_block" "positive2" { bucket = awss3bucket.example.id blockpublicacls = true blockpublicpolicy = true } ``` </details> ```tf title="Negative test num. 1 - tf file" resource "awss3bucket" "negative1" { bucket = "example" } resource "awss3bucketpublicaccess_block" "negative2" { bucket = awss3bucket.example.id blockpublicacls = true blockpublicpolicy = true ignorepublicacls = true } ``` ```tf title="Negative test num. 2 - tf file" module "s3_bucket" { source = "terraform-aws-modules/s3-bucket/aws" version = "3.7.0" bucket = "my-s3-bucket" acl = "private" ignorepublicacls = true versioning = { enabled = true } } ```
Project: ThreatMapper (Provisioning / Security & Compliance)
File: slack.md

title: Slack ThreatMapper raises notifications to Slack Workspaces using Slack webhooks. Navigate to https://[YourWorkspace].slack.com/apps and search for Incoming Webhooks app from Slack: Click on Add to Slack where you will be asked to choose a channel: Locate the webhook URL: Paste the webhook URL and the corresponding channel name into Deepfence Slack integration page.
Project: KICS (Provisioning / Security & Compliance)
File: be41f891-96b1-4b9d-b74f-b922a918c778.md

title: COS Node Image Not Used hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: be41f891-96b1-4b9d-b74f-b922a918c778 Query name: COS Node Image Not Used Platform: Ansible Severity: <span style="color:#edd57e">Low</span> Category: Insecure Configurations URL: The node image should be Container-Optimized OS(COS)<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="13" name: create a node pool google.cloud.gcpcontainernode_pool: name: my-pool initialnodecount: 4 cluster: "{{ cluster }}" location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present config: imagetype: WINDOWSLTSC ``` ```yaml title="Negative test num. 1 - yaml file" name: create a node pool google.cloud.gcpcontainernode_pool: name: my-pool initialnodecount: 4 cluster: '{{ cluster }}' location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: /tmp/auth.pem state: present config: image_type: COS ``` ```yaml title="Negative test num. 2 - yaml file" name: create a node pool google.cloud.gcpcontainernode_pool: name: my-pool initialnodecount: 4 cluster: "{{ cluster }}" location: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: /tmp/auth.pem state: present config: imagetype: COSCONTAINERD ```
Project: HertzBeat (Observability and Analysis / Observability)
File: alert_threshold_expr.md

id: alertthresholdexpr title: Threshold trigger expression sidebar_label: Threshold trigger expression When we configure the threshold alarm, we need to configure the threshold trigger expression. The system calculates whether to trigger the alarm according to the expression and the monitoring index value. Here is a detailed introduction to the use of the expression. ``` equals(str1,str2) == < <= = != ( ) && || ``` Rich operators allow us to define expressions freely. Note For the equality of string, please use `equals(str1,str2)`, while for the equality judgment of number, please use == or != Environment variables, i.e. supported variables such as Metric values, are used in the expression. When the threshold value is calculated and judged, the variables will be replaced with actual values for calculation. Non fixed environment variablesThese variables will change dynamically according to the monitoring Metric object we choose. For example, if we choose response time Metric of website monitoring, the environment variables will have `responseTime - This is the response time variable` If we want to set when the response time of website monitoring is greater than 400 to trigger an alarmthe expression is `responseTime>400` Fixed environment variables(Rarely used)`instance : Row instance value` This variable is mainly used to calculate multiple instances. For example, we collected `usage`(`usage is non fixed environment variables`) of disk C and disk D, but we only want to set the alarm when the usage of C disk is greater than 80. Then the expression is `equals(instance,"c")&&usage>80` Website monitoring -> Trigger alarm when the response time is greater than or equal to 400ms `responseTime>=400` API monitoring -> Trigger alarm when the response time is greater than 3000ms `responseTime>3000` Entire site monitoring -> Trigger alarm when URL(instance) path is `https://baidu.com/book/3` and the response time is greater than 200ms `equals(instance,"https://baidu.com/book/3")&&responseTime>200` MYSQL monitoring -> status Metric group -> Trigger alarm when hreads_running(number of running threads) Metric is greater than 7 `threads_running>7` Other issues can be fed back through the communication group ISSUE!
Project: OpenTracing (Observability and Analysis / Observability)
File: ISSUE_TEMPLATE.md

<!-- Welcome to the OpenTracing Go repo! Please be respectful and considerate of others when commenting on issues. Please search for existing issues in order to ensure we don't have duplicate bugs/feature requests. If you have a question please ask it on our Gitter chat https://gitter.im/opentracing/public instead of creating an issue. Please provide as much information as possible so we all understand the issue. --> Please explain your user story, what you are trying to do, which problem you are trying to solve. What prevents you from solving your use case. A proposal that from your POV would solve the problem or improve the existing situation. If you don't have a proposed solution, that's fine too. Questions that should be answered during the discussion of this issue before jumping into code.
Project: SkyWalking (Observability and Analysis / Observability)
File: otlp-trace.md

SkyWalking can receive traces from Traces in OTLP format and convert them to Zipkin Trace format eventually. For data analysis and queries related to Zipkin Trace, please . OTLP Trace handler references the to convert the data format. Make sure to enable otlp-traces handler in OTLP receiver of `application.yml`. ```yaml receiver-otel: selector: default default: enabledHandlers: otlp-traces ``` Make sure to enable zipkin receiver and zipkin query in `application.yml` for config the zipkin. Please read for query OTLP traces.