cwielenb/CNCF-Dataset huggingface dataset:
Project: Salt Project (Provisioning / Automation & Configuration)
File: BUILD_ENVIRONMENT.md

This is intentionally currently not marked executable. There are some hard coded bits, it depends on a binary copy of patchelf, etc. However it does document pretty thoroughly how I initially created a build environment for packaging up esky builds for SmartOS ```bash set -ux export PATH=$PATH:/opt/local/gcc49/bin/ BLDPATH=/tmp/bbfreeze_loader SALTBASE=/data pkgin -y in build-essential salt swig py27-pip unzip py27-mysqldb libsodium mysql-client patchelf pkgin -y rm salt py27-zmq pip install --no-use-wheel --egg esky bbfreeze COMPILE="gcc -fno-strict-aliasing -O2 -pipe -DHAVEDB185_H -I/usr/include -I/opt/local/include -I/opt/local/include/db4 -I/opt/local/include/gettext -I/opt/local/include/ncurses -DNDEBUG -fPIC -I/opt/local/include/python2.7 -static-libgcc" LINK_OPTS="-L/opt/local/lib -L/opt/local/lib/python2.7/config -lsocket -lnsl -ldl -lrt -lm -lssp -static-libgcc" mkdir -p ${BLDPATH} cd ${BLDPATH} curl -kO 'https://pypi.python.org/packages/source/b/bbfreeze-loader/bbfreeze-loader-1.1.0.zip' unzip bbfreeze-loader-1.1.0.zip ${COMPILE} -c bbfreeze-loader-1.1.0/bbfreezeloader/console.c -o ${BLDPATH}/console.o ${COMPILE} -c bbfreeze-loader-1.1.0/bbfreezeloader/getpath.c -o ${BLDPATH}/getpath.o gcc ${BLDPATH}/console.o ${BLDPATH}/getpath.o /opt/local/lib/python2.7/config/libpython2.7.a ${LINK_OPTS} -o ${BLDPATH}/console.exe find /opt/local -name console.exe -exec cp ${BLDPATH}/console.exe {} \; cd ${SALTBASE} git clone git://github.com/saltstack/salt -b 2016.11 cd ${SALTBASE}/salt until pip install --no-use-wheel --egg -r pkg/smartos/esky/zeromq_requirements.txt ; do sleep 1 ; done ; until pip install --no-use-wheel --egg -r pkg/smartos/esky/raet_requirements.txt ; do sleep 1 ; done ; cd ${SALTBASE}/salt python2.7 pkg/smartos/esky/sodiumgrabberinstaller.py install rm -r ${BLDPATH} cd ${SALTBASE}/salt pkg/smartos/esky/build-tarball.sh ```
Project: KICS (Provisioning / Security & Compliance)
File: d0b4d550-c001-46c3-bbdb-d5d75d33f05f.md

title: OSLogin Is Disabled For VM Instance hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: d0b4d550-c001-46c3-bbdb-d5d75d33f05f Query name: OSLogin Is Disabled For VM Instance Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Check if any VM instance disables OSLogin<br> ```tf title="Positive test num. 1 - tf file" hl_lines="30" resource "googlecomputeinstance" "positive1" { name = "test" machine_type = "e2-medium" zone = "us-central1-a" tags = ["foo", "bar"] boot_disk { initialize_params { image = "debian-cloud/debian-9" } } // Local SSD disk scratch_disk { interface = "SCSI" } network_interface { network = "default" access_config { // Ephemeral IP } } metadata = { enable-oslogin = "FALSE" } metadatastartupscript = "echo hi > /test.txt" service_account { scopes = ["userinfo-email", "compute-ro", "storage-ro"] } } ``` ```tf title="Negative test num. 1 - tf file" resource "googlecomputeinstance" "negative1" { name = "test" machine_type = "e2-medium" zone = "us-central1-a" tags = ["foo", "bar"] boot_disk { initialize_params { image = "debian-cloud/debian-9" } } // Local SSD disk scratch_disk { interface = "SCSI" } network_interface { network = "default" access_config { // Ephemeral IP } } metadata = { enable-oslogin = true } metadatastartupscript = "echo hi > /test.txt" service_account { scopes = ["userinfo-email", "compute-ro", "storage-ro"] } } ```
Project: KubeEdge (Provisioning / Automation & Configuration)
File: bug-report.md

