cwielenb/CNCF-Dataset huggingface dataset:
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_cluster_delete-ops.md

title: kbcli cluster delete-ops Delete an OpsRequest. ``` kbcli cluster delete-ops [flags] ``` ``` kbcli cluster delete-ops mycluster kbcli cluster delete-ops --name=mysql-restart-82zxv ``` ``` -A, --all-namespaces If present, list the requested object(s) across all namespaces. Namespace in current context is ignored even if specified with --namespace. --auto-approve Skip interactive approval before deleting --force If true, immediately remove resources from API and bypass graceful deletion. Note that immediate deletion of some resources may result in inconsistency or data loss and requires confirmation. --grace-period int Period of time in seconds given to the resource to terminate gracefully. Ignored if negative. Set to 1 for immediate shutdown. Can only be set to 0 when --force is true (force deletion). (default -1) -h, --help help for delete-ops --name strings OpsRequest names --now If true, resources are signaled for immediate shutdown (same as --grace-period=1). -l, --selector string Selector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - Cluster command.
Project: YugabyteDB (App Definition and Development / Database)
File: type_inet.md

title: INET data type [YCQL] headerTitle: INET type linkTitle: INET description: Use the INET data type to specify columns for data of IP addresses. menu: v2.18: parent: api-cassandra weight: 1410 type: docs Use the `INET` data type to specify columns for data of IP addresses. ``` type_specification ::= INET ``` Columns of type `INET` can be part of the `PRIMARY KEY`. Implicitly, values of type `INET` data types are neither convertible nor comparable to other data types. Values of text data types with correct format are convertible to `INET`. `INET` value format supports text literals for both IPv4 and IPv6 addresses. ```sql example> CREATE TABLE dnstable(sitename TEXT PRIMARY KEY, ip_address INET); ``` ```sql example> INSERT INTO dnstable(sitename, ip_address) VALUES ('localhost', '127.0.0.1'); ``` ```sql example> INSERT INTO dnstable(sitename, ip_address) VALUES ('example.com', '93.184.216.34'); ``` `INET` type supports both ipv4 and ipv6 addresses. ```sql example> UPDATE dnstable SET ipaddress = '2606:2800:220:1:248:1893:25c8:1946' WHERE site_name = 'example.com'; ``` ```sql example> SELECT * FROM dns_table; ``` ``` sitename | ipaddress -+ example.com | 2606:2800:220:1:248:1893:25c8:1946 localhost | 127.0.0.1 ```
Project: YugabyteDB (App Definition and Development / Database)
File: dcl_alter_group.md

title: ALTER GROUP statement [YSQL] headerTitle: ALTER GROUP linkTitle: ALTER GROUP description: Use the `ALTER GROUP` statement to alter attributes for a group (role). menu: v2.18: identifier: dclaltergroup parent: statements type: docs Use the `ALTER GROUP` statement to alter attributes for a group (role). This is added for compatibility with Postgres. Its usage is discouraged. is the preferred way to change attributes of a role. {{%ebnf%}} alter_group, role_specification, altergrouprename {{%/ebnf%}} See for more details. `ALTER GROUP` can be used to add or remove roles from a group. Please use or instead. It can also be used to rename a role.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: runit_service.md

+++ title = "runit_service resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "runit_service" identifier = "inspec/resources/os/runitservice.md runitservice resource" parent = "inspec/resources/os" +++ Use the `runit_service` Chef InSpec audit resource to test a service using runit. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.0.0 of InSpec. A `runit_service` resource block declares the name of a service and then one (or more) matchers to test the state of the service: describe runitservice('servicename') do it { should be_installed } it { should be_enabled } it { should be_running } end where `('service_name')` must specify a service name `beinstalled`, `beenabled`, and `be_running` are valid matchers for this resource; all matchers available to the `service` resource may be used The path to the service manager's control may be specified for situations where the path isn't available in the current `PATH`. For example: describe runitservice('servicename', '/path/to/control') do it { should be_enabled } it { should be_installed } it { should be_running } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The `be_enabled` matcher tests if the named service is enabled: it { should be_enabled } The `be_installed` matcher tests if the named service is installed: it { should be_installed } The `be_running` matcher tests if the named service is running: it { should be_running }
Project: KICS (Provisioning / Security & Compliance)
File: 66cd88ac-9ddf-424a-b77e-e55e17630bee.md

title: Batch Job Definition With Privileged Container Properties hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 66cd88ac-9ddf-424a-b77e-e55e17630bee Query name: Batch Job Definition With Privileged Container Properties Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Insecure Configurations URL: Batch Job Definition should not have Privileged Container Properties<br> ```tf title="Positive test num. 1 - tf file" hl_lines="11" resource "awsbatchjob_definition" "positive1" { name = "tftestbatchjobdefinition" type = "container" containerproperties = <<CONTAINERPROPERTIES { "command": ["ls", "-la"], "image": "busybox", "memory": 1024, "vcpus": 1, "privileged": true, "volumes": [ { "host": { "sourcePath": "/tmp" }, "name": "tmp" } ], "environment": [ {"name": "VARNAME", "value": "VARVAL"} ], "mountPoints": [ { "sourceVolume": "tmp", "containerPath": "/tmp", "readOnly": false } ], "ulimits": [ { "hardLimit": 1024, "name": "nofile", "softLimit": 1024 } ] } CONTAINER_PROPERTIES } ``` ```tf title="Negative test num. 1 - tf file" resource "awsbatchjob_definition" "negative1" { name = "tftestbatchjobdefinition" type = "container" containerproperties = <<CONTAINERPROPERTIES { "command": ["ls", "-la"], "image": "busybox", "memory": 1024, "vcpus": 1, "privileged": false, "volumes": [ { "host": { "sourcePath": "/tmp" }, "name": "tmp" } ], "environment": [ {"name": "VARNAME", "value": "VARVAL"} ], "mountPoints": [ { "sourceVolume": "tmp", "containerPath": "/tmp", "readOnly": false } ], "ulimits": [ { "hardLimit": 1024, "name": "nofile", "softLimit": 1024 } ] } CONTAINER_PROPERTIES } resource "awsbatchjob_definition" "negative2" { name = "tftestbatchjobdefinition2" type = "container" containerproperties = <<CONTAINERPROPERTIES { "command": ["ls", "-la"], "image": "busybox", "memory": 1024, "vcpus": 1, "volumes": [ { "host": { "sourcePath": "/tmp" }, "name": "tmp" } ], "environment": [ {"name": "VARNAME", "value": "VARVAL"} ], "mountPoints": [ { "sourceVolume": "tmp", "containerPath": "/tmp", "readOnly": false } ], "ulimits": [ { "hardLimit": 1024, "name": "nofile", "softLimit": 1024 } ] } CONTAINER_PROPERTIES } ```
Project: Open Application Model (App Definition and Development / Application Definition & Image Build)
File: 1.purpose_and_goals.md

The goal of Open Application Model is to define a standard, infrastructure-agnostic way to describe application deployment across hybrid environments, clouds or even edge devices. The central problem this model seeks to address is how distributed applications can be composed and then successfully handed off to those responsible for operating them. The problem is not so much about how to write programs, but how to take components of a service oriented (or microservice oriented) architecture, and streamline the workflow that surrounds such applications. For example, a contemporary cloud application may be composed of dozens of microservices, each responsible for a discrete chunk of what, broadly speaking, is "an application." Such applications need to be configured, deployed, audited, updated, and deleted. Sometimes the application must be treated as a whole, and sometimes finer levels of granularity are required. And most importantly, often such applications are managed not by one person or one team, but by multiple teams who must cooperate to achieve reliability, stability, and timeliness. This model provides a description of such workflow, where the description itself is declarative, extensible and with best clarity. Furthermore, it suggests patterns and processes for operating such applications. The model will focus on cloud native (i.e. highly distributed) applications, encompass public cloud technologies, on-prem solutions, and IoT/edge technologies. This sets a solid foundation for modern application delivery systems with a standard yet higher level description of cloud native application deployment. Non-goals include: Defining or prescribing specific orchestrating tool. Defining the schemas of operational resources, for example (but not limited to): Secrets (secure, encrypted values) Networks Volumes Describing or defining the runtime infrastructures themselves. | Next Part | | - | | |
Project: YugabyteDB (App Definition and Development / Database)
File: hset.md

title: HSET linkTitle: HSET description: HSET menu: preview: parent: api-yedis weight: 2180 aliases: /preview/api/redis/hset /preview/api/yedis/hset type: docs `HSET key field value` This command sets the data for the given `field` of the hash that is associated with the given `key` with the given `value`. If the `field` already exists in the hash, it is overwritten. If the given `key` does not exist, an associated hash is created, and the `field` and `value` are inserted. If the given `key` is not associated with a hash, an error is raised. Depends on the configuration parameter `emulateredisresponses`. If `emulateredisresponses` is true, returns 1 if a new field is inserted and 0 if an existing field is updated. If `emulateredisresponses` is false, returns OK `emulateredisresponses` is `true`. ```sh $ HSET yugahash area1 "America" ``` ``` 1 ``` ```sh $ HSET yugahash area1 "North America" ``` ``` 0 ``` ```sh $ HGET yugahash area1 ``` ``` "North America" ``` `emulateredisresponses` is `false`. ```sh $ HSET yugahash area1 "America" ``` ``` "OK" ``` ```sh $ HSET yugahash area1 "North America" ``` ``` "OK" ``` ```sh $ HGET yugahash area1 ``` ``` "North America" ``` , , , , , , , , , ,
Project: YugabyteDB (App Definition and Development / Database)
File: depends-on-extension-semantics.md

title: Semantics of "depends on extension" [YSQL] headerTitle: The semantics of the "depends on extension" subprogram attribute linkTitle: Depends on extension semantics description: Describes the semantics of the depends on extension subprogram attribute [YSQL]. menu: v2.18: identifier: depends-on-extension-semantics parent: subprogram-attributes weight: 10 type: docs Installing an extension typically brings several subprograms. For example, installing the tablefunc extension brings the normalrand() function. If, later, you drop the extension, then all the subprograms that it brought are silently dropped as a consequence. You don't need to say cascade to bring this outcome. Occasionally, users enlarge an extension's functionality with their own subprograms. They consider that these, too, are part of the extension and they want, therefore, to have these be silently dropped if the extension is dropped. This is what "depends on extension"_ achieves. You can test this easily, if you have a sandbox cluster, by creating a brand-new database and installing, say, the tablefunc extension into it, specifying, for example, "with schema extensions". (You need to do this as a superuser.) Then create a test function, say f(), and a test procedure, say p() in the same database and schema and use "alter... depends on extension..." to make these "part of" tablefunc. Use this query to observe this outcome: ```plpgsql select p.proname::text, e.extname from pgcatalog.pgproc p inner join pgcatalog.pgdepend d on p.oid = d.objid inner join pgcatalog.pgextension e on d.refobjid = e.oid where p.pronamespace::regnamespace::text = 'extensions' order by 1, 2, 3; ``` You'll see this: ```output proname | extname -+-- connectby | tablefunc connectby | tablefunc connectby | tablefunc connectby | tablefunc crosstab | tablefunc crosstab | tablefunc crosstab | tablefunc crosstab2 | tablefunc crosstab3 | tablefunc crosstab4 | tablefunc f | tablefunc normal_rand | tablefunc p | tablefunc ``` Then do this: ```plpgsql drop extension tablefunc restrict; ``` the restrict keyword is used to emphasize the pedagogy. Usually, it prevents the attempt to drop an object when the object has dependent objects. But dropping an extension is a special case. And "alter ... depends on extension..." recruits your user-defined subprograms into the special-case regime. You can confirm the outcome by attempting to execute f() or p(). You'll get the 42883 (undefinedfunction_) error. {{< note title="'alter ... depends on extension ...' currently draws a warning." >}} If you use "alter ... depends on extension ...", then you'll get this warning: ```output 0A000: This statement not supported yet Please report the issue on https://github.com/YugaByte/yugabyte-db/issues ``` But don't create a new issue. Rather, just look at this: The "alter function/procedure depends on extension" variant causes a spurious warning but produces the expected result {{< /note >}}
Project: KICS (Provisioning / Security & Compliance)
File: 2b856bf9-8e8c-4005-875f-303a8cba3918.md

