cwielenb/CNCF-Dataset huggingface dataset:
Project: ArangoDB (App Definition and Development / Database)
File: exception_ptr_rethrow_result.md

+++ title = "`exceptionptrrethrow<T, EC, void>`" description = "Policy class defining that the ADL discovered free function `rethrowexception()` should be called on incorrect wide value observation. Inherits publicly from `base`. Can only be used with `basicresult`." +++ Note: This policy class specialisation can only be used with `basicresult`, not `basicoutcome`. Use {{% api "exceptionptrrethrow<T, EC, EP>" %}} with `basic_outcome`. Policy class defining that the ADL discovered free function `rethrowexception(impl.assumeerror())` should be called on incorrect wide value observation. Generally this will ADL discover {{% api "std::rethrowexception()" %}} or `boost::rethrowexception()` depending on the `EC` type. Incorrect wide error observation performs: ```c++ BOOSTOUTCOMETHROWEXCEPTION(badresult_access("no error")); ``` Inherits publicly from {{% api "base" %}}, and its narrow value, error and exception observer policies are inherited from there. Requires: Nothing. Namespace: `BOOSTOUTCOMEV2_NAMESPACE::policy` Header: `<boost/outcome/policy/resultexceptionptr_rethrow.hpp>`
Project: Sonobuoy (Provisioning / Security & Compliance)
File: feature_enhancement_request.md

name: Feature enhancement request about: Suggest an idea for this project Describe the solution you'd like [A clear and concise description of what you want to happen.] Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.] Environment: Sonobuoy version: Kubernetes version: (use `kubectl version`): Kubernetes installer & version: Cloud provider or hardware configuration: OS (e.g. from `/etc/os-release`):
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: manage_user_accounts.md

title: Manage user accounts description: How to manage user accounts keywords: [user account] sidebar_position: 1 sidebar_label: Manage user accounts KubeBlocks offers a variety of services to enhance the usability, availability, and observability of database clusters. Different components require user accounts with different permissions to create connections. *Steps* Create a user account ```bash kbcli cluster create-account <clustername> --name <username> --password <pwd> ``` Grant a role to a user ```bash kbcli cluster grant-role <clustername> --name <username> --role <rolename> ``` KubeBlocks provides three role levels of permission. Superuser: with all permissions. ReadWrite: read and write. ReadOnly: read only. For different database engines, the detailed permission are varied. Check the table below. | Role | MySQL | PostgreSQL | Redis | | : | :- | : | :-- | | Superuser | GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, RELOAD, SHUTDOWN, PROCESS, FILE, REFERENCES, INDEX, ALTER, SHOW DATABASES, SUPER, CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE, REPLICATION SLAVE, REPLICATION CLIENT, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE, CREATE USER, EVENT, TRIGGER, CREATE TABLESPACE, CREATE ROLE, DROP ROLE ON * a user | ALTER USER WITH SUPERUSER | +@ALL allkeys| | ReadWrite | GRANT SELECT, INSERT, DELETE ON * TO a user | GRANT pgwriteall_data TO a user | -@ALL +@Write +@READ allkeys | | ReadOnly | GRANT SELECT, SHOW VIEW ON * TO a user | GRANT pgreadall_data TO a user | -@ALL +@READ allkeys | Check role level of a user account ```bash kbcli cluster describe-account <clustername> --name <username> ``` Revoke role from a user account ```bash kbcli cluster revoke-role <clustername> --name <name> --role <rolename> ``` List all user accounts ```bash kbcli cluster list-accounts <clustername> ``` :::note For security reasons, the `list-accounts` command does not show all accounts. Accounts with high privilege such as operational accounts and superuser accounts that meet certain rules are hidden. Refer to the table below to view the hidden accounts. ::: | Database | Hidden Accounts | | : | : | | MySQL | root <br />kb* <br />Localhost = '' | | PostgreSQL | Postgres <br />kb* | Delete a user account ```bash kbcli cluster delete-account <clustername> --name <username> ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_target_https_proxies.md

+++ title = "googlecomputetargethttpsproxies resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputetargethttpsproxies" identifier = "inspec/resources/gcp/googlecomputetargethttpsproxies.md googlecomputetargethttpsproxies resource" parent = "inspec/resources/gcp" +++ A `googlecomputetargethttpsproxies` is used to test a Google TargetHttpsProxy resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputetargethttpsproxies(project: 'chef-gcp-inspec') do its('names') { should include 'inspec-gcp-https-proxy' } its('descriptions') { should include 'A HTTPS target proxy' } end ``` Properties that can be accessed from the `googlecomputetargethttpsproxies` resource: See the resource for more information. `creation_timestamps` : an array of `googlecomputetargethttpsproxy` creation_timestamp `descriptions` : an array of `googlecomputetargethttpsproxy` description `ids` : an array of `googlecomputetargethttpsproxy` id `names` : an array of `googlecomputetargethttpsproxy` name `quic_overrides` : an array of `googlecomputetargethttpsproxy` quic_override `ssl_certificates` : an array of `googlecomputetargethttpsproxy` ssl_certificates `ssl_policies` : an array of `googlecomputetargethttpsproxy` ssl_policy `url_maps` : an array of `googlecomputetargethttpsproxy` url_map This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_data_drop_mongodb.md

