cwielenb/CNCF-Dataset huggingface dataset:
Project: Carvel (App Definition and Development / Application Definition & Image Build)
File: README_S3_Batch_Job.md

The following is a sample class and Lambda function that receives Amazon S3 event record data as an input and writes some of the record data to CloudWatch Logs. (Note that anything written to stdout or stderr will be logged as CloudWatch Logs events.) ```go import ( "fmt" "context" "github.com/aws/aws-lambda-go/events" ) func handler(ctx context.Context, e events.S3BatchJobEvent) (response events.S3BatchJobResponse, err error) { fmt.Printf("InvocationSchemaVersion: %s\n", e.InvocationSchemaVersion) fmt.Printf("InvocationID: %s\n", e.InvocationID) fmt.Printf("Job.ID: %s\n", e.Job.ID) for _, task := range e.Tasks { fmt.Printf("TaskID: %s\n", task.TaskID) fmt.Printf("S3Key: %s\n", task.S3Key) fmt.Printf("S3VersionID: %s\n", task.S3VersionID) fmt.Printf("S3BucketARN: %s\n", task.S3BucketARN) } fmt.Printf("InvocationSchemaVersion: %s\n", response.InvocationSchemaVersion) fmt.Printf("TreatMissingKeysAs: %s\n", response.TreatMissingKeysAs) fmt.Printf("InvocationID: %s\n", response.InvocationID) for _, result := range response.Results { fmt.Printf("TaskID: %s\n", result.TaskID) fmt.Printf("ResultCode: %s\n", result.ResultCode) fmt.Printf("ResultString: %s\n", result.ResultString) } return } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.8.md

layout: release date: 2024-01-08 tag: v0.7.8 [LocalProvider] Cleanup keys when server is shutdown. @MUzairS15 (#9879) [Models] Rename `relationships.reqo_query` to `relationships.evaluationQuery`. @MUzairS15 (#9875) [Server] Auto Register for Connections @MUzairS15 (#9785) [Models] Add support to update component `capabilities`. @MUzairS15 (#9848) [Docker Extension] chore: update ui deps @leecalcote (#9841) chore: remove mesheryctl unit test assertions @leecalcote (#9853) [UI] Fix connection page crash @Yashsharma1911 (#9871) Enhance dashboard ui elements @sudhanshutech (#9872) [bug] fix null check for environment @sudhanshutech (#9860) [FIX] Sorting in designs and filters and fix some UI issues @sudhanshutech (#9859) [WIP] Enforced CASL in UI @Yashsharma1911 (#9778) [FIX] Routing error in workspace @sudhanshutech (#9852) [bug] fix null check for environment @sudhanshutech (#9860) fix: fixed broken link @ameeetgaikwad (#9874) Docs: Relocate Adapters Under Extensibility @leecalcote (#9855) docs: refresh overview and structure @leecalcote (#9854) Thank you to our contributors for making this release possible: @MUzairS15, @Yashsharma1911, @alphaX86, @ameeetgaikwad, @leecalcote and @sudhanshutech
Project: Meshery (Provisioning / Automation & Configuration)
File: in-toto.md

layout: integration title: In Toto subtitle: Collaborative and visual infrastructure as code for In Toto image: /assets/img/integrations/in-toto/icons/color/in-toto-color.svg permalink: extensibility/integrations/in-toto docURL: https://docs.meshery.io/extensibility/integrations/in-toto description: integrations-category: Provisioning integrations-subcategory: Security & Compliance registrant: Artifact Hub components: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] 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: YugabyteDB (App Definition and Development / Database)
File: yba_universe_node_start.md

Start a node instance in YugabyteDB Anywhere universe Start a node instance in YugabyteDB Anywhere universe. Start the server processes on a previously stopped node. Ideally it is added back very soon. ``` yba universe node start [flags] ``` ``` -h, --help help for start ``` ``` -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") -n, --name string [Required] The name of the universe for the corresponding node operations. --node-name string [Optional] The name of the universe node for the corresponding node operations. Required for add, reboot, release, remove, reprovision, start, stop. -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 universe nodes
Project: Trivy (Provisioning / Security & Compliance)
File: reporting.md

