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

displayed_sidebar: "English" A policy in AWS IAM declares a set of permissions on a specific AWS resource. After creating a policy, you need to attach it to an IAM role or user. As such, the IAM role or user is assigned the permissions declared in the policy to access the specified AWS resource. Different operations in StarRocks require you to have access permissions on different AWS resources, and therefore you need to configure different policies. This topic provides the IAM policies that you need to configure for StarRocks to integrate with different AWS resources in various business scenarios when you choose . If you want to load data from your S3 bucket, configure the following IAM policy: NOTICE Replace `<bucket_name>` in the following JSON policy template with the name of your S3 bucket that stores your data files. ```SQL { "Version": "2012-10-17", "Statement": [ { "Sid": "s3", "Effect": "Allow", "Action": [ "s3:GetObject" ], "Resource": [ "arn:aws:s3:::<bucket_name>/*" ] }, { "Sid": "s3list", "Effect": "Allow", "Action": [ "s3:ListBucket" ], "Resource": [ "arn:aws:s3:::<bucket_name>" ] } ] } ``` If you want to query data from your S3 bucket, configure the following IAM policy: NOTICE Replace `<bucket_name>` in the following JSON policy template with the name of your S3 bucket that stores your data files. ```SQL { "Version": "2012-10-17", "Statement": [ { "Sid": "s3", "Effect": "Allow", "Action": [ "s3:GetObject", "s3:PutObject" ], "Resource": [ "arn:aws:s3:::<bucket_name>/*" ] }, { "Sid": "s3list", "Effect": "Allow", "Action": [ "s3:ListBucket" ], "Resource": [ "arn:aws:s3:::<bucket_name>" ] } ] } ``` If you want to integrate with your AWS Glue Data Catalog, configure the following IAM policy: ```SQL { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "glue:GetDatabase", "glue:GetDatabases", "glue:GetPartition", "glue:GetPartitions", "glue:GetTable", "glue:GetTableVersions", "glue:GetTables", "glue:GetConnection", "glue:GetConnections", "glue:GetDevEndpoint", "glue:GetDevEndpoints", "glue:BatchGetPartition" ], "Resource": [ "*" ] } ] } ```
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.0.20.en.md

Errors returned by rule engine API are formatted in a more human readable way rather than dumping the raw error including the stacktrace. When resources on some nodes in the cluster are still in the 'initializing/connecting' state, the `bridges/` API will crash due to missing Metrics information for those resources. This fix will ignore resources that do not have Metrics information. Fix node information formatter for stopped nodes in the cluster. The bug was introduced by v5.0.18. Fix the problem that the obfuscated password is used when using the `/bridges_probe` API to test the connection in Data-Bridge. Deprecate unused QUIC TLS options. Only following TLS options are kept for the QUIC listeners: cacertfile certfile keyfile verify Fix webhook bridge error handling: connection timeout should be a retriable error. Prior to this fix, connection timeout was classified as unrecoverable error and led to request being dropped. Fix an issue that invalid QUIC listener setting could casue segfault. Fix problem when joining core nodes running different EMQX versions into a cluster. Upgrade HTTP client ehttpc to `0.4.7`. Prior to this upgrade, HTTP clients for authentication, authorization and webhook may crash if `body` is empty but content-type HTTP header is set. For more details see .
Project: Apache RocketMQ (App Definition and Development / Streaming & Messaging)
File: quick_start.md