title: Kubectl-Dba Data Drop Mongodb menu: docs_{{ .version }}: identifier: kubectl-dba-data-drop-mongodb name: Kubectl-Dba Data Drop Mongodb parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Drop data from mongodb Use this cmd to drop data from a mongodb database. ``` kubectl-dba data drop mongodb [flags] ``` ``` kubectl dba data drop mg -n demo mg-rs ``` ``` -h, --help help for mongodb ``` ``` --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/runner/.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 --default-seccomp-profile-type string Default seccomp profile --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 --password string Password for basic authentication to the API server --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 --username string Username for basic authentication to the API server ``` - Drop data from a database
Project: Paladin Cloud (Provisioning / Security & Compliance)
File: ---bug-report.md

name: "\U0001F41B Bug report" about: Create a bug to help us improve title: "[BUG]" labels: bug assignees: '' <! Verify first that your issue/request is not already reported on GitHub. Also, test on the latest release. --> Spring boot Applications: <!--Which Spring boot application has the issue, pick items below and delete the rest--> Admin Service Auth Service Asset Service Compliance Service Statistics Service Notification Service OS Type: Windows/Linux/MacOS Java version: <!--Pick one below and delete the rest--> 1.9 1.8 1.7 <!--Describe the issue briefly--> <!--steps to reproduce the issue--> <!--What did you expect to happen when running the steps above--> <!--What actually happened-->
Project: ClickHouse (App Definition and Development / Database)
File: v20.12.4.5-stable.md

Backported in : Fix empty `system.stack_trace` table when server is running in daemon mode. (). Backported in : Fix possible segfault in `topK` aggregate function. This closes . (). Backported in : Fix maxdistributedconnections (affects `preferlocalhostreplica=1` and `maxthreads!=maxdistributed_connections`). (). Backported in : Trivial query optimization was producing wrong result if query contains ARRAY JOIN (so query is actually non trivial). (). Backported in : fixes fixes support convert MySQL prefix index for MaterializeMySQL CC: @tavplubix. (). Backported in : Fixed `std::outofrange: basic_string` in S3 URL parsing. (). Backported in : Fix `Unknown setting profile` error on attempt to set settings profile. (). Backported in : fixes fixes fix unique key convert crash in MaterializeMySQL database engine. (). Backported in : Fix key comparison between Enum and Int types. This fixes . (). Backported in : - Fixed issue when `clickhouse-odbc-bridge` process is unreachable by server on machines with dual IPv4/IPv6 stack; - Fixed issue when ODBC dictionary updates are performed using malformed queries and/or cause crashes; Possibly closes . ().
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: suspend.eg.md

The `duration` parameter is supported in KubeVela v1.4 or higher. ```yaml apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: first-vela-workflow namespace: default spec: components: name: express-server type: webservice properties: image: oamdev/hello-world port: 8000 workflow: steps: name: slack-message type: notification properties: slack: url: value: <your-slack-url> message: text: Ready to apply the application, ask the administrator to approve and resume the workflow. name: manual-approval type: suspend name: express-server type: apply-component properties: component: express-server ```
Project: Updatecli (Provisioning / Automation & Configuration)
File: advice.md

<!-- See https://github.com/check-spelling/check-spelling/wiki/Configuration-Examples%3A-advice --> <!-- markdownlint-disable MD033 MD041 --> <details><summary>If the flagged items are :exploding_head: false positives</summary> If items relate to a ... binary file (or some other file you wouldn't want to check at all). Please add a file path to the `excludes.txt` file matching the containing file. File paths are Perl 5 Regular Expressions - you can [test]( https://www.regexplanet.com/advanced/perl/) yours before committing to verify it will match your files. `^` refers to the file's path from the root of the repository, so `^README\.md$` would exclude [README.md]( ../tree/HEAD/README.md) (on whichever branch you're using). well-formed pattern. If you can write a [pattern]( https://github.com/check-spelling/check-spelling/wiki/Configuration-Examples:-patterns ) that would match it, try adding it to the `patterns.txt` file. Patterns are Perl 5 Regular Expressions - you can [test]( https://www.regexplanet.com/advanced/perl/) yours before committing to verify it will match your lines. Note that patterns can't match multiline strings. </details>
Project: external-secrets (Provisioning / Security & Compliance)
File: controller-class.md