name: Bug Report about: Report a bug encountered while operating KubeEdge labels: kind/bug <!-- Please use this template while reporting a bug and provide as much info as possible. Thanks!--> What happened: What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment: Kubernetes version (use `kubectl version`): KubeEdge version(e.g. `cloudcore --version` and `edgecore --version`): <details><summary>Cloud nodes Environment:</summary> Hardware configuration (e.g. `lscpu`): OS (e.g. `cat /etc/os-release`): Kernel (e.g. `uname -a`): Go version (e.g. `go version`): Others: </details> <details><summary>Edge nodes Environment:</summary> edgecore version (e.g. `edgecore --version`): Hardware configuration (e.g. `lscpu`): OS (e.g. `cat /etc/os-release`): Kernel (e.g. `uname -a`): Go version (e.g. `go version`): Others: </details>
Project: EDB (App Definition and Development / Database)
File: image_catalog.md

`ImageCatalog` and `ClusterImageCatalog` are essential resources that empower you to define images for creating a `Cluster`. The key distinction lies in their scope: an `ImageCatalog` is namespaced, while a `ClusterImageCatalog` is cluster-scoped. Both share a common structure, comprising a list of images, each equipped with a `major` field indicating the major version of the image. !!! Warning The operator places trust in the user-defined major version and refrains from conducting any PostgreSQL version detection. It is the user's responsibility to ensure alignment between the declared major version in the catalog and the PostgreSQL image. The `major` field's value must remain unique within a catalog, preventing duplication across images. Distinct catalogs, however, may expose different images under the same `major` value. Example of a Namespaced `ImageCatalog`: ```yaml apiVersion: postgresql.cnpg.io/v1 kind: ImageCatalog metadata: name: postgresql namespace: default spec: images: major: 15 image: ghcr.io/cloudnative-pg/postgresql:15.6 major: 16 image: ghcr.io/cloudnative-pg/postgresql:16.2 ``` Example of a Cluster-Wide Catalog using `ClusterImageCatalog` Resource: ```yaml apiVersion: postgresql.cnpg.io/v1 kind: ClusterImageCatalog metadata: name: postgresql spec: images: major: 15 image: ghcr.io/cloudnative-pg/postgresql:15.6 major: 16 image: ghcr.io/cloudnative-pg/postgresql:16.2 ``` A `Cluster` resource has the flexibility to reference either an `ImageCatalog` or a `ClusterImageCatalog` to precisely specify the desired image. ```yaml apiVersion: postgresql.cnpg.io/v1 kind: Cluster metadata: name: cluster-example spec: instances: 3 imageCatalogRef: apiGroup: postgresql.cnpg.io kind: ImageCatalog name: postgresql major: 16 storage: size: 1Gi ``` Clusters utilizing these catalogs maintain continuous monitoring. Any alterations to the images within a catalog trigger automatic updates for all associated clusters referencing that specific entry. The CloudNativePG project maintains `ClusterImageCatalogs` for the images it provides. These catalogs are regularly updated with the latest images for each major version. By applying the `ClusterImageCatalog.yaml` file from the CloudNativePG project's GitHub repositories, cluster administrators can ensure that their clusters are automatically updated to the latest version within the specified major release. You can install the ( repository) with: ```shell kubectl apply \ -f https://raw.githubusercontent.com/cloudnative-pg/postgres-containers/main/Debian/ClusterImageCatalog.yaml ``` You can install the ( repository) with: ```shell kubectl apply \ -f https://raw.githubusercontent.com/cloudnative-pg/postgis-containers/main/PostGIS/ClusterImageCatalog.yaml ```
Project: YugabyteDB (App Definition and Development / Database)
File: create_view.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="776" height="80" viewbox="0 0 776 80"><path class="connector" d="M0 52h15m67 0h30m37 0h10m74 0h20m-156 0q5 0 5 5v8q0 5 5 5h131q5 0 5-5v-8q0-5 5-5m5 0h10m53 0h10m111 0h30m25 0h30m-5 0q-5 0-5-5v-20q0-5 5-5h20m24 0h20q5 0 5 5v20q0 5-5 5m-5 0h30m25 0h20m-199 0q5 0 5 5v8q0 5 5 5h174q5 0 5-5v-8q0-5 5-5m5 0h10m36 0h10m54 0h15"/><polygon points="0,59 5,52 0,45" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="35" width="67" height="25" rx="7"/><text class="text" x="25" y="52">CREATE</text><rect class="literal" x="112" y="35" width="37" height="25" rx="7"/><text class="text" x="122" y="52">OR</text><rect class="literal" x="159" y="35" width="74" height="25" rx="7"/><text class="text" x="169" y="52">REPLACE</text><rect class="literal" x="263" y="35" width="53" height="25" rx="7"/><text class="text" x="273" y="52">VIEW</text><a xlink:href="../../../syntaxresources/grammardiagrams#qualified-name"><rect class="rule" x="326" y="35" width="111" height="25"/><text class="text" x="336" y="52">qualifiedname</text></a><rect class="literal" x="467" y="35" width="25" height="25" rx="7"/><text class="text" x="477" y="52">(</text><rect class="literal" x="537" y="5" width="24" height="25" rx="7"/><text class="text" x="547" y="22">,</text><a xlink:href="../../../syntaxresources/grammardiagrams#name"><rect class="rule" x="522" y="35" width="54" height="25"/><text class="text" x="532" y="52">name</text></a><rect class="literal" x="606" y="35" width="25" height="25" rx="7"/><text class="text" x="616" y="52">)</text><rect class="literal" x="661" y="35" width="36" height="25" rx="7"/><text class="text" x="671" y="52">AS</text><a xlink:href="../../../syntaxresources/grammar_diagrams#select"><rect class="rule" x="707" y="35" width="54" height="25"/><text class="text" x="717" y="52">select</text></a><polygon points="772,59 776,59 776,45 772,45" style="fill:black;stroke-width:0"/></svg>
Project: KICS (Provisioning / Security & Compliance)
File: 6d173be7-545a-46c6-a81d-2ae52ed1605d.md

