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

Describe a NFS YugabyteDB Anywhere storage configuration Describe a NFS storage configuration in YugabyteDB Anywhere ``` yba storage-config nfs describe [flags] ``` ``` -h, --help help for describe ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -n, --name string [Optional] The name of the storage configuration for the operation. Required for create, delete, describe, update. -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage a YugabyteDB Anywhere NFS storage configuration
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: bug-report.md

name: Bug Report about: If things aren't working as expected. title: '' labels: '' assignees: '' <!-- Thanks for filing an issue! Before hitting the button, please answer these questions. Fill in as much of the template below as you can. If you leave out information, we can't help you as well. Note: Make sure to first check the prerequisites that can be found in the main README.md file! --> <!-- A clear and concise description of the steps you took (or insert a code snippet). --> <!-- A clear and concise description of what you expected to happen (or insert a code snippet). --> <!-- A clear and concise description of what ACTUALLY happened (or insert a code snippet). --> Operator type: <!-- Uncomment one or more of the following lines corresponding to the language of the operator type --> <!-- /language go --> <!-- /language ansible - For ansible operator related bugs, please create the issue in https://github.com/operator-framework/ansible-operator-plugins --> <!-- /language helm --> Kubernetes cluster type: <!-- The type of cluster used for testing/deployment, ex. "vanilla", "OpenShift" --> `$ operator-sdk version` <!-- Insert the output of `operator-sdk version` here. --> `$ go version` (if language is Go) <!-- Insert the output of `go version` here --> `$ kubectl version` <!-- Insert the output of `kubectl version` here --> <!-- Only if you have suggestions on a fix for the bug --> <!-- Add any other context about the problem here. -->
Project: StarRocks (App Definition and Development / Database)
File: ALTER_RESOURCE_GROUP.md

displayed_sidebar: "English" Alters the configuration of a resource group. :::tip This operation requires the ALTER privilege on the target resource group. You can follow the instructions in to grant this privilege. ::: ```SQL ALTER RESOURCE GROUP resourcegroupname { ADD CLASSIFIER1, CLASSIFIER2, ... | DROP (CLASSIFIERID1, CLASSIFIERID2, ...) | DROP ALL | WITH resource_limit }; ``` | Parameter | Description | | - | | | resourcegroupname | Name of the resource group to be altered. | | ADD | Add classifiers to the resource group. See for more information on how to define a classifier. | | DROP | Drop classifiers from the resource group via classifier IDs. You can check the ID of a classifier via statement. | | DROP ALL | Drop all classifiers from the resource group. | | WITH | Modify the resource limits of the resource group. See for more information on how to set resource limits. | Example 1: Adds a new classifier to the resource group `rg1`. ```SQL ALTER RESOURCE GROUP rg1 ADD (user='root', query_type in ('select')); ``` Example 2: Drops classifiers with ID `300040`, `300041`, and `300041` from the resource group `rg1`. ```SQL ALTER RESOURCE GROUP rg1 DROP (300040, 300041, 300041); ``` Example 3: Drops all classifiers from the resource group `rg1`. ```SQL ALTER RESOURCE GROUP rg1 DROP ALL; ``` Example 4: modifies the resource limits of the resource group `rg1`. ```SQL ALTER RESOURCE GROUP rg1 WITH ( 'cpucorelimit' = '20' ); ```
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: first-deployment.md

description: >- It's time! It's time for the first deployment into Lagoon! We hope you are as excited as we are! !!! Note If you are deploying a Drupal Project, skip this and read the . In order to make your first deployment a successful one, please make sure that your project is Lagoonized and that you have set up the project in Lagoon. If not, or you're not sure, or that doesn't sound familiar, don't worry, go back and follow the which show you how this works, and then come back and deploy! With Lagoon, you create a new deployment by pushing into a branch that is configured to be deployed. If you don't have any new code to push, don't worry! Run: ```bash title="Git push" git commit --allow-empty -m "go, go! Power Rangers!" git push ``` This will trigger a push, and your Git hosting will inform Lagoon about this push via the configured webhook. If all is correct, you should see a notification in your configured chat system \(this has been configured by your friendly Lagoon administrator\): This informs you that Lagoon has just started to deploy your code. Depending on the size of the code and amount of containers, this will take a couple of seconds. Just relax. If you want to know what's happening now, check out the . You can also check your Lagoon UI to see the progress of any deployment \(your Lagoon administrator has the info\). As soon as Lagoon is done building and deploying it will send a second notification to the chat system, here an example: It tells you: Which project has been deployed. Which branch and Git SHA have been deployed. A link to the full logs of the build and deployment. Links to all routes \(URLs\) where the environment can be reached. You can also quickly tell what kind of notification it is by the emoji at the beginning - whether it's just info that the build has started, a success, or fail. That's it! We hope that wasn't too hard - making devOps accessible is what we are striving for! That's the beauty of Lagoon: it's exactly the same! Just push the name of the branch and that one will be deployed. Did the deployment fail? Oh no! But we're here to help: If you deployed a Drupal site, make sure to read the , which explains why this happens. Click on the `Logs` link in the error notification, it will tell you where in the deployment process the failure happened. If you can't figure it out, just ask your Lagoon support, we are here to help! Reach out to us in your support channel or in .
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: Neo4j.md

Neo4j source connector Read data from Neo4j. `neo4j-java-driver` version 4.4.9 | name | type | required | default value | |-|--|-|| | uri | String | Yes | - | | username | String | No | - | | password | String | No | - | | bearer_token | String | No | - | | kerberos_ticket | String | No | - | | database | String | Yes | - | | query | String | Yes | - | | schema | Object | Yes | - | | maxtransactionretry_time | Long | No | 30 | | maxconnectiontimeout | Long | No | 30 | The URI of the Neo4j database. Refer to a case: `neo4j://localhost:7687` username of the Neo4j password of the Neo4j. required if `username` is provided base64 encoded bearer token of the Neo4j. for Auth. base64 encoded kerberos ticket of the Neo4j. for Auth. database name. Query statement. returned fields of `query` see maximum transaction retry time(seconds). transaction fail if exceeded The maximum amount of time to wait for a TCP connection to be established (seconds) ``` source { Neo4j { uri = "neo4j://localhost:7687" username = "neo4j" password = "1234" database = "neo4j" maxtransactionretry_time = 1 maxconnectiontimeout = 1 query = "MATCH (a:Person) RETURN a.name, a.age" schema { fields { a.age=INT a.name=STRING } } } } ``` Add Neo4j Source Connector
Project: YugabyteDB (App Definition and Development / Database)
File: alter_function,subprogram_signature,arg_decl,special_fn_and_proc_attribute,alterable_fn_and_proc_attribute,alterable_fn_only_attribute,volatility,on_null_input,parallel_mode.grammar.md