NOTE: this feature is experimental and not highly tested Controller classes are a property set during the deployment that allows multiple controllers to work in a group of workload. It works by separating which secretStores are going to be attributed to which controller. For the behavior of a single controller, no extra configuration is needed. In order to deploy the controller with a specific class, install the helm charts specifying the controller class, and create a `SecretStore` with the appropriate `spec.controller` values: ``` helm install custom-external-secrets external-secrets/external-secrets --set controllerClass=custom ``` ``` yaml {% include 'controller-class-store.yaml' %} ``` Now, any `ExternalSecret` bound to this secret store will be evaluated by the operator with the controllerClass custom. Note: Any SecretStore without `spec.controller` set will be considered as valid by any operator, regardless of their respective controllerClasses.
Project: KICS (Provisioning / Security & Compliance)
File: ba766c53-fe71-4bbb-be35-b6803f2ef13e.md

title: ElastiCache Without VPC hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ba766c53-fe71-4bbb-be35-b6803f2ef13e Query name: ElastiCache Without VPC Platform: CloudFormation Severity: <span style="color:#edd57e">Low</span> Category: Networking and Firewall URL: ElastiCache should be launched in a Virtual Private Cloud (VPC)<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4" Resources: ElasticacheCluster: Type: 'AWS::ElastiCache::CacheCluster' Properties: Engine: memcached CacheNodeType: cache.t2.micro NumCacheNodes: '1' ``` ```json title="Positive test num. 2 - json file" hl_lines="5" { "Resources": { "ElasticacheCluster": { "Type": "AWS::ElastiCache::CacheCluster", "Properties": { "CacheNodeType": "cache.m3.medium", "Engine": "memcached", "NumCacheNodes": "1" } } } } ``` ```yaml title="Negative test num. 1 - yaml file" Resources: ElasticacheCluster: Type: 'AWS::ElastiCache::CacheCluster' Properties: Engine: memcached CacheNodeType: cache.t2.micro NumCacheNodes: '1' CacheSubnetGroupName: default ``` ```json title="Negative test num. 2 - json file" { "Resources": { "ElasticacheCluster": { "Type": "AWS::ElastiCache::CacheCluster", "Properties": { "CacheNodeType": "cache.m3.medium", "Engine": "memcached", "NumCacheNodes": "1", "CacheSubnetGroupName": "default" } } } } ```
Project: Scylla (App Definition and Development / Database)
File: timestamp-conflict-resolution.md