title: Tiller (Helm v2) Is Deployed hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 6d173be7-545a-46c6-a81d-2ae52ed1605d Query name: Tiller (Helm v2) Is Deployed Platform: Kubernetes Severity: <span style="color:#bb2124">High</span> Category: Insecure Configurations URL: Check if Tiller is deployed.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="8 10 20 15" apiVersion: extensions/v1beta1 kind: Deployment metadata: labels: app: helm name: tiller name: tiller-deploy spec: containers: image: tiller-image name: tiller-v1 template: metadata: labels: app: helm name: tiller spec: containers: args: "--listen=10.7.2.8:44134" image: tiller-image name: tiller-v2 ports: containerPort: 44134 name: tiller protocol: TCP containerPort: 44135 name: http protocol: TCP serviceAccountName: tiller ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: security-context-demo spec: securityContext: runAsUser: 1000 runAsGroup: 3000 fsGroup: 2000 volumes: name: sec-ctx-vol containers: name: sec-ctx-demo image: busybox command: [ "sh", "-c", "sleep 1h" ] volumeMounts: name: sec-ctx-vol mountPath: /data/demo securityContext: allowPrivilegeEscalation: false ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: developmentplan.md

Integration into Kubernetes and potentially other tools. The biggest requirement for this is to be able run Buildah within a standard linux container without SYS_ADMIN privileges. This would allow Buildah to run non-privileged containers inside of Kubernetes, so you could distribute your container workloads. Integration with User Namespace, Podman has this already and the goal is to get `buildah build` and `buildah run` to be able to run its containers in a usernamespace to give the builder better security isolation from the host. Buildah `buildah build` command's goal is to have feature parity with other OCI image and container build systems. Addressing issues from the community as reported in the page.
Project: Meshery (Provisioning / Automation & Configuration)
File: karmada.md

