cwielenb/CNCF-Dataset huggingface dataset:
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_clusterdefinition_list-service-reference.md

title: kbcli clusterdefinition list-service-reference List cluster references declared in a cluster definition. ``` kbcli clusterdefinition list-service-reference [flags] ``` ``` kbcli clusterdefinition list-service-reference apecloud-mysql ``` ``` -h, --help help for list-service-reference ``` ``` --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 ``` - ClusterDefinition command.
Project: Harbor (Provisioning / Container Registry)
File: 7-09-Proj-replication-jobs-log-view.md

Test 7-09 Project replication jobs log view ======= To verify admin user can view replication jobs log. User guide This test requires at least two Harbor instance are running and available. At least one replication job exist. Login source registry UI as admin user. In `Administration->Replications` page, select a replication job and view job log. Repeat steps 1-2 under `Projects->Project_Name->Replication` page. In step2, user can view job log. None
Project: Siddhi (App Definition and Development / Streaming & Messaging)
File: issue_template.md

Description: <!-- Give a brief description of the issue --> Affected Siddhi Version: OS, DB, other environment details and versions: Steps to reproduce: <!-- We would appreciate it if you can provide a testcase :), this help us reproduce the issue much faster --> Related Issues: <!-- Any related issues such as sub tasks, issues reported in other repositories (e.g component repositories), similar problems, etc. -->
Project: ThreatMapper (Provisioning / Security & Compliance)
File: sumo-logic.md

title: Sumo Logic ThreatMapper raises notifications to Sumo Logic using Sumo Logic collectors. Under Manage data, navigate to Collection Click on Add Collector and select Hosted Collector Fill in the details and save the new collector Choose to add Source to the newly created collector and choose HTTP Logs & Metrics Fill in the Source details and click save Paste the URL displayed on to Deepfence Sumo Logic integration page
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.25.md