```output.ebnf alterfunction ::= ALTER FUNCTION subprogramname ( [ subprogram_signature ] ) { specialfnandprocattribute | { alterablefnandprocattribute | alterablefnonly_attribute } [ ... ] [ RESTRICT ] } subprogramsignature ::= argdecl [ , ... ] argdecl ::= [ argname ] [ argmode ] argtype specialfnandprocattribute ::= RENAME TO subprogram_name | OWNER TO { role_name | CURRENT_ROLE | CURRENT_USER | SESSION_USER } | SET SCHEMA schema_name | [ NO ] DEPENDS ON EXTENSION extension_name alterablefnandprocattribute ::= SET configuration_parameter { TO value | = value | FROM CURRENT } | RESET configuration_parameter | RESET ALL | [ EXTERNAL ] SECURITY { INVOKER | DEFINER } alterablefnonly_attribute ::= volatility | onnullinput | PARALLEL parallel_mode | [ NOT ] LEAKPROOF | COST int_literal | ROWS int_literal volatility ::= IMMUTABLE | STABLE | VOLATILE onnullinput ::= CALLED ON NULL INPUT | RETURNS NULL ON NULL INPUT | STRICT parallel_mode ::= UNSAFE | RESTRICTED | SAFE ```
Project: YugabyteDB (App Definition and Development / Database)
File: yba_storage-config_list.md

