cwielenb/CNCF-Dataset huggingface dataset:
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: harborregistryctl.md

HarborRegistryCtl requires a configuration file to start, which is located at `/etc/registryctl/config.yml` within the container. Any changes made to this config file are temporary and will not persist once the pod is restarted. The configmap from which this config file is generated is stored within Lagoon in the `services/harborregistryctl/harborregistry.yml` file. Any changes made to this configmap will be persisted across container restarts. `CORE_SECRET`* This value is a pre-shared key that must match between the various services connecting to `harbor-core`. The default value is set to `secret123` when Harbor is run locally or during CI testing. This value is retrieved from a secret created when Harbor is first set up on a running Lagoon. `JOBSERVICE_SECRET`* This value is a pre-shared key that must match between the various services connecting to `harbor-jobservice`. The default value is set to `secret123` when Harbor is run locally or during CI testing. This value is retrieved from a secret created when Harbor is first set up on a running Lagoon. `REGISTRY_HTTP_SECRET`* This value is a pre-shared key that must match between the various services connecting to `harborregistry`. The default value is set to `secret123` when Harbor is run locally or during CI testing. This value is retrieved from a secret created when Harbor is first set up on a running Lagoon. `REGISTRY_REDIS_PASSWORD`* This environment variable tells `harborregistryctl` the password that should be used to connect to Redis. The default value is an empty string.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.154.md

