cwielenb/CNCF-Dataset huggingface dataset:
Project: ShardingSphere (App Definition and Development / Database)
File: alter-storage-unit.en.md

+++ title = "ALTER STORAGE UNIT" weight = 2 +++ The `ALTER STORAGE UNIT` syntax is used to alter storage units for the currently selected logical database. {{< tabs >}} {{% tab name="Grammar" %}} ```sql AlterStorageUnit ::= 'ALTER' 'STORAGE' 'UNIT' storageUnitDefinition (',' storageUnitDefinition)* storageUnitDefinition ::= storageUnitName '(' ('HOST' '=' hostName ',' 'PORT' '=' port ',' 'DB' '=' dbName | 'URL' '=' url) ',' 'USER' '=' user (',' 'PASSWORD' '=' password)? (',' propertiesDefinition)?')' storageUnitName ::= identifier hostname ::= string port ::= int dbName ::= string url ::= string user ::= string password ::= string propertiesDefinition ::= 'PROPERTIES' '(' key '=' value (',' key '=' value)* ')' key ::= string value ::= literal ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} Before altering the storage units, please confirm that a database exists in Proxy, and execute the `use` command to successfully select a database; `ALTER STORAGE UNIT` is not allowed to change the real data source associated with this storageUnit; `ALTER STORAGE UNIT` will switch the connection pool. This operation may affect the ongoing business, please use it with caution; `storageUnitName` is case-sensitive; `storageUnitName` needs to be unique within the current database; `storageUnitName` name only allows letters, numbers and `_`, and must start with a letter; `poolProperty` is used to customize connection pool parameters, `key` must be the same as the connection pool parameter name. Alter storage unit using standard mode ```sql ALTER STORAGE UNIT ds_0 ( HOST=127.0.0.1, PORT=3306, DB=db_0, USER=root, PASSWORD=root ); ``` Alter storage unit and set connection pool parameters using standard mode ```sql ALTER STORAGE UNIT ds_0 ( HOST=127.0.0.1, PORT=3306, DB=db_1, USER=root, PASSWORD=root PROPERTIES("maximumPoolSize"=10) ); ``` Alter storage unit and set connection pool parameters using URL patterns ```sql ALTER STORAGE UNIT ds_0 ( URL="jdbc:mysql://127.0.0.1:3306/db_2?serverTimezone=UTC&useSSL=false", USER=root, PASSWORD=root, PROPERTIES("maximumPoolSize"=10,"idleTimeout"="30000") ); ``` `ALTER`, `STORAGE`, `UNIT`, `HOST`, `PORT`, `DB`, `USER`, `PASSWORD`, `PROPERTIES`, `URL`
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: i2scim.md

title: i2scim.io SCIM Restful User/Group Provisioning API labels: category: security layer: application software: i2scim code: https://github.com/i2-open/i2scim https://i2scim.io inventors: i2 tutorials: https://i2scim.io/OPA_AccessControl.html docs_features: rest-api-integration: note: | i2scim supports externalized access control decisions using OPA's REST API. The integration is described in the . i2scim.io is an open source, Apache 2 Licensed, implementation of SCIM (System for Cross-domain Identity Management RFC7643/7644) for use cloud-native kubernetes platforms. i2scim supports externalized access control decisions through OPA. SCIM is a RESTful HTTP API that can be used to provide a standardized way to provision accounts from Azure, Okta, PingIdentity and other providers and tools. SCIM can also be used as a backing identity store for OAuth and other authentication services.
Project: YugabyteDB (App Definition and Development / Database)
File: links.md

Ideas and Resources ================================================================================ Videos / Presentations -- French: https://www.youtube.com/watch?v=KGSlp4UygdU Chinese: https://www.youtube.com/watch?v=n9atI31FcSM Similar technologies -- Anonymous dump utility written in Golang A commandline tool for anonymizing PostgreSQL databases Anonymous dumps based on masking rules written in a YAML file Pseudononymous Access To Encrypted Table PostgreSQL extension implementing differential privacy (inactive) PostgreSQL extension implementing dynamic data anonymization Dump anonymized PostgreSQL database with a NodeJS CLI Similar Implementations -- GDPR -- Concepts -- Academic Research -- L. Sweeney. k-anonymity: a model for protecting privacy. International Journal on Uncertainty, Fuzziness and Knowledge-based Systems, 10 (5), 2002, pp. 557-570. <https://epic.org/wp-content/uploads/privacy/reidentification/Sweeney_Article.pdf> A. Narayanan and V. Shmatikov, Robust de-anonymization of large sparse datasets, in 29th IEEE Symposium on Security and Privacy, 2008, pp. 111125. <https://www.cs.cornell.edu/~shmat/shmat_oak08netflix.pdf>
Project: StarRocks (App Definition and Development / Database)
File: kafka_connector.md

displayed_sidebar: "English" User guide: Source codes: Naming format of the compressed file: `starrocks-kafka-connector-${connector_version}.tar.gz` Download link of the compressed file: Version requirements: | Kafka Connector | StarRocks | Java | | | | - | | 1.0.3 | 2.1 and later | 8 | | 1.0.2 | 2.1 and later | 8 | | 1.0.1 | 2.1 and later | 8 | | 1.0.0 | 2.1 and later | 8 | Release date: December 19, 2023 Features Added Apache License as the open-source software license. Release date: December 14, 2023 Features Supports the source data to be of DECIMAL type. Release date: November 28, 2023 Features Supports loading Debezium data into Primary Key tables. Supports parsing JSON data without schema registry. Release date: June 25, 2023 Features Supports loading CSV, JSON, Avro, and Protobuf data. Supports loading data from a self-managed Apache Kafka cluster or Confluent cloud.
Project: YugabyteDB (App Definition and Development / Database)
File: upgrade-yp-kubernetes.md

title: Upgrade YugabyteDB Anywhere installation on Kubernetes headerTitle: Upgrade YugabyteDB Anywhere linkTitle: Upgrade installation description: Upgrade YugabyteDB Anywhere installation on Kubernetes menu: v2.18_yugabyte-platform: identifier: upgrade-yp-3-kubernetes parent: upgrade weight: 80 type: docs <ul class="nav nav-tabs-alt nav-tabs-yb"> <li> <a href="../upgrade-yp-installer/" class="nav-link"> <i class="fa-solid fa-building"></i>YBA Installer</a> </li> <li> <a href="../upgrade-yp-replicated/" class="nav-link"> <i class="fa-solid fa-cloud"></i>Replicated</a> </li> <li> <a href="../upgrade-yp-kubernetes/" class="nav-link active"> <i class="fa-regular fa-dharmachakra" aria-hidden="true"></i>Kubernetes</a> </li> </ul> You can use to upgrade your YugabyteDB Anywhere installed on to a newer version. If you are upgrading a YugabyteDB Anywhere installation with high availability enabled, follow the instructions provided in . Before running an upgrade, execute the following command to obtain the latest versions of YugabyteDB Anywhere from Helm charts: ```sh helm repo update ``` To upgrade to a specific version while preserving overrides you might have applied to your initial YugabyteDB Anywhere installation or previous upgrades, execute the following command: ```sh helm upgrade yw-test yugabytedb/yugaware --version 2.15.2 -n yb-platform --reuse-values --set image.tag=2.15.2.0-b87 --wait ``` To obtain the value for `--set image.tag`, execute the following command: ```sh helm list | awk '{if (NR!=1) print $NF}' ``` If you do not wish to port your overrides, do not include `reuse-values`. Instead, you may choose to pass your existing overrides file by adding `--values custom-values.yaml` to your command during the upgrade. If you have upgraded YugabyteDB Anywhere to version 2.12 or later and for your universe was set up via `yb-admin` instead of the UI, follow the instructions provided in .
Project: StarRocks (App Definition and Development / Database)
File: bitmap_remove.md

displayed_sidebar: "English" Removes `input` from the Bitmap value `lhs` and returns a result set. ```Haskell bitmap_remove(BITMAP lhs, BIGINT input) ``` ```plain text mysql> select bitmaptostring(bitmap_remove(bitmapfromstring('1, 3'), 3)) cnt; ++ |cnt | ++ |1 | ++ mysql> select bitmaptostring(bitmap_remove(bitmapfromstring('1,3,5'), 6)) cnt; ++ |cnt | ++ |1,3,5 | ++ ``` BITMAP_REMOVE, BITMAP
Project: YugabyteDB (App Definition and Development / Database)
File: cloud-machine-types-analysis.md

This is an analysis of the most cost-effective AWS machines to run YugabyteDB. 3 nodes of 16 cores each with replication factor 3, fully cached workload can handle 100K reads and 20K writes. See for details. 3 nodes of 8 cores each with replication factor 3, fully uncached workload with 1.4TB total can handle77K read ops/sec. See for more details. The app needs between 1TB and 2TB of storage per node. Analyzed many other machine types, concluded they are not as effective to run YugabyteDB ``` machine-type vCPUs memory raw-cost storage-cost Total (1TB) Total (2TB) c5.2xlarge 8 16GiB $248/month +$100/TB/month $350/month $450/month c5.4xlarge 16 32GiB $496/month +$100/TB/month $600/month $700/month i3.2xlarge 8 61GiB $455/month +$0 (1.9TB disk) $455/month $455/month (1.9TB local SSD) ``` ](https://github.com/yugabyte/ga-beacon)
Project: Trivy (Provisioning / Security & Compliance)
File: data.md

Custom checks may require additional data in order to determine an answer. For example, an allowed list of resources that can be created. Instead of hardcoding this information inside your policy, Trivy allows passing paths to data files with the `--data` flag. Given the following yaml file: ```bash $ cd examples/misconf/custom-data $ cat data/ports.yaml [~/src/github.com/aquasecurity/trivy/examples/misconf/custom-data] services: ports: "20" "20/tcp" "20/udp" "23" "23/tcp" ``` This can be imported into your policy: ```rego import data.services ports := services.ports ``` Then, you need to pass data paths through `--data` option. Trivy recursively searches the specified paths for JSON (`.json`) and YAML (`.yaml`) files. ```bash $ trivy conf --policy ./policy --data data --namespaces user ./configs ```
Project: Chef Infra (Provisioning / Automation & Configuration)
File: debugging_effortless.md

There are some occasions in which Chef Infra Client runs in Effortless may fail. This document will help you debug those failures. In a Powershell console, run as administrator: ```powershell Set-ExecutionPolicy Bypass -Scope Process -Force Invoke-Expression ((New-Object System.Net.WebClient).DownloadString('https://raw.githubusercontent.com/habitat-sh/habitat/master/components/hab/install.ps1')) ``` (You may need to restart your shell after installing hab) ```powershell tar -xvf customer-export.tar.gz ``` ```powershell Copy-Item -Path customer-export\hab -Destination C:\hab -Recurse ``` or `start path\to\customer-export` and `start C:\` and drag/copy `hab` directory from the customer export to `C:\` In a Powershell console, run as administrator: ```powershell hab sup run ``` In a separate Powershell console, run as administrator: ```powershell hab svc load <origin>/<service> ``` This will output to `c:\hab\svc\<service>\...` The service will start up based on an interval of seconds defined in `c:\hab\pkgs\<origin>\<service>\...\default.toml`: ```toml interval = 14400 splay = 7200 splayfirstrun = 1000 runlocktimeout = 600 log_level = "info" envpathprefix = ";C:/WINDOWS;C:/WINDOWS/system32/;C:/WINDOWS/system32/WindowsPowerShell/v1.0;" [chef_license] acceptance = "accept-no-persist" ``` You can see the loop that runs this in `c:\hab\pkgs\<origin>\<service>\...\hooks\run` to see how the intervals are used. The `hab sup run` window will display any output from the service run. If an error occurs that results in a stacktrace, the stacktrace will be output to the `sup` window, such as `C:/hab/svc/<service>/data/cache/cache/chef-stacktrace.out` If you want to make changes to the service, `hab svc unload <origin>/<service>` and make changes to the files in the `c:\hab\pkgs\<origin>\<service>` directory, Then, `hab svc load <origin>/<service>` to start the service again.
Project: KICS (Provisioning / Security & Compliance)
File: 0a592060-8166-49f5-8e65-99ac6dce9871.md

title: Role With Privilege Escalation By Actions 'glue:CreateDevEndpoint' And 'iam:PassRole' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 0a592060-8166-49f5-8e65-99ac6dce9871 Query name: Role With Privilege Escalation By Actions 'glue:CreateDevEndpoint' And 'iam:PassRole' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Role with privilege escalation by actions 'glue:CreateDevEndpoint' and 'iam:PassRole' and Resource set to '*'. For more information see https://rhinosecuritylabs.com/aws/aws-privilege-escalation-methods-mitigation/.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsiamrole" "cosmic" { name = "cosmic" } resource "awsiamrolepolicy" "testinline_policy" { name = "testinlinepolicy" role = awsiamrole.cosmic.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "glue:CreateDevEndpoint", ] Effect = "Allow" Resource = "*" }, ] }) } resource "awsiampolicy_attachment" "test-attach" { name = "test-attachment" roles = [awsiamrole.cosmic.name] policyarn = awsiam_policy.policy.arn } resource "awsiampolicy" "policy" { name = "test-policy" description = "A test policy" policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "iam:PassRole", ] Effect = "Allow" Resource = "*" }, ] }) } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamuser" "cosmic2" { name = "cosmic2" } resource "awsiamuserpolicy" "inlinepolicyruninstances2" { name = "inlinepolicyrun_instances" user = awsiamuser.cosmic2.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "ec2:Describe*", ] Effect = "Allow" Resource = "*" }, ] }) } ```
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.0.22.1.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Minor | Allow wildcards to be used in ProxyUsers configurations* When configuring proxy users and hosts, the special wildcard value "\*" may be specified to match any host or any user. | Major | add Kerberos HTTP SPNEGO authentication support to Hadoop JT/NN/DN/TT web-consoles* Adding support for Kerberos HTTP SPNEGO authentication to the Hadoop web-consoles | Major | Shortcut a local client reads to a Datanodes files directly* New configurations a. dfs.block.local-path-access.user is the key in datanode configuration to specify the user allowed to do short circuit read. b. dfs.client.read.shortcircuit is the key to enable short circuit read at the client side configuration. c. dfs.client.read.shortcircuit.skip.checksum is the key to bypass checksum check at the client side. By default none of the above are enabled and short circuit read will not kick in. If security is on, the feature can be used only for user that has kerberos credentials at the client, therefore map reduce tasks cannot benefit from it in general. | Major | Hadoop 22 hadoop job -list returns user name as NULL* Submitting the patch after setting the user name at the client side | Minor | Hadoop wrapper script shouldn't ignore an existing JAVA\_LIBRARY\_PATH* WARNING: No release note provided for this change.
Project: Meshery (Provisioning / Automation & Configuration)
File: cubefs.md