List YugabyteDB Anywhere storage-configurations List YugabyteDB Anywhere storage-configurations ``` yba storage-config list [flags] ``` ``` -n, --name string [Optional] Name of the storage configuration. -c, --code string [Optional] Code of the storage configuration, defaults to list all storage configurations. Allowed values: s3, gcs, nfs, az. -h, --help help for list ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage YugabyteDB Anywhere storage configurations
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: opa-errors.md

title: OPA Errors subtitle: OPA error message reference labels: category: learning inventors: styra code: https://docs.styra.com/opa/errors tutorials: https://docs.styra.com/opa/errors docs_features: debugging-rego: note: | is a guide aimed at helping users debug OPA errors by documenting common errors and fixes in detail. is a guide is designed to help you understand the most common errors you'll encounter when working with OPA. Each page provides examples of an OPA error, why it's an error, and how to fix it. If you'd like to request that a new error is listed, please drop us a message in the .
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-exp-connections-list.md

layout: default title: mesheryctl-exp-connections-list permalink: reference/mesheryctl/exp/connections/list redirect_from: reference/mesheryctl/exp/connections/list/ type: reference display-title: "false" language: en command: exp subcommand: connections List all the connections List all the connections <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl exp connections list [flags] </div> </pre> List all the connections <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl exp connections list </div> </pre> List all the connections with page number <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl exp connections list --page 2 </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -c, --count Display the count of models -h, --help help for list -p, --page int Page number (default 1) </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -v, --verbose verbose output </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: go-sdk.md

title: "Go SDK Roadmap" <!-- 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. --> The Go SDK is . The Go SDK the first SDK purely on the and can execute pipelines on portable runners, like Flink, Spark, Samza, and Google Cloud Dataflow. Current roadmap: continue building up unbounded pipeline facing features, as described on the . improve IO support via cross language transforms, and add scalable native transforms. Otherwise, improving examples and documentation for devs and users alike is ongoing. Contributions are welcome. Please contact the for assistance in finding a place to help out. Issues: Contact: Robert Burke (@lostluck) - Please also cc the dev@beam.apache.org list. I strongly prefer public discussion of Go SDK matters.
Project: Hazelcast Jet (App Definition and Development / Streaming & Messaging)
File: xa.md

title: Compatibility of XA Support description: How to check the compatibility of XA Support for JMS brokers and JDBC databases. id: version-4.1.1-xa original_id: xa Jet supports exactly-once processing internally, but in order to have end-to-end exactly-once processing sources and sinks need to support it too. Jet introduced XA transaction support, by which source and sink will actively participate to achieve this goal. Basically Jet starts transactions for the source, sink and any stage between these two, prepares them and commit them only after snapshot completed on all nodes. We've found that many resources we use as either sinks or sources, claiming to support XA have a common flaw: the transaction doesn't survive a client disconnect. Their behavior is sufficient to ensure atomicity (that is all distributed participants either commit or all rollback), but not to achieve fault-tolerance. We've introduced a set of tests to check compatibility of the XA support in your JMS broker or JDBC database with Jet's fault tolerance. The tests check only one feature, namely that a prepared transaction can be committed after the client reconnects. Clone the ```bash git clone git@github.com:hazelcast/hazelcast-jet-contrib.git ``` Head to `xa-tests` module. ```bash cd hazelcast-jet-contrib/xa-tests ``` The module contains two tests: Let's test compatibility of XA support for `PostgreSQL`. Add the database connector dependency to `build.gradle`: ```groovy compile group: 'org.postgresql', name: 'postgresql', version: '42.2.9' ``` Edit `JdbcXaTest.java` Create a `PGXADataSource` as the XA connection factory and configure it with the URL of the database, username, password and database name: ```java ... private static XADataSource getXADataSource() { PGXADataSource factory = new PGXADataSource(); factory.setUrl("jdbc:postgresql://localhost:32773/test-database"); factory.setUser("the-user"); factory.setPassword("the-pass"); factory.setDatabaseName("test-database"); return factory; } ... ``` Run the class, you should see `"Success!"` in the output. Testing compatibility of XA support for JMS brokers is similar to JDBC. Add the dependency to `build.gradle`: ```groovy compile group: 'org.apache.activemq', name:'activemq-all', version:'5.15.11' ``` Edit `JmsXaTest.java` Create an `ActiveMQXAConnectionFactory` with the broker URL as the XA connection factory. ```java ... private static XAConnectionFactory getXAConnectionFactory() { ActiveMQXAConnectionFactory factory = new ActiveMQXAConnectionFactory("broker:(tcp://localhost:61616)"); return factory; } ... ``` Run the class, you should see `"Success!"` in the output.
Project: YugabyteDB (App Definition and Development / Database)
File: data-modeling-ysql.md

title: YSQL data modeling in YugabyteDB headerTitle: Data modeling linkTitle: 2. Data modeling description: Learn data modeling in YSQL and how to identify the patterns used to access data and the types of queries to be performed. menu: v2.18: identifier: data-modeling-2-ysql parent: learn weight: 562 type: docs <ul class="nav nav-tabs-alt nav-tabs-yb"> <li > <a href="../data-modeling-ysql/" class="nav-link active"> <i class="icon-postgres" aria-hidden="true"></i> YSQL </a> </li> <li > <a href="../data-modeling-ycql/" class="nav-link"> <i class="icon-cassandra" aria-hidden="true"></i> YCQL </a> </li> </ul> Data modeling is a process that involves identifying the entities (items to be stored) and the relationships between entities. To create your data model, identify the patterns used to access data and the types of queries to be performed. These two ideas inform the organization and structure of the data, and the design and creation of the database's tables. YSQL content coming soon.
Project: Meshery (Provisioning / Automation & Configuration)
File: 10-11-2023-01-32-10_a31ecf14.md

timestamp: "2023-10-11 01:32:27 UTC Wed" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "*name" k8s-distro: minikube k8s-version: "v1.21.5" service-mesh: Consul service-mesh-version: "v1.2.2" tests: consul-client: null consul-server: null overall-status: "failing"
Project: KICS (Provisioning / Security & Compliance)
File: a3a055d2-9a2e-4cc9-b9fb-12850a1a3a4b.md

title: AD Admin Not Configured For SQL Server hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: a3a055d2-9a2e-4cc9-b9fb-12850a1a3a4b Query name: AD Admin Not Configured For SQL Server Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: The Active Directory Administrator is not configured for a SQL server<br> ```tf title="Positive test num. 1 - tf file" hl_lines="6" resource "azurermresourcegroup" "positive1" { name = "acceptanceTestResourceGroup1" location = "West US" } resource "azurermsqlserver" "positive2" { name = "mysqlserver1" resourcegroupname = "acceptanceTestResourceGroup1" location = "West US" version = "12.0" administrator_login = "4dm1n157r470r" administratorloginpassword = "4-v3ry-53cr37-p455w0rd" } resource "azurermsqlactivedirectoryadministrator" "positive3" { server_name = "mysqlserver2" resourcegroupname = "acceptanceTestResourceGroup1" login = "sqladmin" tenantid = data.azurermclientconfig.current.tenantid objectid = data.azurermclientconfig.current.objectid } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermresourcegroup" "negative1" { name = "acceptanceTestResourceGroup1" location = "West US" } resource "azurermsqlserver" "negative2" { name = "mysqlserver" resourcegroupname = "acceptanceTestResourceGroup1" location = "West US" version = "12.0" administrator_login = "4dm1n157r470r" administratorloginpassword = "4-v3ry-53cr37-p455w0rd" } resource "azurermsqlactivedirectoryadministrator" "negative3" { server_name = "mysqlserver" resourcegroupname = "acceptanceTestResourceGroup1" login = "sqladmin" tenantid = data.azurermclientconfig.current.tenantid objectid = data.azurermclientconfig.current.objectid } ```
Project: StarRocks (App Definition and Development / Database)
File: bitmap_max.md