layout: release date: 2023-10-04 tag: v0.6.154 [Server] Fix race cond in k8s comp registration @MUzairS15 (#9015) [Server] Add APIs for bulk operations on events @MUzairS15 (#8999) Bump eslint-config-next from 13.4.19 to 13.5.3 in /provider-ui @dependabot (#8987) UI enhancements and Standardized Data Tables @sudhanshutech (#8939) Bump eslint-plugin-cypress from 2.14.0 to 2.15.1 in /provider-ui @dependabot (#8986) Bump cypress from 13.1.0 to 13.3.0 in /provider-ui @dependabot (#8984) Bump @fortawesome/fontawesome-svg-core from 6.2.0 to 6.4.2 in /ui @dependabot (#8983) Bump @cypress/code-coverage from 3.11.0 to 3.12.1 in /provider-ui @dependabot (#8985) Bump next from 13.4.12 to 13.5.3 in /provider-ui @dependabot (#8988) refactor(server): remove redundant `len` check @Juneezee (#8992) Bump eslint-config-next from 13.4.19 to 13.5.3 in /provider-ui @dependabot (#8987) Bump eslint-plugin-cypress from 2.14.0 to 2.15.1 in /provider-ui @dependabot (#8986) Bump cypress from 13.1.0 to 13.3.0 in /provider-ui @dependabot (#8984) Bump @fortawesome/fontawesome-svg-core from 6.2.0 to 6.4.2 in /ui @dependabot (#8983) Bump @cypress/code-coverage from 3.11.0 to 3.12.1 in /provider-ui @dependabot (#8985) Bump next from 13.4.12 to 13.5.3 in /provider-ui @dependabot (#8988) Thank you to our contributors for making this release possible: @Juneezee, @MUzairS15, @dependabot, @dependabot[bot], @l5io, @leecalcote, @nebula-aac, @sudhanshutech, @theBeginner86 and l5io
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.65.md

layout: release date: 2021-10-08 tag: v0.5.65 Fix Pattern Configurator @utkarsh-pro (#4360) [Extensions] Change RJSF Appbar position to be sticky in order for it to be maximisable @sudo-NithishKarthik (#4355) [mesheryctl] Fixing `system start` panic @piyushsingariya (#4357) Bump github.com/99designs/gqlgen from 0.13.0 to 0.14.0 @dependabot (#4308) Thank you to our contributors for making this release possible: @dependabot, @dhruv0000, @l5io, @leecalcote, @navendu-pottekkat, @piyushsingariya, @sudo-NithishKarthik, @utkarsh-pro and l5io
Project: secureCodeBox (Provisioning / Security & Compliance)
File: troubleshooting.md

title: "Troubleshooting" sidebar_label: Troubleshooting path: "docs/getting-started/troubleshooting" If you experience any problems using the secureCodeBox, you may find an answer here. Should your problem not be covered here, however, you can also join the (Channel `#project-securecodebox`) to get more specific help. If you think that you encountered a general problem that should be fixed, we are very grateful if you take the time to create an issue in our . Check if you have added the secureCodeBox repository: ```bash helm repo add secureCodeBox https://charts.securecodebox.io ``` Check your spelling: Helm repo is case-sensitive and no backslash at the end of a resource ```bash helm upgrade --install nmap securecodebox/nmap helm upgrade --install nmap secureCodeBox/nmap/ helm upgrade --install nmap secureCodeBox/nmap ``` Try to update your helm repository before installing the scanner (it is a good idea to do this periodically): ```bash helm repo update secureCodeBox ``` Check that you actually use a scanner from the repo instead of a local one: ```bash helm upgrade --install nmap ./scanners/nmap/ helm upgrade --install nmap secureCodeBox/nmap ``` If you want to use a local docker image for your scanner, check that your values.yaml* file is correct and follow these . If you use an image from the repository, make sure that it has already been included in the latest .
Project: YugabyteDB (App Definition and Development / Database)
File: txn_begin.md

title: BEGIN statement [YSQL] headerTitle: BEGIN linkTitle: BEGIN description: Use the `BEGIN` statement to start a transaction with the default (or specified) isolation level. menu: v2.18: identifier: txn_begin parent: statements type: docs Use the `BEGIN` statement to start a transaction with the default (or specified) isolation level. {{%ebnf%}} begin {{%/ebnf%}} ```plpgsql BEGIN [ TRANSACTION | WORK ] [ transaction_mode [ ... ] ] ``` Add optional keyword has no effect. Add optional keyword has no effect. Supports Serializable, Snapshot, and Read Committed Isolation<sup>$</sup> using the PostgreSQL isolation level syntax of `SERIALIZABLE`, `REPEATABLE READ`, and `READ COMMITTED` respectively. PostgreSQL's `READ UNCOMMITTED` also maps to Read Committed Isolation. <sup>$</sup> Read Committed support is currently in . Read Committed Isolation is supported only if the YB-TServer flag `ybenablereadcommittedisolation` is set to `true`. By default this flag is `false` and in this case the Read Committed isolation level of YugabyteDB's transactional layer falls back to the stricter Snapshot Isolation (in which case `READ COMMITTED` and `READ UNCOMMITTED` of YSQL also in turn use Snapshot Isolation). Create a sample table. ```plpgsql CREATE TABLE sample(k1 int, k2 int, v1 int, v2 text, PRIMARY KEY (k1, k2)); ``` Begin a transaction and insert some rows. ```plpgsql BEGIN TRANSACTION; SET TRANSACTION ISOLATION LEVEL REPEATABLE READ; ``` ```plpgsql INSERT INTO sample(k1, k2, v1, v2) VALUES (1, 2.0, 3, 'a'), (1, 3.0, 4, 'b'); ``` Start a new shell with `ysqlsh` and begin another transaction to insert some more rows. ```plpgsql BEGIN TRANSACTION; SET TRANSACTION ISOLATION LEVEL REPEATABLE READ; ``` ```plpgsql INSERT INTO sample(k1, k2, v1, v2) VALUES (2, 2.0, 3, 'a'), (2, 3.0, 4, 'b'); ``` In each shell, check the only the rows from the current transaction are visible. 1st shell. ```plpgsql yugabyte=# SELECT * FROM sample; -- run in first shell ``` ``` k1 | k2 | v1 | v2 -+-+-+- 1 | 2 | 3 | a 1 | 3 | 4 | b (2 rows) ``` 2nd shell ```plpgsql yugabyte=# SELECT * FROM sample; -- run in second shell ``` ``` k1 | k2 | v1 | v2 -+-+-+- 2 | 2 | 3 | a 2 | 3 | 4 | b (2 rows) ``` Commit the first transaction and abort the second one. ```plpgsql COMMIT TRANSACTION; -- run in first shell. ``` Abort the current transaction (from the first shell). ```plpgsql ABORT TRANSACTION; -- run second shell. ``` In each shell check that only the rows from the committed transaction are visible. ```plpgsql yugabyte=# SELECT * FROM sample; -- run in first shell. ``` ``` k1 | k2 | v1 | v2 -+-+-+- 1 | 2 | 3 | a 1 | 3 | 4 | b (2 rows) ``` ```plpgsql yugabyte=# SELECT * FROM sample; -- run in second shell. ``` ``` k1 | k2 | v1 | v2 -+-+-+- 1 | 2 | 3 | a 1 | 3 | 4 | b (2 rows) ```
Project: YugabyteDB (App Definition and Development / Database)
File: drop_table.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="577" height="100" viewbox="0 0 577 100"><path class="connector" d="M0 52h15m53 0h10m58 0h30m32 0h10m64 0h20m-141 0q5 0 5 5v8q0 5 5 5h116q5 0 5-5v-8q0-5 5-5m5 0h30m-5 0q-5 0-5-5v-20q0-5 5-5h38m24 0h39q5 0 5 5v20q0 5-5 5m-5 0h50m77 0h22m-109 25q0 5 5 5h5m79 0h5q5 0 5-5m-104-25q5 0 5 5v33q0 5 5 5h89q5 0 5-5v-33q0-5 5-5m5 0h15"/><polygon points="0,59 5,52 0,45" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="35" width="53" height="25" rx="7"/><text class="text" x="25" y="52">DROP</text><rect class="literal" x="78" y="35" width="58" height="25" rx="7"/><text class="text" x="88" y="52">TABLE</text><rect class="literal" x="166" y="35" width="32" height="25" rx="7"/><text class="text" x="176" y="52">IF</text><rect class="literal" x="208" y="35" width="64" height="25" rx="7"/><text class="text" x="218" y="52">EXISTS</text><rect class="literal" x="355" y="5" width="24" height="25" rx="7"/><text class="text" x="365" y="22">,</text><a xlink:href="../../../syntaxresources/grammardiagrams#table-name"><rect class="rule" x="322" y="35" width="91" height="25"/><text class="text" x="332" y="52">table_name</text></a><rect class="literal" x="463" y="35" width="77" height="25" rx="7"/><text class="text" x="473" y="52">CASCADE</text><rect class="literal" x="463" y="65" width="79" height="25" rx="7"/><text class="text" x="473" y="82">RESTRICT</text><polygon points="573,59 577,59 577,45 573,45" style="fill:black;stroke-width:0"/></svg>
Project: Apache Spark (App Definition and Development / Streaming & Messaging)
File: sql-ref-syntax-aux-describe-query.md

layout: global title: DESCRIBE QUERY displayTitle: DESCRIBE QUERY license: | Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You 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 `DESCRIBE QUERY` statement is used to return the metadata of output of a query. A shorthand `DESC` may be used instead of `DESCRIBE` to describe the query output. ```sql { DESC | DESCRIBE } [ QUERY ] input_statement ``` QUERY* This clause is optional and may be omitted. input_statement* Specifies a result set producing statement and may be one of the following: a `SELECT` statement a `CTE(Common table expression)` statement an `INLINE TABLE` statement a `TABLE` statement a `FROM` statement` Please refer to for a detailed syntax of the query parameter. ```sql -- Create table `person` CREATE TABLE person (name STRING , age INT COMMENT 'Age column', address STRING); -- Returns column metadata information for a simple select query DESCRIBE QUERY SELECT age, sum(age) FROM person GROUP BY age; +--++-+ |colname|datatype| comment| +--++-+ | age| int|Age column| |sum(age)| bigint| null| +--++-+ -- Returns column metadata information for common table expression (`CTE`). DESCRIBE QUERY WITH allnamescte AS (SELECT name from person) SELECT * FROM allnamescte; +--++-+ |colname|datatype|comment| +--++-+ | name| string| null| +--++-+ -- Returns column metadata information for an inline table. DESC QUERY VALUES(100, 'John', 10000.20D) AS employee(id, name, salary); +--++-+ |colname|datatype|comment| +--++-+ | id| int| null| | name| string| null| | salary| double| null| +--++-+ -- Returns column metadata information for `TABLE` statement. DESC QUERY TABLE person; +--++-+ |colname|datatype| comment| +--++-+ | name| string| null| | age| int| Agecolumn| | address| string| null| +--++-+ -- Returns column metadata information for a `FROM` statement. -- `QUERY` clause is optional and can be omitted. DESCRIBE FROM person SELECT age; +--++-+ |colname|datatype| comment| +--++-+ | age| int| Agecolumn| +--++-+ ```
Project: YDB (App Definition and Development / Database)
File: topic-consumer-drop.md

You can use the `topic consumer drop` command to delete a consumer. General format of the command: ```bash {{ ydb-cli }} [global options...] topic consumer drop [options...] <topic-path> ``` `global options`: . `options`: . `topic-path`: Topic path. View the description of the delete consumer command: ```bash {{ ydb-cli }} topic consumer drop --help ``` | Name | Description | | | `--consumer VAL` | Name of the consumer to be deleted. | {% include %} Delete the consumer with the `my-consumer` name for the `my-topic` topic: ```bash {{ ydb-cli }} -p quickstart topic consumer drop \ --consumer my-consumer \ my-topic ```
Project: StarRocks (App Definition and Development / Database)
File: microseconds_add.md

displayed_sidebar: "English" Adds a time interval to a date value. The time interval is in microseconds. ```Haskell DATETIME microseconds_add(DATETIME expr1,INT expr2); ``` `expr1`: the time expression. It must be of the DATETIME type. `expr2`: the time interval you want to add, in microseconds. It must be of the INT type. Returns a value of the DATETIME type. If the input value is of the DATE type, the hour, minute, and seconds parts are processed as `00:00:00`. ```Plain Text select microseconds_add('2010-11-30 23:50:50', 2); +--+ | microseconds_add('2010-11-30 23:50:50', 2) | +--+ | 2010-11-30 23:50:50.000002 | +--+ 1 row in set (0.00 sec) select microseconds_add('2010-11-30', 2); +--+ | microseconds_add('2010-11-30', 2) | +--+ | 2010-11-30 00:00:00.000002 | +--+ ```
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: creating-resources.md

While using Monokle Desktop, you can directly add new K8s resources. Once you have browsed and added your project folder, click on the Create Resource button at the top of the navigator to open the Create Resource drop down. Select "New from scratch" or New from template". While creating a resource, it is possible to select an existing resource as a template from the drop-down menu. The options for this template are Save to folder, Add to file and Don't save. If the last drop down is left as Don't save, that resource will be added to the Navigator resources but it will be highlighted in yellow: These unsaved resources will have to be saved by the user to be able to reuse them. Clicking on a yellow resource will show the Save button in the Editor panel to save the highlighted resource. Monokle Desktop allows the use of templates to start a new project via the Start from a template option: The Create a Project from a Template dialog appears: Name your project, select its location and click Next: Select a Template. Monokle Desktop includes a default set of templates which are installed automatically when starting Monokle Desktop for the first time and available in the Templates Explorer when working with your Monokle Desktop projects: Check out the repository to see the complete list of templates that are included along with their corresponding schemas and manifests. Click the ellipsis to the right of a resource name to see the options available: You can deploy a resource to a namespace, selecting an existing namespace, creating a new namespace or not choosing a namespace. <!--### Diff a Resource --> You can rename resources and update all the references associated with that resource to ensure the integrity of that link. You can use the Clone action to create a new resource by using existing resources as a template. You can use the Delete action in the cluster mode to delete the resource from the actual cluster.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: stop-start-a-cluster.md

title: Stop/Start a MySQL cluster description: How to stop/start a MySQL cluster keywords: [mysql, stop a cluster, start a cluster] sidebar_position: 5 sidebar_label: Stop/Start You can stop/start a cluster to save computing resources. When a cluster is stopped, the computing resources of this cluster are released, which means the pods of Kubernetes are released, but the storage resources are reserved. You can start this cluster again by snapshots if you want to restore the cluster resources. Configure the name of your cluster and run the command below to stop this cluster. ```bash kbcli cluster stop mysql-cluster ``` Run the command below to stop a cluster. ```bash kubectl apply -f - <<EOF apiVersion: apps.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: name: mysql-cluster generateName: stop- spec: clusterRef: mysql-cluster type: Stop EOF ``` Configure replicas as 0 to delete pods. ```yaml apiVersion: apps.kubeblocks.io/v1alpha1 kind: Cluster metadata: name: mysql-cluster spec: clusterDefinitionRef: apecloud-mysql clusterVersionRef: ac-mysql-8.0.30 terminationPolicy: WipeOut componentSpecs: name: mysql componentDefRef: mysql monitor: false replicas: 0 volumeClaimTemplates: name: data spec: storageClassName: standard accessModes: ReadWriteOnce resources: requests: storage: 1Gi ``` Configure the name of your cluster and run the command below to start this cluster. ```bash kbcli cluster start mysql-cluster ``` Run the command below to start a cluster. ```bash kubectl apply -f - <<EOF apiVersion: apps.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: name: mysql-cluster generateName: start- spec: clusterRef: mysql-cluster type: Start EOF ``` Change replicas back to the original amount to start this cluster again. ```yaml apiVersion: apps.kubeblocks.io/v1alpha1 kind: Cluster metadata: name: mysql-cluster spec: clusterDefinitionRef: apecloud-mysql clusterVersionRef: ac-mysql-8.0.30 terminationPolicy: WipeOut componentSpecs: name: mysql componentDefRef: mysql monitor: false replicas: 3 volumeClaimTemplates: name: data spec: storageClassName: standard accessModes: ReadWriteOnce resources: requests: storage: 1Gi ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.20.md

layout: release date: 2024-02-14 tag: v0.7.20 [Server] Design upload events. @MUzairS15 (#10306) [chore] fix mesheryctl lint issue @MUzairS15 (#10307) Thank you to our contributors for making this release possible: @MUzairS15 and @leecalcote
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: publish.md

Publish a container's port, or range of ports,<<| within this pod>> to the host. Both hostPort and containerPort can be specified as a range of ports. When specifying ranges for both, the number of container ports in the range must match the number of host ports in the range. If host IP is set to 0.0.0.0 or not set at all, the port is bound on all IPs on the host. By default, Podman publishes TCP ports. To publish a UDP port instead, give `udp` as protocol. To publish both TCP and UDP ports, set `--publish` twice, with `tcp`, and `udp` as protocols respectively. Rootful containers can also publish ports using the `sctp` protocol. Host port does not have to be specified (e.g. `podman run -p 127.0.0.1::80`). If it is not, the container port is randomly assigned a port on the host. Use podman port to see the actual mapping: `podman port $CONTAINER $CONTAINERPORT`. Note that the network drivers `macvlan` and `ipvlan` do not support port forwarding, it will have no effect on these networks.
Project: Trivy (Provisioning / Security & Compliance)
File: schema.md

Policies can be defined with custom schemas that allow inputs to be verified against them. Adding a policy schema enables Trivy to show more detailed error messages when an invalid input is encountered. In Trivy we have been able to define a schema for a . Without input schemas, a policy would be as follows: !!! example ``` package mypackage deny { input.evil == "foo bar" } ``` If this policy is run against offending Dockerfile(s), there will not be any issues as the policy will fail to evaluate. Although the policy's failure to evaluate is legitimate, this should not result in a positive result for the scan. For instance if we have a policy that checks for misconfigurations in a `Dockerfile`, we could define the schema as such !!! example ``` package mypackage deny { input.evil == "foo bar" } ``` Here `input: schema["dockerfile"]` points to a schema that expects a valid `Dockerfile` as input. An example of this can be found . Now if this policy is evaluated against, a more descriptive error will be available to help fix the problem. ```bash 1 error occurred: testpolicy.rego:8: regotypeerror: undefined ref: input.evil input.evil ^ have: "evil" want (one of): ["Stages"] ``` Currently, out of the box the following schemas are supported natively: You can also bring a custom policy that defines one or more custom schema. !!! example ``` package mypackage deny { input.evil == "foo bar" } ``` The checks can be placed in a structure as follows !!! example ``` /Users/user/my-custom-checks my_policy.rego schemas fooschema.json barschema.json ``` To use such a policy with Trivy, use the `--config-policy` flag that points to the policy file or to the directory where the schemas and checks are contained. ```bash $ trivy --config-policy=/Users/user/my-custom-checks <path/to/iac> ``` For more details on how to define schemas within Rego checks, please see the that describes it in more detail.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_runtime_config_config_iam_binding.md

+++ title = "googleruntimeconfigconfigiam_binding resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleruntimeconfigconfigiam_binding" identifier = "inspec/resources/gcp/googleruntimeconfigconfigiambinding.md googleruntimeconfigconfigiambinding resource" parent = "inspec/resources/gcp" +++ A `googleruntimeconfigconfigiam_binding` is used to test a Google Config Iam Bindings ```ruby describe googleruntimeconfigconfigiam_binding(project: "project", name: "name", role: "roles/editor") do it { should exist } its('members') { should include 'user:testuser@example.com' } end ``` Properties that can be accessed from the `googleruntimeconfigconfigiam_binding` resource: `role` : Role that is assigned to members. For example, roles/viewer, roles/editor, or roles/owner. `members` : Specifies the identities requesting access for a Cloud Platform resource. Ensure the is enabled for the current project.