cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: 4eb5f791-c861-4afd-9f94-f2a6a3fe49cb.md

title: MQ Broker Is Publicly Accessible hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 4eb5f791-c861-4afd-9f94-f2a6a3fe49cb Query name: MQ Broker Is Publicly Accessible Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Insecure Configurations URL: Check if any MQ Broker is not publicly accessible<br> ```tf title="Positive test num. 1 - tf file" hl_lines="19" resource "awsmqbroker" "positive1" { broker_name = "example" configuration { id = awsmqconfiguration.test.id revision = awsmqconfiguration.test.latest_revision } engine_type = "ActiveMQ" engine_version = "5.15.0" hostinstancetype = "mq.t2.micro" securitygroups = [awssecurity_group.test.id] user { username = "ExampleUser" password = "MindTheGap" } publicly_accessible = true } ``` ```tf title="Negative test num. 1 - tf file" resource "awsmqbroker" "negative1" { broker_name = "example" configuration { id = awsmqconfiguration.test.id revision = awsmqconfiguration.test.latest_revision } engine_type = "ActiveMQ" engine_version = "5.15.0" hostinstancetype = "mq.t2.micro" securitygroups = [awssecurity_group.test.id] user { username = "ExampleUser" password = "MindTheGap" } } ```
Project: Harbor (Provisioning / Container Registry)
File: bug_report.md

name: Bug report about: Create a report to help us improve If you are reporting a problem, please make sure the following information are provided: Expected behavior and actual behavior: A clear and concise description of what you expected to happen and what's the actual behavior. If applicable, add screenshots to help explain your problem. Steps to reproduce the problem: Please provide the steps to reproduce this problem. Versions: Please specify the versions of following systems. harbor version: [x.x.x] docker engine version: [y.y.y] docker-compose version: [z.z.z] Additional context: Harbor config files: You can get them by packaging `harbor.yml` and files in the same directory, including subdirectory. Log files: You can get them by package the `/var/log/harbor/` .
Project: StarRocks (App Definition and Development / Database)
File: lpad.md

displayed_sidebar: "English" This function returns strings with a length of `len` (starting counting from the first syllable) in `str`. If `len` is longer than `str`, the return value is lengthened to `len` characters by adding pad characters in front of `str`. If `str` is longer than `len`, the return value is shortened to `len` characters. `len` means the length of characters, not bytes. ```Haskell VARCHAR lpad(VARCHAR str, INT len[, VARCHAR pad]) ``` `str`: required, the string to be padded, which must evaluate to a VARCHAR value. `len`: required, the length of return value, it means the length of characters, not bytes, which must evaluate to an INT value. `pad`: optional, the characters to be added in front of str, which must be a VARCHAR value. If this parameter is not specified, spaces are added by default. Returns a VARCHAR value. ```Plain Text MySQL > SELECT lpad("hi", 5, "xy"); ++ | lpad('hi', 5, 'xy') | ++ | xyxhi | ++ MySQL > SELECT lpad("hi", 1, "xy"); ++ | lpad('hi', 1, 'xy') | ++ | h | ++ MySQL > SELECT lpad("hi", 5); ++ | lpad('hi', 5, ' ') | ++ | hi | ++ ``` LPAD
Project: StarRocks (App Definition and Development / Database)
File: bitmap_union_count.md

displayed_sidebar: "English" Returns the union of a set of bitmap values and returns the cardinality of the union. This function is supported from v2.3. ```Haskell BIGINT bitmapunioncount(BITMAP value) ``` `value`: a set of bitmap values. The supported data type is BITMAP. Returns a value of the BIGINT type. Calculate the unique views (UVs) of a web page. If `user_id` is of the INT type, the latter two queries are equivalent. ```Plaintext mysql> select * from test +++ | pageid | userid | +++ | 1 | 1 | | 1 | 2 | | 2 | 1 | +++ mysql> select pageid,count(distinct userid) from test group by page_id; ++-+ | pageid | count(DISTINCT userid) | ++-+ | 1 | 2 | | 2 | 1 | ++-+ mysql> select pageid,bitmapunioncount(tobitmap(userid)) from test group by pageid; ++-+ | pageid | bitmapunioncount(tobitmap(user_id)) | ++-+ | 1 | 2 | | 2 | 1 | ++-+ ```
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: permit.md

