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

title: Upgrade the YugabyteDB software headerTitle: Upgrade the YugabyteDB software linkTitle: Upgrade YugabyteDB description: Use YugabyteDB Anywhere to upgrade the YugabyteDB software. menu: v2.18_yugabyte-platform: identifier: upgrade-software parent: manage-deployments weight: 80 type: docs The YugabyteDB release that is powering a universe can be upgraded to get new features and fixes included in the release. Before starting the upgrade: If you're upgrading a universe from v2.15.x or earlier to v2.16.0 or later, ensure that port 18018 is open on all YugabyteDB nodes so that YB Controller (introduced in v2.16.0) can operate. Consider importing a specific YugabyteDB release into YugabyteDB Anywhere, as follows: Click the user profile icon and select Releases. Click Import to open the Import Releases dialog shown in the following illustration: Specify the release version to import. Select the storage or URL that contains the release. If the release is located on Amazon S3, you would need to provide the access information; if the release is located on Google Cloud Storage, you would need to copy and paste the contents of the JSON file with the access credentials; if the release is accessible via a HTTP, you would need to specify the checksum value of the download. Provide the path to the storage location. Click OK. When imported, the release is added to the Releases list shown in the following illustration: <br> To delete or disable a release, click its corresponding Actions. You can perform a rolling upgrade on a live universe deployment as follows: Navigate to Universes and select your universe. Click Actions > Upgrade Software. In the Upgrade Software dialog, ensure that Rolling Upgrade is enabled, define the delay between servers or accept the default value, and then use the Server Version field to select the new YugabyteDB version, as per the following illustration: To trigger an upgrade that involves downtime, deselect Rolling Upgrade. For information on how rolling upgrades are performed in YugabyteDB, see . {{< note title="Note" >}} Currently, you cannot downgrade a universe to an older YugabyteDB release. For assistance with downgrades, contact Yugabyte Support. {{< /note >}} {{< note title="Upgrading manually-provisioned on-premises universes" >}} If you are upgrading a manually-provisioned universe, you must additionally manually install YB Controller after the otherwise-automated software upgrade procedure completes. YB Controller was introduced in YugabyteDB Anywhere 2.16.0, and is required for YugabyteDB Anywhere 2.16.0 and later. To install YB Controller, call the following API after the software upgrade: ```sh curl --location --request PUT '<YBA-url>/api/v1/customers/<customerID>/universes/<UniverseID>/ybc/install' \ --header 'X-AUTH-YW-API-TOKEN: <YBA-api-auth-token>' ``` To view your Customer ID and API Token, click the Profile icon in the top right corner of the YugabyteDB Anywhere window. You can view your Universe ID from your YugabyteDB Anywhere universe URL (`<YB-Anywhere-IP-address>/universes/<universeID>`). {{< /note >}}
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: disable-compression.md

Don't compress filesystem layers when building the image unless it is required by the location where the image is being written. This is the default setting, because image layers are compressed automatically when they are pushed to registries, and images being written to local storage only need to be decompressed again to be stored. Compression can be forced in all cases by specifying --disable-compression=false.
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_data_verify.md

title: Kubectl-Dba Data Verify menu: docs_{{ .version }}: identifier: kubectl-dba-data-verify name: Kubectl-Dba Data Verify parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Verify data in a database Verify data in a database. ``` kubectl-dba data verify ``` ``` kubectl dba data verify postgres sample-pg -n demo --rows=100 kubectl dba data verify mongodb -n demo mg-shard --rows=100 Valid resource types include: elasticsearch mongodb mariadb mysql postgres redis ``` ``` -h, --help help for verify ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "/home/runner/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --default-seccomp-profile-type string Default seccomp profile --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --password string Password for basic authentication to the API server --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use --username string Username for basic authentication to the API server ``` - Insert, Drop or Verify data in a database - Verify rows in a elasticsearch database - Verify rows to a mariadb resource - Verify data to a mongodb resource - Verify rows to a mysql resource - Verify rows in a postgres database - Verify rows in a redis database
Project: YDB (App Definition and Development / Database)
File: create_demo_tables.md

