cwielenb/CNCF-Dataset huggingface dataset:
Project: sso (Provisioning / Key Management)
File: CONTRIBUTING.md

Thank you for your interest in contributing to BuzzFeed's SSO! Help us keep SSO open and inclusive. Please read and follow our . If you've never contributed to a project on Github before, take a look at . Make sure you have a Submit a ticket for your issue, assuming one does not already exist. In that issue: Clearly describe the issue including steps to reproduce when it is a bug Identify specific versions of the binaries and client libraries Fork the repository on GitHub Create a branch from where you want to base your work We typically name branches according to the following format: `helpfulname<issue_number>` Make commits of logical units Make sure your are in a clear and readable format, example: ``` sso: added structured logging use Logrus to add structured logging update logging documentation ... ``` If you want to get SSO up and running, please see our . All bug fixes and new features are expected to include tests, so it's helpful to know how to run them locally while you're developing! Here are the steps to running the tests for SSO: Be sure to set your workspace directory and set your GOPATH Add the sso repo to your gopath: ```sh ln -s path/to/sso $GOPATH/src/github.com/buzzfeed/sso ``` Install gpm and dependencies: ```sh brew install gpm gpm install ``` Run the tests in the root directory ```sh ./scripts/test ``` Push your changes to your branch in your fork of the repository Submit a Comment in the pull request when you're ready for the changes to be reviewed: `"ready for review"` Changes to `buzzfeed/sso` happen via GitHub pull requests, which is where at least one other engineer reviews and approves all code changes. Some tips for pull requests and code review: Each pull request is a branch from `main` there are no other long-lived branches A single pull request is used for each set of changes i.e., once a pull request has been opened, any follow-up commits to address code review and discussion should be pushed to that pull request instead of a new one Before a pull request is merged, it must get a green check mark from our CI for passing tests Before a pull request is merged, the author should take the opportunity to clean up and rewrite the commits on the branch (see . A maintainer will merge your changes once they're approved and ready! Most importantly: Practice !* In order to allow SSO to be the most useful, while balancing feature needs with security concerns, we take an approach, which means: We will do our best to merge every contribution that enables a requested feature or solves an issue that blocks folks using SSO. As we find more efficient, secure, or otherwise stronger solutions, we will deprecate old features and replace them. Our strategy will be to announce deprecation as part of a stable release, and remove functionality as part of the next stable release. While this is a very quick cycle, we believe it is the best approach for keeping SSO up to date and preventing reliance on outdated featuresets.
Project: KICS (Provisioning / Security & Compliance)
File: b86987e1-6397-4619-81d5-8807f2387c79.md

