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

meta: name: description content: "Fairwinds Pluto | Quickstart Documentation" First, follow the install instructions to install pluto. Run `pluto detect-files -d <DIRECTORY YOU WANT TO SCAN>` You should see an output something like: ``` $ pluto detect-files -d pkg/finder/testdata NAME KIND VERSION REPLACEMENT REMOVED DEPRECATED utilities Deployment extensions/v1beta1 apps/v1 true true utilities Deployment extensions/v1beta1 apps/v1 true true ``` This indicates that we have two files in our directory that have deprecated apiVersions. This will need to be fixed prior to a 1.16 upgrade. ``` $ pluto detect-helm -owide NAME NAMESPACE KIND VERSION REPLACEMENT DEPRECATED DEPRECATED IN REMOVED REMOVED IN cert-manager/cert-manager-webhook cert-manager MutatingWebhookConfiguration admissionregistration.k8s.io/v1beta1 admissionregistration.k8s.io/v1 true v1.16.0 false v1.19.0 ``` This indicates that the StatefulSet audit-dashboard-prod-rabbitmq-ha was deployed with apps/v1beta1 which is deprecated in 1.16 If you want to see information for a single namespace, you can pass the `--namespace` or `-n` flag to restrict the output. ``` $ pluto detect-helm -n cert-manager -owide NAME NAMESPACE KIND VERSION REPLACEMENT DEPRECATED DEPRECATED IN REMOVED REMOVED IN cert-manager/cert-manager-webhook cert-manager MutatingWebhookConfiguration admissionregistration.k8s.io/v1beta1 admissionregistration.k8s.io/v1 true v1.16.0 false v1.19.0 ``` You can run `helm template <chart-dir> | pluto detect -` This will output something like so: ``` $ helm template e2e/tests/assets/helm3chart | pluto detect - KIND VERSION DEPRECATED DEPRECATED IN RESOURCE NAME Deployment extensions/v1beta1 true v1.16.0 RELEASE-NAME-helm3chart-v1beta1 ``` ``` $ pluto detect-api-resources -owide NAME NAMESPACE KIND VERSION REPLACEMENT DEPRECATED DEPRECATED IN REMOVED REMOVED IN psp <UNKNOWN> PodSecurityPolicy policy/v1beta1 true v1.21.0 false v1.25.0 ``` This indicates that the PodSecurityPolicy was deployed with apps/v1beta1 which is deprecated in 1.21 ``` $ pluto detect-all-in-cluster -o wide 2>/dev/null NAME NAMESPACE KIND VERSION REPLACEMENT DEPRECATED DEPRECATED IN REMOVED REMOVED IN testing/viahelm viahelm Ingress networking.k8s.io/v1beta1 networking.k8s.io/v1 true v1.19.0 true v1.22.0 webapp default Ingress networking.k8s.io/v1beta1 networking.k8s.io/v1 true v1.19.0 true v1.22.0 eks.privileged <UNKNOWN> PodSecurityPolicy policy/v1beta1 true v1.21.0 false v1.25.0 ``` This combines all available in-cluster detections, showing results from Helm releases and API resources.
Project: YugabyteDB (App Definition and Development / Database)
File: jsonb-to-record.md

