cwielenb/CNCF-Dataset huggingface dataset:
Project: Distribution (Provisioning / Container Registry)
File: gcs.md

description: Explains how to use the Google Cloud Storage drivers keywords: registry, service, driver, images, storage, gcs, google, cloud title: Google Cloud Storage driver An implementation of the `storagedriver.StorageDriver` interface which uses Google Cloud for object storage. | Parameter | Required | Description | |:--|:|:--| | `bucket` | yes | The name of your Google Cloud Storage bucket where you wish to store objects (needs to already be created prior to driver initialization). | | `keyfile` | no | A private service account key file in JSON format used for . | | `rootdirectory` | no | The root directory tree in which all registry files are stored. Defaults to the empty string (bucket root). If a prefix is used, the path `bucketname/<prefix>` has to be pre-created before starting the registry. The prefix is applied to all Google Cloud Storage keys to allow you to segment data in your bucket if necessary.| | `chunksize` | no (default 5242880) | This is the chunk size used for uploading large blobs, must be a multiple of 256*1024. | {{< hint type=note >}} Instead of a key file you can use . To use redirects with default credentials assigned to a virtual machine you have to enable "IAM Service Account Credentials API" and grant `iam.serviceAccounts.signBlob` permission on the used service account. To use redirects with default credentials from Google Cloud CLI, in addition to the permissions mentioned above, you have to . {{< /hint >}}
Project: Rundeck (Provisioning / Automation & Configuration)
File: README.md

To launch the following integration test, make sure to have rundeck launched and listening on port 4440 (default). export vars pointing at correct directories, and specify name of xmlstarlet executable: ```shell export TMP_DIR=/tmp \ export RDECK_BASE=/var/lib/rundeck \ export RDECK_ETC=/etc/rundeck \ export RDECK_PROJECTS=/var/rundeck/projects \ export XMLSTARLET=xmlstarlet \ sh src/test.sh http://localhost:4440 admin admin ``` These tests run against a docker image built from a `<rundeck-oss-package-name>.war` file located in `rundeck/rundeckapp/build/libs/`, make sure it's present before running any of the tests below. Before running any test, export the following variable to prevent scripts from stopping containers after exiting ```shell export DEBUGRDSERVER=true ``` ```shell bash test/run-docker-tests.sh ``` ```shell DOCKERCOMPOSESPEC=docker-compose-ldap-binding-test.yaml bash test/run-docker-ldap-tests.sh ``` ```shell bash test/run-docker-ldap-tests.sh ``` ```shell bash test/run-docker-pam-tests.sh ``` ```shell bash test/run-docker-ssl-tests.sh ``` ```shell bash test/run-docker-tomcat-tests.sh 8-jdk11 ``` ```shell bash test/run-docker-tomcat-tests.sh 9-jdk11 ``` ```shell bash test/run-docker-plugin-blocklist-test.sh ``` ```shell bash test/run-docker-ansible-tests.sh ```
Project: Updatecli (Provisioning / Automation & Configuration)
File: README.md

File | Purpose | Format | Info -|-|-|- | Replacement dictionary (creating this file will override the default dictionary) | one word per line | | Add words to the dictionary | one word per line (only letters and `'`s allowed) | | Remove words from the dictionary (after allow) | grep pattern matching whole dictionary words | | Files to ignore entirely | perl regular expression | | Only check matching files (applied after excludes) | perl regular expression | | Patterns to ignore from checked lines | perl regular expression (order matters, first match wins) | | Patterns that might be worth adding to | perl regular expression with optional comment block introductions (all matches will be suggested) | | Patterns to flag in checked lines | perl regular expression (order matters, first match wins) | | Expected words that aren't in the dictionary | one word per line (sorted, alphabetically) | | Supplement for GitHub comment when unrecognized words are found | GitHub Markdown | Note: you can replace any of these files with a directory by the same name (minus the suffix) and then include multiple files inside that directory (with that suffix) to merge multiple files together.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: azurerm_postgresql_databases.md

