cwielenb/CNCF-Dataset huggingface dataset:
Project: YugabyteDB (App Definition and Development / Database)
File: array-to-json.md

title: arraytojson() [JSON] headerTitle: arraytojson() linkTitle: arraytojson() summary: arraytojson() description: Create a JSON array from a SQL array using the arraytojson() function. menu: v2.18: identifier: array-to-json parent: json-functions-operators weight: 53 type: docs Purpose: Create a JSON array from a SQL array. Signature: ``` input value: anyarray pretty: boolean (optional) return value: json ``` Notes: This has only a `json` variant. The first (mandatory) formal parameter is any SQL array whose elements might be compound values. The second formal parameter is optional. When it is true, line feeds are added between dimension-1 elements. ```plpgsql do $body$ declare sql_array constant text[] := array['a', 'b', 'c']; jfalse constant json := arraytojson(sqlarray, false); jtrue constant json := arraytojson(sqlarray, true); expectedjfalse constant json := '["a","b","c"]'; expectedjtrue constant json := '["a", "b", "c"]'; begin assert (jfalse::text = expectedj_false::text) and (jtrue::text = expectedj_true::text), 'unexpected'; end; $body$; ``` The `arraytojson()` function has no practical advantage over or and is restricted because it explicitly handles a SQL array and cannot handle a SQL `record` (at top level). Moreover, it can produce only a JSON array whose values all have the same data type. If you want to pretty-print the text representation of the result JSON value, you can use the `::text` typecast or .
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_remote-config_postgres.md

title: Kubectl-Dba Remote-Config Postgres menu: docs_{{ .version }}: identifier: kubectl-dba-remote-config-postgres name: Kubectl-Dba Remote-Config Postgres parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference generate appbinding , secrets for remote replica generate appbinding , secrets for remote replica ``` kubectl-dba remote-config postgres [flags] ``` ``` kubectl dba remote-config mysql -n <ns> -u <username> -p$<password> -d<dnsname> <db_name> kubectl dba remote-config mysql -n <ns> -u <username> -p$<password> -d<dnsname> <db_name> ``` ``` -d, --dns string dns name for the remote replica (default "localhost") -h, --help help for postgres -n, --namespace string host namespace for the remote replica (default "default") -p, --pass string password name for the remote replica (default "password") -u, --user string user name for the remote replica (default "postgres") -y, --yes permission for alter password for the remote replica ``` ``` --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 --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 --username string Username for basic authentication to the API server ``` - generate appbinding , secrets for remote replica
Project: SPIFFE (Provisioning / Key Management)
File: BRIAN_MARTIN.md

I've been working with SPIFFE (and SPIRE) for three years, beginning with a demonstration of "cloudless" computing on zero trust networks at HPE. I have engaged with SPIFFE SIG-SPEC, driving changes to ease adoption and application of SVIDs for workloads. I also contributed to work on refactoring the SPIRE datastore, and delivering a working design prototype for adding Key Value store support. I use SPIFFE and SPIRE on an ARM cluster in a mobile datacenter. As SPIFFE crosses the tipping point into broader adoption, I hope to help steward it through increasing visibility and reducing friction. I'm excited to bring my passion for simplifying IT, and security in particular, to the SPIFFE Steering Committee. Having worked with Kubernetes since 2016, I feel the applicability of SPIFFE across networks, service meshes, and applications. I have previous experience with technical leadership roles at HPE, Plexxi, VMWare, Virsto and EMC. GitHub Handle: @bri365 Email Address: bri365@gmail.com LinkedIn Profile: https://www.linkedin.com/in/mrbrianjmartin/ Current Affiliation: Gradient Technologies
Project: Harbor (Provisioning / Container Registry)
File: 4-03-DB-admin-view-logs.md