title: jsonbtorecord() and jsontorecord() headerTitle: jsonbtorecord() and jsontorecord() linkTitle: jsonbtorecord() description: Convert a JSON object into the equivalent SQL record. Offers no practical advantage over the jsonbpopulaterecord() variant. menu: v2.18: identifier: jsonb-to-record parent: json-functions-operators weight: 230 type: docs Purpose: Convert a JSON object into the equivalent SQL `record`. Signature For the `jsonb` variant: ``` input value: jsonb return value: record ``` Notes: The `jsonbtorecord()` function is a syntax variant of the same functionality that provides. It doesn't need a schema-level type but, rather, uses this special SQL locution: ``` select... as onthefly(<record definition>) ``` Use this `ysqlsh` script to create the type "t" that just `jsonbpopulaterecord()` requires, to convert the input `jsonb` into a SQL `record` using each of `jsonbpopulaterecord()` and `jsonbtorecord`, and then to execute the `ASSERT`. Notice that "onthefly" is a nonce name, made up for this example. Anything will suffice. ```plpgsql create type t as (a int, b text); do $body$ declare object constant jsonb := '{"a": 42, "b": "dog"}'; result1 constant t := jsonbpopulate_record(null::t, object); result_2 t; expected_result constant t := (42, 'dog'); begin select a, b into strict result_2 from jsonbtorecord(object) as onthefly(a int, b text); assert (result1 = expectedresult) and (result2 = expectedresult), 'unexpected'; end; $body$; ``` The nominal advantage of `jsonbtorecord()`, that it doesn't need a schema-level type, is lost when the input JSON object has another object as the value of one of its keys. Consider this `ysqlsh` script: ```plpgsql create type t1 as ( d int, e text); create type t2 as (a int, b text[], c t1); do $body$ declare nested_object constant jsonb := '{"a": 42, "b": ["cat", "dog"], "c": {"d": 17, "e": "frog"}}'; result1 constant t2 := jsonbpopulaterecord(null::t2, nestedobject); result_2 t2; expected_a constant int := 42; expected_b constant text[] := array['cat', 'dog']; expected_c constant t1 := (17, 'frog'); expectedresult constant t2 := (expecteda, expectedb, expectedc); begin select a, b, c into strict result_2 from jsonbtorecord(nested_object) as onthefly(a int, b text[], c t1); assert (result1 = expectedresult) and (result2 = expectedresult), 'unexpected'; end; $body$; ``` It does show that and `jsonbtorecord()` both produce the same result from the same input. But, here, the "onthefly" type definition in the `AS` clause So the outer type "t2" can be defined on the fly in the `as` clause but it references the inner schema-level type "t1". It isn't possible to absorb "t1"'s definition into the `as` clause. Moreover, the fact that `jsonbtorecord()` cannot be used in an ordinary assignment but requires a SQL `SELECT ... INTO` statement is a serious drawback. The `jsonbtorecord()` syntax variant therefore has no practical advantage over the variant.
Project: StarRocks (App Definition and Development / Database)
File: bitmap_count.md

displayed_sidebar: "English" Returns the 1-bit count for the input bitmap. ```Haskell INT BITMAPCOUNT(anybitmap) ``` ```Plain Text MySQL > select bitmapcount(bitmapfrom_string("1,2,4")); +-+ | bitmapcount(bitmapfrom_string('1,2,4')) | +-+ | 3 | +-+ MySQL > select bitmap_count(NULL); +--+ | bitmap_count(NULL) | +--+ | 0 | +--+ ``` BITMAP,BITMAP_COUNT
Project: Paralus (Provisioning / Security & Compliance)
File: GOVERNANCE.md

Welcome! We are so glad you're here. Before we get started, please be aware this is a living document. As our project grows, we expect to add additional roles and groups and expand this document and our governance model to help keep everything running smoothly. If youd like to contribute to this document and the governance plans it describes, go ahead and create a new GitHub Issue and let us know. Its our intention to be as transparent and open as possible. We do our best to ensure a positive experience for our community. To that end, we ask everyone in the community to adhere to the . Paralus has been created and open sourced by . Our governance structure consists of maintainers and contributors, with one maintainer designated as the project leader. After one year, the project leader is elected annually by the maintainers in consensus based on their ongoing contribution to the growth and development of the project. The project leader has to: Guide the project direction Manage the feature roadmap Accept/reject major feature changes from contributors Perform other Maintainer tasks Maintainers: Submit, review, comment, label, and approve issues and pull requests Participate in code reviews and attend project meetings Test code and merge code changes Manage templates Contribute to the project Release Notes Answer questions from users and contributors Contributors: Submit Issues, Pull Requests, and code reviews. Users become contributors by submitting Pull Requests and Issues, and engaging in meetings and discussions on . Contributors who wish to become maintainers can be nominated by other contributors or maintainers, or nominate themselves. Approved feature requests and bug fixes whose code has been tested and approved are merged and published as part of an official release at least once a month. Code can be approved by any two maintainers in consensus, or by the project leader. Were always looking for contributors and maintainers to help guide the project and grow the project! There are a few ways you can get involved as a contributor or a maintainer: Review and comment on open Issues Submit new Issues with feature requests and bug fixes Create Pull Requests Make sure to review the `CONTRIBUTING.md` file before making changes. If you have any questions, concerns, or would just like to chat, catch us on !
Project: Crunchy Postgres Operator (App Definition and Development / Database)
File: bug_report.md