layout: integration title: Karmada subtitle: Collaborative and visual infrastructure as code for Karmada image: /assets/img/integrations/karmada/icons/color/karmada-color.svg permalink: extensibility/integrations/karmada docURL: https://docs.meshery.io/extensibility/integrations/karmada description: integrations-category: Orchestration & Management integrations-subcategory: Scheduling & Orchestration registrant: Artifact Hub components: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs.Deploy workloads: When deploying workloads, you can request that scheduling constraints be met to direct which nodes Karpenter provisions for those workloads. " language: en list: include type: extensibility category: integrations
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: plugins.md

Simply, any GitHub repository that contains a `package.json` file (the plugin entry file) can be installed as a plugin if the entry file follows the structure of a Monokle Desktop plugin. Monokle Desktop uses the following properties: `name`, `author`, `version` `repository`, `description`, and `monoklePlugin`. The `monoklePlugin` property should be an object containing an array named `modules`. Heres an example of a `package.json` for a Monokle Desktop plugin: ```json { "name": "My first plugin", "description": "Hello world!", "version": "1.0.0", "author": "Kubeshop", "repository": "https://github.com/kubeshop/monokle-default-templates-plugin", "monoklePlugin": { "modules": [] } } ``` With the release of 1.5.0 we are only supporting Template modules. More module types will be added in future versions. Each plugin may have multiple modules. Here is how you can reference a template module: ```json "monoklePlugin": { "modules": [ { "type": "template", "path": "<relative-path-to-template-folder>" } ] } ``` Open the Plugins manager from the top right icon: Click on the + Install button: A modal will appear asking for the Plugin URL: The URL must be a valid GitHub repository url in the format https://github.com/[user]/[repository]. The primary branch should be `main`. The plugin installer will search there for the `package.json` file. This should be used only as a workaround for developing plugins. On Mac: Copy your plugin folder to `/Users/<YourUser>/Libray/Application Support/monokle/monoklePlugins`. Reopen or reload Monokle Desktop (from Window -> Reload). On Windows: Copy your plugin folder to `C:\Users\<YourUser>\AppData\Roaming\monokle\monoklePlugins`. Reopen or reload Monokle Desktop (from Window -> Reload).
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_cluster_start.md

title: kbcli cluster start Start the cluster if cluster is stopped. ``` kbcli cluster start NAME [flags] ``` ``` kbcli cluster start mycluster ``` ``` --dry-run string[="unchanged"] Must be "client", or "server". If with client strategy, only print the object that would be sent, and no data is actually sent. If with server strategy, submit the server-side request, but no data is persistent. (default "none") -h, --help help for start --name string OpsRequest name. if not specified, it will be randomly generated -o, --output format Prints the output in the specified format. Allowed values: JSON and YAML (default yaml) --ttlSecondsAfterSucceed int Time to live after the OpsRequest succeed ``` ``` --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 ``` - Cluster command.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.2-rc-2.md