This document is mainly introduced for how to build and deploy auto failover RocketMQ cluster based on DLedger. For detailed new cluster deployment and old cluster upgrade document, please refer to . Build phase contains two parts, first, build DLedger, then build RocketMQ. ```shell $ git clone https://github.com/openmessaging/dledger.git $ cd dledger $ mvn clean install -DskipTests ``` ```shell $ git clone https://github.com/apache/rocketmq.git $ cd rocketmq $ git checkout -b storewithdledger origin/storewithdledger $ mvn -Prelease-all -DskipTests clean install -U ``` after build successful ```shell $ cd distribution/target/rocketmq-{rocketmq-version}/rocketmq-{rocketmq-version} $ sh bin/dledger/fast-try.sh start ``` if the above commands executed successfully, then check cluster status by using mqadmin operation commands. ```shell $ sh bin/mqadmin clusterList -n 127.0.0.1:9876 ``` If everything goes well, the following content will appear: BID is 0 indicate Master, the others are Follower After startup successful, producer can produce message, and then test failover scenario. Stop cluster fastly, execute the following command: ```shell $ sh bin/dledger/fast-try.sh stop ``` Quick deployment, default configuration is in directory conf/dledger, default storage path is /tmp/rmqstore. After successful deployment, kill Leader process(as the above example, kill process that binds port 30931), about 10 seconds elapses, use clusterList command check cluster's status, Leader switch to another node.
Project: KOTS (App Definition and Development / Application Definition & Image Build)
File: CONTRIBUTING.md

Contributions are definitely welcome! We've published documentation on how to set up a local dev environment (or, least one way to do it!) here: The recommended configuration to build and run kotsadm on a microk8s cluster, locally. Required Software: 1.10.1 or later 2.0 or later Kubernetes (Recommended to run microk8s) Build Kotsadm go binary: ``` GOOS=linux make build ``` Next, you can build and run all server components in the Kubernetes cluster with: ``` skaffold dev ``` To enable delve run: ``` DEBUG_KOTSADM=1 skaffold dev ```
Project: Metal³ (Provisioning / Automation & Configuration)
File: baremetalhost-states.md

The following diagram shows the possible Provisioning State transitions for the BaremetalHost object: Newly created hosts move immediately to Discovered or Registering. No host stays in the Created state while the operator is working properly. An Unmanaged host is missing both the BMC address and credentials secret name, and does not have any information to access the BMC for registration. An Externally Provisioned host was deployed using another tool and then a host object was created with the externallyProvisioned flag set. Hosts in this state are monitored, and only their power status is managed. The host will stay in the Registering state while the BMC access details are being validated. After the host is registered, an agent image will be booted on it using a ramdisk. The agent collects information about the available hardware components, and this process is called "inspection." The host will stay in the Inspecting state until this process is completed. When setting up RAID, BIOS and other similar configurations, the host will be in Preparing state. For ironic provisioner, we build and set up manual clean steps in Preparing state. A host in the Available state is available to be provisioned. In older versions of the baremetal-operator, this state was called Ready. While an image is being copied to the host and it is being configured to run the image the host will be in the Provisioning state. After an image is copied to the host and the host is running the image, it will be in the Provisioned state. When the previously provisioned image is being removed from the host, it will be in the Deprovisioning state. If an error occurs during one of the processing states (Registering, Inspecting, Provisioning, Deprovisioning) the host will enter the Error state. When the host is marked to be deleted, it will move from its current state to Deleting, at which point the resource record is deleted from kubernetes.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.11.1.md

