cwielenb/CNCF-Dataset huggingface dataset:
Project: FOSSA (Provisioning / Security & Compliance)
File: clojure.md

When developing in Clojure, is the most common package manager. Dependencies are specified in a manifest file by users which is used by the `lein` tool to build a dependency graph and download the correct dependencies. | Strategy | Direct Deps | Transitive Deps | Edges | Container Scanning | | -- | | | | | | `lein deps` | :whitecheckmark: | :whitecheckmark: | :whitecheckmark: | :x: | In order to find Leiningen projects, we look for `project.clj` files which specify the root of a Leiningen project. Once we find a `leiningen` file we quit walking the file tree because the downloaded dependencies will have their own `project.clj` files in subdirectories which would create an incorrect dep graph if scanned. run `lein deps :tree-data` and generate output similar to: ``` {[clojure-complete "0.2.5" :exclusions [[org.clojure/clojure]]] nil, [koan-engine "0.2.5"] {[fresh "1.0.2"] nil}, [lein-koan "0.1.5" :scope "test"] nil, [nrepl "0.6.0" :exclusions [[org.clojure/clojure]]] nil, [org.clojure/clojure "1.10.0"] {[org.clojure/core.specs.alpha "0.2.44"] nil, [org.clojure/spec.alpha "0.2.176"] nil}} ``` Parse this output to determine the full dependency graph and dependency versions. Dependencies which have the same groupID and artifactID (nrepl above) are expanded to satisfy Maven's repository standard. The differences can be seen in where only `nrepl` is required by Leiningen, but nrepl:nrepl is required by Gradle and Maven.
Project: YugabyteDB (App Definition and Development / Database)
File: cr-do-ntile.md

title: crdontile.sql linkTitle: crdontile.sql headerTitle: crdontile.sql description: crdontile.sql - Part of the code kit for the "Analyzing a normal distribution" section within the YSQL window functions documentation. menu: v2.18: identifier: cr-do-ntile parent: analyzing-a-normal-distribution weight: 110 type: docs Save this script as `crdontile.sql`. ```plpgsql create or replace procedure dontile(noof_buckets in int) language sql as $body$ insert into results(method, bucket, n, mins, maxs) with ntiles as ( select score, (ntile(noofbuckets) over w) as bucket from t4_view window w as (order by score)) select 'ntile', bucket, count(*), min(score), max(score) from ntiles group by bucket; $body$; ```
Project: Hazelcast IMDG (App Definition and Development / Database)
File: CONTRIBUTING.md

Hazelcast is Open Source software, licensed under the . The main benefit of Open Source is that you don't need to wait for a vendor to provide a fix or a feature. If you've got the skills (and the will), it's already at your fingertips. There are multiple ways to contribute: . Note that you don't need to be a developer to help us. Contributions that improve the documentation are always appreciated. If you feel yourself in need of assistance, please reach us directly via . Thanks for reporting your issue. To help us resolve your issue quickly and efficiently, we need as much data for diagnostics as possible. Please share with us the following information: Exact Hazelcast version that you use (e.g. `4.0.1`, also whether it is a minor release, or the latest snapshot). Cluster size, i.e. the number of Hazelcast cluster members. Number of clients. Java version. It is also helpful to mention the JVM parameters. Operating system. If it is Linux, kernel version is helpful. Logs and stack traces, if available. Detailed description of the steps to reproduce your issue. Unit test with the `hazelcast.xml` file. If you could include a unit test which reproduces your issue, it would speed the resolution time. If it's related to integration with an external system (e.g. Tomcat, Spring, Hibernate, Kafka) details about the external system and configuration parameters for connecting to it. Thanks a lot for creating your <abbr title="Pull Request">PR</abbr>! A PR can target many different subjects: : either fix typos or improve the documentation as a whole Fix a bug Add a feature Add additional tests to improve the test coverage, or fix flaky tests Anything else that makes Hazelcast better! All PRs follow the same process: Contributions are submitted, reviewed, and accepted using the PR system on GitHub. For first time contributors, our bot will automatically ask you to sign the Hazelcast Contributor Agreement on the PR. The latest changes are in the `master` branch. Make sure to design clean commits that are easily readable. That includes descriptive commit messages. Please keep your PRs as small as possible, i.e. if you plan to perform a huge change, do not submit a single and large PR for it. For an enhancement or larger feature, you can create a GitHub issue first to discuss. Before you push, run: ```bash ./mvnw clean validate ``` Pushing your PR once it is free of CheckStyle errors. If you submit a PR as the solution to a specific issue, please mention the issue number either in the PR description or commit message. Your PRs will first be merged into our internal repo. Following internal merging, the final commit will be pushed back to this repository. You will be acknowledged as a co-author of the final commit, recognizing your valuable contribution. Your original PR will be closed, accompanied by a comment indicating that it has been merged internally as part of the monorepo process.
Project: ShardingSphere (App Definition and Development / Database)
File: commit-migration.en.md