title: Small Activity Log Retention Period hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 2b856bf9-8e8c-4005-875f-303a8cba3918 Query name: Small Activity Log Retention Period Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Observability URL: Ensure that Activity Log Retention is set 365 days or greater<br> ```tf title="Positive test num. 1 - tf file" hl_lines="64 41 20" resource "azurermmonitorlog_profile" "positive1" { name = "default" categories = [ "Action", "Delete", "Write", ] locations = [ "westus", "global", ] servicebusruleid = "${azurermeventhubnamespace.example.id}/authorizationrules/RootManageSharedAccessKey" storageaccountid = azurermstorageaccount.example.id retention_policy { enabled = true days = 7 } } resource "azurermmonitorlog_profile" "positive2" { name = "default" categories = [ "Action", "Delete", "Write", ] locations = [ "westus", "global", ] servicebusruleid = "${azurermeventhubnamespace.example.id}/authorizationrules/RootManageSharedAccessKey" storageaccountid = azurermstorageaccount.example.id retention_policy { enabled = true } } resource "azurermmonitorlog_profile" "positive3" { name = "default" categories = [ "Action", "Delete", "Write", ] locations = [ "westus", "global", ] servicebusruleid = "${azurermeventhubnamespace.example.id}/authorizationrules/RootManageSharedAccessKey" storageaccountid = azurermstorageaccount.example.id retention_policy { enabled = false } } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermmonitorlog_profile" "negative1" { name = "default" categories = [ "Action", "Delete", "Write", ] locations = [ "westus", "global", ] servicebusruleid = "${azurermeventhubnamespace.example.id}/authorizationrules/RootManageSharedAccessKey" storageaccountid = azurermstorageaccount.example.id retention_policy { enabled = true days = 367 } } resource "azurermmonitorlog_profile" "negative2" { name = "default" categories = [ "Action", "Delete", "Write", ] locations = [ "westus", "global", ] servicebusruleid = "${azurermeventhubnamespace.example.id}/authorizationrules/RootManageSharedAccessKey" storageaccountid = azurermstorageaccount.example.id retention_policy { enabled = true days = 0 } } ```
Project: YDB (App Definition and Development / Database)
File: syntax.md