RabbitMQ `3.11.1` is a maintenance release in the `3.11.x` . Please refer to the upgrade section from if upgrading from a version prior to 3.11.0. This release requires Erlang 25. has more details on Erlang version requirements for RabbitMQ. As of 3.11.0, RabbitMQ requires Erlang 25. Nodes will fail to start on older Erlang releases. Erlang 25 as our new baseline means much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation available to all RabbitMQ 3.11 users. Release notes can be found on GitHub at . A rolling upgrade on Kubernetes could hang. GitHub issue: In mixed 3.11/3.10 clusters, channels that performed operations on classic queues could run into an exception. GitHub issue: A quorum queue consumer was cancelled and immediately re-registered while some deliveries were in flight could result in a channel exception. GitHub issue: More strings from external sources are converted to Unicode-aware representation internally, in log messages, CLI tools output and UI, and so on. GitHub issues: During plugin activation on a running node, plugins with dependencies were added to runtime code path in an order that could break if a plugin had hard transitive dependencies (that must be loaded first). Contributed by @gomoripeti. GitHub issue: Support for paths with non-ASCII (Unicode) characters in paths. `rabbitmq-diagnostics observer` now includes a new tab that provides access to internal classic queue metrics. GitHub issue: Replicas of a stream that had a Single Active Consumer on it could run into an exception. GitHub issue: Stream protocol implementation used incorrect keys in `RouteResponse` and `PartitionResponse` frames. GitHub issue: When a superstream (partitioned stream) is added using CLI tools, its primary replica will now be placed according to the `balanced` leader placement strategy. Previously it was using "node local" which resulted in much less even superstream leader replica distribution across cluster nodes. GitHub issue: `rabbitmqctl listamqp10connections` were not listing connections correctly. GitHub issue: Shovel management HTTP API endpoint could run into an exception. Contributed by @gomoripeti. GitHub issue: `cuttlefish` upgraded to To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.1.tar.xz` instead of the source tarball produced by GitHub.
Project: KubeMQ (App Definition and Development / Streaming & Messaging)
File: kubemq_queries.md

Execute Kubemq 'queries' Execute Kubemq 'queries' ``` kubemq queries [flags] ``` ``` kubemq queries send kubemq queries receive kubemq queries attach query ``` ``` -h, --help help for queries ``` - - Queries attach to 'queries' channels command - Queries receive a body from a 'queries' channel - Queries send messages to a 'queries' channel command
Project: YugabyteDB (App Definition and Development / Database)
File: schema-evolution-mgr.md

title: Use Schema Evolution Manager with YugabyteDB YSQL headerTitle: Schema Evolution Manager linkTitle: Schema Evolution Manager description: Use Schema Evolution Manager to work with distributed SQL databases in YugabyteDB. menu: preview_integrations: identifier: schema-evolution-mgr parent: schema-migration weight: 571 type: docs makes it feasible for engineers to contribute schema changes to a PostgreSQL database, managing the schema evolutions as proper source code. Because YugabyteDB's YSQL API is wire-compatible with PostgreSQL, Schema Evolution Manager can connect to YugabyteDB just like with PostgreSQL. Start a YugabyteDB cluster. Refer to . Install Schema Evolution Manager following the instructions from the GitHub repository. To connect to the YugabyteDB database, follow the steps. Replace the connection string that you use to connect to the database for a cluster created with `yugabyted`, as per the following configuration: ```sh sem-init --dir /tmp/sample --url postgresql://yugabyte:yugabyte@ybtserverip:5433/database_name ```
Project: Checkov (Provisioning / Security & Compliance)
File: Migration.md

layout: default published: true title: Migration nav_order: 5 With v3 not only new features were added, but following behaviour changed or was completely removed. Since Bridgecrew standalone edition will be shutting down at the we removed the "level up" flow, which is triggered by just running `checkov` without any flag. If you are still using the old syntax of running your custom code ```python from future import annotations from typing import Any from checkov.common.models.enums import CheckResult from checkov.terraform.checks.resource.baseresourcecheck import BaseResourceCheck class Example(BaseResourceCheck): ... def scanresourceconf(self, conf: dict[str, list[Any]], entity_type: str) -> CheckResult: ... ``` then you can easily use the simplified syntax and still access `entity_type`, if needed ```python from future import annotations from typing import Any from checkov.common.models.enums import CheckResult from checkov.terraform.checks.resource.baseresourcecheck import BaseResourceCheck class Example(BaseResourceCheck): ... def scanresourceconf(self, conf: dict[str, list[Any]]) -> CheckResult: if self.entitytype == 'awsinstance': ... ... ``` For anyone using `checkov` with an API key will now require to set the repo ID via flag. ```shell checkov -d. --bc-api-key xyz --repo-id example/example ``` Following flags were deprecated a while ago and are now completely removed `--no-guide` `--skip-suppressions` `--skip-policy-download` They were combined and replaced by the `--skip-download` flag.
Project: YugabyteDB (App Definition and Development / Database)
File: check-stats.md