Create the tables and set the data schema for them using the statement . {% note info %} Keywords are case-insensitive and written in capital letters for clarity only. {% endnote %} ```sql CREATE TABLE series -- series is the table name. ( -- Must be unique within the folder. series_id Uint64, title Utf8, series_info Utf8, release_date Uint64, PRIMARY KEY (series_id) -- The primary key is a column or -- combination of columns that uniquely identifies -- each table row (contains only -- non-repeating values). A table can have -- only one primary key. For every table -- in YDB, the primary key is required. ); CREATE TABLE seasons ( series_id Uint64, season_id Uint64, title Utf8, first_aired Uint64, last_aired Uint64, PRIMARY KEY (seriesid, seasonid) ); CREATE TABLE episodes ( series_id Uint64, season_id Uint64, episode_id Uint64, title Utf8, air_date Uint64, PRIMARY KEY (seriesid, seasonid, episode_id) ); COMMIT; ```
Project: StarRocks (App Definition and Development / Database)
File: replace.md

displayed_sidebar: "English" Replaces all occurrences of characters in a string with another string. This function performs a case-sensitive match when searching for `pattern`. This function is supported from v3.0. Note: Prior to 3.0, this function was implemented as . ```SQL VARCHAR replace(VARCHAR str, VARCHAR pattern, VARCHAR repl) ``` `str`: the original string. `pattern`: the characters to replace. Note that this is not a regular expression. `repl`: the string used to replace characters in `pattern`. Returns a string with the specified characters replaced. If any argument is NULL, the result is NULL. If no matching characters are found, the original string is returned. ```plain -- Replace '.' in 'a.b.c' with '+'. MySQL > SELECT replace('a.b.c', '.', '+'); +-+ | replace('a.b.c', '.', '+') | +-+ | a+b+c | +-+ -- No matching characters are found and the original string is returned. MySQL > SELECT replace('a b c', '', '*'); +-+ | replace('a b c', '', '*') | +-+ | a b c | +-+ -- Replace 'like' with an empty string. MySQL > SELECT replace('We like StarRocks', 'like', ''); ++ | replace('We like StarRocks', 'like', '') | ++ | We StarRocks | ++ -- No matching characters are found and the original string is returned. MySQL > SELECT replace('He is awesome', 'handsome', 'smart'); +--+ | replace('He is awesome', 'handsome', 'smart') | +--+ | He is awesome | +--+ ``` REPLACE, replace
Project: SPIFFE (Provisioning / Key Management)
File: NOMINEE_TEMPLATE.md

A brief biography of the nominee goes here. What is their background? How does their work relate to SPIFFE and/or why is SPIFFE important to them? What about them makes them a good fit for the SSC? This information is very important and will be heavily considered by voters in order to make an informed decision. Be sure to preserve the two empty spaces at the end of each line below. GitHub Handle: @NOMINEE\GITHUB\HANDLE\_HERE Email Address: NOMINEE\EMAIL\ADDRESS\_HERE LinkedIn Profile: LINK\TO\NOMINEE\LINKEDIN\HERE Current Affiliation: NOMINEE\AFFILIATION\HERE
Project: KICS (Provisioning / Security & Compliance)
File: a9dfec39-a740-4105-bbd6-721ba163c053.md

