cwielenb/CNCF-Dataset huggingface dataset:
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: chef-automate.md

title: Chef Automate subtitle: Operational Visibility Dashboard tutorials: https://github.com/chef/automate/tree/master/components/authz-service#authz-with-opa videos: title: 'OPA in Practice: From Angular to OPA in Chef Automate' speakers: name: Michael Sorens organization: chef venue: OPA Summit at Kubecon San Diego 2019 link: https://www.youtube.com/watch?v=jrrW855xL3s docs_features: go-integration: note: | Chef Automate uses the Go Rego API to evaluate authorization policies controlling access to its own API endpoints. The feature is . allowmissingimage: true Application require authorization decisions made at the API gateway, frontend, backend, and database. OPA helps developers decouple authorization logic from application code, define a custom authorization model that enables end-users to control tenant permissions, and enforce that policy across the different components of the application (gateway, frontend, backend, database).
Project: CyberArk Conjur (Provisioning / Key Management)
File: Readme.md

The web development environment uses Docker to provide an expertly configured local Ruby environment. To build and serve the site on your computer, first run the following command from this directory: ```sh-session $ _deploy/run.sh ``` Then `open localhost:4000` to view it in your browser. The site is rebuilt automatically every time you save a file. Just refresh your browser tab (<kbd>&#8984;-R</kbd> on Mac, <kbd>Ctrl-R</kbd> elsewhere) to see updates. To stop the container, press <kbd>Ctrl-C</kbd> in the terminal. This website is generated using Jekyll. We've documented our use and best practices in . ```sh-session $ cd $(git rev-parse --show-cdup) # start in the project root $ _deploy/checklinks.sh ``` This script uses Docker to run on the rendered site and will report broken links as errors. It's automatically run as part of our continuous integration pipeline, but it's a good idea to run it yourself whenever you add or remove links.
Project: KICS (Provisioning / Security & Compliance)
File: 3d3f6270-546b-443c-adb4-bb6fb2187ca6.md

title: EBS Default Encryption Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 3d3f6270-546b-443c-adb4-bb6fb2187ca6 Query name: EBS Default Encryption Disabled Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: EBS Encryption should be enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="2" resource "awsebsencryptionbydefault" "positive1" { enabled = false } ``` ```tf title="Negative test num. 1 - tf file" resource "awsebsencryptionbydefault" "negative1" { enabled = true } resource "awsebsencryptionbydefault" "negative2" { } ```
Project: KICS (Provisioning / Security & Compliance)
File: d15db953-a553-4b8a-9a14-a3d62ea3d79d.md

title: Components Callback Definition Is Unused hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: d15db953-a553-4b8a-9a14-a3d62ea3d79d Query name: Components Callback Definition Is Unused Platform: OpenAPI Severity: <span style="color:#5bc0de">Info</span> Category: Best Practices URL: Components callbacks definitions should be referenced or removed from Open API definition<br> ```json title="Positive test num. 1 - json file" hl_lines="22" { "openapi": "3.0.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "$ref": "#/components/schemas/Success" } } } } }, "components": { "callbacks": { "inProgress": { "{$request.body#/inProgressUrl}": { "post": { "requestBody": { "$ref": "#/components/requestBodies/callbackMessage1" }, "responses": { "200": { "description": "OK" } } } } } } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="15" openapi: 3.0.0 info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '200': "$ref": "#/components/schemas/Success" components: callbacks: inProgress: "{$request.body#/inProgressUrl}": post: requestBody: "$ref": "#/components/requestBodies/callbackMessage1" responses: '200': description: OK ``` ```json title="Negative test num. 1 - json file" { "openapi": "3.0.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "$ref": "#/components/schemas/Success" } }, "callbacks": { "myEvent": { "$ref": "#/components/callbacks/inProgress" } } } } }, "components": { "callbacks": { "inProgress": { "{$request.body#/inProgressUrl}": { "post": { "requestBody": { "$ref": "#/components/requestBodies/callbackMessage1" }, "responses": { "200": { "description": "OK" } } } } } } } } ``` ```yaml title="Negative test num. 2 - yaml file" openapi: 3.0.0 info: title: Simple API overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": $ref: "#/components/schemas/Success" callbacks: myEvent: $ref: "#/components/callbacks/inProgress" components: callbacks: inProgress: "{$request.body#/inProgressUrl}": post: requestBody: $ref: "#/components/requestBodies/callbackMessage1" responses: "200": description: OK ```
Project: Scylla (App Definition and Development / Database)
File: system_schema_keyspace.md

This section describes layouts and usage of system\_schema.* tables. Computed columns are a special kind of columns. Rather than having their value provided directly by the user, they are computed - possibly from other column values. Examples of such computed columns could be: token column generated from the base partition key for secondary indexes map value column, generated as the extraction of a single value from a map stored in a different column Computed columns in many ways act as regular columns, so they are also present in the `system_schema.columns` table - `systemschema.computedcolumns` is an additional mapping that marks the column as computed and provides its computation. Schema: ~~~ CREATE TABLE systemschema.computedcolumns ( keyspace_name text, table_name text, column_name text, computation blob, PRIMARY KEY (keyspacename, tablename, column_name) ) WITH CLUSTERING ORDER BY (tablename ASC, columnname ASC); ~~~ `computation` is stored as a blob and its contents are assumed to be a JSON representation of computation's type and any custom fields needed. Example representations: ~~~ {'type':'token'} {'type':'mapvalue','map':'mymapcolumnname','key':'AF$^GESHHgge6yhf'} ~~~ The token computation does not need additional arguments, as it returns the token of base's partition key. In order to compute a map value, what's additionally needed is the column name that stores the map and the key at which the value is expected.
Project: KusionStack (Provisioning / Automation & Configuration)
File: kusion_workspace_create.md

Create a new workspace This command creates a workspace with specified name and configuration file, where the file must be in the YAML format. ``` kusion workspace create ``` ``` kusion workspace create dev -f dev.yaml ``` ``` -f, --file string the path of workspace configuration file -h, --help help for create ``` ``` --profile string Name of profile to capture. One of (none|cpu|heap|goroutine|threadcreate|block|mutex) (default "none") --profile-output string Name of the file to write the profile to (default "profile.pprof") ``` - Workspace is a logical concept representing a target that stacks will be deployed to
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: 1.10.md

Today we have some BIG news! We're excited to announce out 1.10.0 release . But, we're even more excited to be celebrating our one-year anniversary! We want to celebrate this milestone with each of our users! Please take a few minutes to give us the gift of your insight and feedback by taking our birthday survey. Our Monokle team wishes to build a bigger and better tool for YOU! So, please help us make this birthday wish a reality.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: join-beam.md

title: "Join Beam Community" aliases: /community/ /use/issue-tracking/ /use/mailing-lists/ /get-started/support/ <!-- 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. --> <div class="wrapper-join-beam"> Were so glad you want to join the Apache Beam community. Heres a pathway you can follow to help you get started. This is not the only way to join, but its the recommended progression so youre successful at reaching your objectives. {{< community/joinbeamcolumns number-of-data="0" >}} {{< community/joinbeamcolumns number-of-data="1" >}} {{< community/joinbeamcolumns number-of-data="2" >}} {{< community/joinbeamcolumns number-of-data="3" >}} Send us a note at <a href="mailto:dev@beam.apache.org">user@beam.apache.org</a> OR mention <a target="_blank" href="https://twitter.com/apachebeam?lang=en">@ApacheBeam</a> on Twitter OR ask us in the #beam slack channel. We look forward to seeing you in the community! </div>
Project: KICS (Provisioning / Security & Compliance)
File: 19ffbe31-9d72-4379-9768-431195eae328.md

title: User With Privilege Escalation By Actions 'cloudformation:CreateStack' And 'iam:PassRole' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 19ffbe31-9d72-4379-9768-431195eae328 Query name: User With Privilege Escalation By Actions 'cloudformation:CreateStack' And 'iam:PassRole' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: User with privilege escalation by actions 'cloudformation:CreateStack' and 'iam:PassRole' and Resource set to '*'. For more information see https://rhinosecuritylabs.com/aws/aws-privilege-escalation-methods-mitigation/.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsiamuser" "cosmic" { name = "cosmic" } resource "awsiamuserpolicy" "testinline_policy" { name = "testinlinepolicy" user = awsiamuser.cosmic.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "cloudformation:CreateStack", ] Effect = "Allow" Resource = "*" }, ] }) } resource "awsiampolicy_attachment" "test-attach" { name = "test-attachment" users = [awsiamuser.cosmic.name] roles = [awsiamrole.role.name] groups = [awsiamgroup.group.name] policyarn = awsiam_policy.policy.arn } resource "awsiampolicy" "policy" { name = "test-policy" description = "A test policy" policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "iam:PassRole", ] Effect = "Allow" Resource = "*" }, ] }) } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamuser" "cosmic2" { name = "cosmic2" } resource "awsiamuserpolicy" "inlinepolicyruninstances2" { name = "inlinepolicyrun_instances" user = awsiamuser.cosmic2.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "ec2:Describe*", ] Effect = "Allow" Resource = "*" }, ] }) } ```
Project: BOSH (Provisioning / Automation & Configuration)
File: CONTRIBUTING.md

Your contributions to Ginkgo are essential for its long-term maintenance and improvement. Please open an issue first - describe what problem you are trying to solve and give the community a forum for input and feedback ahead of investing time in writing code! Ensure adequate test coverage: When adding to the Ginkgo library, add unit and/or integration tests (under the `integration` folder). When adding to the Ginkgo CLI, note that there are very few unit tests. Please add an integration test. Make sure all the tests succeed via `ginkgo -r -p` Vet your changes via `go vet ./...` Update the documentation. Ginkgo uses `godoc` comments and documentation in `docs/index.md`. You can run `bundle exec jekyll serve` in the `docs` directory to preview your changes. Thanks for supporting Ginkgo! RELEASING.md to learn how to cut a release. Thanks for supporting Gomega!
Project: Scylla (App Definition and Development / Database)
File: CONTRIBUTING.md

Use the or the for general questions and help. Join the for deeper technical discussions and to discuss your ideas for contributions. Please use the to report issues or to suggest features. Fill in as much information as you can in the issue template, especially for performance problems. Before you can contribute code to Scylla for the first time, you should sign the and send the signed form cla@scylladb.com. You can then submit your changes as patches to the to the or as a pull request to the . If you need help formatting or sending patches, . The Scylla C++ source code uses the so please adhere to that in your patches. Note that Scylla code is written with `using namespace seastar`, so should not explicitly add the `seastar::` prefix to Seastar symbols. You will usually not need to add `using namespace seastar` to new source files, because most Scylla header files have `#include "seastarx.hh"`, which does this. Header files in Scylla must be self-contained, i.e., each can be included without having to include specific other headers first. To verify that your change did not break this property, run `ninja dev-headers`. If you added or removed header files, you must `touch configure.py` first - this will cause `configure.py` to be automatically re-run to generate a fresh list of header files. For more criteria on what reviewers consider good code, see the .
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.9.22.md

RabbitMQ `3.9.22` is a maintenance release in the `3.9.x` release series. Please refer to the Upgrading to 3.9 section from if upgrading from a version prior to 3.9.0. This release requires at least Erlang 24.x, and supports Erlang 25. has more details on Erlang version requirements for RabbitMQ. Release notes can be found on GitHub at . In environments where DNS resolution is not yet available at the time RabbitMQ nodes boot and try to perform , such as CoreDNS with default caching interval of 30s on Kubernetes, nodes now will retry hostname resolution (including of their own host) several times with a wait interval. The recommended solution is to . GitHub issue: Reduce log noise when `sysctl` cannot be accessed by node memory monitor. GitHub issue: Prometheus plugin now exposes one more metric, `processstarttime_seconds`, the moment of node process startup in seconds. GitHub issue: Shovels now handle consumer delivery timeouts gracefully and restart. Contributed by @Haster2004. GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.9.22.tar.xz` instead of the source tarball produced by GitHub.
Project: zot (Provisioning / Container Registry)
File: README.md

In order to create a new generator (which will generate new tasks one by one) and add it to the scheduler there are 4 methods which should be implemented: *Next() (Task, error)* ``` This method should implement the logic for generating a new task. Basically, when this method is called by the scheduler it should return the next task until there are no more tasks to be generated. Also, the Task returned by this method should implement DoWork(ctx context.Context) method which should contain the logic that should be executed when this task is run by the scheduler. ``` *IsDone() bool* ``` This method should return true after the generator finished all the work and has no more tasks to generate. ``` *IsReady() bool* ``` This method should return true if the generator is ready to generate a new task and should be used when it is needed to generate tasks with some delay between. ``` *Reset()* ``` When this method is called the generator should reset to its initial state. After the generator is reset, it will generate new tasks as if it hadn't been used before. This is useful for periodic generators, because the scheduler will call this method when the generator is done and has to wait a specific interval of time for this generator to become ready to run again. ``` The scheduler accepts both periodic and non-periodic generators. To submit a generator to the scheduler, *SubmitGenerator* should be called with the implemented generator, interval of time (which should be time.Duration(0) in case of non-periodic generator, or the interval for the periodic generator) and the priority of the tasks which will be generated by this generator as parameters. Notes: A generator should submit only tasks having the same priority The priority of a task can be: LowPriority, MediumPriority or HighPriority In order to create a new task and add it to the scheduler we need to implement below methods: *DoWork(ctx context.Context) error* ``` This should contain the logic that should be executed when this task is run by the scheduler. ``` *Name() string* ``` Name of the task. ``` *String() string* ``` Description of the task. Used in debugging to identify executed task. ``` To submit a task to the scheduler *SubmitTask* should be called with the implemented task and the priority of the task as parameters. Note: A task can not be periodic. In order to add a periodic task, it can be created a generator which will generate periodically the same task.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_plugin_describe.md

title: kbcli plugin describe Describe a plugin ``` kbcli plugin describe [flags] ``` ``` kbcli plugin describe [PLUGIN] kbcli plugin describe [INDEX/PLUGIN] ``` ``` -h, --help help for describe ``` ``` --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 ``` - Provides utilities for interacting with plugins.
Project: Apache StreamPipes (App Definition and Development / Streaming & Messaging)
File: index.md

<!-- ~ 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. ~ --> <h4 align="center"><a href="https://github.com/apache/streampipes">StreamPipes</a> is a self-service (Industrial) IoT toolbox to enable non-technical users to connect, analyze and explore IoT data streams.</h4> <h3 align="center">Apache StreamPipes for Python </h3> <p align="center"> Apache StreamPipes meets Python! We are working highly motivated on a Python library to interact with StreamPipes. In this way, we would like to unite the power of StreamPipes to easily connect to and read from different data sources, especially in the IoT domain, and the amazing universe of data analytics libraries in Python. </p> As a quick example, we demonstrate how to set up and configure a StreamPipes client. In addition, we will get the available data lake measures out of StreamPipes. ```python from streampipes.client import StreamPipesClient from streampipes.client.config import StreamPipesClientConfig from streampipes.client.credential_provider import StreamPipesApiKeyCredentials config = StreamPipesClientConfig( credential_provider = StreamPipesApiKeyCredentials( username = "test@streampipes.apache.org", api_key = "DEMO-KEY", ), host_address = "localhost", https_disabled = True, port = 80 ) client = StreamPipesClient(client_config=config) measures = client.dataLakeMeasureApi.all() len(measures) ``` Output: ``` 1 ``` <br> ``` measures.to_pandas() ``` Output: ``` measurename timestampfield ... pipelineisrunning numeventproperties 0 test s0::timestamp ... False 2 [1 rows x 6 columns] ``` <br> Alternatively, you can provide your credentials via environment variables. Simply define your credential provider as follows: ```python from streampipes.client.credential_provider import StreamPipesApiKeyCredentials StreamPipesApiKeyCredentials() ``` This requires to set the following environment variables: `SPAPIKEY` and `SP_USERNAME` <br> `username` is always the username that is used to log in into StreamPipes. <br> ??? tip "How to get your StreamPipes API key" The `api_key` can be generated within the UI as demonstrated below: <br>