layout: integration title: Cubefs subtitle: Collaborative and visual infrastructure as code for Cubefs image: /assets/img/integrations/cubefs/icons/color/cubefs-color.svg permalink: extensibility/integrations/cubefs docURL: https://docs.meshery.io/extensibility/integrations/cubefs description: integrations-category: Runtime integrations-subcategory: Cloud Native Storage registrant: Artifact Hub components: featureList: [ "Multiple Access Protocol Support.", "Elasticity, scalability and strong consistency of metadata.", "Specific performance optimizations for large/small files and sequential/random writes." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: Ansible (Provisioning / Automation & Configuration)
File: collections.md

Hi! Thank you very much for your submission to Ansible. It means a lot to us that you've taken the time to contribute. Since Ansible 2.10 we are no longer accepting new modules/plugins into Ansible core. However, we recommend looking into providing this functionality through Ansible Galaxy via Ansible Collections. You can find more information about collections at: <https://docs.ansible.com/ansible/devel/devguide/developingcollections.html>. Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time. The mailing list and irc are great ways to ask questions, or post if you don't think this particular issue is resolved. See this page for a complete and up to date list of communication channels and their purposes: <https://docs.ansible.com/ansible/latest/community/communication.html> Thank you once again for this and your interest in Ansible!
Project: Polaris (Provisioning / Security & Compliance)
File: contributing.md