title: Ram Account Password Policy Not Required Minimum Length hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: a9dfec39-a740-4105-bbd6-721ba163c053 Query name: Ram Account Password Policy Not Required Minimum Length Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Secret Management URL: Ram Account Password Policy should have 'minimumpasswordlength' defined and set to 14 or above<br> ```tf title="Positive test num. 1 - tf file" hl_lines="2" resource "alicloudramaccountpasswordpolicy" "corporate" { minimumpasswordlength = 9 requirelowercasecharacters = false requireuppercasecharacters = false require_numbers = false require_symbols = false hard_expiry = true maxpasswordage = 12 passwordreuseprevention = 5 maxloginattempts = 3 } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="1" resource "alicloudramaccountpasswordpolicy" "corporate" { requirelowercasecharacters = false requireuppercasecharacters = false require_numbers = false require_symbols = false hard_expiry = true maxpasswordage = 12 passwordreuseprevention = 5 maxloginattempts = 3 } ``` ```tf title="Negative test num. 1 - tf file" resource "alicloudramaccountpasswordpolicy" "corporate" { minimumpasswordlength = 14 requirelowercasecharacters = false requireuppercasecharacters = false require_numbers = false require_symbols = false hard_expiry = true maxpasswordage = 14 passwordreuseprevention = 5 maxloginattempts = 3 } ```
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_add_image.md

title: "Command - devspace add image" sidebar_label: devspace add image Add an image ``` devspace add image [flags] ``` ``` Adds a new image to this project's devspace.yaml Examples: devspace add image my-image --image=dockeruser/devspaceimage2 devspace add image my-image --image=dockeruser/devspaceimage2 --tag=alpine devspace add image my-image --image=dockeruser/devspaceimage2 --context=./context devspace add image my-image --image=dockeruser/devspaceimage2 --dockerfile=./Dockerfile devspace add image my-image --image=dockeruser/devspaceimage2 --buildtool=docker devspace add image my-image --image=dockeruser/devspaceimage2 --buildtool=kaniko ``` ``` --buildtool string Specify which engine should build the file. Should match this regex: docker|kaniko --context string The path of the images' context --dockerfile string The path of the images' dockerfile -h, --help help for image --image string The image name of the image (e.g. myusername/devspace) --tag string The tag of the image ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --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 string The devspace profile to use (if there is any) --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context 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) ```
Project: StarRocks (App Definition and Development / Database)
File: statistics.md

displayed_sidebar: "English" `statistics` provides information about table indexes. The following fields are provided in `statistics`: | Field | Description | | - | | | TABLE_CATALOG | The name of the catalog to which the table containing the index belongs. This value is always `def`. | | TABLE_SCHEMA | The name of the database to which the table containing the index belongs. | | TABLE_NAME | The name of the table containing the index. | | NON_UNIQUE | 0 if the index cannot contain duplicates, 1 if it can. | | INDEX_SCHEMA | The name of the database to which the index belongs. | | INDEX_NAME | The name of the index. If the index is the primary key, the name is always `PRIMARY`. | | SEQININDEX | The column sequence number in the index, starting with 1. | | COLUMN_NAME | The column name. See also the description for the `EXPRESSION` column. | | COLLATION | How the column is sorted in the index. This can have values `A` (ascending), `D` (descending), or `NULL` (not sorted). | | CARDINALITY | An estimate of the number of unique values in the index. | | SUB_PART | The index prefix. That is, the number of indexed characters if the column is only partly indexed, `NULL` if the entire column is indexed. | | PACKED | Indicates how the key is packed. `NULL` if it is not. | | NULLABLE | Contains `YES` if the column may contain `NULL` values and `''` if not. | | INDEX_TYPE | The index method used (`BTREE`, `FULLTEXT`, `HASH`, `RTREE`). | | COMMENT | Information about the index not described in its own column, such as `disabled` if the index is disabled. | | INDEX_COMMENT | Any comment provided for the index with a `COMMENT` attribute when the index was created. |
Project: Chef InSpec (Provisioning / Security & Compliance)
File: mongodb_session.md