name: Report a Bug about: Found an issue? Let us fix it. Please ensure you do the following when reporting a bug: [ ] Provide a concise description of what the bug is. [ ] Provide information about your environment. [ ] Provide clear steps to reproduce the bug. [ ] Attach applicable logs. Please do not attach screenshots showing logs unless you are unable to copy and paste the log data. for legibility. Note that some logs needed to troubleshoot may be found in the `/pgdata/<CLUSTERNAME>/pg_log` directory on your Postgres instance. An incomplete bug report can lead to delays in resolving the issue or the closing of a ticket, so please be as detailed as possible. If you are looking for , please view the page for where you can ask questions. Thanks for reporting the issue, we're looking forward to helping you! Add a concise description of what the bug is. Please provide the following details: Platform: (`Kubernetes`, `OpenShift`, `Rancher`, `GKE`, `EKS`, `AKS` etc.) Platform Version: (e.g. `1.20.3`, `4.7.0`) PGO Image Tag: (e.g. `ubi8-5.x.y-0`) Postgres Version (e.g. `15`) Storage: (e.g. `hostpath`, `nfs`, or the name of your storage class) Provide steps to get to the error condition: Run `...` Do `...` Try `...` Provide the behavior that you expected. Describe what actually happens Please provided appropriate log output or any configuration files that may help troubleshoot the issue. DO NOT include sensitive information, such as passwords. Please provide any additional information that may be helpful.
Project: Druid (App Definition and Development / Database)
File: datasourcemetadataquery.md

id: datasourcemetadataquery title: "DatasourceMetadata queries" sidebar_label: "DatasourceMetadata" <!-- ~ 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. --> :::info Apache Druid supports two query languages: and . This document describes a query type that is only available in the native language. ::: Data Source Metadata queries return metadata information for a dataSource. These queries return information about: The timestamp of the latest ingested event for the dataSource. This is the ingested event without any consideration of rollup. The grammar for these queries is: ```json { "queryType" : "dataSourceMetadata", "dataSource": "sample_datasource" } ``` There are 2 main parts to a Data Source Metadata query: |property|description|required?| |--|--|| |queryType|This String should always be "dataSourceMetadata"; this is the first thing Apache Druid looks at to figure out how to interpret the query|yes| |dataSource|A String or Object defining the data source to query, very similar to a table in a relational database. See for more information.|yes| |context|See |no| The format of the result is: ```json [ { "timestamp" : "2013-05-09T18:24:00.000Z", "result" : { "maxIngestedEventTime" : "2013-05-09T18:24:09.007Z" } } ] ```
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: kustomize.md

Kustomize can be used to do lots of powerful operations such as ConfigMap and Secret generations, applying common labels and annotations, updating image names and tags. To use these features with Numaflow CRD objects, download into your kustomize directory, and add it to `configurations` section. ```yaml kind: Kustomization apiVersion: kustomize.config.k8s.io/v1beta1 configurations: numaflow-transformer-config.yaml ``` Here is an to use transformers with a Pipeline. Starting from version 4.5.5, kustomize can use Kubernetes to provide merge key and patch strategy information. To use that with Numaflow CRD objects, download into your kustomize directory, and add it to `openapi` section. ```yaml apiVersion: kustomize.config.k8s.io/v1beta1 kind: Kustomization openapi: path: schema.json ``` For example, given the following Pipeline spec: ```yaml apiVersion: numaflow.numaproj.io/v1alpha1 kind: Pipeline metadata: name: my-pipeline spec: vertices: name: in source: generator: rpu: 5 duration: 1s name: my-udf udf: container: image: my-pipeline/my-udf:v0.1 name: out sink: log: {} edges: from: in to: my-udf from: my-udf to: out ``` You can update the `source` spec via a patch in a kustomize file. ```yaml apiVersion: kustomize.config.k8s.io/v1beta1 kind: Kustomization resources: my-pipeline.yaml openapi: path: https://raw.githubusercontent.com/numaproj/numaflow/main/api/json-schema/schema.json patches: patch: |- apiVersion: numaflow.numaproj.io/v1alpha1 kind: Pipeline metadata: name: my-pipeline spec: vertices: name: in source: generator: rpu: 500 ``` See the full example .
Project: YugabyteDB (App Definition and Development / Database)
File: savepoint_rollback.md

