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

// TODO(user): Add simple overview of use/purpose // TODO(user): An in-depth paragraph about your project and overview of use go version v1.20.0+ docker version 17.03+. kubectl version v1.11.3+. Access to a Kubernetes v1.11.3+ cluster. Build and push your image to the location specified by `IMG`: ```sh make docker-build docker-push IMG=<some-registry>/memcached-operator:tag ``` NOTE: This image ought to be published in the personal registry you specified. And it is required to have access to pull the image from the working environment. Make sure you have the proper permission to the registry if the above commands dont work. Install the CRDs into the cluster: ```sh make install ``` Deploy the Manager to the cluster with the image specified by `IMG`: ```sh make deploy IMG=<some-registry>/memcached-operator:tag ``` NOTE: If you encounter RBAC errors, you may need to grant yourself cluster-admin privileges or be logged in as admin. Create instances of your solution You can apply the samples (examples) from the config/sample: ```sh kubectl apply -k config/samples/ ``` NOTE: Ensure that the samples has default values to test it out. Delete the instances (CRs) from the cluster: ```sh kubectl delete -k config/samples/ ``` Delete the APIs(CRDs) from the cluster: ```sh make uninstall ``` UnDeploy the controller from the cluster: ```sh make undeploy ``` // TODO(user): Add detailed information on how you would like others to contribute to this project NOTE: Run `make help` for more information on all potential `make` targets More information can be found via the Copyright 2024. 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.
Project: ClickHouse (App Definition and Development / Database)
File: v21.3.12.2-lts.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Some `ALTER PARTITION` queries might cause `Part A intersects previous part B` and `Unexpected merged part C intersecting drop range D` errors in replication queue. It's fixed. Fixes . (). Backported in : Fixed using const `DateTime` value vs `DateTime64` column in WHERE. ... (). Backported in : Bug: explain pipeline with` select xxx final `shows wrong pipeline: ``` dell123 :) explain pipeline select z from prewheremoveselect_final final;. (). Backported in : Fix a rare bug that could lead to a partially initialized table that can serve write requests (insert/alter/so on). Now such tables will be in readonly mode. (). Backported in : Fix race condition which could happen in RBAC under a heavy load. This PR fixes , ,. (). Backported in : Fix abnormal server termination due to hdfs becoming not accessible during query execution. Closes . (). Backported in : Fix wrong typo at StorageMemory, this bug was introduced at , now fixed, Closes . (). Backported in : Fixed a bug in moving Materialized View from Ordinary to Atomic database (`RENAME TABLE` query). Now inner table is moved to new database together with Materialized View. Fixes . (). Fix segfault in TSan on _exit (). Use memmove in PODArray::insert to handle memory overlapping. (). Fix cli argument in clickhouse-server.init ().
Project: CloudARK KubePlus (App Definition and Development / Application Definition & Image Build)
File: license.md

Copyright (c) 2011-2013, 'pq' Contributors Portions Copyright (C) 2011 Blake Mizerany Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-volume-rm.1.md

% podman-volume-rm 1 podman\-volume\-rm - Remove one or more volumes podman volume rm [options] volume [...] Removes one or more volumes. Only volumes that are not being used are removed. If a volume is being used by a container, an error is returned unless the --force flag is being used. To remove all volumes, use the --all flag. Volumes can be removed individually by providing their full name or a unique partial name. Remove all volumes. Remove a volume by force. If it is being used by containers, the containers are removed first. Print usage statement Seconds to wait before forcibly stopping running containers that are using the specified volume. The --force option must be specified to use the --time option. Use -1 for infinite wait. Remove multiple specified volumes. ``` $ podman volume rm myvol1 myvol2 ``` Remove all volumes. ``` $ podman volume rm --all ``` Remove the specified volume even if it is in use. Note, this removes all containers using the volume. ``` $ podman volume rm --force myvol ``` 0 All specified volumes removed 1 One of the specified volumes did not exist, and no other failures 2 One of the specified volumes is being used by a container 125 The command fails for any other reason , November 2018, Originally compiled by Urvashi Mohnani <umohnani@redhat.com>
Project: KICS (Provisioning / Security & Compliance)
File: 4d080822-5ee2-49a4-8984-68f3d4c890fc.md

title: Key Expiration Not Set hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 4d080822-5ee2-49a4-8984-68f3d4c890fc Query name: Key Expiration Not Set Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Secret Management URL: Make sure that for all keys the expiration date is set<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "azurermkeyvault_key" "positive1" { name = "generated-certificate" keyvaultid = azurermkeyvault.example.id key_type = "RSA" key_size = 2048 key_opts = [ "decrypt", "encrypt", "sign", "unwrapKey", "verify", "wrapKey", ] } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermkeyvault_key" "negative1" { name = "generated-certificate" keyvaultid = azurermkeyvault.example.id key_type = "RSA" key_size = 2048 key_opts = [ "decrypt", "encrypt", "sign", "unwrapKey", "verify", "wrapKey", ] expiration_date = "2020-12-30T20:00:00Z" } ```
Project: Apache Heron (App Definition and Development / Streaming & Messaging)
File: uploaders-hdfs.md