+++ title = "mongodb_session resource" draft = false gh_repo = "inspec" platform = "os" [menu] [menu.inspec] title = "mongodb_session" identifier = "inspec/resources/os/mongodbsession.md mongodbsession resource" parent = "inspec/resources/os" +++ Use the `mongodb_session` Chef InSpec audit resource to run MongoDB command against a MongoDB Database. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} A `mongodb_session` resource block declares the `user`, `password`, and `database` to use for the session and then the command to be run: describe mongodb_session(user: "username", password: "password", database: "test").query(key: value) do its("params") { should match(/expected-result/) } end where `mongodb_session` declares a user, password, and database, connecting locally, with permission to run the query. `query` contains the query to be run. `its("params") { should eq(/expected-result/) }` compares the results of the query against the expected result in the test The `mongodbsession` InSpec resource accepts `user`, `password`, `host`, `port`, `authsource`, `authmech`, `ssl`, `sslcert`, `sslcacert`, and `authmechproperties` parameters. In Particular: The server host IP address. Default value: `127.0.0.1`. The server port. Default value: `27017`. The authentication mechanism. The available options are: `:scram`, `:scram256`, `:mongodb_x509`, and `:aws`. Default value: `:scram`. See the MongoDB documentation on for more information. The database where the users authentication credentials are stored. The default value is the database name that is passed as a parameter to the resource. Whether to use the SSL security protocol or not. Set to `true` to use SSL transport, default value: `false`. See the MongoDB documentation on for more information. Path to the SSL certificate file. Path to the SSL Certificate Authority (CA) certificate file. Path to SSL key file. A hash of the authentication mechanism properties. This option is generally used with the AWS authentication mechanism. See the MongoDB documentation on for more information. This resource uses the to fetch the data. The following examples show how to use this Chef InSpec audit resource. describe mongodb_session(user: "foo", password: "bar", database: "test").query(rolesInfo: "dbAdmin").params["roles"].first do its(["role"]) { should eq "dbAdmin" } end describe mongodb_session(user: "foo", password: "bar", database: "test").query(usersInfo: "foo").params["users"].first["roles"].first do its(["role"]) { should eq "readWrite" } end describe mongodb_session(user: "foo", password: "bar", database: "test").query(rolesInfo: "dbAdmin") do its("params") { shouldnot beempty } its("params") { should include "roles" } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The `params` contains all the query data.
Project: Chef Habitat (App Definition and Development / Application Definition & Image Build)
File: aks.md

+++ title = "Azure Container Services (AKS)" description = "Azure and Kubernetes K8" gh_repo = "habitat" [menu] [menu.habitat] title = "Azure Container Services (AKS)" identifier = "habitat/containers/aks Chef Habitat Azure Kubernetes" parent = "habitat/containers" weight = 40 +++ is a fully managed Kubernetes service running on the Azure platform. Azure Container Registry is a managed Docker container registry service used for storing private Docker container images. It's a fully managed Azure resource and gives you local, network-close storage of your container images when deploying to AKS. Chef Habitat Builder has native integration with this service so you can publish your packages directly to Azure Container Registry. In order to do this you need to create an Azure Service Principal that has `Owner` rights on your ACR instance. You can do this with the following script, changing the environment variable values to match your environment. ``` !/bin/bash RRESOURCEGROUP=myACRResourceGroup R_NAME=myACRRegistry BLDRPRINCIPALNAME=myPrincipalName BLDRPRINCIPALPASSWORD="ThisIsVeryStrongPassword" Create Service Principal for Chef Habitat Builder RID=$(az acr show --name $ACRNAME --resource-group $ACRRESOURCEGROUP --query "id" --output tsv) ad sp create-for-rbac --scopes $ACRID --role Owner --password "$BLDRPRINCIPALPASSWORD" --name $BLDRPRINCIPAL_NAME BLDRID=$(az ad sp list --display-name $BLDRPRINCIPAL_NAME --query "[].appId" --output tsv) ho "Configuration details for Habitat Builder Principal:" echo " ID : $BLDR_ID" echo " Password : $BLDRPRINCIPALPASSWORD" ``` Note: The unique Service Principal Name (the UUID) should be provided in the Chef Habitat Builder configuration. Since ACR is a private Docker registry, AKS must be authorized to pull images from it. The best way is to create a role assignment on the Service Principal that is automatically created for AKS, granting it `Reader` access on your ACR instance. To do this you can use the following script, changing the environment variable values to match your configuration. ``` AKSRESOURCEGROUP=myAKSResourceGroup AKSCLUSTERNAME=myAKSCluster ACRRESOURCEGROUP=myACRResourceGroup ACR_NAME=myACRRegistry CLIENTID=$(az aks show --resource-group $AKSRESOURCEGROUP --name $AKSCLUSTER_NAME --query "servicePrincipalProfile.clientId" --output tsv) ACRID=$(az acr show --name $ACRNAME --resource-group $ACRRESOURCEGROUP --query "id" --output tsv) az role assignment create --assignee $CLIENTID --role Reader --scope $ACRID ```
Project: ClickHouse (App Definition and Development / Database)
File: v20.8.18.32-lts.md