title: ROLLBACK TO statement [YSQL] headerTitle: ROLLBACK TO linkTitle: ROLLBACK TO SAVEPOINT description: Use the `ROLLBACK TO` statement to start a subtransaction within the current transaction. menu: v2.18: identifier: savepoint_rollback parent: statements type: docs Use the `ROLLBACK TO SAVEPOINT` statement to revert the state of the transaction to a previously established savepoint. This can be particularly useful to handle and unwind errors like key/index constraint violations. {{%ebnf%}} savepoint_rollback {{%/ebnf%}} ```plpgsql ROLLBACK [ WORK | TRANSACTION ] TO [ SAVEPOINT ] name ``` The name of the savepoint to which you wish to roll back. Create a sample table and add one row to start. ```plpgsql CREATE TABLE sample(k int PRIMARY KEY, v int); INSERT INTO sample(k, v) VALUES (1, 2); ``` Begin a transaction and insert some rows. ```plpgsql BEGIN TRANSACTION; INSERT INTO sample(k, v) VALUES (3, 4); ``` Now, create a savepoint before inserting a duplicate row for `k=1`: ```plpgsql SAVEPOINT test; INSERT INTO sample(k, v) VALUES (1, 3); ``` You should get the following error: ```output ERROR: duplicate key value violates unique constraint "k_pkey" ``` Any other operations should error, since the transaction is now in a bad state: ```plpgsql SELECT * FROM sample; ``` ```output ERROR: current transaction is aborted, commands ignored until end of transaction block ``` However, you can roll back to our earlier savepoint and continue with the transaction without losing our earlier insert: ```plpgsql ROLLBACK TO test; INSERT INTO sample(k, v) VALUES (5, 6); COMMIT; ``` If you check the rows in the table, you will see the row you inserted before the primary key violation, as well as the one you inserted after roll back: ```plpgsql SELECT * FROM sample; ``` ```output k | v -+- 1 | 2 3 | 4 5 | 6 (3 rows) ```
Project: LinuxKit (Provisioning / Automation & Configuration)
File: trusted-computing.md

LinuxKit has support for using Platform Modules (tpm) chips. Supporting tpm requires support at three levels: Hardware Kernel Software - The Trusted Computing Software Stack (TSS) You need to have a tpm chip installed in your computer to use tpm. Alternatively, you can use one of the virtual tpms implemented in software, provided that either: your kernel supports it your hardware virtualization platform supports it As of , the in-tree linux kernel modules that support tpm are shipped with LinuxKit by default. The shipped modules support both tpm chip versions 1.2 and tpm 2.0. The software stack (TSS) functions differently between tpm versions 1.2 and 2.0. In tss 1.2, the character device `/dev/tpm0` is meant to be addresses only by a single process. All other clients are expected to communicate with this single client that handles multiplexing of requests and various other low-level functionality. The single client normally used is . It creates a daemon, `tcsd`, that communicates with the character device (and via the character device and the kernel module to the actual tpm). `tcsd` in turn listens on `localhost:30003` for tpm commands. All other clients are expected to communicate via tcp to `tcsd`. LinuxKit provides the `linuxkit/tss` image which includes: `tcsd` the various `tpm_` tools To make a `tcsd` available to your LinuxKit image, just include it: ```yml services: name: tss image: linuxkit/tss:<hash> ``` For a full example, see In tss 2.0, the character device `/dev/tpmrm0` can be addressed by as many processes, in parallel, as desired. All of the multiplexing and low-level services are built into the kernel module. To use a tpm 2.0 device, you do not need any special tss container. You just need an container that: Bind-mounts `/dev` in Has your tools or libraries installed Talks directly to `/dev/tpmrm0` The image `linuxkit/tss` ships with the version 1.2 `tcsd` and the `tpm*` tools for tpm version 1.2. The tools for tpm version 2.0 `tpm2*` and its attendant libs are not included in the image. We intend to release a tss 2.0 compatible image in the near future. In the meantime, nothing prevents you from using and compiling your own tss and including it in a LinuxKit image.
Project: Metal³ (Provisioning / Automation & Configuration)
File: bug_report.md

name: Bug report about: Tell us about a problem you are experiencing What steps did you take and what happened: [A clear and concise description on how to REPRODUCE the bug.] What did you expect to happen: Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.] Environment: Baremetal Operator version: Environment (metal3-dev-env or other): /kind bug
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: getting-involved.md