id: version-0.20.0-incubating-uploaders-hdfs title: HDFS sidebar_label: HDFS original_id: uploaders-hdfs <!-- 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. --> With Heron, you have the option to use HDFS as stable storage for user submitted topology jars. Since HDFS replicates the data, it provides a scalable mechanism for distributing the user topology jars. This is desirable when the job runs in a distributed cluster and requires several hundred containers to run. There are a few things you should be aware of HDFS uploader: It requires hadoop client be installed in the machine where the topology is being submitted You can make Heron use HDFS uploader by modifying the `uploader.yaml` config file specific for the Heron cluster. You'll need to specify the following for each cluster: `heron.class.uploader` Indicate the uploader class to be loaded. You should set this to `org.apache.heron.uploader.hdfs.HdfsUploader` `heron.uploader.hdfs.config.directory` Specifies the directory of the config files for hadoop. This is used by hadoop client to upload the topology jar `heron.uploader.hdfs.topologies.directory.uri` URI of the directory name for uploading topology jars. The name of the directory should be unique per cluster, if they are sharing the storage. In those cases, you could use the Heron environment variable `${CLUSTER}` that will be substituted by cluster name for distinction. Below is an example configuration (in `uploader.yaml`) for a HDFS uploader: ```yaml heron.class.uploader: org.apache.heron.uploader.hdfs.HdfsUploader heron.uploader.hdfs.config.directory: /home/hadoop/hadoop heron.uploader.hdfs.topologies.directory.uri: hdfs://heron/topologies/${CLUSTER} ```
Project: ArangoDB (App Definition and Development / Database)
File: type_can_be_used_in_basic_result.md

+++ title = "`typecanbeusedinbasicresult<R>`" description = "A constexpr boolean true for types permissible in `basic_result<T, E, NoValuePolicy>`." +++ A constexpr boolean true for types permissible in `basic_result<T, E, NoValuePolicy>`. Overridable: Not overridable. Definition: True for a type which: Is not a reference. Is not an {{% api "inplacetype_t<T>" %}}. Is not a {{% api "success_type<T>" %}}. Is not a {{% api "failure_type<EC, EP = void>" %}}. Is not an array. Is either `void`, or else is an `Object` and is `Destructible`. Namespace: `BOOSTOUTCOMEV2_NAMESPACE::trait` Header: `<boost/outcome/trait.hpp>`
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_status_sync.md

title: "Command - devspace status sync" sidebar_label: devspace status sync Shows the sync status ``` devspace status sync [flags] ``` ``` Shows the sync status ``` ``` -h, --help help for sync ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile string The devspace profile to use (if there is any) --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) ```
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_debug_mongodb.md

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

This file provides a guideline on steps that need to be taken to properly release a new version of Terrascan: The following command will kick off both unit tests and end-to-end tests. These tests should finish clean before a release is made: ``` make cicd ``` Once tests look clean, edit `pkg/version/version.go` and update the version number around line 22. Running the following command will generate new entries in `CHANGELOG.md` since since-tag. They will be placed in the changelog file under a heading related to future-release. In the example below, changelogs will be generated for any changes since the `v1.4.0` tag, and placed under a section titled v1.5.0. Before running this command, you'll need to have a GitHub set in the `GITHUB_TOKEN` OS environment variable. ``` docker run -it --rm -v "$(pwd)":/usr/local/src/your-app ferrarimarco/github-changelog-generator -u tenable -p terrascan -t $GITHUB_TOKEN -b CHANGELOG.md --since-tag v1.4.0 --future-release v1.5.0 ``` Next, Review `CHANGELOG.md` to ensure there are notes for the new release Once complete, commit changes and submit a pull request. This should be the last PR before cutting the release. Once the changelog PR has been merged, pull the updated code, tag it with the new version number, and push the tag back to the repo: (again, substitute v1.5.0 for the appropriate version being released) ``` git pull git tag v1.5.0 git push --tags git push upstream v1.5.0 ``` This will kick off the GitHub workflow to run goreleaser to perform the release. Run the commands below to update Brew to the latest Terrascan version. If you are on macOS use `shasum -a 256` instead of `sha256sum` in below command. Release version number in below command for example should be v1.5.0 ``` $ export TERRASCANVERSION=<releaseversion_number> $ brew bump-formula-pr --no-browse --url https://github.com/tenable/terrascan/archive/${TERRASCANVERSION}.tar.gz --sha256 $(curl -sL https://github.com/tenable/terrascan/archive/${TERRASCANVERSION}.tar.gz | sha256sum | awk '{print $1}') terrascan ``` Manually change the version for the terrascan container image in files `deploy/helm/values.yaml` and `deploy/kustomize/base/deployment.yaml`.
Project: Flink (App Definition and Development / Streaming & Messaging)
File: downloads.md

title: Download weight: 100 type: docs bookToc: false aliases: /dev/table/connectors/downloads.html <!-- 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. --> {{< unstable >}} {{< hint info >}} Download links are available only for stable releases. {{< /hint >}} {{< /unstable >}} The page contains links to optional SQL Client connectors and formats that are not part of the binary distribution. {{< sqloptionalformats >}} {{< sqloptionalconnectors >}}
Project: KICS (Provisioning / Security & Compliance)
File: 12944ec4-1fa0-47be-8b17-42a034f937c2.md

