cwielenb/CNCF-Dataset huggingface dataset:
Project: StarRocks (App Definition and Development / Database)
File: DROP_MATERIALIZED_VIEW.md

displayed_sidebar: "English" Drops a materialized view. You cannot drop a synchronous materialized view that is being created in process with this command. To drop a synchronous materialized view that is being created in process, see for further instructions. :::tip This operation requires the DROP privilege on the target materialized view. ::: ```SQL DROP MATERIALIZED VIEW [IF EXISTS] [database.]mv_name ``` Parameters in brackets [] is optional. | Parameter | Required | Description | | - | | | | IF EXISTS | no | If this parameter is specified, StarRocks will not throw an exception when deleting a materialized view that does not exist. If this parameter is not specified, the system will throw an exception when deleting a materialized view that does not exist. | | mv_name | yes | The name of the materialized view to delete. | Example 1: Drop an existing materialized view View all existing materialized views in the database. ```Plain MySQL > SHOW MATERIALIZED VIEWS\G row * id: 470740 name: order_mv1 databasename: defaultcluster:sr_hub text: SELECT `srhub`.`orders`.`dt` AS `dt`, `srhub`.`orders`.`orderid` AS `orderid`, `srhub`.`orders`.`userid` AS `userid`, sum(`srhub`.`orders`.`cnt`) AS `totalcnt`, sum(`srhub`.`orders`.`revenue`) AS `totalrevenue`, count(`srhub`.`orders`.`state`) AS `statecount` FROM `srhub`.`orders` GROUP BY `srhub`.`orders`.`dt`, `srhub`.`orders`.`orderid`, `srhub`.`orders`.`user_id` rows: 0 1 rows in set (0.00 sec) ``` Drop the materialized view `order_mv1`. ```SQL DROP MATERIALIZED VIEW order_mv1; ``` Check if the dropped materialized view exists. ```Plain MySQL > SHOW MATERIALIZED VIEWS; Empty set (0.01 sec) ``` Example 2: Drop a non-existing materialized view If the parameter `IF EXISTS` is specified, StarRocks will not throw an exception when deleting a materialized view that does not exist. ```Plain MySQL > DROP MATERIALIZED VIEW IF EXISTS k1_k2; Query OK, 0 rows affected (0.00 sec) ``` If the parameter `IF EXISTS` is not specified, the system will throw an exception when deleting a materialized view that does not exist. ```Plain MySQL > DROP MATERIALIZED VIEW k1_k2; ERROR 1064 (HY000): Materialized view k1_k2 is not find ```
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_drop_foreign_data_wrapper.md

title: DROP FOREIGN DATA WRAPPER statement [YSQL] headerTitle: DROP FOREIGN DATA WRAPPER linkTitle: DROP FOREIGN DATA WRAPPER description: Use the DROP FOREIGN DATA WRAPPER statement to drop a foreign-data wrapper. menu: v2.18: identifier: ddldropforeigndatawrapper parent: statements type: docs Use the `DROP FOREIGN DATA WRAPPER` command to remove a foreign-data wrapper. The user who executes the command must be the owner of the foreign-data wrapper. {{%ebnf%}} dropforeigndata_wrapper {{%/ebnf%}} Drop a foreign-data wrapper named fdw_name. If it doesnt exist in the database, an error will be thrown unless the `IF EXISTS` clause is used. `RESTRICT` is the default and it will not drop the foreign-data wrapper if any objects depend on it. `CASCADE` will drop the foreign-data wrapper and any objects that transitively depend on it. Drop the foreign-data wrapper `my_wrapper`, along with any objects that depend on it. ```plpgsql yugabyte=# DROP FOREIGN DATA WRAPPER my_wrapper CASCADE; ```
Project: KICS (Provisioning / Security & Compliance)
File: 3ddfa124-6407-4845-a501-179f90c65097.md