title: Not Using JSON In CMD And ENTRYPOINT Arguments hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b86987e1-6397-4619-81d5-8807f2387c79 Query name: Not Using JSON In CMD And ENTRYPOINT Arguments Platform: Dockerfile Severity: <span style="color:#ff7213">Medium</span> Category: Build Process URL: Ensure that we are using JSON in the CMD and ENTRYPOINT Arguments<br> ```dockerfile title="Positive test num. 1 - dockerfile file" hl_lines="10 11" FROM alpine:3.5 RUN apk add --update py2-pip RUN sudo yum install bundler RUN yum install COPY requirements.txt /usr/src/app/ RUN pip install --no-cache-dir -r /usr/src/app/requirements.txt COPY app.py /usr/src/app/ COPY templates/index.html /usr/src/app/templates/ EXPOSE 5000 CMD [python, /usr/src/app/app.py] ENTRYPOINT [top, -b] ``` ```dockerfile title="Negative test num. 1 - dockerfile file" FROM alpine:3.5 RUN apk add --update py2-pip RUN sudo yum install bundler RUN yum install COPY requirements.txt /usr/src/app/ RUN pip install --no-cache-dir -r /usr/src/app/requirements.txt COPY app.py /usr/src/app/ COPY templates/index.html /usr/src/app/templates/ EXPOSE 5000 CMD ["python", "/usr/src/app/app.py"] ENTRYPOINT ["top", "-b"] ``` ```dockerfile title="Negative test num. 2 - dockerfile file" FROM golang:1.16 AS builder WORKDIR /go/src/github.com/foo/href-counter/ RUN go get -d -v golang.org/x/net/html COPY app.go ./ RUN CGO_ENABLED=0 GOOS=linux go build -a -installsuffix cgo -o app . CMD [python, /usr/src/app/app.py] ENTRYPOINT [top, -b] FROM alpine:latest RUN apk --no-cache add ca-certificates WORKDIR /root/ COPY --from=builder /go/src/github.com/foo/href-counter/app ./ CMD ["./app"] RUN useradd -ms /bin/bash patrick USER patrick ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.26.md

layout: release date: 2021-06-24 tag: v0.5.26 [UI]Update remote-component.config.js @killbotXD (#3249) Partial Bugfix for #3245 ( Kubernetes part ) @anirudhjain75 (#3252) MeshKit errors for Handlers + bug fixes @dhruv0000 (#3263) margins for menu items adjusted @Ayush-Khandelwal-007 (#3261) CRUD for applications @navendu-pottekkat (#3213) Fix for Grafana breaking changes in v7.4 + minor bug fixes @dhruv0000 (#3247) [Meshery] Handle the temp directory creation/deletion for mac OS @hexxdump (#3242) Unit Testing Setup @piyushsingariya (#3137) Updated Jekyll tutorial to Meshery Documentation @debjani1413 (#3116) updated performance docs @NagaHarshita (#3218) [Docs] Fix and cleanup issues in Meshery docs @alphaX86 (#3229) [Roadmap] Adding milestone hyperlinks @leecalcote (#3265) [Docs] Updated contributing docs for better instructions to compile and run meshery server from source @pranav-bhatt (#3236) Thank you to our contributors for making this release possible: @Ayush-Khandelwal-007, @NagaHarshita, @alphaX86, @anirudhjain75, @debjani1413, @dhruv0000, @hexxdump, @killbotXD, @kumarabd, @leecalcote, @navendu-pottekkat, @piyushsingariya and @pranav-bhatt
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.117.md

layout: release date: 2023-08-04 tag: v0.6.117 [Meshmodel] Restructure file system for `meshmodels`. @MUzairS15 (#8372) [helm] revert to "namespace: .Release.Namespaces" @leecalcote (#8382) Add endpoint for all connections @abdullah1308 (#8356) [feat] Add Support for Comments @theBeginner86 (#8315) [chore] Removed OSM @nebula-aac (#8375) [chore] Fix Filter Upload @theBeginner86 (#8370) [chore] Removed OSM @nebula-aac (#8375) Speed dial color update @Shivam-AfA (#8380) [chore] Fix Filter Upload @theBeginner86 (#8370) Downgrade react-dom to 17.0.2 @aabidsofi19 (#8369) [UI] Added new colors in Theme @Yashsharma1911 (#8366) Remove multiple instances of Layer5 and fix indentation of bulleted list @Aritra8438 (#8361) feat: images are aligned now @abhijeetgauravm (#8326) [Docs] Add Integrations List Docs @Boombag0607 (#8373) Thank you to our contributors for making this release possible: @Aritra8438, @Boombag0607, @Chadha93, @MUzairS15, @Shivam-AfA, @Yashsharma1911, @aabidsofi19, @abdullah1308, @abhijeetgauravm, @l5io, @leecalcote, @nebula-aac, @theBeginner86 and l5io
Project: Tarantool (App Definition and Development / Database)
File: feature_request.md

name: Feature request about: Suggest a feature for the project labels: feature, incoming 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. Definition of Done A clear and concise understanding of expectations that the current feature request must meet in order to be released to users.
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.1.1.2.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Major | Port conf servlet to dump running configuration to branch 1.x* Users can use the conf servlet to get the server-side configuration. Users can 1) connect to http\server\url/conf or http\server\url/conf?format=xml and get XML-based configuration description; 2) connect to http\server\url/conf?format=json and get JSON-based configuration description. | Major | TaskTracker's heartbeat is out of control* Fixed a bug in TaskTracker's heartbeat to keep it under control. | Blocker | Deadlock in configuration when writing configuration to hdfs* This fixes a bug where Hive could trigger a deadlock condition in the Hadoop configuration management code. | Major | hadoop 1.1.2. hdfs write bug* someone has discovered this bug and it has been resolved
Project: secureCodeBox (Provisioning / Security & Compliance)
File: 2021-01-27-drop-support-of-k8s-1.16.md

title: Drop Support of k8s 1.16 author: Sven Strittmatter author_title: Core Developer author_url: https://github.com/Weltraumschaf authorimageurl: https://www.gravatar.com/avatar/3fe213284598b5cb69009665902c77a1 tags: secureCodeBox v2 kubernetes description: We no longer support Kubernetes v1.16 in secureCodeBox v2. image: /img/blog/2021-01-27-drop.jpg Photo by on . As we only support the latest four releases of . This means we removed support for 1.16 with the secureCodeBox . If you rely on that particular version of , we may help you with custom paid support. Please contact us via or open an .
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-history.1.md

% podman-history 1 podman\-history - Show the history of an image podman history [options] image[:tag|@digest] podman image history [options] image[:tag|@digest] podman history displays the history of an image by printing out information about each layer used in the image. The information printed out for each layer include Created (time and date), Created By, Size, and Comment. The output can be truncated or not using the --no-trunc flag. If the --human flag is set, the time of creation and size are printed out in a human readable format. The --quiet flag displays the ID of the image only when set and the --format flag is used to print the information using the Go template provided by the user. Alter the output for a format like 'json' or a Go template. Valid placeholders for the Go template are listed below: | Placeholder | Description | ||| | .Comment | Comment for the layer | | .Created | if --human, time elapsed since creation, otherwise time stamp of creation | | .CreatedAt | Time when the image layer was created | | .CreatedBy | Command used to create the layer | | .CreatedSince | Elapsed time since the image layer was created | | .ID | Image ID | | .Size | Size of layer on disk | | .Tags | Image tags | Print usage statement Display sizes and dates in human readable format (default true). Do not truncate the output (default false). Print the numeric IDs only (default false). Show the history of the specified image: ``` $ podman history debian ID CREATED CREATED BY SIZE COMMENT b676ca55e4f2c 9 weeks ago /bin/sh -c #(nop) CMD ["bash"] 0 B <missing> 9 weeks ago /bin/sh -c #(nop) ADD file:ebba725fb97cea4... 45.14 MB ``` Show the history of the specified image without truncating content and using raw data: ``` $ podman history --no-trunc=true --human=false debian ID CREATED CREATED BY SIZE COMMENT b676ca55e4f2c 2017-07-24T16:52:55Z /bin/sh -c #(nop) CMD ["bash"] 0 <missing> 2017-07-24T16:52:54Z /bin/sh -c #(nop) ADD file:ebba725fb97cea4... 45142935 ``` Show the formatted history of the specified image: ``` $ podman history --format "{{.ID}} {{.Created}}" debian b676ca55e4f2c 9 weeks ago <missing> 9 weeks ago ``` Show the history in JSON format for the specified image: ``` $ podman history --format json debian [ { "id": "b676ca55e4f2c0ce53d0636438c5372d3efeb5ae99b676fa5a5d1581bad46060", "created": "2017-07-24T16:52:55.195062314Z", "createdBy": "/bin/sh -c #(nop) CMD [\"bash\"]", "size": 0, "comment": "" }, { "id": "b676ca55e4f2c0ce53d0636438c5372d3efeb5ae99b676fa5a5d1581bad46060", "created": "2017-07-24T16:52:54.898893387Z", "createdBy": "/bin/sh -c #(nop) ADD file:ebba725fb97cea45d0b1b35ccc8144e766fcfc9a78530465c23b0c4674b14042 in / ", "size": 45142935, "comment": "" } ] ``` July 2017, Originally compiled by Urvashi Mohnani <umohnani@redhat.com>
Project: Druid (App Definition and Development / Database)
File: cassandra.md