title: Storage Account Not Forcing HTTPS hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 12944ec4-1fa0-47be-8b17-42a034f937c2 Query name: Storage Account Not Forcing HTTPS Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: Storage Accounts should enforce the use of HTTPS<br> ```tf title="Positive test num. 1 - tf file" hl_lines="10 7" resource "azurermstorageaccount" "positive1" { name = "example1" resourcegroupname = data.azurermresourcegroup.example.name location = data.azurermresourcegroup.example.location account_tier = "Standard" accountreplicationtype = "GRS" enablehttpstraffic_only = false } resource "azurermstorageaccount" "positive2" { name = "example2" resourcegroupname = data.azurermresourcegroup.example.name location = data.azurermresourcegroup.example.location account_tier = "Standard" accountreplicationtype = "GRS" } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermstorageaccount" "negative1" { name = "example" resourcegroupname = data.azurermresourcegroup.example.name location = data.azurermresourcegroup.example.location account_tier = "Standard" accountreplicationtype = "GRS" enablehttpstraffic_only = true } ```
Project: Salt Project (Provisioning / Automation & Configuration)
File: docs.md

name: Docs about: Issue related to Salt Documentation title: "[DOCS]" labels: Documentation, needs-triage assignees: '' Description A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Suggested Fix What did you expect to see in the documentation that is missing or needs updating? Type of documentation This could be Salt documentation, Salt modules, the Salt Repo or the Getting Started guide. Location or format of documentation Insert page URL if applicable. Additional context Add any other context or screenshots about the feature request here.
Project: CyberArk Conjur (Provisioning / Key Management)
File: STYLE.md

Use this guide to maintain consistent style across the Conjur project. If youre editing code, take a few minutes to look at the code around you and determine its style. If they use spaces around all their arithmetic operators, you should too. If their comments have little boxes of hash marks around them, make your comments have little boxes of hash marks around them too. The point of having style guidelines is to have a common vocabulary of coding so people can concentrate on what youre saying rather than on how youre saying it. We present global style rules here so people know the vocabulary, but local style is also important. If code you add to a file looks drastically different from the existing code around it, it throws readers out of their rhythm when they go to read it. Avoid this. Conjur prose should be warm, direct, and clear about its intended audience. When editing copy, follow the [Chicago Manual of Style][cmos]. The API documentation is written in a pithy, imperative style inspired by the . It is familiar with the reader. Use you & your to refer to the reader, we us & our to refer to CyberArk. When giving examples, use a generic example that the reader can relate to. For example: a website connecting to a database. Give names to machines according to their function, eg `database-server`. Give names to humans using the [alphabetical convention][names] common in cryptography research. When writing RSpec or Cucumber tests, treat your descriptions as prose to be read and understood by humans. When writing tests, look for style and organization suggestions in . Conjur code favors readability over cleverness. Consider the guidelines in the . Consider the guidelines in . If this guide is lacking, please feel free to open a pull request to include additional guidelines. Good guideline are: Distinctive The reader can tell which part of the guide covers the project they're working on. Definitive The readers can distinguish whether their work follows the guidelines or not. Actionable The reader has clear guidance on how to improve content that doesn't follow the style.
Project: KICS (Provisioning / Security & Compliance)
File: 6a6d7e56-c913-4549-b5c5-5221e624d2ec.md

title: S3 Bucket With All Permissions hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 6a6d7e56-c913-4549-b5c5-5221e624d2ec Query name: S3 Bucket With All Permissions Platform: Ansible Severity: <span style="color:#ff0000">Critical</span> Category: Access Control URL: S3 Buckets should not have all permissions, as to prevent leaking private information to the entire internet or allow unauthorized data tampering / deletion. This means the 'Effect' must not be 'Allow' when the 'Action' is '*', for all Principals.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="5" name: Create s3 bucket amazon.aws.s3_bucket: name: mys3bucket policy: Id: "id113" Version: "2012-10-17" Statement: Action: "s3:*" Effect: "Allow" Resource: "arn:aws:s3:::S3B_181355/*" Principal: "*" requester_pays: yes versioning: yes ``` ```yaml title="Negative test num. 1 - yaml file" name: Create s3 bucket amazon.aws.s3_bucket: name: mys3bucket policy: Id: id113 Version: '2012-10-17' Statement: Action: s3:put Effect: Allow Resource: arn:aws:s3:::S3B_181355/* Principal: '*' requester_pays: yes versioning: yes ```
Project: StarRocks (App Definition and Development / Database)
File: DROP_USER.md

displayed_sidebar: "English" import UserManagementPriv from '../../../assets/commonMarkdown/userManagementPriv.md' Drops a specified user identity. <UserManagementPriv /> ```sql DROP USER '<user_identity>' `user_identity`: user@'host' user@['domain'] ``` Drop user `jack@'192.%'`. ```sql DROP USER 'jack'@'192.%' ```