title: Authentication Without MFA hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 3ddfa124-6407-4845-a501-179f90c65097 Query name: Authentication Without MFA Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Access Control URL: Users should authenticate with MFA (Multi-factor Authentication) to ensure an extra layer of protection when authenticating<br> ```tf title="Positive test num. 1 - tf file" hl_lines="23" provider "aws" { region = "us-east-1" } resource "awsiamuser" "positive1" { name = "aws-foundations-benchmark-1-4-0-terraform-user" path = "/" } resource "awsiamuserloginprofile" "positive1" { user = awsiamuser.positive1.name pgp_key = "gpgkeybase64gpgkeybase64gpgkeybase64gpgkeybase64" } resource "awsiamaccess_key" "positive1" { user = awsiamuser.positive1.name } resource "awsiamuser_policy" "positive1" { name = "aws-foundations-benchmark-1-4-0-terraform-user" user = awsiamuser.positive1.name policy = <<EOF { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Resource": "${awsiamuser.positive1.arn}", "Action": "sts:AssumeRole", "Condition": { "BoolIfExists": { "aws:MultiFactorAuthPresent" : "false" } } } ] } EOF } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="19" provider "aws" { region = "us-east-1" } resource "awsiamuser" "positive1" { name = "aws-foundations-benchmark-1-4-0-terraform-user" path = "/" } resource "awsiamuserloginprofile" "positive2" { user = awsiamuser.positive2.name pgp_key = "gpgkeybase64gpgkeybase64gpgkeybase64gpgkeybase64" } resource "awsiamuser_policy" "positive2" { name = "aws-foundations-benchmark-1-4-0-terraform-user" user = awsiamuser.positive2.name policy = <<EOF { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Resource": "${awsiamuser.positive2.arn}", "Action": "sts:AssumeRole" } ] } EOF } ``` ```tf title="Negative test num. 1 - tf file" provider "aws" { region = "us-east-1" } resource "awsiamuser" "negative1" { name = "aws-foundations-benchmark-1-4-0-terraform-user" path = "/" } resource "awsiamuserloginprofile" "negative1" { user = awsiamuser.negative1.name pgp_key = "gpgkeybase64gpgkeybase64gpgkeybase64gpgkeybase64" } resource "awsiamaccess_key" "negative1" { user = awsiamuser.negative1.name } resource "awsiamuser_policy" "negative1" { name = "aws-foundations-benchmark-1-4-0-terraform-user" user = awsiamuser.negative1.name policy = <<EOF { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Resource": ${awsiamuser.negative1.arn}, "Action": "sts:AssumeRole", "Condition": { "BoolIfExists": { "aws:MultiFactorAuthPresent" : "true" } } } ] } EOF } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: aperture-controller.md

layout: integration title: Aperture Controller subtitle: Collaborative and visual infrastructure as code for Aperture Controller image: /assets/img/integrations/aperture-controller/icons/color/aperture-controller-color.svg permalink: extensibility/integrations/aperture-controller docURL: https://docs.meshery.io/extensibility/integrations/aperture-controller description: integrations-category: Orchestration & Management integrations-subcategory: Scheduling & Orchestration registrant: Artifact Hub components: name: controller colorIcon: assets/img/integrations/aperture-controller/components/controller/icons/color/controller-color.svg whiteIcon: assets/img/integrations/aperture-controller/components/controller/icons/white/controller-white.svg description: name: policy colorIcon: assets/img/integrations/aperture-controller/components/policy/icons/color/policy-color.svg whiteIcon: assets/img/integrations/aperture-controller/components/policy/icons/white/policy-white.svg description: featureList: [ "Monitor golden signals to rapidly detect service deterioration and load build-up.", "Adjusts the concurrency limit of the service.", "Regulate and prioritize flows based on rules via a scheduler." ] 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: secureCodeBox (Provisioning / Security & Compliance)
File: 07_deployment_view.md

title: "Deployment View" sidebar_label: "Deployment View" sidebar_position: 7 This section describes the deployment of secureCodeBox. We do not cover all possible deployments, and instead concentrate on the most common scenarios. Cluster internal security scans with one dedicated namespace. The whole secureCodeBox with all Scan Types are deployed in the same namespace. :::note The S3 Bucket, the optional build pipline ( is just an example, may be any other CI/CD tool), and the vulnerability management system ( is just an example, it may be any other VMS) are deployd on different nodes in the diagram above. It is also possible to deploy them in the same cluster, on a different cluster, pr on a bare-metal machine or somewhere in the cloud. ::: The motivation behind this scenario is to have one central point to accumulate all findings of all scanned namespaces. Typically, this scenario is for a team which wants to monitor a whole landscape of applications and services (e.g. a security operations (SOC) team). Cluster internal security scans directly in the business service's namespace. Only the engine (operator, lurker, hooks) are deployed in a central dedicated namespace. The Scan Types are deployed into the namespaces of the scanned application. :::note The S3 Bucket, the optional build pipline ( is just an example, may be any other CI/CD tool), and the vulnerability management system ( is just an example, it may be any other VMS) are deployd on different nodes in the diagram above. It is also possible to deploy them in the same cluster, on a different cluster, pr on a bare-metal machine or somewhere in the cloud. ::: The motivation behind this scenario is to provide each development team its own instance of secureCodeBox. The common parts like operator is shared, but each team deploys its own scans inside their namespace. Typically, you will use this scenario if you do not want to allow teams to see the findings of other teams.
Project: Apache Hadoop (App Definition and Development / Database)
File: SystemServices.md

<! 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. See accompanying LICENSE file. --> System services are admin configured services which are auto deployed during bootstrap of ResourceManager. This would work only when API-Server is started as part of ResourceManager. Refer . This document describes how to configure and deploy system services. | Name | Description | | | - | |yarn.service.system-service.dir| FS directory path to load and deploy admin configured services. These service spec files should be kept with proper hierarchy.| After configuring yarn.service.system-service.dir path, the spec files should be kept with below hierarchy. ```` $SYSTEMSERVICEDIR_PATH/<Launch-Mode>/<Users>/<Yarnfiles>. ```` Launch-Mode indicates that how the service should be deployed. Services can be auto deployed either synchronously or asynchronously. These services are started synchronously along with RM. This might delay a bit RM transition to active period. This is useful when deploying critical services to get started sooner. These services are started asynchronously without impacting RM transition period. Users are the owner of the system service who has full access to modify it. Each users can own multiple services. Note that service names are unique per user. YarnFiles are the spec files to launch services. These files must have .yarnfile extension otherwise those files are ignored. ``` SYSTEMSERVICEDIR_PATH |- sync | | user1 | | |- service1.yarnfile | | |- service2.yarnfile | | user2 | | |- service3.yarnfile | | .... | | |- async | | user3 | | |- service1.yarnfile | | |- service2.yarnfile | | user4 | | |- service3.yarnfile | | .... | | ```
Project: ArangoDB (App Definition and Development / Database)
File: hook_result_in_place_construction.md

+++ title = "`void hookresultinplaceconstruction(T *, inplacetype_t<U>, Args &&...) noexcept`" description = "(Until v2.2.0) ADL discovered free function hook invoked by the in-place constructors of `basic_result`." +++ Removed in Outcome v2.2.0, unless {{% api "BOOSTOUTCOMEENABLELEGACYSUPPORT_FOR" %}} is set to less than `220` to enable emulation. Use {{% api "onresultinplaceconstruction(T *, inplacetype_t<U>, Args &&...) noexcept" %}} instead in new code. One of the constructor hooks for {{% api "basicresult<T, E, NoValuePolicy>" %}}, generally invoked by the in-place constructors of `basicresult`. See each constructor's documentation to see which specific hook it invokes. Overridable: By Argument Dependent Lookup. Requires: Nothing. Namespace: `BOOSTOUTCOMEV2_NAMESPACE::hooks` Header: `<boost/outcome/basic_result.hpp>`
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_monitor_get-alerts.md

title: Kubectl-Dba Monitor Get-Alerts menu: docs_{{ .version }}: identifier: kubectl-dba-monitor-get-alerts name: Kubectl-Dba Monitor Get-Alerts parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Alerts associated with a database Get the prometheus alerts for a specific database in just one command ``` kubectl-dba monitor get-alerts ``` ``` kubectl dba monitor get-alerts [DATABASE] [DATABASE_NAME] -n [NAMESPACE] \ --prom-svc-name=[PROMSVCNAME] --prom-svc-namespace=[PROMSVCNS] --prom-svc-port=[PROMSVCPORT] kubectl dba monitor get-alerts mongodb sample-mongodb -n demo \ --prom-svc-name=prometheus-kube-prometheus-prometheus --prom-svc-namespace=monitoring --prom-svc-port=9090 Valid resource types include: elasticsearch kafka mariadb mongodb mysql perconaxtradb postgres proxysql redis ``` ``` -h, --help help for get-alerts ``` ``` --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 --prom-svc-name string name of the prometheus service --prom-svc-namespace string namespace of the prometheus service --prom-svc-port int port of the prometheus service (default 9090) --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 ``` - Monitoring related commands for a database
Project: Anchore (Provisioning / Security & Compliance)
File: PULL_REQUEST_TEMPLATE.md

<!-- Thank you for contributing to anchore-engine! We really appreciate your time and effort to help out the community. Before submitting this PR, we'd like to make sure you are aware of our technical requirements and PR process. https://github.com/anchore/anchore-engine/tree/master/CONTRIBUTING.rst When updates to your PR are requested, please add new commits and do not squash the history. This will make it easier to identify new changes. The PR will be squashed when we merge it to ensure a clean history. Thanks. --> What this PR does / why we need it: Which issue this PR fixes (optional, in `fixes #<issue number>)(, fixes #<issue_number, ...)` format, will close the issue when PR is merged: fixes #: Special notes:
Project: KICS (Provisioning / Security & Compliance)
File: 7c96920c-6fd0-449d-9a52-0aa431b6beaf.md