id: cassandra title: "Apache Cassandra" <!-- ~ 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. --> To use this Apache Druid extension, `druid-cassandra-storage` in the extensions load list. can also be leveraged for deep storage. This requires some additional Druid configuration as well as setting up the necessary schema within a Cassandra keystore.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: calico.md

title: "Calico" icon: /images/logos/powered-by/calico.png hasLink: "https://www.calicolabs.com/" <!-- Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -->
Project: Meshery (Provisioning / Automation & Configuration)
File: consul.md

layout: integration title: Consul subtitle: Collaborative and visual infrastructure as code for Consul image: /assets/img/integrations/consul/icons/color/consul-color.svg permalink: extensibility/integrations/consul docURL: https://docs.meshery.io/extensibility/adapters/consul description: integrations-category: Cloud Native Network integrations-subcategory: Service Mesh registrant: Artifact Hub components: featureList: [ "Visualize the topology of your Consul service mesh deployment", "Analyze Consul Connects configuration", "Explore Consuls Service Splitter" ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: OpenYurt (Provisioning / Automation & Configuration)
File: SECURITY.md

OpenYurt commits to supporting the n-2 version minor version of the current major release; as well as the last minor version of the previous major release. Here's an overview: | Version | Supported | || - | | 1.4.x | :whitecheckmark: | | 1.3.x | :whitecheckmark: | | < 1.3 | :x: | Container images are scanned in every pull request (PR) with to detect new vulnerabilities. OpenYurt maintainers are working to improve our prevention by adding additional measures: Scan code in master/nightly build and PR/master/nightly for Go. Scan published container images on Dockerhub Container Registry. We strive to ship secure software, but we need the community to help us find security breaches. In case of a confirmed breach, reporters will get full credit and can be keep in the loop, if preferred. We ask that all suspected vulnerabilities be privately and responsibly disclosed by . If you know of a publicly disclosed security vulnerability please IMMEDIATELY email the to inform about the vulnerability so they may start the patch, release, and communication process. We do not provide compensations for reporting vulnerabilities except for eternal gratitude. will be used to communicate during the process of identifying, fixing & shipping the mitigation of the vulnerability. The advisory will only be made public when the patched version is released to inform the community of the breach and its potential security impact.
Project: StarRocks (App Definition and Development / Database)
File: ends_with.md