title: Permit.io labels: category: authorization layer: application inventors: permitio code: https://github.com/permitio tutorials: https://docs.permit.io/ videos: https://docs.permit.io/tutorials/onboarding_demo blogs: https://www.permit.io/blog/introduction-to-opa https://www.permit.io/blog/implement-abac-using-opa https://www.permit.io/blog/implement-rbac-using-opa Permit.io empowers developers to bake in permissions and access-control into any product in minutes and takes away the pain of constantly rebuilding them. Permit is based on OPA.
Project: secureCodeBox (Provisioning / Security & Compliance)
File: 06_runtime_view.md

title: "Runtime View" sidebar_label: "Runtime View" sidebar_position: 6 This section describes the runtime view of secureCodeBox. In contrast to the static building block view, this view shows the interactions of participants (components/actors) over time. This is typically done with . Since sequence diagrams are hard to maintain and tend to be very complicated we focus here only on the top most important scenarios, and do not draw diagrams for every possible scenario. This scenario describes a simple scan which is initialized by a Developer actor and which persists the findings in and .
Project: DragonflyDB (App Definition and Development / Database)
File: PULL_REQUEST_TEMPLATE.md

<!-- Commits Must Be Signed and Your PR title must conform to the conventional commit spec See: https://github.com/dragonflydb/dragonfly/blob/main/CONTRIBUTING.md Please follow the section on `pre-commit hooks`, a linter will validate before you push Example PR Title: <type>(<scope>)!: <description> `type` = bug, chore, feat, fix, docs, build, style, refactor, perf, test `!` = OPTIONAL: signals a breaking change `scope` = Optional when `type` is "chore" or "docs" `description` = short description of the change Examples: chore(examples): Clarify `docker` usage #120 docs(readme): Fix Example Links #121 feat(ingest)!: Add new ingest #122 fix(ingest): Refactor for loop to list comprehension #123 -->
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: CHANGELOG-v2023.01.17.md