title: Role With Privilege Escalation By Actions 'iam:AttachUserPolicy' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 7c96920c-6fd0-449d-9a52-0aa431b6beaf Query name: Role With Privilege Escalation By Actions 'iam:AttachUserPolicy' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Role with privilege escalation by actions 'iam:AttachUserPolicy' 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 = [ "iam:AttachUserPolicy", ] 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: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: e5.2.1.en.md

The bcrypt work factor is limited to the range 5-10, because higher values consume too much CPU resources. Bcrypt library is updated to allow parallel hash evaluation. Improve some error reasons when parsing invalid packets. Added support for defining templates for MQTT 5.0 publish properties and user properties in Republish rule action. During node evacuation, evacuate all disconnected sessions, not only those started with `clean_start` set to `false`. Examples and documentation for /api/v5/publish bad request response have been fixed. Previously the documentation example said that the bad request response could return a list in the body which was not actually the case. Upgrade Erlang/OTP to 25.3.2-2 Erlang/OTP 25.3.2-2 excludes sensitive data from mnesia_hook log message. Don't download a trace log file if it is empty. After this fix, GET `/api/v5/trace/clientempty/download` returns 404 `{"code":"NOT_FOUND","message":"Trace is empty"}` If no events matching the trace condition occurred. Improved error message for rule engine schema registry when schema name exceeds permissible length. Fixed issue where authorization cache cleaning cli was not working properly for specific client ID. Fix cluster partition autoheal functionality. Implement autohealing for the clusters that split into multiple partitions. Fixed an issue where an ill-defined built-in rule action config could be interpreted as a custom user function. Upgrade Kafka producer client `wolff` from 1.7.6 to 1.7.7. This fixes a potential race condition which may cause all Kafka producers to crash if some failed to initialize. When running one of the rule engine SQL `mongo_date` functions in the EMQX dashboard test interface, the resulting date is formatted as `ISODate()`, where is the date in ISO date format instead of only the ISO date string. This is the format used by MongoDB to store dates. Fix several emqx_bridge issues: fix Cassandra bridge connect error occurring when the bridge is configured without username/password (Cassandra doesn't require user credentials when it is configured with `authenticator: AllowAllAuthenticator`) fix SQL Server bridge connect error caused by an empty password make `username` a required field in Oracle bridge fix IoTDB bridge error caused by setting base URL without scheme (e.g. `<host>:<port>`) Fixed an issue where the core node could get stuck in the `mria_schema:bootstrap/0` state, preventing new nodes from joining the cluster.
Project: ShardingSphere (App Definition and Development / Database)
File: show-mask-rule.en.md