Backported in : Fix null dereference with `joinusenulls=1`. (). Backported in : Fix bug in partial merge join with `LowCardinality`. Close , close . (). Backported in : Fix approx total rows accounting for reverse reading from MergeTree. (). Backported in : Some values were formatted with alignment in center in table cells in `Markdown` format. Not anymore. ().
Project: KICS (Provisioning / Security & Compliance)
File: a6847dc6-f4ea-45ac-a81f-93291ae6c573.md

title: Path Scheme Accepts HTTP (v2) hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: a6847dc6-f4ea-45ac-a81f-93291ae6c573 Query name: Path Scheme Accepts HTTP (v2) Platform: OpenAPI Severity: <span style="color:#ff7213">Medium</span> Category: Encryption URL: The Scheme list of Operation Object should only allow 'HTTPS' protocol to ensure an encrypted connection<br> ```json title="Positive test num. 1 - json file" hl_lines="13" { "swagger": "2.0", "info": { "title": "Simple API overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "schemes": [ "http" ], "responses": { "200": { "description": "200 response" } } } } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="11" swagger: "2.0" info: title: Simple API overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions schemes: http responses: "200": description: 200 response ``` ```json title="Negative test num. 1 - json file" { "swagger": "2.0", "info": { "title": "Simple API overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "schemes": [ "https" ], "responses": { "200": { "description": "200 response" } } } } } } ``` ```yaml title="Negative test num. 2 - yaml file" swagger: "2.0" info: title: Simple API overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions schemes: https responses: "200": description: 200 response ```
Project: YugabyteDB (App Definition and Development / Database)
File: delete-universe.md

title: Pause, Resume, and Delete universes headerTitle: Pause, resume, and delete universes linkTitle: Pause or delete universe description: Use YugabyteDB Anywhere to pause, resume, and delete a universe. menu: v2.18_yugabyte-platform: identifier: delete-universe parent: manage-deployments weight: 70 type: docs To reduce costs on unused universes, you can pause or delete them. To pause a universe via the YugabyteDB Anywhere UI, navigate to Universes, select your universe, then click Actions > Pause Universe. Note that you can't pause universes created using an on-premises provider. You can't change the configuration, or read and write data to a paused universe. Alerts and backups are also stopped. Existing backups remain until they expire. Note that for public clouds, such as Amazon Web Services (AWS) and Google Cloud Platform (GCP), pausing a universe reduces costs for instance vCPU capacity, but disk and backup storage costs are not affected. To resume a paused universe via the YugabyteDB Anywhere UI, navigate to Universes, select the paused universe, then click Actions > Resume Universe. To delete a universe via the YugabyteDB Anywhere UI, navigate to Universes, select your universe, then click Actions > Delete Universe. For public clouds, the underlying compute instances are terminated after the database has been uninstalled from those nodes. For on-premises data centers, the underlying compute instances are no longer marked as `In Use`, which then opens those instances up to be reused for new universes.