cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: 1b2bf3ff-31e9-460e-bbfb-45e48f4f20cc.md

title: Ansible Tower Exposed To Internet hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 1b2bf3ff-31e9-460e-bbfb-45e48f4f20cc Query name: Ansible Tower Exposed To Internet Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Best Practices URL: Avoid exposing Ansible Tower to the public internet, effectively reducing the potential attack surface of your deployment<br> ```ini title="Positive test num. 1 - ini file" hl_lines="1" [tower] 150.50.1.1 [automationhub] automationhub.acme.org [database] database-01.acme.org [all:vars] admin_password='<password>' pg_host='database-01.acme.org' pg_port='5432' pg_database='awx' pg_username='awx' pg_password='<password>' pg_sslmode='prefer' ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="24" all: children: automationhub: hosts: automationhub.acme.org: admin_password: <password> pg_database: awx pg_host: database-01.acme.org pg_password: <password> pg_port: '5432' pg_sslmode: prefer pg_username: awx database: hosts: database-01.acme.org: admin_password: <password> pg_database: awx pg_host: database-01.acme.org pg_password: <password> pg_port: '5432' pg_sslmode: prefer pg_username: awx tower: hosts: 139.50.1.1: admin_password: <password> pg_database: awx pg_host: database-01.acme.org pg_password: <password> pg_port: '5432' pg_sslmode: prefer pg_username: awx ungrouped: {} ``` ```ini title="Negative test num. 1 - ini file" [tower] 172.27.0.2 172.27.0.3 172.27.0.4 ``` ```yaml title="Negative test num. 2 - yaml file" all: children: automationhub: hosts: automationhub.acme.org: admin_password: <password> pg_database: awx pg_host: database-01.acme.org pg_password: <password> pg_port: '5432' pg_sslmode: prefer pg_username: awx database: hosts: database-01.acme.org: admin_password: <password> pg_database: awx pg_host: database-01.acme.org pg_password: <password> pg_port: '5432' pg_sslmode: prefer pg_username: awx tower: hosts: 172.27.0.5: admin_password: <password> pg_database: awx pg_host: database-01.acme.org pg_password: <password> pg_port: '5432' pg_sslmode: prefer pg_username: awx ungrouped: {} ```
Project: StarRocks (App Definition and Development / Database)
File: array_append.md

displayed_sidebar: "English" Adds a new element to the end of the array. Returns an array. ```Haskell arrayappend(anyarray, any_element) ``` ```plain text mysql> select array_append([1, 2], 3); ++ | array_append([1,2], 3) | ++ | [1,2,3] | ++ 1 row in set (0.00 sec) ``` You can add NULL to the array. ```plain text mysql> select array_append([1, 2], NULL); ++ | array_append([1,2], NULL) | ++ | [1,2,NULL] | ++ 1 row in set (0.01 sec) ``` ARRAY_APPEND,ARRAY
Project: OAuth2 Proxy (Provisioning / Key Management)
File: adfs.md

id: adfs title: ADFS Open the ADFS administration console on your Windows Server and add a new Application Group Provide a name for the integration, select Server Application from the Standalone applications section and click Next Follow the wizard to get the client-id, client-secret and configure the application credentials Configure the proxy with ``` --provider=adfs --client-id=<application ID from step 3> --client-secret=<value from step 3> ``` Note: When using the ADFS Auth provider with nginx and the cookie session store you may find the cookie is too large and doesn't get passed through correctly. Increasing the proxybuffersize in nginx or implementing the should resolve this.
Project: StarRocks (App Definition and Development / Database)
File: bitmap_has_any.md

displayed_sidebar: "English" Calculates whether there are intersecting elements between two Bitmap columns, and the return value is Boolean value. ```Haskell B00LEAN BITMAPHASANY(BITMAP lhs, BITMAP rhs) ``` ```Plain Text MySQL > select bitmaphasany(tobitmap(1),tobitmap(2)) cnt; ++ | cnt | ++ | 0 | ++ MySQL > select bitmaphasany(tobitmap(1),tobitmap(1)) cnt; ++ | cnt | ++ | 1 | ++ ``` BITMAPHASANY,BITMAP
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.29.md