```sql SELECT [<table column>, ... | *] FROM [<table name> | <sub query>] AS <table name alias> LEFT | RIGHT | CROSS | INNER JOIN <another table> AS <table name alias> ON <join condition> WHERE <condition> GROUP BY <table column> HAVING <condition> UNION | UNION ALL | EXCEPT | INTERSECT ORDER BY <table column> [ASC | DESC] LIMIT [<limit value>] OFFSET <offset number> ```
Project: Salt Project (Provisioning / Automation & Configuration)
File: 0002-adding-minion-id-to-fileserver-calls.md

Feature Name: addingminionidtofileserver_calls Start Date: 2018-09-13 RFC PR: Salt Issue: Add minion id to all fileserver events sent to request server and optionally sign the payload as well. Currently there is no possibility to determine on master which minion requested particular fileserver operation (file list, file request, etc.), which makes it impossible to implement any minion-based permissions level onto fileserver. Implementing this RFC would make it possible to implement custom fileservers that support various layers of security, allowing to restrict access for particular minions to environments/files and achieving some level of fileserver multitenancy. Proposed design is to add `id` key to all fileserver-related payloads in `RemoteClient`, optionally allowing to also sign the messages similarly as it's done via (either reusing same configuration option or introducing new one). After master can receive minion identity and signature, custom fileserver modules can be implemented or existing modules can be extended with the functionality (out of scope for this RFC). To actually propagate that load data to custom fileserver, appropriate changes need to be done to because not all methods propagate full load to underlying modules (, ). To avoid issue when all existing fileserver modules would have to be refactored to support new function arguments, similar usage of `_argspec` can be used as for `envs` method. Include id/signature automatically to everything going through `channel.send` so every function in / can verify minion validity. This would however either require necessary validations for every master request - for some calls this would be unnecessary and others are already validating this via , or just sending unnecessary data to masters. Reuse `minionsignmessages` configuration option or introduce new option such as `minionsignfileserver_messages`? When this gets introduced, every fileserver payload will be larger by minion id and signature, increasing traffic slightly. Also additional load can be introduced to minions when payload signature is computed (only applicable if enabled). As there will be no default processing for the id/signature, no additional load should be placed on masters and existing functionality should be preserved.
Project: ClickHouse (App Definition and Development / Database)
File: v22.4.4.7-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Queries with aliases inside special operators returned parsing error (was broken in 22.1). Example: `SELECT substring('test' AS t, 1, 1)`. (). Backported in : Fix merges of wide parts with type `Object`. (). Add passphrase for certificates ().
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: InfluxDB.md