title: Changelog | KubeDB description: Changelog menu: docs_{{.version}}: identifier: changelog-kubedb-v2023.01.17 name: Changelog-v2023.01.17 parent: welcome weight: 20230117 product_name: kubedb menuname: docs{{.version}} sectionmenuid: welcome url: /docs/{{.version}}/welcome/changelog-v2023.01.17/ aliases: /docs/{{.version}}/CHANGELOG-v2023.01.17/ Update deps Prepare for release v0.15.1 (#131) Set registryFQDN to use docker for local development (#130) Prepare for release v0.30.1 (#695) Prepare for release v0.6.1 (#58) Set registryFQDN to use docker for local development (#57) Disable usage collection from ES (#56) Prepare for release v0.30.1 (#624) Add --insecure-registries flag (#623) Set registryFQDN to use docker for local development (#622) Prepare for release v2023.01.17 (#584) Add --insecure-registries flag (#583) Fix Grafana dashboard crd url Prepare for release v0.1.1 (#12) Add --insecure-registries flag (#11) Set registryFQDN to use docker for local development (#10) Prepare for release v0.14.1 (#196) Add --insecure-registries flag (#195) Set registryFQDN to use docker for local development (#194) Prepare for release v0.10.1 (#70) Prepare for release v0.23.1 (#382) Prepare for release v0.23.1 (#531) Add --insecure-registries flag (#530) Set registryFQDN to use docker for local development (#529) Prepare for release v0.23.1 (#519) Add --insecure-registries flag (#518) Set registryFQDN to use docker for local development (#517) Prepare for release v0.8.1 (#68) Remove slack link Prepare for release v0.17.1 (#407) Add --insecure-registries flag (#406) Set registryFQDN to use docker for local development (#405) Refactor Redis Ops Requests (#404) Prepare for release v0.17.1 (#297) Add --insecure-registries flag (#296) Set registryFQDN to use docker for local development (#295) Prepare for release v0.3.1 (#27) Prepare for release v0.14.1 (#109) Prepare for release v0.17.1 (#258) Add --insecure-registries flag (#257) Set registryFQDN to use docker for local development (#256) Prepare for release v0.30.1 (#623) Add --insecure-registries flag (#622) Set registryFQDN to use docker for local development (#621) Prepare for release v0.30.1 (#35) Add --insecure-registries flag (#34) Prepare for release v0.17.1 (#277) Add --insecure-registries flag (#276) Set registryFQDN to use docker for local development (#275) Prepare for release v0.23.1 (#447) Add --insecure-registries flag (#446) Set registryFQDN to use docker for local development (#445) Add redis client-go (#444) Prepare for release v0.9.1 (#60) Prepare for release v0.17.1 (#222) Prepare for release v0.6.1 (#62) Update KubeVault crds (#61) Set registryFQDN to use docker for local development (#60) Prepare for release v0.15.1 (#214) Add Percona XtraDB Tests (Provisioner, OpsManager, Autoscaler) (#181) Add MariaDB OpsReq and Autoscaler Tests (#160) Update Redis Sentinel Tests (#211) Prepare for release v0.6.1 (#64) Remove slack link Prepare for release v0.6.1 (#47) Set registryFQDN to use docker for local development (#45)
Project: Athenz (Provisioning / Key Management)
File: zts_accesstoken.md

ZTS OAuth2 Access Token Client application in Go to request an access token from ZTS Server for the given identity to access a role in a provider domain. Download latest ZTS OAuth2 Access Token Client package from : click on the `Browse` button, choose the latest version directory and then download the `athenz-utils-<latest-version>-bin.tar.gz`. ```shell $ tar xvfz athenz-utils-X.Y-bin.tar.gz ``` Before you can use the ZTS AccessToken utility, you need to have asked the Athenz administrators to create your top level domain. -- An access token from ZTS service can be fetched using Service Identity x.509 certificates. The optional `expire-time` argument specifies how long the access token should be valid for. The value must be specified in minutes. The default if no value is specified is 120 minutes. The optional `roles` argument requests an access token for the given roles only (comma separated) as opposed to all the roles the service identity has access to in the requested domain. The optional `service` argument requests an id token for the given service. The full `domain.service` value will be set as the audience for the id token. ``` $ zts-accesstoken -domain <domain> [-roles <roles>] [-service <service>] -svc-key-file <private-key-file> -svc-cert-file <service-cert-file> -zts <ZTS url> [-expire-time <expire-time-in-mins>] ```
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_create_operator.md

title: CREATE OPERATOR statement [YSQL] headerTitle: CREATE OPERATOR linkTitle: CREATE OPERATOR description: Use the CREATE OPERATOR statement to create an operator. menu: v2.18: identifier: ddlcreateoperator parent: statements type: docs Use the `CREATE OPERATOR` statement to create an operator. {{%ebnf%}} create_operator, operator_option {{%/ebnf%}} See the semantics of each option in the . Basic example. ```plpgsql yugabyte=# CREATE OPERATOR @#@ ( rightarg = int8, procedure = numeric_fac ); yugabyte=# SELECT @#@ 5; ``` ``` ?column? 120 ```
Project: YugabyteDB (App Definition and Development / Database)
File: type-time.md

title: The time data type [YSQL] headerTitle: The time data type linkTitle: Time data type description: The semantics of the time data type. [YSQL] menu: v2.18: identifier: type-time parent: date-time-data-types-semantics weight: 20 type: docs Values whose data type is time represent the time-of-day component of some moment (the hours and minutes as integer values and the seconds as a real number value with microsecond precision) in the "local" (a.k.a. "wall-clock") regime. Time values know nothing about timezones, and represent the time of day at some unspecified location. You can picture a time value as the number of microseconds from the exact midnight that starts the day. And because time values know nothing about timezones, they know nothing about Daylight Savings regimes, either: every day ought to run from midnight (inclusive) through the next midnight (exclusive). But notice this quirk: ```plpgsql select ('00:00:00.000000'::time)::text as "starting midnight", ('23:59:59.999999'::time)::text as "just before ending midnight", ('24:00:00.000000'::time)::text as "ending midnight"; ``` This is the result: ```output starting midnight | just before ending midnight | ending midnight -+--+-- 00:00:00 | 23:59:59.999999 | 24:00:00 ``` The fact that this is allowed is a minor annoyance. The two times test as unequal" ```plpgsql select ( '00:00:00.000000'::time = '24:00:00.000000'::time )::text; ``` The result is false. But because the time value carries no date information, you'd need to define and advertise auxiliary application semantics to interpret 24:00:00 as the end of a particular day rather than the start of the day that immediately follows the previous day. Notice that subtracting one time value from another time value uses clock-time-semantics. Try this: ```plpgsql select ('02:00:00'::time - '01:00:00'::time)::text as "interval 1", ('24:00:00'::time - '00:00:00'::time)::text as "interval 2", justify_hours('24:00:00'::time - '00:00:00'::time)::text as "interval 3"; ``` This is the result: ```output interval 1 | interval 2 | interval 3 ++ 01:00:00 | 24:00:00 | 1 day ``` See the section. This section explains the mental model that allows 24 hours to be different (in a subtle way) from 1 day. Here's another quirk: adding an interval value to a date value can cause silent wrap-around. Try this: ```plpgsql select '24:00:00'::time + '1 second'::interval; ``` This is the result: ```output 00:00:01 ``` This suggests that you might get the same result from this attempt: ```plpgsql select '24:00:01'::time; ``` But the attempt causes this error: ```output 22008: date/time field value out of range: "24:00:01" ``` Compare these quirky outcomes with those of corresponding tests that use plain timestamp values. See the section . You should think very carefully about your reasons to prefer the time data type over the plain timestamp data type in application code and describe these reasons in your application's functional specification document.
Project: Docker Compose (App Definition and Development / Application Definition & Image Build)
File: compose_cp.md

<!MARKERGENSTART--> Copy files/folders between a service container and the local filesystem | Name | Type | Default | Description | |:-|:|:--|:--| | `-a`, `--archive` | | | Archive mode (copy all uid/gid information) | | `--dry-run` | | | Execute command in dry run mode | | `-L`, `--follow-link` | | | Always follow symbol link in SRC_PATH | | `--index` | `int` | `0` | Index of the container if service has multiple replicas | <!MARKERGENEND-->
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.3.9.md

layout: release date: 2020-2-2 tag: v0.3.9 language: en Mesheryctl Addition of `mesheryctl version` to provide server-side version number. Improvement of `mesheryctl logs | stop | start` to provide appropriate grammar in situations when Meshery is stopped or Docker is not present. Meshery Server Strip off extraneous information beyond IP address and port in Grafana and Prometheus endpoints ()
Project: SlimToolkit (Provisioning / Security & Compliance)
File: README.md

](https://travis-ci.org/kubernetes-sigs/yaml) kubernetes-sigs/yaml is a permanent fork of . A wrapper around designed to enable a better way of handling YAML when marshaling to and from structs. In short, this library first converts YAML to JSON using go-yaml and then uses `json.Marshal` and `json.Unmarshal` to convert to or from the struct. This means that it effectively reuses the JSON struct tags as well as the custom JSON methods `MarshalJSON` and `UnmarshalJSON` unlike go-yaml. For a detailed overview of the rationale behind this method, . This package uses and therefore supports . Caveat #1: When using `yaml.Marshal` and `yaml.Unmarshal`, binary data should NOT be preceded with the `!!binary` YAML tag. If you do, go-yaml will convert the binary data from base64 to native binary data, which is not compatible with JSON. You can still use binary in your YAML files though - just store them without the `!!binary` tag and decode the base64 in your code (e.g. in the custom JSON methods `MarshalJSON` and `UnmarshalJSON`). This also has the benefit that your YAML and your JSON binary data will be decoded exactly the same way. As an example: ``` BAD: exampleKey: !!binary gIGC GOOD: exampleKey: gIGC ... and decode the base64 data in your code. ``` Caveat #2: When using `YAMLToJSON` directly, maps with keys that are maps will result in an error since this is not supported by JSON. This error will occur in `Unmarshal` as well since you can't unmarshal map keys anyways since struct fields can't be keys. To install, run: ``` $ go get sigs.k8s.io/yaml ``` And import using: ``` import "sigs.k8s.io/yaml" ``` Usage is very similar to the JSON library: ```go package main import ( "fmt" "sigs.k8s.io/yaml" ) type Person struct { Name string `json:"name"` // Affects YAML field names too. Age int `json:"age"` } func main() { // Marshal a Person struct to YAML. p := Person{"John", 30} y, err := yaml.Marshal(p) if err != nil { fmt.Printf("err: %v\n", err) return } fmt.Println(string(y)) /* Output: age: 30 name: John */ // Unmarshal the YAML back into a Person struct. var p2 Person err = yaml.Unmarshal(y, &p2) if err != nil { fmt.Printf("err: %v\n", err) return } fmt.Println(p2) /* Output: {John 30} */ } ``` `yaml.YAMLToJSON` and `yaml.JSONToYAML` methods are also available: ```go package main import ( "fmt" "sigs.k8s.io/yaml" ) func main() { j := []byte(`{"name": "John", "age": 30}`) y, err := yaml.JSONToYAML(j) if err != nil { fmt.Printf("err: %v\n", err) return } fmt.Println(string(y)) /* Output: age: 30 name: John */ j2, err := yaml.YAMLToJSON(y) if err != nil { fmt.Printf("err: %v\n", err) return } fmt.Println(string(j2)) /* Output: {"age":30,"name":"John"} */ } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.59.md

layout: release date: 2021-09-26 tag: v0.5.59 [Extension] Modify RJSF custom string field styles @sudo-NithishKarthik (#4241) Update helm charts to be consistent with mesheryctl @panyuenlau (#4227) [manifests] update cluster role verbs for `meshery-server` service account @DelusionalOptimist (#4237) added filter deploy post and delete @Shreyas220 (#4188) updated copyright notice w/signoff @fuadnafiz98 (#4231) replaced mesheryctl command using Bash @kartik1918 (#4213) Added remote dependency @NikhilSharma03 (#4210) UX improvements in mesh command @navendu-pottekkat (#4238) [Docs] [Remake] Add `app` command to `mesheryctl` reference @alphaX86 (#4224) Update the mesheryctl contributing docs to include using contexts to write to central struct @navendu-pottekkat (#4239) [mesheryctl] add missing struct fields for k8s manifests @DelusionalOptimist (#4244) detailed description for login and logout @warunicorn19 (#4228) [mesheryctl]add subcommands for system config command @hexxdump (#4183) [mesheryctl] Add unit tests for utils/sse-client.go @krithikvaidya (#4176) added beta badge @ishitakeshawani (#4043) centered the icons and the chevron @warunicorn19 (#4222) [mesheryctl] add missing struct fields for k8s manifests @DelusionalOptimist (#4244) Update roadmap for v0.6.0 @Aisuko (#4240) [CI] label commenter modified @amino19 (#4226) [build] reduce meshery server's docker image size @DelusionalOptimist (#4215) [mesheryctl] Add unit tests for utils/sse-client.go @krithikvaidya (#4176) [Docs] [Remake] Add `app` command to `mesheryctl` reference @alphaX86 (#4224) Update the mesheryctl contributing docs to include using contexts to write to central struct @navendu-pottekkat (#4239) The link in Contributing.md is rectified @shubham-tyagi (#4243) Performance Management with Meshery @Anand-Theertha (#4225) add open service mesh lab to docs @shreyaansjain06 (#4206) detailed description for login and logout @warunicorn19 (#4228) added login and logout to docs @warunicorn19 (#3973) Thank you to our contributors for making this release possible: @Aisuko, @Anand-Theertha, @DelusionalOptimist, @NikhilSharma03, @Shreyas220, @alphaX86, @amino19, @fuadnafiz98, @hexxdump, @ishitakeshawani, @kartik1918, @krithikvaidya, @leecalcote, @navendu-pottekkat, @panyuenlau, @piyushsingariya, @shreyaansjain06, @shubham-tyagi, @sudo-NithishKarthik and @warunicorn19
Project: YDB (App Definition and Development / Database)
File: aggr_factory.md

Create a factory for to separately describe the methods of aggregation and data types subject to aggregation. Arguments: A string in double quotes with the name of an aggregate function, for example . Optional parameters of the aggregate function that are data-independent. For example, the percentile value in . The resulting factory can be used as the second parameter of the function . If the aggregate function is applied to two columns instead of one, as, for example, , then in , the first argument passes a `Tuple` of two values. See more details in the description of the applicable aggregate function. Examples: ```yql $factory = AggregationFactory("MIN"); SELECT AGGREGATEBY (value, $factory) AS minvalue -- apply the MIN aggregation to the "value" column FROM my_table; ``` `AggregateTransformInput()` converts an , for example, obtained using the function, to other factory, in which the specified transformation of input items is performed before starting aggregation. Arguments: Aggregation factory. A lambda function with one argument that converts an input item. Examples: ```yql $f = AggregationFactory("sum"); $g = AggregateTransformInput($f, ($x) -> (cast($x as Int32))); $h = AggregateTransformInput($f, ($x) -> ($x * 2)); select ListAggregate([1,2,3], $f); -- 6 select ListAggregate(["1","2","3"], $g); -- 6 select ListAggregate([1,2,3], $h); -- 12 ``` `AggregateTransformOutput()` converts an , for example, obtained using the function, to other factory, in which the specified transformation of the result is performed after ending aggregation. Arguments: Aggregation factory. A lambda function with one argument that converts the result. Examples: ```yql $f = AggregationFactory("sum"); $g = AggregateTransformOutput($f, ($x) -> ($x * 2)); select ListAggregate([1,2,3], $f); -- 6 select ListAggregate([1,2,3], $g); -- 12 ``` Adapts a factory for , for example, obtained using the function in a way that allows aggregation of list input items. This operation is similar to : Each list item is aggregated. Arguments: Aggregation factory. Examples: ```yql $i = AggregationFactory("AGGREGATELISTDISTINCT"); $j = AggregateFlatten($i); select AggregateBy(x, $j) from ( select [1,2] as x union all select [2,3] as x ); -- [1, 2, 3] ```