title: System statistics linkTitle: System statistics headerTitle: Check system statistics description: How to check system statistics on your YugabyteDB cluster menu: preview: parent: troubleshoot-nodes weight: 30 type: docs There are some system statistics that might help with troubleshooting. To check the CPU, memory, and disk usage on a Linux machine, you can run the following command: ```sh sudo echo -n "CPUs: ";cat /proc/cpuinfo | grep processor | wc -l; echo -n "Mem: ";free -h | grep Mem | tr -s " " | cut -d" " -f 2; echo -n "Disk: "; df -h / | grep -v Filesystem; ``` ```output CPUs: 72 Mem: 251G Disk: /dev/sda2 160G 13G 148G 8% / 10.1.12.104 CPUs: 88 Mem: 251G Disk: /dev/sda2 208G 22G 187G 11% / 10.1.12.105 CPUs: 88 Mem: 251G Disk: /dev/sda2 208G 5.1G 203G 3% / ``` Generally, common tools such as `top` or `iostat` may be useful. If `top` reports high CPU usage for the `auditd` process, it may have rules auditing some system calls frequently used by YugabyteDB which can significantly affect performance. You can try temporarily disabling `audit` by running the following command on each YugabyteDB node: ```sh auditctl -e 0 ``` Then you would check if this improves performance. To re-enable `audit` afterwards, run the following command: ```sh auditctl -e 1 ``` YugabyteDB provides the following web endpoints where the current state of each process is aggregated. This includes logs, flags, as well as memory, disk, and network usage metrics. Additionally, it provides dedicated metrics endpoints for YCQL and YSQL requests: | Description | URL | |-|--| | Master Web Page | `<node-ip>:7000` | | TServer Web Page | `<node-ip>:9000` | | YCQL Metrics | `<node-ip>:12000/metrics` | | YSQL Metrics | `<node-ip>:13000/metrics` | When running `yb-ctl` locally with default values, three local IP addresses are created: `127.0.0.1`, `127.0.0.2`, and `127.0.0.3`, one for each YugabyteDB node.
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_analyze.md

title: "Command - devspace analyze" sidebar_label: devspace analyze Analyzes a kubernetes namespace and checks for potential problems ``` devspace analyze [flags] ``` ``` Analyze checks a namespaces events, replicasets, services and pods for potential problems Example: devspace analyze devspace analyze --namespace=mynamespace ``` ``` -h, --help help for analyze --ignore-pod-restarts If true, analyze will ignore the restart events of running pods --patient If true, analyze will ignore failing pods and events until every deployment, statefulset, replicaset and pods are ready or the timeout is reached --timeout int Timeout until analyze should stop waiting (default 120) --wait Wait for pods to get ready if they are just starting (default true) ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --disable-profile-activation If true will ignore all profile activations --inactivity-timeout int Minutes the current user is inactive (no mouse or keyboard interaction) until DevSpace will exit automatically. 0 to disable. Only supported on windows and mac operating systems (default 180) --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile strings The DevSpace profiles to apply. Multiple profiles are applied in the order they are specified --profile-parent strings One or more profiles that should be applied before the specified profile (e.g. devspace dev --profile-parent=base1 --profile-parent=base2 --profile=my-profile) --profile-refresh If true will pull and re-download profile parent sources --restore-vars If true will restore the variables from kubernetes before loading the config --save-vars If true will save the variables to kubernetes after loading the config --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context DEPRECATED: Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) --vars-secret string The secret to restore/save the variables from/to, if --restore-vars or --save-vars is enabled (default "devspace-vars") ```
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: README.md

Place files in here that you want to add to your Drupal site. You will also need to add them to the extra/file-mapping section in composer.json. As per https://www.drupal.org/docs/develop/using-composer/using-drupals-composer-scaffold e.g. ``` "file-mapping": { "[web-root]/sites/default/all.settings.php": "assets/all.settings.php" }, ``` Settings files are loaded in this order: Loaded by amazeeio/drupal-integrations settings.php settings.lagoon.php For settings and services that should be applied to all environments (dev, prod, staging, docker, etc). all.settings.php all.services.yml For settings and services that should be applied only for the production environment. production.settings.php production.services.yml For settings and services that should be applied only for the development (Lagoon and local) environments. development.settings.php development.services.yml For settings and services only for the local environment, these files will not be committed in Git! settings.local.php services.local.yml
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_backuprepo_describe.md