+++ title = "COMMIT MIGRATION" weight = 16 +++ The `COMMIT MIGRATION` syntax is used to commit migration process. {{< tabs >}} {{% tab name="Grammar" %}} ```sql CommitMigration ::= 'COMMIT' 'MIGRATION' migrationJobId migrationJobId ::= string ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} `migrationJobId` needs to be obtained through syntax query Commit migration process ```sql COMMIT MIGRATION 'j010180026753ef0e25d3932d94d1673ba551'; ``` `COMMIT`, `MIGRATION`
Project: external-secrets (Provisioning / Security & Compliance)
File: externalsecret.md

The `ExternalSecret` describes what data should be fetched, how the data should be transformed and saved as a `Kind=Secret`: tells the operator what secrets should be synced by using `spec.data` to explicitly sync individual keys or use `spec.dataFrom` to get all values from the external API. you can specify how the secret should look like by specifying a `spec.target.template` When the controller reconciles the `ExternalSecret` it will use the `spec.template` as a blueprint to construct a new `Kind=Secret`. You can use golang templates to define the blueprint and use template functions to transform secret values. You can also pull in `ConfigMaps` that contain golang-template data using `templateFrom`. See for details. The `Kind=Secret` is updated when: the `spec.refreshInterval` has passed and is not `0` the `ExternalSecret`'s `labels` or `annotations` are changed the `ExternalSecret`'s `spec` has been changed You can trigger a secret refresh by using kubectl or any other kubernetes api client: ``` kubectl annotate es my-es force-sync=$(date +%s) --overwrite ``` Individual features are described in the : Take a look at an annotated example to understand the design behind the `ExternalSecret`. ``` yaml {% include 'full-external-secret.yaml' %} ```
Project: ClickHouse (App Definition and Development / Database)
File: template-server-setting.md

Description. Describe what is configured in this section of settings. Possible value: ... Default value: ... Settings (Optional) If the section contains several settings, list them here. Specify possible values and default values: setting_1 Description. setting_2 Description. Example ```xml <serversettingname> <setting1> ... </setting1> <setting2> ... </setting2> </serversettingname> ``` Additional Info (Optional) The name of an additional section can be any, for example, Usage. See Also (Optional)
Project: KICS (Provisioning / Security & Compliance)
File: bcd3fc01-5902-4f2a-b05a-227f9bbf5450.md

title: SQL Server Predictable Active Directory Account Name hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: bcd3fc01-5902-4f2a-b05a-227f9bbf5450 Query name: SQL Server Predictable Active Directory Account Name Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: Azure SQL Server must avoid using predictable Active Directory Administrator Account names, like 'Admin', which means the attribute 'login' must be set to a name that is not easy to predict<br> ```tf title="Positive test num. 1 - tf file" hl_lines="29 21" data "azurermclientconfig" "current" {} resource "azurermresourcegroup" "positive1" { name = "acceptanceTestResourceGroup1" location = "West US" } resource "azurermsqlserver" "positive2" { name = "mysqlserver" resourcegroupname = azurermresourcegroup.example.name location = azurermresourcegroup.example.location version = "12.0" administrator_login = "4dm1n157r470r" administratorloginpassword = "4-v3ry-53cr37-p455w0rd" } resource "azurermsqlactivedirectoryadministrator" "positive3" { servername = azurermsql_server.example.name resourcegroupname = azurermresourcegroup.example.name login = "" tenantid = data.azurermclientconfig.current.tenantid objectid = data.azurermclientconfig.current.objectid } resource "azurermsqlactivedirectoryadministrator" "positive4" { servername = azurermsql_server.example.name resourcegroupname = azurermresourcegroup.example.name login = "Admin" tenantid = data.azurermclientconfig.current.tenantid objectid = data.azurermclientconfig.current.objectid } ``` ```tf title="Negative test num. 1 - tf file" data "azurermclientconfig" "current" {} resource "azurermresourcegroup" "negative1" { name = "acceptanceTestResourceGroup1" location = "West US" } resource "azurermsqlserver" "negative2" { name = "mysqlserver" resourcegroupname = azurermresourcegroup.example.name location = azurermresourcegroup.example.location version = "12.0" administrator_login = "4dm1n157r470r" administratorloginpassword = "4-v3ry-53cr37-p455w0rd" } resource "azurermsqlactivedirectoryadministrator" "negative3" { servername = azurermsql_server.example.name resourcegroupname = azurermresourcegroup.example.name login = "NotEasyToPredictAdmin" tenantid = data.azurermclientconfig.current.tenantid objectid = data.azurermclientconfig.current.objectid } ```
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.20.0.md

Update README.md by @qixiaojian310 in https://github.com/Edgenesis/shifu/pull/621 @qixiaojian310 made their first contribution in https://github.com/Edgenesis/shifu/pull/621 Bump golang.org/x/crypto from 0.8.0 to 0.9.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/611 Bump github.com/gopcua/opcua from 0.3.13 to 0.3.15 by @dependabot in https://github.com/Edgenesis/shifu/pull/618 Bump github.com/minio/minio-go/v7 from 7.0.52 to 7.0.56 by @dependabot in https://github.com/Edgenesis/shifu/pull/624 Bump github.com/stretchr/testify from 1.8.2 to 1.8.4 by @dependabot in https://github.com/Edgenesis/shifu/pull/622 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.19.0...v0.20.0
Project: KICS (Provisioning / Security & Compliance)
File: e401d614-8026-4f4b-9af9-75d1197461ba.md

title: IAM Policies With Full Privileges hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: e401d614-8026-4f4b-9af9-75d1197461ba Query name: IAM Policies With Full Privileges Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: IAM policies shouldn't allow full administrative privileges (for all resources)<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4" name: Create IAM Managed Policy community.aws.iammanagedpolicy: policy_name: "ManagedPolicy" policy: Version: "2012-10-17" Statement: Effect: "Allow" Action: ["*"] Resource: "*" make_default: false state: present ``` ```yaml title="Negative test num. 1 - yaml file" name: Create IAM Managed Policy community.aws.iammanagedpolicy: policy_name: ManagedPolicy policy: Version: '2012-10-17' Statement: Effect: Allow Action: logs:CreateLogGroup Resource: '*' make_default: false state: present ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: log-opt.md

Logging driver specific options. Set custom logging configuration. The following names are supported: path: specify a path to the log file (e.g. --log-opt path=/var/log/container/mycontainer.json); max-size: specify a max size of the log file (e.g. --log-opt max-size=10mb); tag: specify a custom log tag for the container (e.g. --log-opt tag="{{.ImageName}}". It supports the same keys as podman inspect --format. This option is currently supported only by the journald log driver.
Project: ArangoDB (App Definition and Development / Database)
File: assume_value_rvalue.md

+++ title = "`valuetype &&assumevalue() && noexcept`" description = "Narrow contract rvalue reference observer of any value present. Constexpr propagating, never throws." categories = ["observers"] weight = 620 +++ Narrow contract rvalue reference observer of any value present. `NoValuePolicy::narrowvaluecheck()` is first invoked, then the reference to the value is returned. The convention is that hard undefined behaviour occurs if no value is actually present, however `NoValuePolicy::narrowvaluecheck()` can do something to avoid that. Note that if `value_type` is `void`, only a `const` overload returning `void` is present. Requires: Always available. Complexity: Depends on `NoValuePolicy::narrowvaluecheck()`. Guarantees: An exception is never thrown.
Project: YugabyteDB (App Definition and Development / Database)
File: alter_foreign_data_wrapper.grammar.md

```output.ebnf alterforeigndatawrapper ::= ALTER FOREIGN DATA WRAPPER fdwname [ HANDLER handler_name | NO HANDLER ] [ VALIDATOR validator_name | NO VALIDATOR ] [ OPTIONS ( alterfdwoptions ) ] [ OWNER TO new_owner ] [ RENAME TO new_name ] ```
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: v1.26.0.md

title: v1.26.0 weight: 998974000 For an ansible operator, update the Makefile's run target to the following to fix a bug in its implementation. ``` .PHONY: run ANSIBLEROLESPATH?="$(shell pwd)/roles" run: ansible-operator ## Run against the configured Kubernetes cluster in ~/.kube/config $(ANSIBLE_OPERATOR) run ``` See for more details.
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: lagoon-core.md