+++ title = "azurermpostgresqldatabases resource" draft = false gh_repo = "inspec" platform = "azure" [menu] [menu.inspec] title = "azurermpostgresqldatabases" identifier = "inspec/resources/azure/azurermpostgresqldatabases.md azurermpostgresqldatabases resource" parent = "inspec/resources/azure" +++ {{< inspec/azurermdeprecated resource="azurepostgresql_databases" >}} Use the `azurermpostgresqldatabases` InSpec audit resource to test properties and configuration of Azure PostgreSQL Databases. This resource interacts with version `2017-12-01` of the Azure Management API. For more information see the . At the moment, there doesn't appear to be a way to select the version of the Azure API docs. If you notice a newer version being referenced in the official documentation please open an issue or submit a pull request using the updated version. This resource is available in the `inspec-azure` [resource pack](/inspec/glossary/#resource-pack). To use it, add the following to your `inspec.yml` in your top-level profile: depends: inspec-azure: git: https://github.com/inspec/inspec-azure.git You'll also need to setup your Azure credentials; see the resource pack . This resource first became available in 1.7.0 of the inspec-azure resource pack. An `azurermpostgresqldatabases` resource block returns all Databases on a PostgreSQL Server, within a Resource Group. describe azurermpostgresqldatabases(resourcegroup: ..., servername: ...) do ... end The following examples show how to use this InSpec audit resource. describe azurermpostgresqldatabases(resourcegroup: 'resource-group-1', servername: 'production') do it { should exist } its('names') { should include 'my-database-name' } end `azurepostgresqldatabases` resources are filterable on all available properties. Below are some examples. Filters the results to include only those databases that match the given name. This is a string value. describe azurermpostgresqldatabases(resourcegroup: 'rg', servername: 'server').where{ name.eql?('production-database') } do it { should exist } end `id` `name` `type` `properties` Azure resource ID. SQL Database name, e.g. `my-sql-database`. its('names') { should include 'my-sql-database' } The type of Resource, typically `Microsoft.Sql/servers/databases`. A collection of additional configuration properties related to the PostgreSQL Database. {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The control will pass if the filter returns at least one result. Use `should_not` if you expect zero matches. describe azurermpostgresqldatabases do it { should exist } end Your [Service Principal](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal) must be setup with a `contributor` role on the subscription you wish to test.
Project: FOSSA (Provisioning / Security & Compliance)
File: packagereference.md

Package references, using the `PackageReference` node, manage NuGet dependencies directly within project files (as opposed to a separate `packages.config` file) Walk the directory and find all NuGet project files, i.e. files with the suffix of `.csproj`, `.xproj`, `.vbproj`, `.dbproj`, or `.fsproj`. Parse the XML project files, and collect dependency data from all `PackageReference` tags: ``` <ItemGroup> <!-- ... --> <PackageReference Include="Sitecore.Kernel" Version="12.0.0" /> <!-- ... --> </ItemGroup> ```
Project: Meshery (Provisioning / Automation & Configuration)
File: 10-12-2023-02-03-10_cb01bc62.md

timestamp: "2023-10-12 02:02:41 UTC Thu" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "*name" k8s-distro: minikube k8s-version: "v1.25.2" service-mesh: Consul service-mesh-version: "v1.2.2" tests: consul-client: null consul-server: null overall-status: "failing"
Project: YugabyteDB (App Definition and Development / Database)
File: dcl_drop_user.md

title: DROP USER statement [YSQL] headerTitle: DROP USER linkTitle: DROP USER description: Use the DROP USER statement to drop a user or role. DROP USER is an alias for DROP ROLE. menu: v2.18: identifier: dcldropuser parent: statements type: docs Use the `DROP USER` statement to drop a user or role. `DROP USER` is an alias for and is used to drop a role. {{%ebnf%}} drop_user {{%/ebnf%}} See for more details. Drop a user. ```plpgsql yugabyte=# DROP USER John; ```
Project: ClickHouse (App Definition and Development / Database)
File: jdbc.md

slug: /en/sql-reference/table-functions/jdbc sidebar_position: 100 sidebar_label: jdbc :::note clickhouse-jdbc-bridge contains experimental codes and is no longer supported. It may contain reliability issues and security vulnerabilities. Use it at your own risk. ClickHouse recommend using built-in table functions in ClickHouse which provide a better alternative for ad-hoc querying scenarios (Postgres, MySQL, MongoDB, etc). ::: `jdbc(datasource, schema, table)` - returns table that is connected via JDBC driver. This table function requires separate program to be running. It supports Nullable types (based on DDL of remote table that is queried). Examples ``` sql SELECT * FROM jdbc('jdbc:mysql://localhost:3306/?user=root&password=root', 'schema', 'table') ``` ``` sql SELECT FROM jdbc('mysql://localhost:3306/?user=root&password=root', 'select from schema.table') ``` ``` sql SELECT * FROM jdbc('mysql-dev?p1=233', 'num Int32', 'select toInt32OrZero(''{{p1}}'') as num') ``` ``` sql SELECT * FROM jdbc('mysql-dev?p1=233', 'num Int32', 'select toInt32OrZero(''{{p1}}'') as num') ``` ``` sql SELECT a.datasource AS server1, b.datasource AS server2, b.name AS db FROM jdbc('mysql-dev?datasource_column', 'show databases') a INNER JOIN jdbc('self?datasource_column', 'show databases') b ON a.Database = b.name ```
Project: external-secrets (Provisioning / Security & Compliance)
File: eso-talks.md

A list of talks given by people at conferences and events. Feel free to let us know if you are talking about ESO at some place! We would be happy to mention you here! ](https://www.youtube.com/watch?v=IsoQWxw3Nk4) ](https://www.youtube.com/watch?v=CsJgfHQA0SQ) ](https://www.youtube.com/watch?v=_ZDkHLRYujo) ](https://www.youtube.com/watch?v=TEV13ELPhI8) ](https://www.youtube.com/watch?v=FityN80Cpto) ](https://www.youtube.com/watch?v=7uYqW6TWf8&abchannel=VMwareTanzu) ](https://www.youtube.com/watch?v=upwIlUHkDf8&ab_channel=CNCF%5BCloudNativeComputingFoundation%5D)
Project: OAuth2 Proxy (Provisioning / Key Management)
File: digitalocean.md

id: digitalocean title: DigitalOcean You can fill in the name, homepage, and description however you wish. In the "Application callback URL" field, enter: `https://oauth-proxy/oauth2/callback`, substituting `oauth2-proxy` with the actual hostname that oauth2-proxy is running on. The URL must match oauth2-proxy's configured redirect URL. Note the Client ID and Client Secret. To use the provider, pass the following options: ``` --provider=digitalocean --client-id=<Client ID> --client-secret=<Client Secret> ``` Alternatively, set the equivalent options in the config file. The redirect URL defaults to `https://<requested host header>/oauth2/callback`. If you need to change it, you can use the `--redirect-url` command-line option.
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_core.PreloadRegistrar.md

/ / PreloadRegistrar .PreloadRegistrar `PreloadRegistrar` listen: `CommandListener` . catchall<`T`, `O`\>(`offer`, `handler`, `prio`, `options?`): `void` | Name | Type | | : | :-- | | `T` | extends <`any`\> | | `O` | extends | | Name | Type | | : | :- | | `offer` | `CatchAllOffer` | | `handler` | <`T`, `O`\> | | `prio` | `number` | | `options?` | | `void` . find<`T`, `O`\>(`route`, `fromPlugin?`, `noOverride?`): `Promise`<`Command`<`T`, `O`\>\> | Name | Type | | : | :-- | | `T` | extends <`any`\> | | `O` | extends | | Name | Type | | : | :-- | | `route` | `string` | | `fromPlugin?` | `string` | | `noOverride?` | `boolean` | `Promise`<`Command`<`T`, `O`\>\> . override<`T`, `O`\>(`route`, `fromPlugin`, `handler`, `options?`): `Promise`<`Command`<`T`, `O`\>\> | Name | Type | | : | :-- | | `T` | extends <`any`\> | | `O` | extends | | Name | Type | | :-- | : | | `route` | `string` | | `fromPlugin` | `string` | | `handler` | `CommandOverrideHandler`<`T`, `O`\> | | `options?` | | `Promise`<`Command`<`T`, `O`\>\> . registerBadge<`Resource`\>(`registration`): `void` sidecar badges | Name | Type | | : | :-- | | `Resource` | extends <`void`, `Resource`\> | | Name | Type | | :- | :- | | `registration` | <`Resource`\> | `void` registerBadges<`Resource`\>(...`registrations`): `void` | Name | Type | | : | :-- | | `Resource` | extends <`void`, `Resource`\> | | Name | Type | | :-- | : | | `...registrations` | <`Resource`\>[] | `void` registerMode<`Resource`\>(`registration`): `void` sidecar modes | Name | Type | | : | :-- | | `Resource` | extends <`void`, `Resource`\> | | Name | Type | | :- | :-- | | `registration` | <`Resource`\> | `void` registerModes<`Resource`\>(...`registrations`): `void` | Name | Type | | : | :-- | | `Resource` | extends <`void`, `Resource`\> | | Name | Type | | :-- | :- | | `...registrations` | <`Resource`\>[] | `void` registerSessionInitializer(`init`): `void` session initializers | Name | Type | | :-- | :- | | `init` | `SessionInitializer` | `void` subtree<`T`, `O`\>(`route`, `options`): `Command`<`T`, `O`\> | Name | Type | | : | :-- | | `T` | extends <`any`\> | | `O` | extends | | Name | Type | | :-- | : | | `route` | `string` | | `options` | | `Command`<`T`, `O`\> . subtreeSynonym<`T`, `O`\>(`route`, `masterTree`, `options?`): `void` | Name | Type | | : | :-- | | `T` | extends <`any`\> | | `O` | extends | | Name | Type | | :-- | : | | `route` | `string` | | `masterTree` | `Command`<`T`, `O`\> | | `options?` | | `void` . synonym<`T`, `O`\>(`route`, `handler`, `master`, `options?`): `void` | Name | Type | | : | :-- | | `T` | extends <`any`\> | | `O` | extends | | Name | Type | | : | :- | | `route` | `string` | | `handler` | <`T`, `O`\> | | `master` | `Command`<`T`, `O`\> | | `options?` | | `void` .
Project: BigchainDB (App Definition and Development / Database)
File: run-node-with-docker-compose.md

<! Copyright 2020 Interplanetary Database Association e.V., BigchainDB and IPDB software contributors. SPDX-License-Identifier: (Apache-2.0 AND CC-BY-4.0) Code is Apache-2.0 and docs are CC-BY-4.0 > We grouped all useful commands under a simple `Makefile`. Run a BigchainDB node in the foreground: ```bash $ make run ``` There are also other commands you can execute: `make start`: Run BigchainDB from source and daemonize it (stop it with `make stop`). `make stop`: Stop BigchainDB. `make logs`: Attach to the logs. `make test`: Run all unit and acceptance tests. `make test-unit-watch`: Run all tests and wait. Every time you change code, tests will be run again. `make cov`: Check code coverage and open the result in the browser. `make doc`: Generate HTML documentation and open it in the browser. `make clean`: Remove all build, test, coverage and Python artifacts. `make reset`: Stop and REMOVE all containers. WARNING: you will LOSE all data stored in BigchainDB. The BigchainDB `Makefile` is a wrapper around some `docker-compose` commands we use frequently. If you need a finer granularity to manage the containers, you can still use `docker-compose` directly. This part of the documentation explains how to do that. ```bash $ docker-compose build bigchaindb $ docker-compose up -d bdb ``` The above command will launch all 3 main required services/processes: ``mongodb`` ``tendermint`` ``bigchaindb`` To follow the logs of the ``tendermint`` service: ```bash $ docker-compose logs -f tendermint ``` To follow the logs of the ``bigchaindb`` service: ```bash $ docker-compose logs -f bigchaindb ``` To follow the logs of the ``mongodb`` service: ```bash $ docker-compose logs -f mdb ``` Simple health check: ```bash $ docker-compose up curl-client ``` Post and retrieve a transaction -- copy/paste a driver basic example of a ``CREATE`` transaction: ```bash $ docker-compose -f docker-compose.yml run --rm bdb-driver ipython ``` TODO: A python script to post and retrieve a transaction(s). Run all the tests using: ```bash $ docker-compose run --rm --no-deps bigchaindb pytest -v ``` Run tests from a file: ```bash $ docker-compose run --rm --no-deps bigchaindb pytest /path/to/file -v ``` Run specific tests: ```bash $ docker-compose run --rm --no-deps bigchaindb pytest /path/to/file -k "<test_name>" -v ``` You can also develop and build the BigchainDB docs using ``docker-compose``: ```bash $ docker-compose build bdocs $ docker-compose up -d bdocs ``` The docs will be hosted on port 33333, and can be accessed over , OR http:/HOST_IP:33333.
Project: YDB (App Definition and Development / Database)
File: azure.md

Create an in Azure and top up your account with the amount, sufficient to operate 9 VMs. You can estimate the approximate cost of maintaining infrastructure depending on the region and other circumstances using . Authentication to the Azure Provider for Terraform goes through the CLI: You can download, install, and configure the Azure CLI by following . Log in using the Azure CLI interactively with the `az login` command. The easiest way to create a pair of SSH keys (Linux, macOS) is to use the `ssh-keygen` command. After logging into Azure and generating SSH keys, you need to change the default value of the following variables in the root file `variables.tf`: `auth_location`the name of the region where the infrastructure will be deployed. The command `az account list-locations | grep "displayName"` can obtain a list of available regions depending on the subscription. `sshkeypath` path to the public part of the generated SSH key. Now, being in the `azure` subdirectory, you can run the following sequence of commands to install the provider, initialize modules, and create the infrastructure: `terraform init` installing the provider and initializing modules. `terraform plan` creating a plan for future infrastructure. `terraform init` create resources in the cloud. Next, use the commands `terraform plan`, `terraform init`, and `terraform destroy` (destruction of the created infrastructure) to apply further changes as necessary.
Project: Tarantool (App Definition and Development / Database)
File: template.md

Status*: In progress/Complete/Deprecated Start date*: DD-MM-YYYY Authors*: \<Name and Last name\> @\<Github login\> \<email inside \<\>\>, \<other authors\> Issues*: \, other issues ... When making a copy of the template, prefix the file name with issue number, for example: 2677-box-session-push.md. Short description what, why and how is implemented. A detailed description of why a described thing is needed, who needs it, and a high-level explanation of a subject (proposed feature, optimization or a complex bugfix). The description must be easy-to-understand both for a technical writer and for a developer seeing the subject in a first time. A low-level extremely detailed design of an implementation. It can contain ASCII diagrams, links to a code, mathematics. Here existing alternatives are described, and why they appeared to be worse than an implemented thing.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.0.16-en.md

The `topics/{topic}` API endpoint would return `500 - Internal Error` if a topic had multiple routes. This is fixed by returning a list of routes. Improve error log when bridge in 'sync' mode timed out to get response. Allow `mqtt.idle_timeout` to be set to `infinity` Make sure that the content of an Authorization header that users have specified for a webhook bridge is not printed to log files. Do not resume all buffer workers on successful health check of any individual resource. Previously after any successful healthcheck, all buffer workers (for all resources) were resumed
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.23.9.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Update log4j.appender.EventCounter to use org.apache.hadoop.log.metrics.EventCounter | Minor | nodemanager | Anthony Rojas | Anthony Rojas | | | Improve history server startup performance | Major | jobhistoryserver | Jason Lowe | Karthik Kambatla | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Permission check of symlink deletion incorrectly throws UnresolvedLinkException | Major | namenode | Andrew Wang | Andrew Wang | | | Log aggregation causes a lot of redundant setPermission calls | Major | nodemanager | Kihwal Lee | Jason Lowe | | | metaSave NPEs when there are invalid blocks in repl queue. | Major | namenode | Kihwal Lee | Plamen Jeliazkov | | | SafeModeInfo.isManual() returns true when resources are low even if it wasn't entered into manually | Major | . | Ravi Prakash | Ravi Prakash | | | Namenode doesn't change the number of missing blocks in safemode when DNs rejoin or leave | Critical | . | Ravi Prakash | Ravi Prakash | | | hadoop --config non-existent directory should result in error | Major | scripts | Ashwin Shankar | Ashwin Shankar | | | Shuffling to memory can get out-of-sync when fetching multiple compressed map outputs | Major | . | Nathan Roberts | Nathan Roberts | | | DistCp reports success even on failure. | Critical | distcp | Mithun Radhakrishnan | Mithun Radhakrishnan | | | On Remove Block, Block is not Removed from neededReplications queue | Major | namenode | Tao Luo | Tao Luo | | | -list-attempt-ids is not working | Minor | client | B Anil Kumar | Ashwin Shankar | | | job -list-attempt-ids command does not handle illegal task-state | Major | client | Ashwin Shankar | Ashwin Shankar | | | Non-existent file to "hadoop fs -conf" doesn't throw error | Major | conf | Ashwin Shankar | Ashwin Shankar | | | fsck fails with symlinks | Major | hdfs-client | Andy Isaacson | Jason Lowe | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | fix coverage org.apache.hadoop.mapreduce.v2.app.webapp and org.apache.hadoop.mapreduce.v2.hs.webapp | Major | . | Aleksey Gorshkov | Aleksey Gorshkov | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Coverage fix for org.apache.hadoop.yarn.server.api.\* | Major | . | Aleksey Gorshkov | Aleksey Gorshkov | | | fix coverage org.apache.hadoop.yarn.webapp.log | Major | . | Aleksey Gorshkov | Aleksey Gorshkov |