meta: name: description content: "Fairwinds Polaris | Contribution Guidelines" Issues, whether bugs, tasks, or feature requests are essential for keeping Polaris great. We believe it should be as easy as possible to contribute changes that get things working in your environment. There are a few guidelines that we need contributors to follow so that we can keep on top of things. This project adheres to a . Please review this document before contributing to this project. Before you can contribute, you will need to sign the . Polaris is built on top of . It can run in 3 different modes, a dashboard, a webhook, or a reporter that prints or exports validation results. All of these modes make use of the shared `validator` and `config` packages. Adding new validations is possible by only making additions to those packages. We label issues with the if we believe they'll be a good starting point for new contributors. If you're interested in working on an issue, please start a conversation on that issue, and we can help answer any questions as they come up. A properly configured Golang environment with Go 1.11 or higher If you want to see the local changes you make on a Polaris dashboard, you will need access to a Kubernetes cluster defined in `~/.kube/config` Install the project with `go get github.com/fairwindsops/polaris` Change into the polaris directory which is installed at `$GOPATH/src/github.com/fairwindsops/polaris` See the dashboard with `go run main.go dashboard`, then open http://localhost:8080/ See the audit data `go run main.go audit`. This command shows the audit information on the command line. The following commands are all required to pass as part of Polaris testing: ```bash go list ./... | grep -v vendor | xargs golint -setexitstatus go list ./... | grep -v vendor | xargs go vet go test ./pkg/... -v -coverprofile cover.out ``` ```bash kind create cluster --wait=90s --image kindest/node:v1.15.11 --name polaris-test docker build -t quay.io/fairwinds/polaris:debug . # or use your own registry docker push quay.io/fairwinds/polaris:debug helm repo add jetstack https://charts.jetstack.io helm install cert-manager jetstack/cert-manager --namespace cert-manager --version v1.12.1 --set "installCRDs=true" --wait POLARISIMAGE=quay.io/fairwinds/polaris:debug ./test/webhooktest.sh ``` to avoid the final cleanup for debugging purposes, you can run ```bash SKIPFINALCLEANUP=true IMAGETAG=debug ./test/webhooktest.sh ``` If you've encountered an issue that is not already reported, please create a , choose `Bug Report`, `Feature Request` or `Misc.` and follow the instructions in the template. Each new pull request should: Reference any related issues Add tests that show the issues have been solved Pass existing tests and linting Contain a clear indication of if they're ready for review, or a work in progress Be up to date and/or rebased on the master branch To create a new release, simply tag this repo with the new version. For major and minor releases, don't forget to update the Helm chart at https://github.com/FairwindsOps/charts
Project: YugabyteDB (App Definition and Development / Database)
File: jsonb-build-object.md