Add Lagoon Charts repository to your Helm Repositories: ```bash title="Add Lagoon Charts repository" helm repo add lagoon https://uselagoon.github.io/lagoon-charts/ ``` Create a directory for the configuration files we will create, and make sure that its version controlled. Ensure that you reference this path in commands referencing your `values.yml` files. Create `values.yml` in the directory youve just created. Update the endpoint URLs (change them from `api.lagoon.example.com` to your values). Example: Now run `helm upgrade --install` command, pointing to `values.yml`, like so: ```bash title="Upgrade Helm with values.yml" helm upgrade --install --create-namespace --namespace lagoon-core -f values.yml lagoon-core lagoon/lagoon-core` ``` Lagoon Core is now installed! !!! warning Sometimes we run into Docker Hub pull limits. We are considering moving our images elsewhere if this continues to be a problem. Visit the Keycloak dashboard at the URL you defined in the `values.yml` for Keycloak. Click "Administration Console" Username: `admin` Password: use `lagoon-core-keycloak` secret, key-value `KEYCLOAKADMINPASSWORD` Retrieve the secret like so: ```bash title="Retrieve secret" kubectl -n lagoon-core get secret lagoon-core-keycloak -o jsonpath="{.data.KEYCLOAKADMINPASSWORD}" | base64 --decode ``` Click on User on top right. Go to Manage Account. Add an Email for the admin account you created. Save. Go to Realm Lagoon -> Realm Settings -> Email Configure email server for Keycloak, test connection via Test connection button. Go to Realm Lagoon -> Realm Settings -> Login Enable Forgot Password Save. You should now be able to visit the Lagoon UI at the URL you defined in the `values.yml` for the UI. Username: `lagoonadmin` Secret: use `lagoon-core-keycloak` secret key-value: `LAGOON-CORE-KEYCLOAK` Retrieve the secret: ```bash title="Retrieve secret" kubectl -n lagoon-core get secret lagoon-core-keycloak -o jsonpath="{.data.KEYCLOAKLAGOONADMIN_PASSWORD}" | base64 --decode ```
Project: ko (App Definition and Development / Application Definition & Image Build)
File: deployment.md

See for information about deploying to Kubernetes. Because the output of `ko build` is an image reference, you can easily pass it to other tools that expect to take an image reference. To run the container locally: ```plaintext docker run -p 8080:8080 $(ko build ./cmd/app) ``` ```plaintext gcloud run deploy --image=$(ko build ./cmd/app) ``` Note: The image must be pushed to or . ```plaintext flyctl launch --image=$(ko build ./cmd/app) ``` Note: The image must be pushed to Fly.io's container registry at `registry.fly.io`, or if not, the image must be publicly available. When pushing to `registry.fly.io`, you must first log in with . ```plaintext aws lambda update-function-code \ --function-name=my-function-name \ --image-uri=$(ko build ./cmd/app) ``` Note: The image must be pushed to , based on the AWS provided base image, and use the framework. See for more information. ```plaintext az containerapp update \ --name my-container-app --resource-group my-resource-group --image $(ko build ./cmd/app) ``` Note: The image must be pushed to or other registry service. See for more information.
Project: Meshery (Provisioning / Automation & Configuration)
File: tuf.md

layout: integration title: Tuf subtitle: Collaborative and visual infrastructure as code for Tuf image: /assets/img/integrations/tuf/icons/color/tuf-color.svg permalink: extensibility/integrations/tuf docURL: https://docs.meshery.io/extensibility/integrations/tuf 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: KICS (Provisioning / Security & Compliance)
File: a7f8ac28-eed1-483d-87c8-4c325f022572.md

title: Serverless Function Environment Variables Not Encrypted hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: a7f8ac28-eed1-483d-87c8-4c325f022572 Query name: Serverless Function Environment Variables Not Encrypted Platform: CloudFormation Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: AWS Serverless Function should encrypt environment variables<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="7" AWSTemplateFormatVersion: '2010-09-09' Transform: AWS::Serverless-2016-10-31 Description: AWS SAM template with a simple API definition Resources: Function: Type: AWS::Serverless::Function Properties: PackageType: Image ImageUri: account-id.dkr.ecr.region.amazonaws.com/ecr-repo-name:image-name ImageConfig: Command: "app.lambda_handler" EntryPoint: "entrypoint1" WorkingDirectory: "workDir" Tags: Key: Type Value: AWS Serverless Function DeadLetterConfig: TargetArn: arn:aws:sqs:us-east-1:2324243535:aaa Type: SQS Environment: Variables: key: value ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: '2010-09-09' Transform: AWS::Serverless-2016-10-31 Description: AWS SAM template with a simple API definition Resources: Function1: Type: AWS::Serverless::Function Properties: PackageType: Image ImageUri: account-id.dkr.ecr.region.amazonaws.com/ecr-repo-name:image-name ImageConfig: Command: "app.lambda_handler" EntryPoint: "entrypoint1" WorkingDirectory: "workDir" Tags: Key: Type Value: AWS Serverless Function DeadLetterConfig: TargetArn: arn:aws:sqs:us-east-1:2324243535:aaa Type: SQS Environment: Variables: key: value KmsKeyArn: arn:aws:kms:us-west-1:123456789123:key/12345678-12cc-45bb-98aa-9876543210cc ```
Project: YugabyteDB (App Definition and Development / Database)
File: managed-cli-auth.md