title: kbcli backuprepo describe Describe a backup repository. ``` kbcli backuprepo describe [flags] ``` ``` kbcli backuprepo describe my-backuprepo ``` ``` -h, --help help for describe ``` ``` --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 ``` - BackupRepo command.
Project: ClickHouse (App Definition and Development / Database)
File: 10_question.md

name: Question about: Ask a question about ClickHouse title: '' labels: question assignees: '' Make sure to check documentation https://clickhouse.com/docs/en/ first. If the question is concise and probably has a short answer, asking it in is probably the fastest way to find the answer. For more complicated questions, consider asking them on StackOverflow with "clickhouse" tag https://stackoverflow.com/questions/tagged/clickhouse If you still prefer GitHub issues, remove all this text and ask your question here.
Project: StarRocks (App Definition and Development / Database)
File: to_tera_timestamp.md

displayed_sidebar: "English" Parses a date or time string according to the specified format and converts the string to a DATETIME value. ```Haskell DATETIME toteratimestamp(VARCHAR str, VARCHAR format) ``` `str`: the time expression to convert. It must be of the VARCHAR type. `format`: the time format specifier for `str`. It is used to parse and convert the input string. `format` must match `string`. Otherwise, NULL is returned. If `format` is invalid, an error is returned. The following table describes the format elements. | Element | Description | | | - | | [ \r \n \t - / , . ;] | Punctuation characters that are ignored in conversion | | dd | Day of month (1 - 31) | | hh | Hour of day (1 - 12) | | hh24 | Hour of day (0 - 23) | | mi | Minute (0 - 59) | | mm | Month (01 - 12) | | ss | Second (0 - 59) | | yyyy | 4-digit year. | | yy | 2-digit year. | | am | Meridian indicator. | | pm | Meridian indicator. | ```SQL select toteratimestamp("1988/04/08","yyyy/mm/dd"); +--+ | toteratimestamp('1988/04/08', 'yyyy/mm/dd') | +--+ | 1988-04-08 00:00:00 | +--+ select toteratimestamp("04-08-1988","mm-dd-yyyy"); +--+ | toteratimestamp('04-08-1988', 'mm-dd-yyyy') | +--+ | 1988-04-08 00:00:00 | +--+ select toteratimestamp("04.1988,08","mm.yyyy,dd"); +--+ | toteratimestamp('04.1988,08', 'mm.yyyy,dd') | +--+ | 1988-04-08 00:00:00 | +--+ select toteratimestamp("1988/04/08 2","yyyy/mm/dd hh"); +-+ | toteratimestamp('1988/04/08 2', 'yyyy/mm/dd hh') | +-+ | 1988-04-08 02:00:00 | +-+ select toteratimestamp("1988/04/08 14","yyyy/mm/dd hh24"); +-+ | toteratimestamp('1988/04/08 14', 'yyyy/mm/dd hh24') | +-+ | 1988-04-08 14:00:00 | +-+ select toteratimestamp("1988/04/08 14:15","yyyy/mm/dd hh24:mi"); +-+ | toteratimestamp('1988/04/08 14:15', 'yyyy/mm/dd hh24:mi') | +-+ | 1988-04-08 14:15:00 | +-+ select toteratimestamp("1988/04/08 2:3:4","yyyy/mm/dd hh24:mi:ss"); +-+ | toteratimestamp('1988/04/08 2:3:4', 'yyyy/mm/dd hh24:mi:ss') | +-+ | 1988-04-08 02:03:04 | +-+ select toteratimestamp("1988/04/08 02 am:3:4","yyyy/mm/dd hh am:mi:ss"); ++ | toteratimestamp('1988/04/08 02 am:3:4', 'yyyy/mm/dd hh am:mi:ss') | ++ | 1988-04-08 02:03:04 | ++ ``` TOTERATIMESTAMP