InfluxDB source connector Read external data source data through InfluxDB. supports query SQL and can achieve projection effect. | name | type | required | default value | |--|--|-|| | url | string | yes | - | | sql | string | yes | - | | schema | config | yes | - | | database | string | yes | | | username | string | no | - | | password | string | no | - | | lower_bound | long | no | - | | upper_bound | long | no | - | | partition_num | int | no | - | | split_column | string | no | - | | epoch | string | no | n | | connecttimeoutms | long | no | 15000 | | querytimeoutsec | int | no | 3 | | common-options | config | no | - | the url to connect to influxDB e.g. ``` http://influxdb-host:8086 ``` The query sql used to search data ``` select name,age from test ``` The schema information of upstream data. e.g. ``` schema { fields { name = string age = int } } ``` The `influxDB` database the username of the influxDB when you select the password of the influxDB when you select the `split_column` of the influxDB when you select Tips: influxDB tags is not supported as a segmented primary key because the type of tags can only be a string influxDB time is not supported as a segmented primary key because the time field cannot participate in mathematical calculation Currently, `split_column` only supports integer data segmentation, and does not support `float`, `string`, `date` and other types. upper bound of the `split_column`column lower bound of the `split_column` column ``` split the $splitcolumn range into $partitionnum parts if partitionnum is 1, use the whole `splitcolumn` range if partitionnum < (upperbound - lowerbound), use (upperbound - lower_bound) partitions eg: lowerbound = 1, upperbound = 10, partition_num = 2 sql = "select * from test where age > 0 and age < 10" split result split 1: select * from test where ($splitcolumn >= 1 and $splitcolumn < 6) and ( age > 0 and age < 10 ) split 2: select * from test where ($splitcolumn >= 6 and $splitcolumn < 11) and ( age > 0 and age < 10 ) ``` the `partition_num` of the InfluxDB when you select Tips: Ensure that `upperbound` minus `lowerbound` is divided `bypartition_num`, otherwise the query results will overlap returned time precision Optional values: H, m, s, MS, u, n default value: n the `query_timeout` of the InfluxDB when you select, in seconds the timeout for connecting to InfluxDB, in milliseconds Source plugin common parameters, please refer to for details Example of multi parallelism and multi partition scanning ```hocon source { InfluxDB { url = "http://influxdb-host:8086" sql = "select label, value, rt, time from test" database = "test" upper_bound = 100 lower_bound = 1 partition_num = 4 split_column = "value" schema { fields { label = STRING value = INT rt = STRING time = BIGINT } } } ``` Example of not using partition scan ```hocon source { InfluxDB { url = "http://influxdb-host:8086" sql = "select label, value, rt, time from test" database = "test" schema { fields { label = STRING value = INT rt = STRING time = BIGINT } } } ``` Add InfluxDB Source Connector