layout: release date: 2024-03-07 tag: v0.7.29 [Add]: Relationship between Kubernetes Components @pandeyshubham03 (#10482) [Server] Fix intermodel relationship registration and eval. @MUzairS15 (#10517) Update Makefile @MUzairS15 (#10511) Update reference table in docs @alphaX86 (#10518) [Docs] Mesheryctl Docs Update fixes #10503 @westcalcote (#10505) Fix layout and theme in layout @sudhanshutech (#10515) Update reference table in docs @alphaX86 (#10518) Update index.md @vishalvivekm (#10508) [Docs] Mesheryctl Docs Update fixes #10503 @westcalcote (#10505) Thank you to our contributors for making this release possible: @MUzairS15, @alphaX86, @captain-Akshay, @leecalcote, @pandeyshubham03, @sudhanshutech, @vishalvivekm, @westcalcote and l5io
Project: Kyverno (Provisioning / Security & Compliance)
File: kyverno_jp_function.md

Provides function informations. Provides function informations. For more information visit https://kyverno.io/docs/kyverno-cli/#jp ``` kyverno jp function [function_name]... [flags] ``` ``` kyverno jp function kyverno jp function truncate ``` ``` -h, --help help for function ``` ``` --adddirheader If true, adds the file directory to the header of the log messages --alsologtostderr log to standard error as well as files (no effect when -logtostderr=true) --logbacktraceat traceLocation when logging hits line file:N, emit a stack trace (default :0) --log_dir string If non-empty, write log files in this directory (no effect when -logtostderr=true) --log_file string If non-empty, use this log file (no effect when -logtostderr=true) --logfilemax_size uint Defines the maximum size a log file can grow to (no effect when -logtostderr=true). Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800) --logtostderr log to standard error instead of files (default true) --one_output If true, only write logs to their native severity level (vs also writing to each lower severity level; no effect when -logtostderr=true) --skip_headers If true, avoid header prefixes in the log messages --skiplogheaders If true, avoid headers when opening log files (no effect when -logtostderr=true) --stderrthreshold severity logs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or -alsologtostderr=true) (default 2) -v, --v Level number for the log level verbosity --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging ``` - Provides a command-line interface to JMESPath, enhanced with Kyverno specific custom functions.
Project: Curiefense (Provisioning / Security & Compliance)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: '' labels: 'enhancement' assignees: '' Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Describe the solution you'd like A clear and concise description of what you want to happen. Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. Additional context Add any other context or screenshots about the feature request here.
Project: ClickHouse (App Definition and Development / Database)
File: v22.10.2.11-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : A segmentation fault related to DNS & c-ares has been reported. The below error ocurred in multiple threads: ``` 2022-09-28 15:41:19.008,2022.09.28 15:41:19.008088 (). Backported in : Fix a bug in ParserFunction that could have led to a segmentation fault. (). Always run `BuilderReport` and `BuilderSpecialReport` in all CI types ().
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_bench.md

title: kbcli bench Run a benchmark. ``` -h, --help help for bench ``` ``` --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 ``` - Delete a benchmark. - Describe a benchmark. - List all benchmarks. - Run pgbench against a PostgreSQL cluster - run a SysBench benchmark - Run tpcc benchmark - Run tpch benchmark - Run YCSB benchmark on a cluster
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_backuprepo_update.md

title: kbcli backuprepo update Update a backup repository. ``` kbcli backuprepo update BACKUPREPONAME [flags] ``` ``` kbcli backuprepo update my-backuprepo --access-key-id=<NEW ACCESS KEY> --secret-access-key=<NEW SECRET KEY> kbcli backuprepo update my-backuprepo --default kbcli backuprepo update my-backuprepo --default=false ``` ``` --default Specify whether to set the created backup repo as default -h, --help help for update ``` ``` --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 ``` - BackupRepo command.
Project: zot (Provisioning / Container Registry)
File: README_mgmt.md

`mgmt` component provides an endpoint for configuration management Response depends on the user privileges: unauthenticated and authenticated users will get a stripped config admins will get full configuration with passwords hidden (not implemented yet) | Supported queries | Input | Output | Description | | | | | | | | None | config json | Get current zot configuration | Sample request ```bash curl http://localhost:8080/v2/_zot/ext/mgmt | jq ``` Sample response ```json { "distSpecVersion": "1.1.0", "binaryType": "-sync-search-scrub-metrics-lint-ui-mgmt", "http": { "auth": { "htpasswd": {}, "bearer": { "realm": "https://auth.myreg.io/auth/token", "service": "myauth" } } } } ``` If ldap or htpasswd are enabled mgmt will return `{"htpasswd": {}}` indicating that clients can authenticate with basic auth credentials. If any key is present under `'auth'` key, in the mgmt response, it means that particular authentication method is enabled.
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: maintainers.md

This file contains information about the primary Lagoon maintainers. Please do not contact them individually. If you have any questions or want to contribute to Lagoon, you can check out the following: Contribution docs: https://docs.lagoon.sh/contributing/ Issue queue: https://github.com/uselagoon/lagoon/issues GitHub discussions: https://github.com/uselagoon/lagoon/discussions Slack channel: Drupal Slack (https://www.drupal.org/community/contributor-guide/reference-information/talk/tools/slack) #Lagoon Website: https://lagoon.sh Blog: https://dev.to/uselagoon Discord: https://discord.gg/te5hHe95JE The Lagoon core team is responsible for the priorization, creation, development and delivery of Lagoon features. They are responsible for the development, testing and release processes. Toby Bellwood Alanna Burke Davit Darsavelidze Chris Goodwin Ben Jackson Blaize Kaye Michael Schmid Matt Swann Brandon Williams Primary contributors have made significant ongoing contributions to Lagoon. They suggest and review features, develop integrations and tools, and work closely with the Lagoon team. Chris Davis Vincenzo De Naro Papa Bryan Gruneberg Sean Hamlin Scott Leggett Salvatore Pappalardo Bastian Widmer Justin Winter The Lagoon team would also like to acknowledge the massive contributions from everyone over the years to help get Lagoon to where we are today. Lagoon comprises a number of individual tools maintained by the Lagoon team in this GitHub organization, with assistance from our primary contributors. The Lagoon team also co-maintains a number of other tools and projects that are not Lagoon-specific in conjunction with our partners:
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: v1.7.3.md

All Actor APIs return errors without an actor state store component being provided. This is the correct behavior for services that register actors, as they require state storage, but clients that invoke actors should operate with or without an actor state store. The code that initializes the Actor API raises an error when there is no actor state storage component available, regardless of whether or not the service registers actors. This fix changes the actor runtime initialization logic such that, when there is no actor state store available, the API will initialize correctly as long as the service does not register actors. As a result, the Actor API will be available to services acting only as clients (i.e invoking actors) with or without an actor state store component; the Actor API will continue to be unavailable in those services that register actors without providing an actor state store component.
Project: TDengine (App Definition and Development / Database)
File: CONTRIBUTING.md

TDengine Community Edition is free, open-source software. Its development is led by the TDengine Team, but we welcome contributions from all community members and open-source developers. This document describes how you can contribute, no matter whether you're a user or a developer yourself. All users can report bugs to us through the . To ensure that the development team can locate and resolve the issue that you experienced, please include the following in your bug report: A detailed description of the issue, including the steps to reproduce it. Any log files that may be relevant to the issue. Developers are encouraged to submit patches to the project, and all contributions, from minor documentation changes to bug fixes, are appreciated by our team. To ensure that your code can be merged successfully and improve the experience for other community members, we ask that you go through the following procedure before submitting a pull request: Read and accept the terms of the TAOS Data Contributor License Agreement (CLA) located at . For bug fixes, search the to check whether the bug has already been filed. If the bug that you want to fix already exists in the issue tracker, review the previous discussion before submitting your patch. If the bug that you want to fix does not exist in the issue tracker, click New issue and file a report. Ensure that you note the issue number in your pull request when you submit your patch. Fork our repository to your GitHub account and create a branch for your patch. Important: The `main` branch is for stable versions and cannot accept patches directly. For all code and documentation changes, create your own branch from the development branch `3.0` and not from `main`. Note: For a documentation change, ensure that the branch name starts with `docs/` so that the change can be merged without running tests. Create a pull request to merge your changes into the development branch `3.0`, and our team members will review the request as soon as possible. If you encounter any difficulties or problems in contributing your code, you can join our and receive assistance from members of the TDengine Team. To thank community members for your support, we are offering a free gift to any developer who submits at least one contribution. You can choose one of the following items: <p align="left"> <img src="docs/assets/contributing-cup.jpg" alt="" width="200" /> <img src="docs/assets/contributing-notebook.jpg" alt="" width="200" /> <img src="docs/assets/contributing-shirt.jpg" alt="" width="200" /> If you would like to claim your gift, send an email to including the following information: Your GitHub account name Your name and mailing address Your preferred gift Note: Limit one per person.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_dns_resource_record_sets.md

+++ title = "googlednsresourcerecordsets resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlednsresourcerecordsets" identifier = "inspec/resources/gcp/googlednsresourcerecordsets.md googlednsresourcerecordsets resource" parent = "inspec/resources/gcp" +++ A `googlednsresourcerecordsets` is used to test a Google ResourceRecordSet resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlednsresourcerecordsets(project: 'chef-gcp-inspec', name: 'backend.my.domain.com.', managed_zone: 'inspec-gcp-managed-zone') do its('count') { should eq 3 } its('types') { should include 'A' } its('ttls') { should include '300' } its('targets.flatten') { should include '8.8.8.8' } its('targets.flatten') { should include '8.8.4.4' } end ``` Properties that can be accessed from the `googlednsresourcerecordsets` resource: See the resource for more information. `names` : an array of `googlednsresourcerecordset` name `types` : an array of `googlednsresourcerecordset` type `ttls` : an array of `googlednsresourcerecordset` ttl `targets` : an array of `googlednsresourcerecordset` target `managed_zones` : an array of `googlednsresourcerecordset` managed_zone This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.
Project: Apache StreamPipes (App Definition and Development / Streaming & Messaging)
File: PULL_REQUEST_TEMPLATE.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. ~ --> <!-- Thanks for contributing! Here are some tips you can follow to help us incorporate your contribution quickly and easily: If this is your first time, please read our contributor guidelines: https://streampipes.apache.org/getinvolved.html https://cwiki.apache.org/confluence/display/STREAMPIPES/Getting+Started Make sure the PR title is formatted like: `[#<GitHub issue id>] PR title ...` If the PR is unfinished, add ' PR title ...`. Please write your PR title to summarize what this PR proposes/fixes. Link the PR to the corresponding GitHub issue (if present) in the `Development` section in the right menu bar. Be sure to keep the PR description updated to reflect all changes. If possible, provide a concise example to reproduce the issue for a faster review. Make sure tests pass via `mvn clean install`. (Optional) If the contribution is large, please file an Apache ICLA http://apache.org/licenses/icla.pdf --> <!-- Please clarify what changes you are proposing and describe how those changes will address the issue. Furthermore, describe potential consequences the changes might have. --> <!-- Is there anything left we need to pay attention on? Are there some references that might be important? E.g. links to Confluence, or discussions on the mailing list or GitHub. --> PR introduces (a) breaking change(s): <yes/no> PR introduces (a) deprecation(s): <yes/no>