DefectDojo can parse Trivy JSON reports. The parser supports deduplication and auto-close features. Get it at: <https://github.com/DefectDojo/django-DefectDojo> SecObserve can parse Trivy results as CycloneDX reports and provides an unified overview of vulnerabilities from different sources. Vulnerabilities can be evaluated with manual and rule based assessments. Get it at: <https://github.com/MaibornWolff/SecObserve> A Trivy plugin that scans and outputs the results to an interactive html file. Get it at: <https://github.com/fatihtokus/scan2html> A Trivy plugin that converts JSON report to SonarQube . Get it at: <https://github.com/umax/trivy-plugin-sonarqube> Trivy-Streamlit is a Streamlit application that allows you to quickly parse the results from a Trivy JSON report. Get it at: <https://github.com/mfreeman451/trivy-streamlit> This project is a web application that allows to load a Trivy report in json format and displays the vulnerabilities of a single target in an interactive data table. Get it at: <https://github.com/dbsystel/trivy-vulnerability-explorer>
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-registry.md

layout: default title: mesheryctl-registry permalink: reference/mesheryctl/registry redirect_from: reference/mesheryctl/registry/ type: reference display-title: "false" language: en command: registry subcommand: nil Meshery Registry Management Manage the state and contents of Meshery's internal registry of capabilities. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl registry [flags] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl registry [subcommand] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for registry </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -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: StarRocks (App Definition and Development / Database)
File: json_keys.md

displayed_sidebar: "English" Returns the top-level keys from a JSON object as a JSON array, or, if a `path` is specified, the top-level keys from the path. ```Haskell jsonkeys(jsondoc[, path]) ``` `json_doc`: required. The JSON document for which to return the keys. It must be a JSON object. `path`: optional. The path generally starts with `$` and uses `.` as the path separator. `[]` is used as the array subscript, which starts from 0. Returns a JSON array. An empty array is returned if the JSON object is empty. `NULL` is returned if the JSON document is not a JSON object or the path does not identify a value in the document. If the JSON document is an array nested with a JSON object, you can use the `path` parameter to obtain keys from that object. Example 1: Return an empty array because the input JSON object is empty. ```Plain select json_keys('{}'); +--+ | json_keys('{}') | +--+ | [] | +--+ ``` Example 2: Return the keys of a JSON object. ```Plain select json_keys('{"a": 1, "b": 2, "c": 3}'); +-+ | json_keys('1') | +-+ |["a", "b", "c"] | +-+ ``` Example 3: Return the keys of a JSON object that matches the specified path. ```Plain select json_keys('{"a": 1, "b": 2, "c": {"d": 3, "e": 4, "f": 5}}', '$.c'); ++ | json_keys('{"a": 1, "b": 2, "c": {"d": 3, "e": 4, "f": 5}}', '$.c') | ++ | ["d", "e", "f"] | ++ ``` Example 4: The path does not exist. ```Plain select json_keys('{"a": 1, "b": 2, "c": {"d": 3, "e": 4, "f": 5}}', '$.e'); ++ | json_keys('{"a": 1, "b": 2, "c": {"d": 3, "e": 4, "f": 5}}', '$.e') | ++ | NULL | ++ ``` Example 5: The JSON document is not a JSON object. ```Plain select json_keys('[1, 2, {"a": 1, "b": 2}]'); ++ | json_keys('[1, 2, {"a": 1, "b": 2}]') | ++ | NULL | ++ ``` Example 6: The JSON document is an array nested with a JSON object. A path is specified to obtain keys from that object. ```Plain select json_keys('[0, 1, {"a": 1, "b": 2}]', '$[2]'); +--+ | json_keys('[0, 1, {"a": 1, "b": 2}]', '$[2]') | +--+ | ["a", "b"] | +--+ ```
Project: StarRocks (App Definition and Development / Database)
File: datediff.md