Test 4-03 - Admin Views Logs (DB Mode) ======= To verify that an admin user can views logs when users are managed locally by Harbor (DB mode). User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against a local database. ( auth_mode is set to db_auth* .) The user data is stored in a local database. A linux host with Docker CLI installed (Docker client). On a Docker client host, use `docker login <harbor_host>` command to log in as a non-admin user. Run some `docker push` and `docker pull` commands to push images to the registry and pull from the registry. Log in to the UI as the non-admin user. Delete a few images from the project. Log out non-admin user and log in to the UI as the admin user. View the logs of the project of the non-admin user. Try below search criteria to see if the search result is correct: push only pull only pull and push delete only all push and delete different date ranges date range and push All operations of non-admin users in Step 2 & 4 should be logged. Logs can be viewed in Step 6, check if the time and operations are correct. Logs can be filtered in Step 7. None
Project: Beam (App Definition and Development / Streaming & Messaging)
File: Wizeline.md

title: "Wizeline" icon: /images/logos/powered-by/Wizeline.png hasLink: "https://www.youtube.com/watch?v=xoQRDzqdODk&list=PL4dEBWmGSIU9OkXQU2OAXmITPLhiMSPRp&index=40" <!-- Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -->
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.0.19.en.md

When the resource manager is busy trying to establish a connection with the remote, the resource might yet lack any metrics information. Prior to this fix, the `bridges/` API handler crashed in such circumstances. Fix Swagger API doc rendering crash. In version 5.0.18, a bug was introduced that resulted in duplicated field names in the configuration schema. This, in turn, caused the Swagger schema generated to become invalid. For influxdb bridge, added integer value placeholder annotation hint to `write_syntax` documentation. Also supported setting a constant value for the `timestamp` field. Improve behavior of the `replicant` nodes when the `core` cluster becomes partitioned (for example when a core node leaves the cluster). Previously, the replicant nodes were unable to rebalance connections to the core nodes, until the core cluster became whole again. This was indicated by the error messages: `[error] line: 182, mfa: mrialb:listcorenodes/1, msg: mrialbcorediscovery divergent cluster`. Fixed two bugs introduced in v5.0.18. The environment varialbe `SSLDISTOPTFILE` was not set correctly for non-boot commands. When cookie is overridden from environment variable, EMQX node is unable to start. Fix node information formatter for stopped nodes in the cluster.
Project: userver (App Definition and Development / Streaming & Messaging)
File: dns_control.md

If your service has a server::handlers::DnsClientControl configured, then you may force hosts reload from cache and wipe DNS caches. The feature is useful to apply DNS changes faster. server::handlers::DnsClientControl provides the following REST API: ``` POST /service/dnsclient/reload_hosts POST /service/dnsclient/flush_cache?name={some name} POST /service/dnsclient/flushcachefull ``` Note that the server::handlers::DnsClientControl handler lives at the separate `components.server.listener-monitor` address, so you have to request them using the `listener-monitor` credentials. See @ref scripts/docs/en/userver/tutorial/production_service.md for more info on configuration and ideas on how to change the `/service/dnsclient/` handle path. ``` bash $ curl -X POST http://localhost:8085/service/dnsclient/reload_hosts -i HTTP/1.1 200 OK Date: Thu, 02 Dec 2021 15:27:49 UTC Content-Type: text/html; charset=utf-8 X-YaRequestId: e952064e60454c19950a534799837479 X-YaSpanId: 2e67da42409d2f2a X-YaTraceId: 6e45cff5d60b4ca2b399d39b8d093351 Server: sample-production-service 1.0 Connection: keep-alive Content-Length: 2 OK ``` ``` bash $ curl -X POST http://localhost:8085/service/dnsclient/flush_cache?name=ya.ru -i HTTP/1.1 200 OK Date: Thu, 02 Dec 2021 15:29:20 UTC Content-Type: text/html; charset=utf-8 X-YaRequestId: 6bfa28dd4ee74d18ab49d871b78426bf X-YaSpanId: 6f886740835e81bf X-YaTraceId: ffc2a2128d4c439891bd3b76ad77f80b Server: sample-production-service 1.0 Connection: keep-alive Content-Length: 2 OK ``` ``` bash $ curl -X POST http://localhost:8085/service/dnsclient/flushcachefull -i HTTP/1.1 200 OK Date: Thu, 02 Dec 2021 15:30:44 UTC Content-Type: text/html; charset=utf-8 X-YaRequestId: 79fc8ca39ac5475ab7be72ff5b9fecf2 X-YaSpanId: dd8ab87efa690283 X-YaTraceId: 2df06ec8be4a4dbdb66d4af78d4eba83 Server: sample-production-service 1.0 Connection: keep-alive Content-Length: 2 OK ``` @htmlonly <div class="bottom-nav"> @endhtmlonly @ref scripts/docs/en/userver/memoryprofilerunningservice.md | @ref scripts/docs/en/userver/ossignals.md @htmlonly </div> @endhtmlonly
Project: MariaDB (App Definition and Development / Database)
File: CONTRIBUTING.md

