cwielenb/CNCF-Dataset huggingface dataset:
Project: Artifact Hub (App Definition and Development / Application Definition & Image Build)
File: backstage_plugins_repositories.md

Backstage plugins repositories are expected to be hosted in GitHub, GitLab or Bitbucket repos. When adding your repository to Artifact Hub, the url used must follow the following format: `https://github.com/user/repo[/path/to/packages]` `https://gitlab.com/user/repo[/path/to/packages]` `https://bitbucket.org/user/repo[/path/to/packages]` By default the `master` branch is used, but it's possible to specify a different one from the UI. Please NOTE that the repository URL used when adding the repository to Artifact Hub must NOT contain the git hosting platform specific parts, like tree/branch, just the path to your packages like it would show in the filesystem. The path/to/packages provided can contain metadata for one or more packages. Each package version must be on a separate folder, and it's up to you to decide if you want to publish one or multiple versions of your package. The structure of a repository with multiple plugins packages and versions could look something like this: ```sh $ tree path/to/packages path/to/packages artifacthub-repo.yml package1 1.0.0 README.md artifacthub-pkg.yml 2.0.0 README.md artifacthub-pkg.yml package2 1.0.0 README.md artifacthub-pkg.yml ``` This structure is flexible, and in some cases it can be greatly simplified. In the case of a single package with a single version available at a time (the publisher doesn't want to make previous ones available, for example), the structure could look like this: ```sh $ tree path/to/packages path/to/packages artifacthub-repo.yml package1 README.md artifacthub-pkg.yml ``` In the previous case, even the `package1` directory could be omitted. The reason is that both packages names and versions are read from the `artifacthub-pkg.yml` metadata file, so directories names are not used at all. Each package version needs an `artifacthub-pkg.yml` metadata file. Please see the file for more details. The repository metadata file shown above can be used to setup features like or . This file must be located at `/path/to/packages`. Once you have added your repository, you are all set up. As you add new versions of your plugins packages or even new packages to your git repository, they'll be automatically indexed and listed in Artifact Hub.
Project: ShardingSphere (App Definition and Development / Database)
File: atomikos.en.md

+++ title = "Atomikos Transaction" weight = 4 +++ Apache ShardingSphere provides XA transactions, and the default XA transaction manager is Atomikos. Configure the transaction type Configure Atomikos Yaml: ```yaml transaction: defaultType: XA providerType: Atomikos ``` Atomikos configuration items can be customized by adding `jta.properties` to the project's classpath. See for more details. `xa_tx.log` is generated in the `logs` directory of the project. This is the log required for recovering XA crash. Do not delete it.
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: setup-ci.md

Dapr uses for continuous integration in order to automate the build and publish processes. As long as you have GitHub Account, you can set up your own private Actions in your fork of the Dapr repo. This document helps you set up the continuous integration for Dapr. GitHub Account Fork the to your GitHub Account Go to `Settings` in the forked repo and click Secrets Add secret variables for Dapr CI `DOCKER_REGISTRY`* : Your private Docker registry name or dockerhub id e.g. `docker.io/[yourdockerhubid]` `DOCKER_REGISTRY_ID`* : Your private Docker registry id `DOCKER_REGISTRY_PASS`* : Your private Docker registry password or Docker Hub password/token `DAPR_BOT_TOKEN`* : Your ; you do not need this unless you want to publish binaries to your forked GitHub release. Go to `Actions` tab Click `I understand my workflows, go ahead and run them` Make sure your Actions is enabled Dapr CI has give different behaviors based on the situations: | | Build binaries | Store binaries into artifact | Publish docker image | GitHub Release | |--|--||-|--| | Create PR against master branch | X | X | | | | Push the commit to master branch | X | X | `dapr:edge` image | | | Push vX.Y.Z-rc.R tag e.g. v0.0.1-rc.0 | X | X | `dapr:vX.Y.Z-rc.R` image | X | | Push vX.Y.Z tag e.g. v0.0.1 | X | X | `dapr:vX.Y.Z` and `dapr:vX.Y.Z:latest` image | X | | Cron schedule ("nightly") | X | X | `dapr:nightly-YYYY-MM-DD` image | |
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.9.md

layout: release date: 2022-09-22 tag: v0.6.9 language: en Change ImagePullPolicy to Always @MUzairS15 (#6234) Clean meshery-operator values.yaml @CyrineG (#6232) Add user facing clean APIs for querying capability registry @Revolyssup (#6050) [UI/Eslint] Enabled important eslint checks + removed all the errors @legendarykamal (#6131) [remote-component] remove MoreVert icon @Abhishek-kumar09 (#6226) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Chadha93, @CyrineG, @MUzairS15, @Revolyssup, @leecalcote and @legendarykamal
Project: YDB (App Definition and Development / Database)
File: rollup_cube_sets.md

The results of calculating the aggregate function as subtotals for the groups and overall totals over individual columns or whole table. Syntax ```sql SELECT c1, c2, -- the columns to group by AGGREGATEFUNCTION(c3) AS outcomec -- an aggregate function (SUM, AVG, MIN, MAX, COUNT) FROM table_name GROUP BY GROUPBYEXTENSION(c1, c2) -- an extension of GROUP BY: ROLLUP, CUBE, or GROUPING SETS ``` `ROLLUP` groups the column values in the order they are listed in the arguments (strictly from left to right), generates subtotals for each group and the overall total. `CUBE` groups the values for every possible combination of columns, generates the subtotals for each group and the overall total. `GROUPING SETS` sets the groups for subtotals. You can combine `ROLLUP`, `CUBE` and `GROUPING SETS`, separating them by commas. The values of columns not used in calculations are replaced with `NULL` in the subtotal. In the overall total, the values of all columns are replaced by `NULL`. `GROUPING`: A function that allows you to distinguish the source `NULL` values from the `NULL` values added while calculating subtotals and overall totals. `GROUPING` returns a bit mask: `0`: If `NULL` is used for the original empty value. `1`: If `NULL` is added for a subtotal or overall total. Example ```sql SELECT column1, column2, column3, CASE GROUPING( column1, column2, column3, ) WHEN 1 THEN "Subtotal: column1 and column2" WHEN 3 THEN "Subtotal: column1" WHEN 4 THEN "Subtotal: column2 and column3" WHEN 6 THEN "Subtotal: column3" WHEN 7 THEN "Grand total" ELSE "Individual group" END AS subtotal, COUNT(*) AS rows_count FROM my_table GROUP BY ROLLUP( column1, column2, column3 ), GROUPING SETS( (column2, column3), (column3) -- if you add here (column2) as well, then together -- the ROLLUP and GROUPING SETS would produce a result -- similar to CUBE ) ; ```
Project: KICS (Provisioning / Security & Compliance)
File: a829b715-cf75-4e92-b645-54c9b739edfb.md

title: Firewall Rule Allows Too Many Hosts To Access Redis Cache hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: a829b715-cf75-4e92-b645-54c9b739edfb Query name: Firewall Rule Allows Too Many Hosts To Access Redis Cache Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: Check if any firewall rule allows too many hosts to access Redis Cache<br> ```tf title="Positive test num. 1 - tf file" hl_lines="5" resource "azurermredisfirewall_rule" "positive1" { name = "someIPrange" rediscachename = azurermrediscache.example.name resourcegroupname = azurermresourcegroup.example.name start_ip = "1.0.0.0" end_ip = "3.0.0.0" } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermredisfirewall_rule" "negative1" { name = "someIPrange" rediscachename = azurermrediscache.example.name resourcegroupname = azurermresourcegroup.example.name start_ip = "1.2.3.4" end_ip = "1.2.3.8" } ```
Project: YugabyteDB (App Definition and Development / Database)
File: replace_tserver.md

title: Replace a failed YB-TServer headerTitle: Replace a failed YB-TServer linkTitle: Replace a failed YB-TServer description: Procedure to replace a failed YB-TServer menu: preview: identifier: replace-failed-tserver parent: troubleshoot-cluster weight: 829 type: docs You can replace a failed YB-TServer in a YugabyteDB cluster, as follows: Install and then start a new YB-TServer, making sure it is in the same placement group as the one you are replacing. For detailed instructions, see . Blacklist the failed YB-TServer by using the following command: ```sh ~/master/bin/yb-admin -masteraddresses $MASTERS changeblacklist ADD $OLD_IP:9100 ``` For details, see in the yb-admin reference page. Wait for the data to drain from the failed YB-TServer and for the data to be loaded into the new one. You can check for the completion of rebalancing by running the following command: ```sh ~/master/bin/yb-admin -masteraddresses $MASTERS getloadmovecompletion ``` Loading and rebalancing will complete only if data from the failed YB-TServer has someplace to be stored. You would need to start the new YB-TServer first, or ensure your remaining YB-TServers have enough capacity and are in the correct placement zones. For details on using this command, see . When the data move is complete (100%), kill the failed YB-TServer by stopping the `yb-tserver` process or terminating the VM. Then wait for the YB-TServer to be marked as `DEAD` by the YB-Master leader. The YB-Master leader will mark the server as `DEAD` after not responding for one minute (based on the `tserverunresponsivetimeout_ms`, with default being `60000`). To verify that the failed YB-TServer is dead, open your web browser to `$MASTERLEADERIP:7000/tablet-servers` and check the output. Because the replacement YB-TServer is running and is loaded with data, remove the address for the failed YB-TServer from the blacklist, as follows: ```sh ~/master/bin/yb-admin -masteraddresses $MASTERS changeblacklist REMOVE $OLD_IP:9100 ```
Project: Docker Compose (App Definition and Development / Application Definition & Image Build)
File: compose_pull.md

<!MARKERGENSTART--> Pull service images | Name | Type | Default | Description | |:-|:|:--|:-| | `--dry-run` | | | Execute command in dry run mode | | `--ignore-buildable` | | | Ignore images that can be built | | `--ignore-pull-failures` | | | Pull what it can and ignores images with pull failures | | `--include-deps` | | | Also pull services declared as dependencies | | `--policy` | `string` | | Apply pull policy ("missing"\|"always") | | `-q`, `--quiet` | | | Pull without printing progress information | <!MARKERGENEND--> Pulls an image associated with a service defined in a `compose.yaml` file, but does not start containers based on those images Consider the following `compose.yaml`: ```yaml services: db: image: postgres web: build: . command: bundle exec rails s -p 3000 -b '0.0.0.0' volumes: .:/myapp ports: "3000:3000" depends_on: db ``` If you run `docker compose pull ServiceName` in the same directory as the `compose.yaml` file that defines the service, Docker pulls the associated image. For example, to call the postgres image configured as the db service in our example, you would run `docker compose pull db`. ```console $ docker compose pull db [+] Running 1/15 db Pulling 12.4s 45b42c59be33 Already exists 0.0s 40adec129f1a Downloading 3.374MB/4.178MB 9.3s b4c431d00c78 Download complete 9.3s 2696974e2815 Download complete 9.3s 564b77596399 Downloading 5.622MB/7.965MB 9.3s 5044045cf6f2 Downloading 216.7kB/391.1kB 9.3s d736e67e6ac3 Waiting 9.3s 390c1c9a5ae4 Waiting 9.3s c0e62f172284 Waiting 9.3s ebcdc659c5bf Waiting 9.3s 29be22cb3acc Waiting 9.3s f63c47038e66 Waiting 9.3s 77a0c198cde5 Waiting 9.3s c8752d5b785c Waiting 9.3s ``` `docker compose pull` tries to pull image for services with a build section. If pull fails, it lets you know this service image must be built. You can skip this by setting `--ignore-buildable` flag.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.8.28.md

RabbitMQ `3.8.28` is a maintenance release. All users are recommended to upgrade to this release. RabbitMQ releases are distributed via , , and . This release and . explains what package repositories and tools can be used to provision modern Erlang versions. See the for general documentation on upgrades and for release notes of other releases. If upgrading from a`3.7.x` release, see upgrade and compatibility notes first. If upgrading from a `3.6.x` or older , first upgrade to and then to this version. Any questions about this release, upgrades or RabbitMQ in general are welcome on the and . Release notes are kept under . Contributors are encouraged to update them together with their changes. This helps with release automation and more consistent release schedule. Inter-node communication listener IP address was hardcoded in the output of `rabbitmq-diagnostics status` and related commands. Contributed by @tomyouyou. GitHub issue: `authoauth2.additionalscopes_key` in `rabbitmq.conf` was not converted correctly during configuration translation and thus had no effect. Contributed by @luos. GitHub issue: Adapt to a breaking Erlang 24.3 LDAP client change. GitHub issue: Shovels now can be declared with `delete-after` parameter set to `0`. Such shovels will immediately stop instead of erroring and failing to start after a node restart. Contributed by @luos. GitHub issue: Support for Consul 1.1 when an operation is attempted on a non-existent health check. Suggested by @maestroes. GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.8.28.tar.xz` instead of the source tarball produced by GitHub.
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.3.0.1.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Major | AliyunOSS: Support multi-thread pre-read to improve sequential read from Hadoop to Aliyun OSS performance* Support multi-thread pre-read in AliyunOSSInputStream to improve the sequential read performance from Hadoop to Aliyun OSS. | Major | Add an option to not disable short-circuit reads on failures* Added an option to not disables short-circuit reads on failures, by setting dfs.domain.socket.disable.interval.seconds to 0. | Major | RBF: Fix doc error setting up client* Fix the document error of setting up HFDS Router Federation | Critical | Change default NameNode RPC port back to 8020* HDFS NameNode default RPC port is changed back to 8020. The only official release that has this differently is 3.0.0, which used 9820. It is recommended for 2.x users to upgrade to 3.0.1+, to reduce the burden on changing default NN RPC port.
Project: Keylime (Provisioning / Security & Compliance)
File: freebsd.md

These instructions were a proof-of-concept for getting keylime to work. These instructions may or may not work, depending on the version of FreeBSD or changes to tpm2-tools. get dependencies `pkg install -y gmake libtool pkgconf wget gcc openssl tpm2-tss tpm2-abrmd` link python and gcc `ln -s /usr/local/bin/gcc /usr/bin/gcc && ln -s /usr/local/bin/python3.7 /usr/bin/python` download swtpm2 from sourceforge ``` wget https://sourceforge.net/projects/ibmswtpm2/files/latest/download -O swtpm.tgz mkdir -p swtpm && tar -xzf swtpm.tgz -C swtpm cd swtpm/src ``` change the syntax for USEBITFIELD_STRUCTURES in TpmBuildSwitches.h (removing default #define) ``` || ((USEBITFIELDSTRUCTURES != NO) && (USEBITFIELDSTRUCTURES != YES)) ``` in BaseTypes.h add this towards the bottom ``` typedef SOCKET int; ``` Now Build ``` make install -c tpmserver /usr/local/bin/tpmserver ``` enable dbus in /etc/rc.conf by adding `dbus_enable="YES"` and then reboot We need to update the tpm2-tools package to be version 4.1. ``` portsnap fetch && portsnap extract cd /usr/ports/security/tpm2-tools/ ``` Update the makefile with version 4.1 `DISTVERSION= 4.1` and remove this line: `BROKEN_SSL= openssl` update the file distinfo with: ```buildoutcfg TIMESTAMP = 1568138495 SHA256 (tpm2-tools-4.1.tar.gz) = 07ce37f552ed47f582fbc3423bc316fea64012ef15a92a25766a36534524dcf2 SIZE (tpm2-tools-4.1.tar.gz) = 779577 ``` Now build and install ``` make make install ``` `pkg install -y git py37-pip py37-pyaml py37-pyzmq py37-tornado py37-cryptography py37-requests py37-sqlite3` clone keylime repo and install ``` git clone keylime python setup.py install ``` ``` tpm_server & tpm2-abrmd --tcti=libtss2-tcti-mssim.so.0:host=127.0.0.1,port=2321 -o ``` Now you should be able to use keylime normally. Note if you're using an emulator, you'll need to set `requireekcert=False` in `/etc/keylime.cconf` On my virtual system, it was very slow, so i had to lengthen the timeouts in `keylime/httpclient_requests.py` ``` keylime_verifier & keylime_registrar & keylime_agent & keylime_tenant -f afile.txt -t 127.0.0.1 ```
Project: KICS (Provisioning / Security & Compliance)
File: ba239cb9-f342-4c20-812d-7b5a2aa6969e.md

title: Non OAuth2 Security Requirement Defining OAuth2 Scopes hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ba239cb9-f342-4c20-812d-7b5a2aa6969e Query name: Non OAuth2 Security Requirement Defining OAuth2 Scopes Platform: OpenAPI Severity: <span style="color:#ff7213">Medium</span> Category: Structure and Semantics URL: If the security scheme is not of type 'oauth2', the array value must be empty<br> ```json title="Positive test num. 1 - json file" hl_lines="33" { "swagger": "2.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } }, "parameters": [ { "name": "limit2", "in": "body", "description": "max records to return", "required": true, "schema": { "type": "object" } } ] } } }, "security": [ { "petstore_auth": [ "write:pets", "read:pets" ] } ], "securityDefinitions": { "petstore_auth": { "type": "basic" } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="21" swagger: "2.0" info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response parameters: name: limit2 in: body description: max records to return required: true schema: type: object security: petstore_auth: write:pets read:pets securityDefinitions: petstore_auth: type: basic ``` ```json title="Negative test num. 1 - json file" { "swagger": "2.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } }, "parameters": [ { "name": "limit2", "in": "body", "description": "max records to return", "required": true, "schema": { "type": "object" } } ] } } }, "security": [ { "petstore_auth": [] } ], "securityDefinitions": { "petstore_auth": { "type": "basic" } } } ``` ```yaml title="Negative test num. 2 - yaml file" swagger: "2.0" info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response parameters: name: limit2 in: body description: max records to return required: true schema: type: object security: petstore_auth: [] securityDefinitions: petstore_auth: type: basic ```
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: digger.md

title: Digger subtitle: GitOps for Terraform labels: layer: cicd category: Infrastructure as Code software: terraform inventors: diggerhq code: https://github.com/diggerhq/digger tutorials: https://docs.digger.dev/readme/introduction https://docs.digger.dev/digger-api/rbac-via-opa-guide https://docs.digger.dev/configuration/using-opa-conftest Digger is an open-source CI/CD orchestrator for Terraform. It provides role-based access control via OPA, and also integrates Conftest to check Terraform plan output against policies.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.64-rc-2.md

layout: release date: 2021-10-08 tag: v0.5.64-rc-2 Migrate from plain manifests to helm charts in mesheryctl @panyuenlau (#4318) [Extension] add remote components for changes @bariqhibat (#4317) index in spanish page had some words still in englosh @alonsolopezr (#4329) [Testing] Integration Test fail resolved @piyushsingariya (#4335) Fix mesheryctl static analysis bugs @navendu-pottekkat (#4330) Bump relay-runtime from 11.0.2 to 12.0.0 in /ui @dependabot (#4298) Fix mesheryctl static analysis bugs @navendu-pottekkat (#4330) Bump relay-runtime from 11.0.2 to 12.0.0 in /ui @dependabot (#4298) Update README.md @helloausrine (#4321) [Tests] Integration Test fix @piyushsingariya (#4336) [Testing] Integration Test fail resolved @piyushsingariya (#4335) Bump google.golang.org/grpc from 1.40.0 to 1.41.0 @dependabot (#4306) use alpine compatible version of jsonschema util @DelusionalOptimist (#4323) Bump billboard.js from 3.1.2 to 3.1.5 in /ui @dependabot (#4295) [error-codes.md] Add anchors for error codes in documentation @awardnasc (#4331) Thank you to our contributors for making this release possible: @DelusionalOptimist, @alonsolopezr, @awardnasc, @bariqhibat, @dependabot, @dependabot[bot], @helloausrine, @leecalcote, @navendu-pottekkat, @panyuenlau, @piyushsingariya, @ramrodo and @utkarsh-pro
Project: YDB (App Definition and Development / Database)
File: disk_end_space.md

When the disk space is used up, the database may start responding to all queries with an error. To keep the database healthy, we recommend deleting a part of the data or adding block store volumes to extend the cluster. Below are instructions that can help you add or free up disk space. When working with the DB, internal VDisk fragmentation is done. You can find out the percentage of fragmentation on the VDisk monitoring page. We do not recommend that you perform defragmentation of VDisks that are fragmented by 20% or less. According to the failure model, the cluster survives the loss of two VDisks in the same group without data loss. If all VDisks in the group are up and there are no VDisks with the error or replication status, then deleting data from one VDisk will result in the VDisk recovering it in a compact format. Please keep in mind that data storage redundancy will be decreased until automatic data replication is complete. During data replication, the load on all the group's VDisks increases, and response times may deteriorate. View the fragmentation coefficient on the VDisk page in the viewer. If its value is more than 20%, defragmentation can help free up VDisk space. Check the status of the group that hosts the VDisk. There should be no VDisks that are unavailable or in the error or replication status in the group. You can view the status of the group in the viewer. Run the wipe command for the VDisk. All data stored on a VDisk will be permanently deleted, whereupon the VDisk will begin restoring the data by reading them from the other VDisks in the group. ```bash ydbd admin blobstorage group reconfigure wipe --domain <Domain number> --node <Node ID> --pdisk <pdisk-id> --vslot <Slot number> ``` You can view the details for the command in the viewer. If the block store volume is running out of space, you can apply defragmentation to the entire block store volume. Check the health of the groups in the cluster. There shouldn't be any problem groups on the same node with the problem block store volume. Log in via SSH to the node hosting this block store volume Check if you can . Stop the process ```bash sudo systemctl stop ydbd ``` Format the block store volume ```bash sudo ydbd admin blobstorage disk obliterate <path to the store volume part label> ``` Run the process ```bash sudo systemctl start ydbd ``` If defragmentation doesn't help free up space on the block store volume, you can individual VDisks.