cwielenb/CNCF-Dataset huggingface dataset:
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.113.md

layout: release date: 2023-07-28 tag: v0.6.113 Add endpoint for connections status @abdullah1308 (#8277) [component-updater-script] update paths for icons for remote-provider @theBeginner86 (#8304) Update affiliation on MAINTAINERS table @alphaX86 (#8290) [UI] Change switch paradigm for grid and table view @duckling69 (#8300) Refactor/diviz11/mesheryctl-filter-import-update @diviz11 (#8254) [mesheryctl] Shortened USER ID in mesheryctl filter list @kunxl-gg (#8282) [UI] Fix publish modal for meshmap and added type as enum in publish modal schema @Yashsharma1911 (#8273) [UI] Change switch paradigm for grid and table view @duckling69 (#8300) fix filter update and filter name provided not being respected @MUzairS15 (#8283) Fix: remove wildcard check by *, and use full string @Abhishek-kumar09 (#8296) [MeshModels] Add support for wildcard versions @Abhishek-kumar09 (#8285) Enhancement: Dont crash the UI on RJSF Form Errors @Abhishek-kumar09 (#8288) Add supported relationships screenshots @Boombag0607 (#8287) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Boombag0607, @MUzairS15, @Yashsharma1911, @abdullah1308, @alphaX86, @diviz11, @duckling69, @kunxl-gg, @leecalcote and @theBeginner86
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_data_insert_elasticsearch.md

title: Kubectl-Dba Data Insert Elasticsearch menu: docs_{{ .version }}: identifier: kubectl-dba-data-insert-elasticsearch name: Kubectl-Dba Data Insert Elasticsearch parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Insert data to a elasticsearch database Use this cmd to insert data into a elasticsearch database ``` kubectl-dba data insert elasticsearch [flags] ``` ``` kubectl dba insert -n demo es es-quickstart --rows 1000 ``` ``` -h, --help help for elasticsearch -r, --rows int number of rows to insert (default 100) ``` ``` --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 ``` - Insert random data in a database
Project: KICS (Provisioning / Security & Compliance)
File: 9232306a-f839-40aa-b3ef-b352001da9a5.md

title: S3 Bucket Without Versioning hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 9232306a-f839-40aa-b3ef-b352001da9a5 Query name: S3 Bucket Without Versioning Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Backup URL: S3 bucket should have versioning enabled<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="3 15" name: foo amazon.aws.s3_bucket: name: mys3bucket policy: "{{ lookup('file','policy.json') }}" requester_pays: yes tags: example: tag1 another: tag2 name: foo2 amazon.aws.s3_bucket: name: mys3bucket policy: "{{ lookup('file','policy.json') }}" requester_pays: yes versioning: no tags: example: tag1 another: tag2 ``` ```yaml title="Negative test num. 1 - yaml file" name: foo amazon.aws.s3_bucket: name: mys3bucket policy: "{{ lookup('file','policy.json') }}" requester_pays: yes versioning: yes tags: example: tag1 another: tag2 ```
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: 04-plugins.md

id: plugins title: Frontend Plugins sidebar_label: Plugins description: Frontend plugins NOTE: The new frontend system is in alpha and is only supported by a small number of plugins. <!-- Introduce frontend plugins and how each of them is shipped as a separate package. Highlight that each package should only export a single plugin instance. --> <!-- How to create a simple plugin --> ```ts export const myPlugin = createPlugin({ id: 'my-plugin', }); ``` <!-- Note that this plugin is useless in itself, and you need to provide extra options to make it useful, in particular extensions. --> <!-- link to relevant docs --> <!-- Example of how this option is used in `createPlugin` link to relevant docs --> <!-- Example of how this option is used in `createPlugin` link to relevant docs --> <!-- Example of how this option is used in `createPlugin` link to relevant docs --> <!-- Example of how this option is used in `createPlugin` link to relevant docs --> <!-- Quick intro, but link back to app docs for more details -->
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_fault_node.md

title: kbcli fault node Node chaos. ``` -h, --help help for node ``` ``` --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 ``` - Inject faults to pod. - Detach volume - Restart instance - Stop instance
Project: Confidential Containers (Provisioning / Security & Compliance)
File: alignment.md

Confidential Containers are connected to a wide array of projects. Some projects are directly implicated in the design of Confidential Containers. Others might be a good pairing for Confidential Containers, and others might be transparently supported or consumed by or via Confidential Containers. If work needs to be done to align a project with Confidential Containers, it will generally involve reconciling the strict trust model of Confidential Containers and the tradional cloud native trust model. Given that Confidential Containers are deployed via containerd/cri-o and Kubernetes, these projects are directly implicated. With Confidential Containers, container images are pulled inside the enclave and are essentially not present on the host. Some changes will be needed higher up the stack to accommodate this. Work is already ongoing in at least one of these communities (containerd) to support Confidential Containers. These projects might pair nicely with Confidential Containers, but are not required. can be used to assign a provable identity to every workload. With some adjustments this might be a good way to deliver secrets to confidential containers or even the containers themselves. The attestation process would most likely have to be linked to platform-specific hardware attestation, perhaps in conjunction with the Attestation Agent. The SPIRE agent would need to be moved inside the enclave and the SPIRE server could not be provided by the Cloud Service Provider (CSP). Further investigation is encouraged. A service mesh (, ) could be a good way to extend the security guarantees of Confidential Containers to the network, essentially by ensuring that traffic is encrypted prior to leaving the enclave. The service mesh would need to be configured such that the CSP could not manipulate sensitive guest network policies. In the case of Istio, the Istio Daemon has a broad authority to reconfigure networking rules. This would break the trust model of Confidential Containers. With Confidential Containers, logs must be carefully configured to avoid exposing Confidential information to the CSP. Locking down the workload logging, monitoring, and tracing difficult. The CNCF has many projects that standardize or centralize logs. These include , , , , and . Perhaps one of these could be used to securely deliver confidential logs to the guest owner. More investigation is needed Since Confidential Containers are a drop-in replacement for traditional containers, Confidential Containers should be able to consume or support a wide range of container-related projects including container registries like or . Tools for defining applications or creating build pipelines should work with minimal modification. Of course any services that can be deployed as containers should also work as Confidential Containers with new security properties.
Project: StarRocks (App Definition and Development / Database)
File: url_extract_parameter.md

displayed_sidebar: "English" Extracts the value of the requested `name` parameter from the query string of a URL. Parameter extraction is handled in the manner as specified in . If the specified parameter name does not exist, NULL is returned. This function is supported from v3.2. ```haskell VARCHAR urlextractparameter(VARCHAR str, VARCHAR name) ``` `str`: the URL string to extract parameters. `name`: the name of the parameter in the query string. Returns a VARCHAR value. ```plaintext mysql> select urlextractparameter("https://starrocks.io/doc?k1=10&k2=3&k1=100", "k1"); ++ | urlextractparameter('https://starrocks.io/doc?k1=10&k2=3&k1=100', 'k1') | ++ | 10 | ++ mysql> select urlextractparameter('https://starrocks.com/doc?k0=10&k1=%21%23%24%26%27%28%29%2A%2B%2C%2F%3A%3B%3D%3F%40%5B%5D%20%22%25%2D%2E%3C%3E%5C%5E%5F%60%7B%7C%7D%7E&k2','k1'); +--+ | urlextractparameter('https://starrocks.com/doc?k0=10&k1=%21%23%24%26%27%28%29%2A%2B%2C%2F%3A%3B%3D%3F%40%5B%5D%20%22%25%2D%2E%3C%3E%5C%5E%5F%60%7B%7C%7D%7E&k2', 'k1') | +--+ | !#$&'()*+,/:;=?@[] "%-.<>\^_`{|}~ | +--+ ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.36.md

layout: release date: 2024-03-23 tag: v0.7.36 Bump webpack-dev-middleware from 5.3.1 to 5.3.4 in /install/docker-extension/ui @dependabot (#10600) Remove comment schema from Meshery definitions @leecalcote (#10604) [Add]: Relationship between KubeArmorPolicy and Kubernetes Components @pandeyshubham03 (#10534) Upgrade to Sistent v0.14.18 @leecalcote (#10605) fix cancel search button @Aseem22 (#10528) [Docs] Commands visibility fix @ritiksaxena124 (#10601) Update patterns.md @leecalcote (#10587) [Docs]: Add a new contrib docs page for Model Relationships @pandeyshubham03 (#10540) [Fix Docs] Improve code formatting for ALL code blocks @sandramsc (#10598) Thank you to our contributors for making this release possible: @Aseem22, @MUzairS15, @Yashsharma1911, @aabidsofi19, @dependabot, @dependabot[bot], @leecalcote, @pandeyshubham03, @ritiksaxena124, @sandramsc and @sudhanshutech
Project: KICS (Provisioning / Security & Compliance)
File: 1ffe7bf7-563b-4b3d-a71d-ba6bd8d49b37.md

title: Namespace Lifecycle Admission Control Plugin Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 1ffe7bf7-563b-4b3d-a71d-ba6bd8d49b37 Query name: Namespace Lifecycle Admission Control Plugin Disabled Platform: Kubernetes Severity: <span style="color:#edd57e">Low</span> Category: Build Process URL: When using kube-apiserver command, the '--disable-admission-plugins' flag should not have 'NamespaceLifecycle' plugin<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: ["--disable-admission-plugins=NamespaceLifecycle"] restartPolicy: OnFailure ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver","--disable-admission-plugins=NamespaceLifecycle"] args: [] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: ["--enable-admission-plugins=NamespaceLifecycle", "--admission-control-config-file=path/to/plugin/config/file.yaml"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 2 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: [] restartPolicy: OnFailure ```
Project: Kyverno (Provisioning / Security & Compliance)
File: GOVERNANCE.md

This document defines governance policies for the Kyverno project. The Kyverno project community adheres to the following principles: Open: The Kyverno community strives to be open, accessible and welcoming to everyone. Anyone may contribute, and contributions are available to all users according to open source values and licenses. Transparent and accessible: Any changes to the Kyverno source code and collaborations on the project are publicly accessible (GitHub issues, PRs, and discussions). Merit: Ideas and contributions are accepted according to their technical merit and alignment with project objectives, scope, and design principles. Kyverno follow the , which is aligned with the . Kyverno community meetings follow a defined . The maintainers will also have closed meetings in order to discuss security reports or Code of Conduct violations. Such meetings should be scheduled by any maintainer on receipt of a security issue or CoC report. All current Maintainers must be invited to such closed meetings, except for any maintainer who is accused of a CoC violation. The Kyverno project welcomes all contributors and has well-defined roles specified at . Typically, it is assumed that disputes will be resolved amicably by those involved. However, if the situation becomes more serious, conflicts will be resolved through a voting process. A supermajority of votes from project maintainers is required to make a decision, and the project lead has the final say in the ruling. This Project Governance is a living document. All key project changes including changes in project governance can be proposed by a GitHub PR and then reviewed and voted on by project maintainers. Sections of this document have been borrowed from the and projects.
Project: Siddhi (App Definition and Development / Streaming & Messaging)
File: pull_request_template.md

Describe the problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc. Describe the solutions that this feature/fix will introduce to resolve the problems described above Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email documentation@wso2.com to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here. Brief description of the new feature or bug fix as it will appear in the release notes Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter N/A plus brief explanation of why theres no doc impact Unit tests > Code coverage information Integration tests > Details about the test cases and coverage Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no Ran FindSecurityBugs plugin and verified report? yes/no Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no Provide high-level details about the samples related to this feature List any other related PRs List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested
Project: ArangoDB (App Definition and Development / Database)
File: has_lost_consistency.md

+++ title = "`bool haslostconsistency() const noexcept`" description = "Returns true if a preceding swap involving this object failed to preserve the strong guarantee. Constexpr, never throws." categories = ["observers"] weight = 596 +++ Returns true if a preceding swap involving this object failed to preserve the strong guarantee. Constexpr where possible. Requires: Always available. Complexity: Constant time. Guarantees: Never throws an exception.
Project: Meshery (Provisioning / Automation & Configuration)
File: 12-16-21_721b787.md

timestamp: meshery-component: meshery-linkerd meshery-component-version: v0.5.12 meshery-server-version: v0.5.61 k8s-distro: minikube k8s-version: v1.21.0 service-mesh: linkerd service-mesh-version: v2.02.8 tests: prometheus: passing jaeger: failing overall-status: partial
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.142.md

layout: release date: 2023-09-19 tag: v0.6.142 Remove adapter references in default env vars @leecalcote (#8810) [Docker Extension] Remove adapters from default configuration @leecalcote (#8811) [chore] fix color undefined @theBeginner86 (#8832) [UI] Notification Center: Update color of "No notifications to show" @leecalcote (#8828) Fix repetitive api calls and UI issues in connections page @sudhanshutech (#8825) changed LoadTestTimerConfig and MeshAdapterConfigComponent to functional component @EraKin575 (#8781) [chore] fix color undefined @theBeginner86 (#8832) Fix repetitive api calls and UI issues in connections page @sudhanshutech (#8825) Meshery End-to-End Tests with mesheryctl @KiptoonKipkurui (#8808) Update "Meshery Deployment Incompatible" error docs @Mohith234 (#8824) Thank you to our contributors for making this release possible: @EraKin575, @KiptoonKipkurui, @Mohith234, @Yashsharma1911, @aabidsofi19, @leecalcote, @sudhanshutech and @theBeginner86
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.0.10-en.md

Improve `/nodes` API responsiveness . Improve the integration of the `banned` and the `delayed` feature . Now when publishing a delayed message will check first if its source client is banned, if true, this publish will be ignored. Update `gen_rpc` library to version 3.0 . Improve memory usage on core nodes when bootstrapping a replicant . Improve stability of Prometheus Push Gateway and log errors when POST fails . Now it is possible to opt out VM internal metrics in prometheus stats . When system load is high, reporting too much metrics data may cause the prometheus stats API timeout. Improve security when converting types such as `binary` `lists` to `atom` types , . Add `/trace/:name/log_detail` HTTP API to return trace file's size and mtime . Add `/status` HTTP API endpoint to api documentation . Binary packages for all platforms are now built on Erlang/OTP version 24.3.4.2 . Added more `client.disconnected` events (and counter bumps) . Prior to this change, the `client.disconnected` event (and counter bump) is triggered when a client performs a 'normal' disconnect, or is 'kicked' by system admin, but NOT triggered when a stale connection had to be 'discarded' (for clean session) or 'takeovered' (for non-clean session) by new connection. Fix error log message when `mechanism` is missing in authentication config . Fix HTTP 500 issue when unknown `status` parameter is used in `/gateway` API call . Fixed the HTTP response status code for the `/status` endpoint . Before the fix, it always returned `200` even if the EMQX application was not running. Now it returns `503` in that case. Fix message delivery related event encoding . This bug was introduced in v5.0.9. For Rule-Engine's input events like `$events/message_delivered` and `$events/message_dropped`, if the message was delivered to a shared-subscription, the encoding (to JSON) of the event will fail. Fix bad HTTP response status code for `/gateways` API, when Gateway name is unknown, it should return `404` instead of `400` . Fix incorrect topic authorize checking of delayed messages . Now will determine the actual topic of the delayed messages, e.g. `$delayed/1/t/foo` will be treated as `t/foo` in authorize checks. Add property `code` to error response for `/authentication/sources/:type` . Align documentation for `/authentication/sources` with what we actually send . Fix query string parameter 'node' to `/configs` resource being ignored, return 404 if node does not exist . Avoid re-dispatching shared-subscription session messages when a session is kicked or taken-over (to a new session) .