+++ title = "SHOW MASK RULES" weight = 1 +++ The `SHOW MASK RULES` syntax is used to query mask rules for specified database. {{< tabs >}} {{% tab name="Grammar" %}} ```sql ShowMaskRule::= 'SHOW' 'MASK' ('RULES' | 'RULE' ruleName) ('FROM' databaseName)? ruleName ::= identifier databaseName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} When `databaseName` is not specified, the default is the currently used `DATABASE`. If `DATABASE` is not used, `No database selected` will be prompted. | Column | Description | |--|| | table | Table name | | column | Column name | | algorithm_type | Mask algorithm type | | algorithm_props | Mask algorithm properties | Query mask rules for specified database ```sql SHOW MASK RULES FROM mask_db; ``` ```sql mysql> SHOW MASK RULES FROM mask_db; ++-++--+ | table | column | algorithmtype | algorithmprops | ++-++--+ | tmask | phoneNum | MASKFROMXTO_Y | to-y=2,replace-char=*,from-x=1 | | t_mask | address | MD5 | | | torder | orderid | MD5 | | | tuser | userid | MASKFROMXTOY | to-y=2,replace-char=*,from-x=1 | ++-++--+ 4 rows in set (0.01 sec) ``` Query mask rules for current database ```sql SHOW MASK RULES; ``` ```sql mysql> SHOW MASK RULES; ++-++--+ | table | column | algorithmtype | algorithmprops | ++-++--+ | tmask | phoneNum | MASKFROMXTO_Y | to-y=2,replace-char=*,from-x=1 | | t_mask | address | MD5 | | | torder | orderid | MD5 | | | tuser | userid | MASKFROMXTOY | to-y=2,replace-char=*,from-x=1 | ++-++--+ 4 rows in set (0.01 sec) ``` Query specified mask rule for specified database ```sql SHOW MASK RULE tmask FROM maskdb; ``` ```sql mysql> SHOW MASK RULE tmask FROM maskdb; +--+--++--+ | table | logiccolumn | maskalgorithm | props | +--+--++--+ | tmask | phoneNum | MASKFROMXTO_Y | to-y=2,replace-char=*,from-x=1 | | t_mask | address | MD5 | | +--+--++--+ 2 rows in set (0.00 sec) ``` Query specified mask rule for current database ```sql SHOW MASK RULE t_mask; ``` ```sql mysql> SHOW MASK RULE t_mask; +--+--++--+ | table | logiccolumn | maskalgorithm | props | +--+--++--+ | tmask | phoneNum | MASKFROMXTO_Y | to-y=2,replace-char=*,from-x=1 | | t_mask | address | MD5 | | +--+--++--+ 2 rows in set (0.00 sec) ``` `SHOW`, `MASK`, `RULE`, `RULES`, `FROM`