The fundamental rule for ordering cells that insert, update, or delete data in a given row and column is that the cell with the highest timestamp wins. However, it is possible that multiple such cells will carry the same `TIMESTAMP`. In this case, conflicts must be resolved in a consistent way by all nodes. Otherwise, if nodes would have picked an arbitrary cell in case of a conflict and they would reach different results, reading from different replicas would detect the inconsistency and trigger read-repair that will generate yet another cell that would still conflict with the existing cells, with no guarantee for convergence. The first tie-breaking rule when two cells have the same write timestamp is that dead cells win over live cells; and if both cells are deleted, the one with the later deletion time prevails. If both cells are alive, their expiration time is examined. Cells that are written with a non-zero TTL (either implicit, as determined by the table's default TTL, or explicit, `USING TTL`) are due to expire TTL seconds after the time they were written (as determined by the coordinator, and rounded to 1 second resolution). That time is the cell's expiration time. When cells expire, they become tombstones, shadowing any data written with a write timestamp less than or equal to the timestamp of the expiring cell. Therefore, cells that have an expiration time win over cells with no expiration time. If both cells have an expiration time, the one with the latest expiration time wins; and if they have the same expiration time (in whole second resolution), their write time is derived from the expiration time less the original time-to-live value and the one that was written at a later time prevails. Finally, if both cells are live and have no expiration, or have the same expiration time and time-to-live, the cell with the lexicographically bigger value prevails. Note that when multiple columns are inserted (`INSERT`) or updated (`UPDATE`) using the same timestamp, selecting (`SELECT`) those columns might return a result that mixes cells from either upsert. This may happen when both upserts have no expiration time, or both their expiration time and TTL are the same, respectively (in whole second resolution). In such a case, cell selection would be based on the cell values in each column, independently of each other.
Project: Cadence Workflow (Provisioning / Automation & Configuration)
File: RELEASES.md

TL;DR: If your Cadence service is running on or above 0.14.0 and you do not have workflows running for more than 6 months. It is safe to upgrade without any operations. If your cluster has open workflows for more than 6 months, please download and run the following CLI command prior to the upgrades. Prior to release 0.16, the workflow state structure contains a field called replication state. Instead, we introduce a new field 'version histories' to manage the replication. In release 0.16, this field 'replication state' has been removed from the code path. From release 0.14, the field 'replication state' has been deprecated. If you are upgrading the service from version below 0.14.0 to 0.16.0 or you may have workflows running for more than 6 months, please consider follow the instruction to see if you have any unsupported workflows. Run the following command based on your database. Cassandra: `cadence admin db unsupported-workflow --dbtype=cassandra --dbaddress <db address> --dbport <port number> --username=<username> --password=<password> --keyspace <keyspace> --lowershardbound=<the start shard id> --uppershardbound=<the end shard id> --rps <scan rps> --outputfilename ./cadence_scan` MySQL/Postgres: `cadence admin db unsupported-workflow --dbtype=<mysql/postgres> --dbaddress <db address> --dbport <port number> --username=<username> --password=<password> --dbname <database name> --lowershardbound=<the start shard id> --uppershardbound=<the end shard id> --rps <scan rps> --outputfilename ./cadencescan` Note: This CLI is a long-running process to scan the database for unsupported workflows. If you have TLS configurations or use customized encoding/decoding type. Please use `cadence adm db unsupported-workflow --help` to configurate the correct connection. After the CLI completes, a list of unsupported workflows will be listed in the file `cadence_scan`. For example: `cadence --address <host>:<port> --domain <ee7316ab-2e42-4f3c-86ee-344a4299791c> workflow reset --wid helloworld7f2fa1fe-594e-44ad-a9e2-7ac7c5f97861 --rid e79ce972-b657-48a4-bba9-e2f2ac6424e2 --resettype LastDecisionCompleted --reason 'release 0.16 upgrade'` Use reset CLI to reset these unsupported workflow. This operation is to migrate these unsupported workflow data. replace the host and port with your cadence host address and port number. replace the domain uuid with the domain name. To find the domain name, you can use `cadence --address <host>:<port> domain describe --domain_id=<domain uuid>`. After replacing the fields with the correct values, you can copy/paste to run the CLI. This is going to reset those workflows to the last decision task completed event. Note: If your workflows has outstanding child workflows, you have to wait for these child workflows completion or terminate the workflows.
Project: StarRocks (App Definition and Development / Database)
File: rtrim.md

displayed_sidebar: "English" Removes the trailing spaces or specified characters from the end (right) of the `str` argument. Removing specified characters are supported from StarRocks 2.5.0. ```Haskell VARCHAR rtrim(VARCHAR str[, VARCHAR characters]); ``` `str`: required, the string to trim, which must evaluate to a VARCHAR value. `characters`: optional, the characters to remove, which must be a VARCHAR value. If this parameter is not specified, spaces are removed from the string by default. If this parameter is set to an empty string, an error is returned. Returns a VARCHAR value. Example 1: Remove the three trailing spaces from the string. ```Plain Text mysql> SELECT rtrim(' ab d '); ++ | rtrim(' ab d ') | ++ | ab d | ++ 1 row in set (0.00 sec) ``` Example 2: Remove specified characters from the end of the string. ```Plain Text MySQL > SELECT rtrim("xxabcdxx", "x"); ++ | rtrim('xxabcdxx', 'x') | ++ | xxabcd | ++ ```
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.3.3.4.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Major | Upgrade okhttp from 2.7.5 to 4.9.3* okhttp has been updated to address CVE-2021-0341 | Major | Upgrade Apache Xerces Java to 2.12.2* Apache Xerces has been updated to 2.12.2 to fix CVE-2022-23437 | Major | remove hadoop-cos as a dependency of hadoop-cloud-storage* We have recently become aware that libraries which include a shaded apache httpclient libraries (hadoop-client-runtime.jar, aws-java-sdk-bundle.jar, gcs-connector-shaded.jar, cos\_api-bundle-5.6.19.jar) all load and use the unshaded resource mozilla/public-suffix-list.txt. If an out of date version of this is found on the classpath first, attempts to negotiate TLS connections may fail with the error "Certificate doesn't match any of the subject alternative names". This release does not declare the hadoop-cos library to be a dependency of the hadoop-cloud-storage POM, so applications depending on that module are no longer exposed to this issue. If an application requires use of the hadoop-cos module, please declare an explicit dependency. | Major | Remove rs-api dependency by downgrading jackson to 2.12.7* Downgrades Jackson from 2.13.2 to 2.12.7 to fix class conflicts in downstream projects. This version of jackson does contain the fix for CVE-2020-36518. | Major | Upgrade Netty to 4.1.77.Final* Netty has been updated to address CVE-2019-20444, CVE-2019-20445 and CVE-2022-24823 | Major | AWS SDK update to 1.12.262 to address jackson CVE-2018-7489* The AWS SDK has been updated to 1.12.262 to address jackson CVE-2018-7489