displayed_sidebar: "English" Obtains the maximum value of a bitmap. If the bitmap is `NULL`, this function returns `NULL`. If the bitmap is empty, this function returns `NULL` by default. ```Haskell bitmap_max(bitmap) ``` `bitmap`: the bitmap whose maximum value you want to obtain. Only the BITMAP data type is supported. You can specify a bitmap that you construct by using functions such as . Returns a value of the LARGEINT data type. ```Plain MySQL > select bitmapmax(bitmapfrom_string("0, 1, 2, 3")); +-+ | bitmapmax(bitmapfrom_string("0, 1, 2, 3")) | +-+ | 3 | +-+ MySQL > select bitmapmax(bitmapfrom_string("-1, 0, 1, 2")); +-+ | bitmapmax(bitmapfrom_string("-1, 0, 1, 2")) | +-+ | NULL | +-+ MySQL > select bitmapmax(bitmapempty()); +-+ | bitmapmax(bitmapempty()) | +-+ | NULL | +-+ mysql> select bitmapmax(bitmapfrom_string("1, 16501189037412846863")); +--+ | bitmapmax(bitmapfrom_string('1, 16501189037412846863')) | +--+ | 16501189037412846863 | +--+ 1 row in set (0.02 sec) ```
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_kubeblocks_describe-config.md

title: kbcli kubeblocks describe-config Describe KubeBlocks config. ``` kbcli kubeblocks describe-config [flags] ``` ``` kbcli kubeblocks describe-config kbcli kubeblocks describe-config --all kbcli kubeblocks describe-config --filter=addonController,affinity ``` ``` -A, --all show all kubeblocks configs value --filter string filter the desired kubeblocks configs, multiple filtered strings are comma separated -h, --help help for describe-config -o, --output format prints the output in the specified format. Allowed values: table, json, yaml, wide (default table) ``` ``` --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 ``` - KubeBlocks operation commands.