layout: release date: 2023-12-15 tag: v0.7.2-rc-2 [UI] Connection to Environments Mapping @theBeginner86 (#9632) update cred def to handle oneOF properly @MUzairS15 (#9631) [Draft] v0.8.0 Roadmap @leecalcote (#9146) add grafana to config @MUzairS15 (#9628) fix: #9399 Changed hovering effect @Raj100679 (#9444) [ui] Add react markdown @aabidsofi19 (#9640) Fix: Added Responsive Style for Dashboard charts. Signed-off-by Danan @Dananjay996 (#9622) [Spaces] Finalize support for Environments @theBeginner86 (#9618) [chore] Fix Environment Payload @theBeginner86 (#9636) [chore] Fix Environment Payload @theBeginner86 (#9636) [DOCS] : removed extra full stop @AdarshRawat1 (#9634) Docs: Update functional categories @leecalcote (#9633) [Spaces] Finalize support for Environments @theBeginner86 (#9618) Access slides and resources link updated @abhijeetgauravm (#9624) Thank you to our contributors for making this release possible: @AdarshRawat1, @Dananjay996, @MUzairS15, @Raj100679, @Yashsharma1911, @aabidsofi19, @abhijeetgauravm, @l5io, @leecalcote, @theBeginner86 and l5io
Project: Beam (App Definition and Development / Streaming & Messaging)
File: beam-2.42.0.md

title: "Apache Beam 2.42.0" date: 2022-10-17 9:00:00 -0700 categories: blog release authors: lostluck <!-- 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. --> We are happy to present the new 2.42.0 release of Beam. This release includes both improvements and new functionality. See the for this release. <!--more--> For more information on changes in 2.42.0, check out the . Added support for stateful DoFns to the Go SDK. Added support for [Batched DoFns](/documentation/programming-guide/#batched-dofns) to the Python SDK. Added support for Zstd compression to the Python SDK. Added support for Google Cloud Profiler to the Go SDK. Added support for stateful DoFns to the Go SDK. The Go SDK's Row Coder now uses a different single-precision float encoding for float32 types to match Java's behavior (). Fixed Python cross-language JDBC IO Connector cannot read or write rows containing Timestamp type values . Go SDK doesn't yet support Slowly Changing Side Input pattern () See a full list of open this version. According to git shortlog, the following people contributed to the 2.42.0 release. Thank you to all contributors! Abirdcfly Ahmed Abualsaud Alexander Zhuravlev Alexey Inkin Alexey Romanenko Anand Inguva Andrej Galad Andrew Pilloud Andy Ye Balzs Nmeth Brian Hulette Bruno Volpato bulat safiullin bullet03 Chamikara Jayalath ChangyuLi28 Clment Guillaume Damon Danny McCormick Darkhan Nausharipov David Huntsperger dpcollins-google Evgeny Antyshev grufino Heejong Lee Ismal Meja Jack McCluskey johnjcasey Jonathan Shen Kenneth Knowles Ke Wu Kiley Sok Liam Miller-Cushon liferoad Lucas Nogueira Luke Cwik MakarkinSAkvelon Manit Gupta masahitojp Michael Hu Michel Davit Moritz Mack Naireen Hussain nancyxu123 Nikhil Nadig oborysevych Pablo Estrada Pranav Bhandari Rajat Bhatta Rebecca Szper Reuven Lax Ritesh Ghorse Robert Bradshaw Robert Burke Ryan Thompson Sam Whittle Sergey Pronin Shivam Shunsuke Otani Shunya Ueta Steven Niemitz Stuart Svetak Sundhar Valentyn Tymofieiev Vitaly Terentyev Vlad Vladislav Chunikhin Yichi Zhang Yi Hu Yixiao Shen
Project: kiosk (Provisioning / Automation & Configuration)
File: MAINTAINERS.md

This page lists all active maintainers of this repository. If you were a maintainer and would like to add your name to the Emeritus list, please send us a PR. See for governance guidelines and how to become a maintainer. See for general contribution guidelines. , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC
Project: ArangoDB (App Definition and Development / Database)
File: has_failure.md

+++ title = "`bool has_failure() const noexcept`" description = "Returns true if there is either an error or an exception. Constexpr, never throws." categories = ["observers"] weight = 595 +++ Returns true if there is either an error or an exception. Constexpr where possible. Requires: Always available. Complexity: Constant time. Guarantees: Never throws an exception.