displayed_sidebar: "English" Calculates the difference between two date values (`expr1 - expr2`) and returns a result in days. `expr1` and `expr2` are valid DATE or DATETIME expressions. Note: Only the date parts of the values are used in the calculation. Difference between datediff and : |Function|Behavior|Example| |||| |datediff|Accurate to the day|The difference between '2020-12-25 23:00:00' and '2020-12-24 23:00:01' is 1.| |days_diff|Accurate to the second and rounded down to the nearest lower integer|The difference between '2020-12-25 23:00:00' and '2020-12-24 23:00:01' is 0.| The difference between datediff and lies in that date_diff supports the `unit` parameter, which can return the difference between two date values in the specified unit. ```Haskell INT DATEDIFF(DATETIME expr1,DATETIME expr2) ``` ```Plain Text MySQL > select datediff(CAST('2007-12-31 23:59:59' AS DATETIME), CAST('2007-12-30' AS DATETIME)); +--+ | datediff(CAST('2007-12-31 23:59:59' AS DATETIME), CAST('2007-12-30' AS DATETIME)) | +--+ | 1 | +--+ MySQL > select datediff(CAST('2010-11-30 23:59:59' AS DATETIME), CAST('2010-12-31' AS DATETIME)); +--+ | datediff(CAST('2010-11-30 23:59:59' AS DATETIME), CAST('2010-12-31' AS DATETIME)) | +--+ | -31 | +--+ ```
Project: Polaris (Provisioning / Security & Compliance)
File: configuration.md

meta: name: description content: "Fairwinds Polaris | Learn about Polaris defaults and how to customize configurations. " The default Polaris configuration can be . You can customize the configuration to do things like: Turn checks Change the of checks Add new Add for particular workloads or namespaces To pass in your custom configuration, follow the instructions for your environment: CLI - set the `--config` argument to point to your `config.yaml` Helm - set the `config` variable in your values file kubectl - create a ConfigMap with your `config.yaml`, mount it as a volume, and use the `--config` argument in your Deployment
Project: YDB (App Definition and Development / Database)
File: gcp.md

Register in the Google Cloud console and a project. Activate your and top it up with funds to launch nine VMs. You can estimate the approximate cost in . Set up GCP CLI: Activate and . Download and install GCP CLI by following . Go to the `.../google-cloud-sdk/bin` subdirectory and run the `./gcloud compute regions list` command to get a list of available regions. Run the command `./gcloud auth application-default login` to configure the connection profile. Go to the `gcp` subdirectory (located in the downloaded repository), and in the `variables.tf` file set the current values for the following variables: `project` the project's name that was set in the Google Cloud cloud console. `region` the region where the infrastructure will be deployed. `zones` list of availability zones in which subnets and VMs will be created. Now, being in the `gcp` subdirectory, you can run the following sequence of commands to install the provider, initialize modules, and create the infrastructure: `terraform init` installing the provider and initializing modules. `terraform plan` creating a plan for future infrastructure. `terraform init` create resources in the cloud. Next, use the commands `terraform plan`, `terraform init`, and `terraform destroy` (destruction of the created infrastructure) to apply further changes as necessary.
Project: KICS (Provisioning / Security & Compliance)
File: b2315cae-b110-4426-81e0-80bb8640cdd3.md