id: getting-involved title: Getting Involved description: How can you help us build Backstage? We welcome contributions of all kinds, from documentation to code to design. We encourage contributions of all kinds, from documentation to code to design, here's some ideas on how you can help us build and improve Backstage! No one likes bugs. Report bugs as an issue . Look through the GitHub issues for , or . The value of Backstage grows with every new plugin that gets added. Wouldn't it be fantastic if there was a plugin for every infrastructure project out there? We think so. And we would love your help. Head over to and get started! A great reference example of a plugin can be found on (thanks !) What kind of plugins should/could be created? Some inspiration from the 120+ plugins that we have developed inside Spotify can be found , but we will keep a running list of suggestions labeled with in our . If you start developing a plugin that you aim to release as open source, we suggest that you create a in the community plugins repo. This helps the community know what plugins are in development. You can also use this process if you have an idea for a good plugin but you hope that someone else will pick up the work. Since there is such a large landscape of possible development, build, and deployment environments, we welcome community contributions in these areas in the folder of the project. This is an excellent place to put things that help out the community at large, but which may not fit within the scope of the core product to support natively. Here, you will find Helm charts, alternative Docker images, and much more. The current documentation is very limited. Help us make the `/docs` folder come alive. Docs are published to . If you contribute to the documentation, you might want to preview your changes before submitting them. You'll find the website sources under with instructions for building and locally serving the website in the . We think the best way to ensure different plugins provide a consistent experience is through a solid set of reusable UI/UX components. Backstage uses . Either help us or improve stories for the existing ones (look for files with `*.stories.tsx`). The best way to send feedback is to file . If you are proposing a feature: Explain in detail how it would work. Keep the scope as narrow as possible, to make it easier to implement. Use appropriate labels Remember that this is a volunteer-driven project, and that contributions are welcome :) Have you started using Backstage? Adding your company to really helps the project, you can do this by filling out this .
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.31.md

layout: release date: 2022-12-02 tag: v0.6.31 language: en Bump decode-uri-component from 0.2.0 to 0.2.2 in /install/docker-extension/ui @dependabot (#6616) Add component updater utility @Revolyssup (#6582) Redirect to login in case of no cookie @MUzairS15 (#6595) Fix : icons and checkbox bg @harkiratsm (#6591) [mesheryctl] Improve error messages for system context commands #6268 @devkapilbansal (#6613) Fix failing mesheryctl tests @Revolyssup (#6593) [Mesheryctl] View/Delete Configurations @harkiratsm (#6174) Added service mesh Icons in Navigator @Harshit-Dandriyal (#6614) Bump eslint-config-next from 12.3.1 to 13.0.6 in /provider-ui @dependabot (#6620) Fix: console errors on hovering navigator-icons @moki1202 (#6590) Bug fixed position on menu in text field @Udit-takkar (#6550) Bump tar from 6.1.11 to 6.1.12 in /ui @dependabot (#6463) Add no-referrer meta tag to fix 403 google avatars @nishantwrp (#6589) fix: ui-integration tests are unable to start @Abhishek-kumar09 (#6584) [UI] fix: use proptypes to fix type error @Udit-takkar (#6556) Fix: extension crash, while closing RJSF Form abruptly @Abhishek-kumar09 (#6583) Changed icons to SVG on RJSF form @asubedy (#6578) Bump eslint-config-next from 12.3.1 to 13.0.6 in /provider-ui @dependabot (#6620) Bump react-relay and @types/react-relay in /ui @dependabot (#6599) Bump eslint-plugin-react from 7.31.10 to 7.31.11 in /provider-ui @dependabot (#6607) Bump decode-uri-component from 0.2.0 to 0.2.2 in /ui @dependabot (#6617) Bump cypress from 10.11.0 to 11.2.0 in /provider-ui @dependabot (#6605) Bump gonum.org/v1/gonum from 0.11.0 to 0.12.0 @dependabot (#6601) Bump github.com/prometheus/client_golang from 1.13.0 to 1.14.0 @dependabot (#6600) Bump tar from 6.1.11 to 6.1.12 in /ui @dependabot (#6463) Bump golang.org/x/text from 0.3.7 to 0.4.0 @dependabot (#6465) [CI] Only run build workflow on upstream @leecalcote (#6585) fix: ui-integration tests are unable to start @Abhishek-kumar09 (#6584) The search bar is now not colliding with the Navbar from 768px to 995px @UtkarshMishra12 (#6615) Update aks.md @acald-creator (#6588) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Harshit-Dandriyal, @MUzairS15, @Nikhil-Ladha, @Revolyssup, @Udit-takkar, @UtkarshMishra12, @acald-creator, @asubedy, @dependabot, @dependabot[bot], @devkapilbansal, @harkiratsm, @l5io, @leecalcote, @moki1202, @nishantwrp and l5io