title: jsonbbuildobject() and jsonbuildobject() headerTitle: jsonbbuildobject() and jsonbuildobject() linkTitle: jsonbbuildobject() description: Build a JSON object from a variadic list that specifies keys with values of arbitrary SQL data type. menu: v2.18: identifier: jsonb-build-object parent: json-functions-operators weight: 100 type: docs Purpose: Create a JSON object from a variadic list that specifies keys with values of arbitrary SQL data type. Signature For the `jsonb` variant: ``` input value: VARIADIC "any" return value: jsonb ``` Notes: The key names are given as SQL `text` values. The SQL data type of key's value argument must have a direct JSON equivalent or allow implicit conversion to such an equivalent. The `jsonbbuildobject()` variadic function is the obvious counterpart to . The argument list has the form: ``` key1::text, value1::thedatatype1, key1::text, value2::thedatatype2, ... keyN::text, valueN::thedatatypeN ``` Use this `ysqlsh` script to create the required type "t" and then to execute the `ASSERT`. ```plpgsql create type t as (a int, b text); do $body$ declare v_17 constant int := 17; v_dog constant text := 'dog'; v_true constant boolean := true; v_t constant t := (17::int, 'cat'::text); j constant jsonb := jsonbbuildobject( 'a', v_17, 'b', v_dog, 'c', v_true, 'd', v_t); expected_j constant jsonb := '{"a": 17, "b": "dog", "c": true, "d": {"a": 17, "b": "cat"}}'; begin assert j = expected_j, 'unexpected'; end; $body$; ``` Just as with , using `jsonbbuildobject()` is straightforward when you know the structure of your target JSON value statically, and just discover the values dynamically. But again, it doesn't accommodate the case that you discover the desired structure dynamically. The following `ysqlsh` script shows a feasible general workaround for this use case. The helper function "f()" generates the variadic argument list as the text representation of a comma-separated list of SQL literals of various data types. Then it invokes `jsonbbuildobject()` dynamically. Obviously this brings a performance cost. But you might not have an alternative. ```plpgsql create function f(variadicarrayelements in text) returns jsonb language plpgsql as $body$ declare stmt text := ' select jsonbbuildobject('||variadicarrayelements||')'; j jsonb; begin execute stmt into j; return j; end; $body$; -- Relies on "type t as (a int, b text)" created above. do $body$ declare v_17 constant int := 17; v_dog constant text := 'dog'; v_true constant boolean := true; v_t constant t := (17::int, 'cat'::text); expectedj constant jsonb := jsonbbuild_object( 'a', v_17, 'b', v_dog, 'c', v_true, 'd', v_t); j constant jsonb := f( $$ 'a'::text, 17::integer, 'b'::text, 'dog'::text, 'c'::text, true::boolean, 'd'::text, (17::int, 'cat'::text)::t $$); begin assert j = expected_j, 'unexpected'; end; $body$; ```
Project: Pluto (Provisioning / Security & Compliance)
File: orb.md

meta: name: description content: "Fairwinds Pluto | Fairwinds publishes an orb called fairwinds/pluto to provide easier configuration inside of CircleCI." CircleCI has introduced the concept of reusable config in the form of . As of pluto v5.1, Fairwinds publishes an orb called in order to provide easier configuration inside of CircleCI.