title: Athena Database Not Encrypted hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b2315cae-b110-4426-81e0-80bb8640cdd3 Query name: Athena Database Not Encrypted Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: AWS Athena Database data in S3 should be encrypted<br> ```tf title="Positive test num. 1 - tf file" hl_lines="5" resource "awss3bucket" "hoge" { bucket = "hoge" } resource "awsathenadatabase" "hoge" { name = "database_name" bucket = awss3bucket.hoge.bucket } ``` ```tf title="Negative test num. 1 - tf file" resource "awss3bucket" "hoge" { bucket = "hoge" } resource "awsathenadatabase" "hoge" { name = "database_name" bucket = awss3bucket.hoge.bucket encryption_configuration { encryptionoption = "SSEKMS" kmskey = "SSEKMS" } } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.1.6.md

layout: default date: 2019-10-14 tag: v0.1.6 language: en What's new? Changelog New UI for managing Meshery's connection to Kubernetes cluster. New `mesheryctl` compatibility for Windows for opening default browser upon `start`. New sample app added to the istio adapter - Hipster app (Google's Microservices demo application).
Project: MongoDB (App Definition and Development / Database)
File: burn_in_tags.md

Similar to , `burnintags` also detects the javascript tests (under the ) that are new or have changed since the last git command and then runs those tests in repeated mode to validate their stability. But instead of running the tests on their original build variants, `burnintags` runs them on the burn_in build variants that are generated separately. You can use `burnintags` on evergreen by selecting the `burnintags_gen` task when creating a patch. The burn_in build variants, i.e., `enterprise-rhel-80-64-bit-inmem` and `enterprise-rhel-80-64-bit-multiversion` will be generated, each of which will have a `burnintests` task generated by the . `burnintests` task, a , may have multiple sub-tasks which run the test suites only for the new or changed javascript tests (note that a javascript test can be included in multiple test suites). Each of those tests will be run 2 times minimum, and 1000 times maximum or for 10 minutes, whichever is reached first. The `! Run All Affected JStests` variant has a single `burnintags_gen` task. This task will create & activate tasks for all required and suggested variants. The end result is that any jstests that have been modified in the patch will run on all required and suggested variants. This should give users a clear signal on whether their jstests changes have introduced a failure that could potentially lead to a revert or follow-up bug fix commit.
Project: ClickHouse (App Definition and Development / Database)
File: 95_sanitizer-report.md

name: Sanitizer alert about: Potential issue has been found by special code instrumentation title: '' labels: testing assignees: '' (you don't have to strictly follow this form) Describe the bug A link to the report How to reproduce Try to reproduce the report and copy the tables and queries involved. Error message and/or stacktrace You can find additional information in server logs.
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: minio.md

title: Minio API Authorization labels: layer: data category: authorization tutorials: https://github.com/minio/minio/blob/master/docs/iam/opa.md inventors: minio styra docs_features: rest-api-integration: note: | Minio implements a native integration with OPA using the REST API. The in the Minio docs. Minio is an open source, on-premise object database compatible with the Amazon S3 API. This integration lets OPA enforce policies on Minio's API.
Project: Pinniped (Provisioning / Key Management)
File: ADOPTERS.md

If you're using Pinniped and want to add your organization to this list, ! <a href="https://tanzu.vmware.com/tanzu" border="0" target="_blank"><img alt="vmware-tanzu" src="site/themes/pinniped/static/img/vmware-tanzu.svg" height="50"></a> <a href="https://kubeapps.com/" border="0" target="_blank"><img alt="kubeapps" src="site/themes/pinniped/static/img/kubeapps.svg" height="50"></a> <a href="https://www.ok.dk/" border="0" target="_blank"><img alt="ok-amba" src="site/themes/pinniped/static/img/ok-amba.svg" height="50"></a> Below is a list of solutions where Pinniped is being used as a component. Kubeapps uses Pinniped to when running on clusters where SSO cannot be configured for the cluster API server. TKG uses Pinniped to provide a seamless SSO experience across management and workload clusters. TMC uses Pinniped to provide a uniform authentication experience across all attached clusters. If you are using Pinniped and would like to be included in the list of Pinniped Adopters, add an SVG version of your logo that is less than 150 KB to the in this repo and submit a pull request with your change including 1-2 sentences describing how your organization is using Pinniped. Name the image file something that reflects your company (e.g., if your company is called Acme, name the image acme.svg). Please feel free to send us a message in with any questions you may have.
Project: StarRocks (App Definition and Development / Database)
File: stddev.md

displayed_sidebar: "English" Returns the population standard deviation of the expr expression. Since v2.5.10, this function can also be used as a window function. ```Haskell STDDEV(expr) ``` `expr`: the expression. If it is a table column, it must evaluate to TINYINT, SMALLINT, INT, BIGINT, LARGEINT, FLOAT, DOUBLE, or DECIMAL. Returns a DOUBLE value. The formula is as follows, where `n` represents the row count of the table: ```plaintext mysql> SELECT stddev(loquantity), stddevpop(lo_quantity) from lineorder; ++-+ | stddev(loquantity) | stddevpop(lo_quantity) | ++-+ | 14.43100708360797 | 14.43100708360797 | ++-+ ``` STDDEV,STDDEV_POP,POP
Project: Tetragon (Provisioning / Security & Compliance)
File: tags.md

title: "Tags" weight: 3 description: "Use Tags to categorize events" Tags are optional fields of a Tracing Policy that are used to categorize generated events. Tags are specified in Tracing policies and will be part of the generated event. ```yaml apiVersion: cilium.io/v1alpha1 kind: TracingPolicy metadata: name: "file-monitoring-filtered" spec: kprobes: call: "securityfilepermission" message: "Sensitive file system write operation" syscall: false args: index: 0 type: "file" # (struct file *) used for getting the path index: 1 type: "int" # 0x04 is MAYREAD, 0x02 is MAYWRITE selectors: matchArgs: index: 0 operator: "Prefix" values: "/etc" # Writes to sensitive directories "/boot" "/lib" "/lib64" "/bin" "/usr/lib" "/usr/local/lib" "/usr/local/sbin" "/usr/local/bin" "/usr/bin" "/usr/sbin" "/var/log" # Writes to logs "/dev/log" "/root/.ssh" # Writes to sensitive files add here. index: 1 operator: "Equal" values: "2" # MAY_WRITE tags: [ "observability.filesystem", "observability.process" ] ``` Every kprobe call can have up to max 16 tags. Events in this namespace relate to collect and export data about the internal system state. "observability.filesystem": the event is about file system operations. "observability.privilege_escalation": the event is about raising permissions of a user or a process. "observability.process": the event is about an instance of a Linux program being executed. Users can define their own tags inside Tracing Policies. The official supported tags are documented in the .
Project: Dragonfly (Provisioning / Container Registry)
File: dfcache_export.md