title: ybm CLI authenticate resource headerTitle: ybm auth linkTitle: auth description: YugabyteDB Managed CLI reference auth resource. headcontent: Authenticate ybm CLI menu: preview_yugabyte-cloud: identifier: managed-cli-auth parent: managed-cli-reference weight: 20 type: docs Use the `auth` command to add an to your ybm CLI configuration. When you enter the `auth` command, you are prompted for an API key. At the prompt, paste your API key and press Enter. By default, this writes the key to the file `.ybm-cli.yaml` under your `$HOME` directory. You can update a different configuration file using the `--config` flag. ```text Usage: ybm auth [flag] ``` Authenticate ybm: ```sh ybm auth ``` | Flag | Description | | : | : | | --config | Path to a configuration file (default is `$HOME/.ybm-cli.yaml`). |
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: delete-a-redis-cluster.md

title: Delete a Redis Cluster description: How to delete a Redis Cluster keywords: [redis, delete a cluster, delete protection] sidebar_position: 6 sidebar_label: Delete protection import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; :::note The termination policy determines how a cluster is deleted. ::: | terminationPolicy | Deleting Operation | |:-- | :-- | | `DoNotTerminate` | `DoNotTerminate` blocks delete operation. | | `Halt` | `Halt` deletes workload resources such as statefulset, deployment workloads but keep PVCs. | | `Delete` | `Delete` deletes workload resources and PVCs but keep backups. | | `WipeOut` | `WipeOut` deletes workload resources, PVCs and all relevant resources included backups. | To check the termination policy, execute the following command. <Tabs> <TabItem value="kbcli" label="kbcli" default> ```bash kbcli cluster list redis-cluster NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME redis-cluster default redis redis-7.0.6 Delete Running Apr 10,2023 20:27 UTC+0800 ``` </TabItem> <TabItem value="kubectl" label="kubectl"> ```bash kubectl -n demo get cluster redis NAME CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS AGE redis redis redis-7.0.6 Delete Running 10m ``` </TabItem> </Tabs> Run the command below to delete a specified cluster. <Tabs> <TabItem value="kbcli" label="kbcli" default> ```bash kbcli cluster delete redis-cluster ``` </TabItem> <TabItem value="kubectl" label="kubectl"> If you want to delete a cluster and its all related resources, you can modify the termination policy to `WipeOut`, then delete the cluster. ```bash kubectl patch -n demo cluster redis -p '{"spec":{"terminationPolicy":"WipeOut"}}' --type="merge" kubectl delete -n demo cluster redis ``` </TabItem> </Tabs>