displayed_sidebar: "English" Returns `true` if a string ends with a specified suffix. Otherwise, it returns `false`. If the argument is NULL, the result is NULL. ```Haskell BOOLEAN ENDS_WITH (VARCHAR str, VARCHAR suffix) ``` ```Plain Text MySQL > select ends_with("Hello starrocks", "starrocks"); +--+ | ends_with('Hello starrocks', 'starrocks') | +--+ | 1 | +--+ MySQL > select ends_with("Hello starrocks", "Hello"); +--+ | ends_with('Hello starrocks', 'Hello') | +--+ | 0 | +--+ ``` ENDS_WITH
Project: YugabyteDB (App Definition and Development / Database)
File: yba_storage-config_nfs.md

Manage a YugabyteDB Anywhere NFS storage configuration Manage a NFS storage configuration in YugabyteDB Anywhere ``` yba storage-config nfs [flags] ``` ``` -n, --name string [Optional] The name of the storage configuration for the operation. Required for create, delete, describe, update. -h, --help help for nfs ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage YugabyteDB Anywhere storage configurations - Create an NFS YugabyteDB Anywhere storage configuration - Delete a NFS YugabyteDB Anywhere storage configuration - Describe a NFS YugabyteDB Anywhere storage configuration - List NFS YugabyteDB Anywhere storage-configurations - Update an NFS YugabyteDB Anywhere storage configuration
Project: zot (Provisioning / Container Registry)
File: COMPARISON.md

A comparison between various registries and their capabilities with respect to zot. Please see for various configuration options. | | docker distribution | zot | |||| | Last stable release | v2.7.1 (Jan 17, 2019) | v1.3.0 (Sep 1, 2021) | | License | Apache 2.0 | Apache 2.0 | | On-premise deployment | yes | yes | | Minimal build* | no | yes | | Storage Layout | project-specific layout [1] | ociv1 image layout [2] | | Authentication | auxiliary [3] | built-in | | Authorization | auxiliary [3] | built-in | | Garbage collection | requires server shutdown | inline | | Storage deduplication | none | inline | | Cloud storage support | yes | yes | | Delete by tag | unsupported [4],[5] | yes | | Vulnerability scanning | none | built-in | | cli | yes | yes | | ui | auxiliary [3],[4] | yes [8] | | External contributions | yes | yes | | CNCF project | yes [9] | no | | dist-spec conformance | pending 3.x release | yes [12] | | Image Signatures | auxiliary | \* NOTE: "minimal build" criterion above means the ability to build a minimal distribution-spec compliant registry in order to reduce library dependencies and the possible attack surface. [1] https://github.com/distribution/distribution/tree/main/registry/storage [2] https://github.com/opencontainers/image-spec [3] https://github.com/cesanta/docker_auth [4] https://github.com/distribution/distribution/issues/3234 [5] https://github.com/distribution/distribution/issues/2747 [6] https://github.com/Joxit/docker-registry-ui [7] https://github.com/parabuzzle/craneoperator [8] https://github.com/project-zot/zot-ui [9] https://www.docker.com/blog/donating-docker-distribution-to-the-cncf/ [10] https://github.com/distribution/distribution/issues/3203 [11] https://github.com/opencontainers/oci-conformance/tree/main/distribution-spec#distributiondistribution [12] https://github.com/opencontainers/oci-conformance/tree/main/distribution-spec#project-zotzot [13] https://docs.docker.com/engine/security/trust/ [14] https://github.com/notaryproject/notation [15] https://github.com/sigstore/cosign
Project: YugabyteDB (App Definition and Development / Database)
File: hmget.md

title: HMGET linkTitle: HMGET description: HMGET menu: preview: parent: api-yedis weight: 2160 aliases: /preview/api/redis/hmget /preview/api/yedis/hmget type: docs `HMGET key field [field ...]` This command fetches one or more values for the given fields of the hash that is associated with the given `key`. For every given `field`, (null) is returned if either `key` or `field` does not exist. If `key` is associated with a non-hash data, an error is raised. Returns list of string values of the fields in the same order that was requested. ```sh $ HMSET yugahash area1 "Africa" area2 "America" ``` ``` "OK" ``` ```sh $ HMGET yugahash area1 area2 area_none ``` ``` 1) "Africa" 2) "America" 3) (null) ``` , , , , , , , , , ,
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: support.md

id: support title: Support and community description: Support and Community Details and Links - Get support or discuss the project. - Start here if you want to contribute. - Help shape the technical direction by reviewing Request for Comments issues. - A Backstage Enhancement Proposal (BEP) is a way to propose, communicate and coordinate on new efforts for the Backstage project. - Frequently Asked Questions. - This is how we roll. - Announcements and updates. - Subscribe to our email newsletter. Give us a star - If you are using Backstage or think it is an interesting project, we would love a star! Check out the Backstage.io for the Community Sessions, recordings, and community resources.