layout: release date: 2021-06-21 tag: v0.5.25 fixes for nighthawk @kumarabd (#3241) [Docs] Release Notes for Meshery v0.5.25 @l5io (#3067) Thank you to our contributors for making this release possible: @kumarabd, @l5io and @leecalcote
Project: OpenAPI (App Definition and Development / Application Definition & Image Build)
File: 2019-03-15-Alternative-Schema.md

|Tag |Value | |- | - | |Proposal || |Authors|| |Review Manager |TBD | |Status |Draft | |Implementations | |Issues || |Previous Revisions | | .Change Log |Date |Responsible Party |Description | |- | - | - | |2019-03-15 |C. Heazel|Initial Markup Draft | |2019-04-17 |C. Heazel|Re-structured based on Apple Swift| This a proposal to add a new field called ``alternativeSchema`` to the OAS. OpenAPI allows APIs to describe the syntax of their request and response messaged using a JSON Schema-like syntax. However, not all messages will be in JSON. The ability to refer to one or more external schema will allow an API to describe the syntax of a message regardless of the format used. For example: Some XML payloads are defined by an XML schema (the syntax) and a suite of Schematron rules (valid values). JSON Schema cannot effectively represent their content. By providing access to the appropriate appropriate XML Schema and Schematron files, the payload can be validated the way it was intended to be. This proposal makes the following changes to the OAS 3.0 specification: Extend the Schema Object by the addition of the x-oas-draft-alternativeSchema field. Addition of the Alternative Schema Object. Addition of Alternative Schema examples. Addition of a preliminary discussion of the Alternative Schema registry. The OpenAPI Schema Object is extended by the addition of the x-oas-draft-alternativeSchema field. The proposed changes to the OpenAPI specification are provided in The new object, the Alternative Schema Object is added to the OpenAPI specification. The proposed changes to the OpenAPI specification are provided in Examples of the use of the Alternative Schema capability is added to the OpenAPI specification. The proposed changes to the OpenAPI specification are provided in Values used to populate the Alternative Schema Object are required to come from the Alternative Schema Registry. The preliminary Alternative Schema Registry is located at <https://spec.openapis.org/registries/alternative-schema>. Note this is a placeholder registry. Don't take the values seriously. * Initial contents of the registry will include: |Name |Link |Description | | | | | |jsonSchema |TBD |JSON Schema | |xsdSchema |TBD |XML Schema | This proposal makes use of the extensibility features of OpenAPI. All changes sould appear as extensions and handled accordingly. Embedding non-JSON content in the OAS document would have imposed an unacceptable burden on tooling. Therefore, an external link was preferred. Considerable discussion was held over exactly how the links should be represented in the Schema Object. The selected option should support the greatest number of possible combinations of external schema that can be expressed with the OpenAPI schema language.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.114.md

layout: release date: 2023-08-01 tag: v0.6.114 Removed smi section in readme.md file @Modern-artist (#8280) [README] Swap star charts @jamieplu (#8308) add logic to treat some comps special @MUzairS15 (#8306) [Unit test] delete_test in filter package @Philip-21 (#8220) Added instructions to update error codes @abdullah1308 (#8251) Removed system checks before login @EraKin575 (#8297) [bug] Fix K8s Ctx Selector @theBeginner86 (#8314) fix display config on row click in filters @sudhanshutech (#8281) Remove Meshery Adapter for Meshery Octarine entry from adaptersList @supzi-del (#8302) fix display config on row click in filters @sudhanshutech (#8281) [bug] Fix K8s Ctx Selector @theBeginner86 (#8314) feat: Removed "above" from label-commenter-config.yml @abhijeetgauravm (#8317) [Readme] Swap Slack image @jamieplu (#8309) description added using CURL @spacemc2 (#8265) [Docs] Update Relationship Screenshots @Boombag0607 (#8320) updated the video with the new one @Debjyoti0404 (#8322) Thank you to our contributors for making this release possible: @Boombag0607, @Debjyoti0404, @EraKin575, @MUzairS15, @Modern-artist, @Philip-21, @abdullah1308, @abhijeetgauravm, @jamieplu, @l5io, @leecalcote, @spacemc2, @sudhanshutech, @supzi-del, @theBeginner86 and l5io
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-pattern-apply.md

layout: default title: mesheryctl-pattern-apply permalink: reference/mesheryctl/pattern/apply redirect_from: reference/mesheryctl/pattern/apply/ type: reference display-title: "false" language: en command: pattern subcommand: apply Apply pattern file Apply pattern file will trigger deploy of the pattern file <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl pattern apply [flags] </div> </pre> apply a pattern file <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl pattern apply -f [file | URL] </div> </pre> deploy a saved pattern <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl pattern apply [pattern-name] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -f, --file string Path to pattern file -h, --help help for apply --skip-save Skip saving a pattern </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -t, --token string Path to token file default from current context -v, --verbose verbose output </div> </pre> Usage of mesheryctl pattern apply Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: NomsDB (App Definition and Development / Database)
File: README.md

Imports a CSV file as `List<T>` where `T` is a struct with fields corresponding to the CSV's column headers. The struct spec can also be set manually with the `-header` flag. ```shell $ cd csv-import $ go build $ ./csv-import <PATH> http://localhost:8000::foo ``` https://data.cityofnewyork.us/api/views/kku6-nxdu/rows.csv?accessType=DOWNLOAD http://www.opendatacache.com/ Export a dataset in CSV format to stdout with column headers. ```shell $ cd csv-export $ go build $ ./csv-export http://localhost:8000:foo ```
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: configuration.md

id: configuration title: TechDocs Configuration Options description: Reference documentation for configuring TechDocs using app-config.yaml Using the `app-config.yaml` in the Backstage app, you can configure TechDocs using several options. This page serves as a reference to all the available configuration options for TechDocs. ```yaml techdocs: generator: runIn: 'docker' dockerImage: 'spotify/techdocs' pullImage: true mkdocs: omitTechdocsCorePlugin: false legacyCopyReadmeMdToIndexMd: false defaultPlugins: ['techdocs-core'] builder: 'local' publisher: type: 'local' local: publishDirectory: '/path/to/local/directory' googleGcs: bucketName: 'techdocs-storage' bucketRootPath: '/' credentials: $file: '/path/to/googleapplicationcredentials.json' awsS3: bucketName: 'techdocs-storage' bucketRootPath: '/' accountId: ${TECHDOCSAWSS3ACCOUNT_ID} credentials: accessKeyId: ${TECHDOCSAWSS3ACCESSKEYID_CREDENTIAL} secretAccessKey: ${TECHDOCSAWSS3SECRETACCESSKEY_CREDENTIAL} region: ${AWS_REGION} endpoint: ${AWS_ENDPOINT} httpsProxy: ${HTTPS_PROXY} s3ForcePathStyle: false sse: 'aws:kms' # or AES256 azureBlobStorage: containerName: 'techdocs-storage' connectionString: '' credentials: accountName: ${TECHDOCSAZUREBLOBSTORAGEACCOUNT_NAME} accountKey: ${TECHDOCSAZUREBLOBSTORAGEACCOUNT_KEY} legacyUseCaseSensitiveTripletPaths: false cache: ttl: 3600000 readTimeout: 500 ```
Project: StarRocks (App Definition and Development / Database)
File: std.md

displayed_sidebar: "English" Returns the standard deviation of an expression. Since v2.5.10, this function can also be used as a window function. ```Haskell STD(expr) ``` `expr`: the expression. If it is a table column, it must evaluate to TINYINT, SMALLINT, INT, BIGINT, LARGEINT, FLOAT, DOUBLE, or DECIMAL. Returns a DOUBLE value. ```plaintext MySQL > select * from std_test; +++ | col0 | col1 | +++ | 0 | 0 | | 1 | 2 | | 2 | 4 | | 3 | 6 | | 4 | 8 | +++ ``` Calculate the standard deviation of `col0` and `col1`. ```plaintext MySQL > select std(col0) as stdofcol0, std(col1) as stdofcol1 from std_test; +--+--+ | stdofcol0 | stdofcol1 | +--+--+ | 1.4142135623730951 | 2.8284271247461903 | +--+--+ ``` STD
Project: ArangoDB (App Definition and Development / Database)
File: explicit_inplace_exception_constructor_il.md

+++ title = "`explicit basicoutcome(inplacetypet<exceptiontypeifenabled>, std::initializerlist<U>, Args ...)`" description = "Explicit inplace exception constructor. Available if `predicate::enableinplaceexceptionconstructor<std::initializerlist<U>, Args ...>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "explicit-constructors", "inplace-constructors"] weight = 435 +++ Explicit inplace exception constructor. Calls {{% api "void onoutcomeinplaceconstruction(T *, inplacetypet<U>, Args &&...) noexcept" %}} with `this`, `inplacetype<exceptiontype>`, `std::initializer_list<U>` and `Args ...`. Requires: `predicate::enableinplaceexceptionconstructor<std::initializerlist<U>, Args ...>` is true. Complexity: Same as for the `exceptiontype` constructor which accepts `std::initializerlist<U>, Args ...`. Constexpr, triviality and noexcept of underlying operations is propagated. Guarantees: If an exception is thrown during the operation, the state of the Args is left indeterminate.
Project: StarRocks (App Definition and Development / Database)
File: feature-request.md

name: Feature Request about: Suggest an idea for this project labels: 'type/feature-request' <!-- (At least include the following, feel free to add if you have more content) --> Is your feature request related to a problem? Please describe. <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] --> Describe the solution you'd like <!-- A clear and concise description of what you want to happen. --> Describe alternatives you've considered <!-- A clear and concise description of any alternative solutions or features you've considered. --> Additional context <!-- Add any other context or screenshots about the feature request here. -->
Project: Beam (App Definition and Development / Streaming & Messaging)
File: 16_advanced_pipeline_lifecycle.md

Prompt: What is a pipeline development lifecycle in Apache Beam? Response: The Apache Beam pipeline development lifecycle is an iterative process that usually involves the following steps: Design your pipeline. Develop your pipeline code. Test your pipeline. Deploy your pipeline. During each iteration, you might need to go back and forth between the different steps to refine your pipeline code and to fix bugs. To design a pipeline, you need answers to the following questions: Where is the data stored? What does the data look like? What do you want to do with your data? What does your output data look like, and where should it go? Beam documentation has more information about and about common . An Apache Beam program expresses a data processing pipeline, from start to finish. To construct a pipeline using the classes in the Apache Beam SDKs, your program needs to perform the following steps: Create a `Pipeline` object. Use a `Read` or `Create` transform to create one or more `PCollection` objects for your pipeline data. Apply transforms to each `PCollection`. Write or otherwise output the final, transformed `PCollection` objects. Run the pipeline. The Apache Beam documentation has more information about and pipelines. Testing pipelines is a particularly important step in developing an effective data processing solution. The indirect nature of the Beam model, in which your user code constructs a pipeline graph to be executed remotely, can make debugging failed runs difficult. For more information about pipeline testing strategies, see . Choosing a is a crucial step in deploying your pipeline. The runner you choose determines where and how your pipeline executes. For more information about pipeline deployment, see .
Project: Tetragon (Provisioning / Security & Compliance)
File: release_template.md

name: Release a new version of Tetragon about: Create a checklist for an upcoming release title: 'vX.Y.Z release' labels: kind/release assignees: '' [ ] Check that there are no [release blockers]. [ ] Set `RELEASE` environment variable. For example, if you are releasing `v0.8.1`: export RELEASE=v0.8.1 [ ] Open a pull request to update the Helm chart and docs version: git checkout -b pr/prepare-$RELEASE ./contrib/update-helm-chart.sh $RELEASE make -C install/kubernetes git add install/kubernetes/tetragon/ sed -i "s/^version =.*/version = \"${RELEASE}\"/" docs/hugo.toml git add docs/ git commit -s -m "Prepare for $RELEASE release" git push origin HEAD [ ] Once the pull request gets merged, create a tag for the release: git checkout main git pull origin main git tag -a $RELEASE -m "$RELEASE release" -s git push origin $RELEASE If release is `X.Y.0`: [ ] Create `vX.Y` branch. https://github.com/cilium/tetragon/blob/main/.github/renovate.json5 [ ] Create a "Starting `X.Y+1` development" PR on the master branch with the following changes: Update to `X.Y+1.0`. [ ] Once PR is merged, tag the first commit in master which is not in the `X.Y` branch as `vX.Y+1.0-pre.0`. The high level view of the status after this tag is shown in the following figure (RELEASE is `v0.10.0` in this example): ```mermaid gitGraph commit commit tag: "v0.10.0" branch "v0.10" commit commit checkout main commit id: "CRD -> v0.11.0" tag: "v0.11.0-pre.0" commit commit checkout "v0.10" commit commit commit tag: "v0.10.1" ``` [ ] Go to [Image CI Releases workflow] and wait for the release image build to finish. Get approval for your release build workflow from [a Tetragon maintainer] https://quay.io/repository/cilium/tetragon?tab=tags https://quay.io/repository/cilium/tetragon-operator?tab=tags [ ] When a tag is pushed, a GitHub Action job takes care of creating a new GitHub draft release, building artifacts and attaching them to the draft release. Once the draft is available in the [releases page]: [ ] Use the "Auto-generate release notes" button to generate the release notes. [ ] Review the release notes and click on "Publish Release" at the bottom. [ ] Publish Helm chart Follow [cilium/charts RELEASE.md] to publish the Helm chart. Once the pull request is merged and the chart is published, go to [cilium/charts GKE workflow] and wait for the CI run to pass.
Project: Flink (App Definition and Development / Streaming & Messaging)
File: orderby.md

title: "ORDER BY clause" weight: 12 type: docs <!-- 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. --> {{< label Batch >}} {{< label Streaming >}} The `ORDER BY` clause causes the result rows to be sorted according to the specified expression(s). If two rows are equal according to the leftmost expression, they are compared according to the next expression and so on. If they are equal according to all specified expressions, they are returned in an implementation-dependent order. When running in streaming mode, the primary sort order of a table must be ascending on a . All subsequent orders can be freely chosen. But there is no this limitation in batch mode. ```sql SELECT * FROM Orders ORDER BY ordertime, orderid ``` {{< top >}}
Project: KICS (Provisioning / Security & Compliance)
File: 6b2739db-9c49-4db7-b980-7816e0c248c1.md

title: API Gateway Endpoint Config is Not Private hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 6b2739db-9c49-4db7-b980-7816e0c248c1 Query name: API Gateway Endpoint Config is Not Private Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: The API Endpoint type in API Gateway should be set to PRIVATE so it's not exposed to the public internet<br> ```tf title="Positive test num. 1 - tf file" hl_lines="5" resource "awsapigatewayrestapi" "positive1" { name = "regional-example" endpoint_configuration { types = ["REGIONAL"] } } ``` ```tf title="Negative test num. 1 - tf file" resource "awsapigatewayrestapi" "negative1" { name = "regional-example" endpoint_configuration { types = ["PRIVATE"] } } ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: become-a-committer.md

title: "Become A Committer" <!-- 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. --> An Apache Beam takes many forms. There are many actions other than coding that build the trust we place in a committer - code review, design discussion, user support, community outreach, improving infrastructure, documentation, project management, etc. An Apache Beam committer has write access to the repository for merging pull requests, but you dont have to be a code contributor to become a committer. Becoming a committer means that you have the projects trust. Read the for more about being a committer in the Apache Software Foundation. Everyone is welcome to join and contribute to the project in many ways, not only with code contributions. Things like asking questions, reporting bugs, proposing new features, improving documentation or the website, organizing events or writing blog posts, are also welcome and recognized. {{< contributor/listwithicons waysofcontribution >}} {{< contributor/rowoftraits committer_traits >}} The makes someone a committer via nomination, discussion, and then majority vote. We use data from as many sources as possible to inform our reasoning. Here are some examples: - - Git metrics for Code reviews given and received on Clear areas of ownership (a runner, a DSL, IO connector, documentation, etc.) Public events Firsthand PMC testimonials
Project: KICS (Provisioning / Security & Compliance)
File: a0b846e8-815f-4f15-b660-bc4ab9fa1e1a.md

title: Nifcloud RDB Has Public DB Ingress Security Group Rule hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: a0b846e8-815f-4f15-b660-bc4ab9fa1e1a Query name: Nifcloud RDB Has Public DB Ingress Security Group Rule Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Networking and Firewall URL: An db ingress security group rule allows traffic from /0<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "nifclouddbsecurity_group" "positive" { group_name = "example" availability_zone = "east-11" rule { cidr_ip = "0.0.0.0/0" } } ``` ```tf title="Negative test num. 1 - tf file" resource "nifclouddbsecurity_group" "negative" { group_name = "example" availability_zone = "east-11" rule { cidr_ip = "10.0.0.0/16" } } ```