% DFCACHE(1) Version v2.1.0 | Frivolous "Dfcache" Documentation dfcache export export file from P2P cache system Export file from P2P cache system. ```shell dfcache export <-i cid> <output>|<-O output> [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 export -l, --local only export file from local cache -O, --output string export file path ``` - the P2P cache client of dragonfly
Project: KICS (Provisioning / Security & Compliance)
File: 6d8f1a10-b6cd-48f0-b960-f7c535d5cdb8.md

title: Secrets As Environment Variables hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 6d8f1a10-b6cd-48f0-b960-f7c535d5cdb8 Query name: Secrets As Environment Variables Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Secret Management URL: Container should not use secrets as environment variables<br> ```tf title="Positive test num. 1 - tf file" hl_lines="11 20" resource "kubernetes_pod" "test" { metadata { name = "terraform-example" } spec { container { image = "nginx:1.7.9" name = "example" env { name = "environment" value = "test" value_from = { secretkeyref = "hjjhjh" } } env_from { secret_ref = "wwww" } port { container_port = 8080 } liveness_probe { http_get { path = "/nginx_status" port = 80 http_header { name = "X-Custom-Header" value = "Awesome" } } initialdelayseconds = 3 period_seconds = 3 } } dns_config { nameservers = ["1.1.1.1", "8.8.8.8", "9.9.9.9"] searches = ["example.com"] option { name = "ndots" value = 1 } option { name = "use-vc" } } dns_policy = "None" } } ``` ```tf title="Negative test num. 1 - tf file" resource "kubernetes_pod" "test55" { metadata { name = "terraform-example" } spec { container { image = "nginx:1.7.9" name = "example" env { name = "environment" value = "test" } port { container_port = 8080 } liveness_probe { http_get { path = "/nginx_status" port = 80 http_header { name = "X-Custom-Header" value = "Awesome" } } initialdelayseconds = 3 period_seconds = 3 } } dns_config { nameservers = ["1.1.1.1", "8.8.8.8", "9.9.9.9"] searches = ["example.com"] option { name = "ndots" value = 1 } option { name = "use-vc" } } dns_policy = "None" } } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: 10-12-2023-03-17-10_81317eb2.md

timestamp: "2023-10-12 03:17:04 UTC Thu" meshery-component: meshery-consul meshery-component-version: v0.6.10 meshery-server-version: "*name" k8s-distro: minikube k8s-version: "v1.25.2" service-mesh: Consul service-mesh-version: "v1.2.2" tests: consul-client: null consul-server: null overall-status: "failing"