MariaDB Server has a vibrant community contributing in a wide range of areas. There are many valuable ways you can contribute to MariaDB. The MariaDB Foundation and MariaDB Corporation have a presence on Reddit, Twitter and Facebook. See the . Contribute towards and its ecosystem by adding new content or improving existing content. existing documentation. -- Test development versions Write code to fix bugs or develop new features (see ).See also Help with code quality control Participate in packaging for different Linux distributions Coding standards for the main source code can be found in . Youre very welcome to support MariaDB Server as an individual, or talk your company into joining the Foundation as a sponsoring member. See the . Attend an event - MariaDB has a dedicated time each week when we answer new contributor questions live on Zulip. From 8:00 to 10:00 UTC on Mondays, and 10:00 to 12:00 UTC on Thursdays, anyone can ask any questions theyd like, and a live developer will be available to assist. New contributors can ask questions any time, but we will provide immediate feedback during that interval. -
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: code-blocks.md

To make a code block executable, make sure to specify a language of either `bash`, `sh`, or `shell`. Inside a code blocks, you may define metadata, such as an identifier when linking code blocks into [Progress Step Lists](#progress-step-lists). ```bash echo hello ``` <!-- Hello viewers of the source to this guidebook! Note that we have used a language of `bashy` here, to prevent Kui from rendering this as an executable code block. --> When given one of those executable languages (e.g. if your code block starts with \`\`\`bash), Kui will display this as a executable code block with the given sample output. Here is that same text, but now repeated as a normal code block: ```bash id: my-first-command echo hello ``` And another example: ```bash id: my-second-command echo world ``` The `id` part is used to help you define a "progress stepper" list. When a referenced code block is executed, the progress stepper will update to show the user the status of that code blocks' execution. When using this syntax for lists: ``` blank This should echo hello. blank This should echo world. ``` you will get a progress step list like this: blank This should echo hello. blank This should echo world. Note the use of the `my-first-command` and `my-second-command` cross-reference identifiers.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: joins.md

type: languages title: "Beam SQL extensions: Joins" aliases: /documentation/dsls/sql/joins/ <!-- Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> Supported `JOIN` types in Beam SQL: `INNER`, `LEFT OUTER`, `RIGHT OUTER` Only equijoins (where join condition is an equality check) are supported Unsupported `JOIN` types in Beam SQL: `CROSS JOIN` is not supported (full cartesian product with no `ON` clause) `FULL OUTER JOIN` is not supported (combination of `LEFT OUTER` and `RIGHT OUTER` joins) The scenarios of join can be categorized into 3 cases: Bounded input `JOIN` bounded input Unbounded input `JOIN` unbounded input Unbounded input `JOIN` bounded input Standard join implementation is used. All elements from one input are matched with all elements from another input. Due to the fact that both inputs are bounded, no windowing or triggering is involved. Standard join implementation is used. All elements from one input are matched with all elements from another input. Windowing and Triggering The following properties must be satisfied when joining unbounded inputs: Inputs must have compatible windows, otherwise `IllegalArgumentException` will be thrown. Triggers on each input should only fire once per window. Currently this means that the only supported trigger in this case is `DefaultTrigger` with zero allowed lateness. Using any other trigger will result in `UnsupportedOperationException` thrown. This means that inputs are joined per-window. That is, when the trigger fires (only once), then join is performed on all elements in the current window in both inputs. This allows to reason about what kind of output is going to be produced. Note: similarly to `GroupByKeys` `JOIN` will update triggers using `Trigger.continuationTrigger()`. Other aspects of the inputs' windowing strategies remain unchanged. For this type of `JOIN` bounded input is treated as a side-input by the implementation. This means that window/trigger is inherited from upstreams.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: attach.md

Attach to STDIN, STDOUT or STDERR. In foreground mode (the default when -d is not specified), podman run can start the process in the container and attach the console to the process's standard input, output, and error. It can even pretend to be a TTY (this is what most command-line executables expect) and pass along signals. The -a option can be set for each of stdin, stdout, and stderr.
Project: TDengine (App Definition and Development / Database)
File: 13-Jupyter.md

title: Connect JupyterLab to TDengine sidebar_label: JupyterLab description: This document describes how to integrate TDengine with JupyterLab. JupyterLab is the next generation of the ubiquitous Jupyter Notebook. In this note we show you how to install the TDengine Python client library to connect to TDengine in JupyterLab. You can then insert data and perform queries against the TDengine instance within JupyterLab. Installing JupyterLab is very easy. Installation instructions can be found at: https://jupyterlab.readthedocs.io/en/stable/getting_started/installation.html. If you don't feel like clicking on the link here are the instructions. Jupyter's preferred Python package manager is pip, so we show the instructions for pip. You can also use conda or pipenv if you are managing Python environments. ```` pip install jupyterlab ```` For conda you can run: ```` conda install -c conda-forge jupyterlab ```` For pipenv you can run: ```` pipenv install jupyterlab pipenv shell ```` You can start JupyterLab from the command line by running: ```` jupyter lab ```` This will automatically launch your default browser and connect to your JupyterLab instance, usually on port 8888. You can now install the TDengine Python client library as follows. Start a new Python kernel in JupyterLab. If using conda run the following: ```` import sys !conda install --yes --prefix {sys.prefix} taospy ```` If using pip run the following: ```` import sys !{sys.executable} -m pip install taospy ```` You can find detailed examples to use the Python client library, in the TDengine documentation here. Once you have installed the TDengine Python client library in your JupyterLab kernel, the process of connecting to TDengine is the same as that you would use if you weren't using JupyterLab. Each TDengine instance, has a database called "log" which has monitoring information about the TDengine instance. In the "log" database there is a called "disks_info". The structure of this table is as follows: ```` taos> desc disks_info; Field | Type | Length | Note | ================================================================================= ts | TIMESTAMP | 8 | | datadirl0used | FLOAT | 4 | | datadirl0total | FLOAT | 4 | | datadirl1used | FLOAT | 4 | | datadirl1total | FLOAT | 4 | | datadirl2used | FLOAT | 4 | | datadirl2total | FLOAT | 4 | | dnode_id | INT | 4 | TAG | dnode_ep | BINARY | 134 | TAG | Query OK, 9 row(s) in set (0.000238s) ```` The code below is used to fetch data from this table into a pandas DataFrame. ```` import sys import taos import pandas def sqlQuery(conn): df: pandas.DataFrame = pandas.readsql("select * from log.disksinfo limit 500", conn) print(df) return df conn = taos.connect() result = sqlQuery(conn) print(result) ```` TDengine has client libraries for various languages including Node.js, Go, PHP and there are kernels for these languages which can be found .
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: index.md

Welcome to Monokle Desktop - K8s configuration analysis and version control editor! Monokle Desktop helps you to: Quickly get a high-level view of your manifests, their contained resources and relationships Leverage Git to manage the lifecycle of your configuration Validate resources using OPA policy rules Easily edit resources without having to learn or look up yaml syntax and see the changes applied Refactor resources with maintained integrity of names and references Preview and debug resources generated with kustomize or helm Visualize extended resources defined in CRD Compare resource versions against your cluster and apply changes immediately or through pull requests Create multi-step forms using Monokle's templating system to quickly generate manifests And much more! For further details on working with Monokle Desktop, read the document or watch the YouTube . <!--](https://www.youtube.com/watch?v=ossBDhP_K-4)--> Check out the following blog posts with Monokle Desktop-related content: 2.0 - - February 22, 2023 1.13 - - December 7, 2022 - October 24, 2022 1.12 - - October 24, 2022 1.11 - - September 30, 2022 1.10 - - August 10, 2022 1.9 - - July 12, 2022 1.8 - - June 6, 2022 1.7 - - May 2, 2022 1.6 - - Mar 21, 2022 1.5 - - Feb 7, 2022 1.4 - - Dec 15, 2021 1.3 - - Nov 15, 2021 1.2 - - Oct 4, 2021 1.1 - - Sep 6, 2021 1.0 - - Aug 10, 2021
Project: Meshery (Provisioning / Automation & Configuration)
File: kuma-past-results.md

layout: past-results-layout title: Meshery-Kuma Past Results permalink: installation/compatibility-matrix/meshery-kuma-past-results abstract: a complete compatibility matrix and project test status dashboard. language: en display-title: "false" list: exclude type: "project" service-mesh: "meshery-kuma" subheading: Meshery-Kuma
Project: KICS (Provisioning / Security & Compliance)
File: dc158941-28ce-481d-a7fa-dc80761edf46.md

title: RDS Instance Retention Period Not Recommended hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: dc158941-28ce-481d-a7fa-dc80761edf46 Query name: RDS Instance Retention Period Not Recommended Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Observability URL: RDS Instance SQL Retention Period should be greater than 180<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "aliclouddbinstance" "default" { engine = "MySQL" engine_version = "5.6" dbinstanceclass = "rds.mysql.t1.small" dbinstancestorage = "10" parameters = [{ name = "innodblargeprefix" value = "ON" },{ name = "connect_timeout" value = "50" },{ name = "log_connections" value = "ON" }] } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="1 6" resource "aliclouddbinstance" "default" { engine = "MySQL" engine_version = "5.6" dbinstanceclass = "rds.mysql.t1.small" dbinstancestorage = "10" sqlcollectorstatus = "Disabled" parameters = [{ name = "innodblargeprefix" value = "ON" },{ name = "connect_timeout" value = "50" },{ name = "log_connections" value = "ON" }] } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="1" resource "aliclouddbinstance" "default" { engine = "MySQL" engine_version = "5.6" dbinstanceclass = "rds.mysql.t1.small" dbinstancestorage = "10" sqlcollectorstatus = "Enabled" parameters = [{ name = "innodblargeprefix" value = "ON" },{ name = "connect_timeout" value = "50" },{ name = "log_connections" value = "ON" }] } ``` <details><summary>Positive test num. 4 - tf file</summary> ```tf hl_lines="7" resource "aliclouddbinstance" "default" { engine = "MySQL" engine_version = "5.6" dbinstanceclass = "rds.mysql.t1.small" dbinstancestorage = "10" sqlcollectorstatus = "Enabled" sqlcollectorconfig_value = 30 parameters = [{ name = "innodblargeprefix" value = "ON" },{ name = "connect_timeout" value = "50" },{ name = "log_connections" value = "ON" }] } ``` </details> ```tf title="Negative test num. 1 - tf file" resource "aliclouddbinstance" "default" { engine = "MySQL" engine_version = "5.6" dbinstanceclass = "rds.mysql.t1.small" dbinstancestorage = "10" sqlcollectorstatus = "Enabled" sqlcollectorconfig_value = 180 parameters = [{ name = "innodblargeprefix" value = "ON" },{ name = "connect_timeout" value = "50" },{ name = "log_connections" value = "ON" }] } ```