cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: 8f75840d-9ee7-42f3-b203-b40e3979eb12.md

title: Role With Privilege Escalation By Actions 'iam:PutUserPolicy' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 8f75840d-9ee7-42f3-b203-b40e3979eb12 Query name: Role With Privilege Escalation By Actions 'iam:PutUserPolicy' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Role with privilege escalation by actions 'iam:PutUserPolicy' 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:PutUserPolicy", ] 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: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_plugin_kubectl.KubeStatus.md

/ / KubeStatus .KubeStatus `Optional` availableReplicas: `number` `Optional` completionTime: `string` `Optional` conditions: [] `Optional` loadBalancer: `KubeLoadBalancer` `Optional` message: `string` `Optional` phase: `string` `Optional` podName: `string` `Optional` qosClass: `string` `Optional` readyReplicas: `number` `Optional` replicas: `number` `Optional` startTime: `string` `Optional` state: `string` `Optional` unavailableReplicas: `number` `Optional` updatedReplicas: `number`
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: AmazonDynamoDB.md

AmazonDynamoDB source connector Read data from Amazon DynamoDB. | name | type | required | default value | |--|--|-|| | url | string | yes | - | | region | string | yes | - | | accesskeyid | string | yes | - | | secretaccesskey | string | yes | - | | table | string | yes | - | | schema | config | yes | - | | common-options | | yes | - | | scanitemlimit | | false | - | | parallelscanthreads | | false | - | The URL to read to Amazon Dynamodb. The region of Amazon Dynamodb. The access id of Amazon DynamoDB. The access secret of Amazon DynamoDB. The table of Amazon DynamoDB. Amazon Dynamodb is a NOSQL database service of support keys-value storage and document data structure,there is no way to get the data type.Therefore, we must configure schema. such as: ``` schema { fields { id = int key_aa = string key_bb = string } } ``` Source Plugin common parameters, refer to for details number of item each scan request should return number of logical segments for parallel scan ```bash Amazondynamodb { url = "http://127.0.0.1:8000" region = "us-east-1" accessKeyId = "dummy-key" secretAccessKey = "dummy-secret" table = "TableName" schema = { fields { artist = string c_map = "map<string, array<int>>" c_array = "array<int>" c_string = string c_boolean = boolean c_tinyint = tinyint c_smallint = smallint c_int = int c_bigint = bigint c_float = float c_double = double c_decimal = "decimal(30, 8)" c_null = "null" c_bytes = bytes c_date = date c_timestamp = timestamp } } } ``` Add Amazon DynamoDB Source Connector Add source split to Amazondynamodb Connectors
Project: StarRocks (App Definition and Development / Database)
File: ceiling.md

displayed_sidebar: "English" Returns values from the input `arg` rounded to the nearest equal or larger integer. ```Shell ceiling(arg) ``` `arg` supports the DOUBLE data type. Returns a value of the BIGINT data type. ```Plain mysql> select ceiling(3.14); ++ | ceiling(3.14) | ++ | 4 | ++ 1 row in set (0.00 sec) ```
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.11.19.md

RabbitMQ `3.11.19` is a maintenance release in the `3.11.x` . Please refer to the upgrade section from if upgrading from a version prior to 3.11.0. This release requires Erlang 25 and supports Erlang versions up to `25.3.x`. has more details on Erlang version requirements for RabbitMQ. As of 3.11.0, RabbitMQ requires Erlang 25. Nodes will fail to start on older Erlang releases. Erlang 25 as our new baseline means much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation available to all RabbitMQ 3.11 users. Release notes can be found on GitHub at . Declaration of a classic queue could run into an exception. GitHub issue: Nodes that had a large number of quorum queues could observe accumulation of Erlang processes under significant load. A follow-up change to . GitHub issue: Feature flag discovery operations will now be retried multiple times in case of network failures. GitHub issue: Feature flag discovery on a newly added node could discover an incomplete inventory of feature flags. GitHub issue: Nodes in clusters that had quorum queues and non-mirrored classic queues on stopped (or failed) nodes could run into an exception. The same exception could affect `rabbitmqctl list_queues`. GitHub issue: Proxy Protocol v2 LOCAL packets were not supported. GitHub issue: When a quorum queue does not find its local replica data files on boot, it will now log a warning. GitHub issue: An attempt to clear limits of a non-existent virtual host failed with a 500 status code. GitHub issue: Management UI will now display node maintenance status. Contributed by @SimonUnge (AWS). GitHub issue: The "Queues" tab in the UI was renamed to "Queue and Streams" to better reflect its contents. GitHub issue: New HTTP API endpoints for quorum queue replica management, equivalent to the `rabbitmq-queues` commands that manage replicas. ``` POST /api/queues/quorum/{vhost}/{name}/replicas/add DELETE /api/queues/quorum/{vhost}/{name}/replicas/remove POST /api/queues/quorum/replicas/on/{node}/grow DELETE /api/queues/quorum/replicas/on/{node}/shrink ``` GitHub issue: Stream client connections that authenticated using x.509 certificates failed. GitHub issue: Only set OAuth 2 client's CA certificate file setting when it is defined. GitHub issue: The plugin will now accept JWT tokens without a `scope`. Such tokens would only be useful when the plugin is used exclusively for authentication and not authorization. GitHub issue: `oauth2` is now an accepted alias for the OAuth 2 authentication and authorization backend: ``` auth_backends.1 = oauth2 ``` Previously the only option for OAuth 2 was using a full module name, `rabbitauthbackend_oauth2`. GitHub issue: STOMP plugin log entries had an extra line feed character. GitHub issue: `ra` was upgraded to `osiris` was upgraded To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.19.tar.xz` instead of the source tarball produced by GitHub.
Project: YugabyteDB (App Definition and Development / Database)
File: jsonb-populate-record.md

title: jsonbpopulaterecord() and jsonpopulaterecord() headerTitle: jsonbpopulaterecord() and jsonpopulaterecord() linkTitle: jsonbpopulaterecord() description: Convert a JSON object into the equivalent SQL record. menu: v2.18: identifier: jsonb-populate-record parent: json-functions-operators weight: 180 type: docs Purpose: Convert a JSON object into the equivalent SQL `record`. Signature For the `jsonb` variant: ``` input value: anyelement, jsonb return value: anyelement ``` Notes: Each function in this pair requires that the supplied JSON value is an object. The data type of the `record` must be defined as a schema-level `type` whose name is passed via the function's first formal parameter using the locution `NULL:type_identifier`. The JSON value is passed using the second formal parameter. Use this `ysqlsh` script to create the required types "t1" and "t2", and then to execute the `ASSERT`. ```plpgsql create type t1 as ( d int, e text); create type t2 as (a int, b text[], c t1); do $body$ declare nested_object constant jsonb := '{"a": 42, "b": ["cat", "dog"], "c": {"d": 17, "e": "frog"}}'; result constant t2 := jsonbpopulaterecord(null::t2, nested_object); expected_a constant int := 42; expected_b constant text[] := array['cat', 'dog']; expected_c constant t1 := (17, 'frog'); expectedresult constant t2 := (expecteda, expectedb, expectedc); begin assert result = expected_result, 'unexpected'; end; $body$; ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.37.md

layout: release date: 2021-07-14 tag: v0.5.37 [mesheryctl] Fix @DelusionalOptimist (#3449) [UI] Naming fix for Patterns, Applications, Filters @Chadha93 (#3448) Bump addressable from 2.7.0 to 2.8.0 in /docs @dependabot (#3494) Add endpoint to serve the filter file @navendu-pottekkat (#3467) [UI] Application actions and endpoints envoked @Chadha93 (#3464) Nithish/pattern UI imp @sudo-NithishKarthik (#3455) [mesheryctl] Updated docker/k8s conflict in @piyushsingariya (#3491) [CI] Open API Specification and Documentation workflow @amino19 (#3239) Bump billboard.js from 3.0.3 to 3.1.2 @sudo-NithishKarthik (#3465) Changed Notification Message Wrapping and Bell Button On Click @jeantiston (#3460) [mesheryctl] Fixing docker/k8s conflict incase of platform docker @piyushsingariya (#3490) updates meshkit error for load test handler @warunicorn19 (#3371) Profile cards changes @Ayush-Khandelwal-007 (#3454) [mesheryctl] system and Integration Testing @piyushsingariya (#3430) skip workflow run on forks @iamsdas (#3432) Updated the meshkit error for performanceprofileshandler and provider_handler @Shreyas220 (#3397) [mesheryctl] Fix for Not Set in stable releases @piyushsingariya (#3461) [Docs] - Refactored Old Docs with Emoji @adithyaakrishna (#3457) Thank you to our contributors for making this release possible: @Ayush-Khandelwal-007, @Chadha93, @DelusionalOptimist, @Shreyas220, @adithyaakrishna, @amino19, @dependabot, @dependabot[bot], @dhruv0000, @iamsdas, @jeantiston, @kumarabd, @leecalcote, @navendu-pottekkat, @piyushsingariya, @ramrodo, @sudo-NithishKarthik and @warunicorn19
Project: Fabric8 Kubernetes Client (App Definition and Development / Application Definition & Image Build)
File: KubernetesClientWithIPv6Clusters.md

Right now Fabric8 Kubernetes Client doesn't work with IPv6 based Kubernetes Clusters due to an issue in OkHttp . The issue is solved for OkHttp 4, but Fabric8 Kubernetes Client depends on OkHttp 3.x. We have decided not to upgrade to OkHttp 4.x, because it's based on Kotlin () and this might be an issue for downstream and dependent projects . We're still discussing a proper replacement for OkHttp (, ). In the meantime you can switch to use OkHttp 4.x in your project by configuring 3.x exclusions and adding your own direct 4.x OkHttp dependencies (): ```xml <properties> <fabric8.version>5.5.0</fabric8.version> <okhttp.version>4.9.0</okhttp.version> </properties> <dependencies> <dependency> <groupId>io.fabric8</groupId> <artifactId>kubernetes-client</artifactId> <version>${fabric8.version}</version> <exclusions> <exclusion> <groupId>com.squareup.okhttp3</groupId> <artifactId>okhttp</artifactId> </exclusion> <exclusion> <groupId>com.squareup.okhttp3</groupId> <artifactId>logging-interceptor</artifactId> </exclusion> </exclusions> </dependency> <dependency> <groupId>com.squareup.okhttp3</groupId> <artifactId>okhttp</artifactId> <version>${okhttp.version}</version> </dependency> <dependency> <groupId>com.squareup.okhttp3</groupId> <artifactId>logging-interceptor</artifactId> <version>${okhttp.version}</version> </dependency> </dependencies> ``` You can find an example demo project .
Project: Apollo (Provisioning / Automation & Configuration)
File: CONTRIBUTING.md

Apollo is released under the non-restrictive Apache 2.0 license, and follows a very standard GitHub development process, using GitHub tracker for issues and merging pull requests into master. If you want to contribute even something trivial please do not hesitate, but follow the guidelines below. Before we accept a non-trivial patch or pull request we will need you to sign the Contributor License Agreement. Signing the contributors agreement does not grant anyone commit rights to the main repository, but it does mean that we can accept your contributions, and you will get an author credit if we do. Active contributors might be asked to join the core team, and given the ability to merge pull requests. Our code style is in line with . We provide template files for IntelliJ IDEA and for Eclipse. If you use other IDEs, then you may config manually by referencing the template files. Make sure all new .java files have a simple Javadoc class comment on what the class is for. Add some Javadocs and, if you change the namespace, some XSD doc elements. A few unit tests should be added for a new feature or an important bug fix. If no-one else is using your branch, please rebase it against the current master (or other target branch in the main project). Normally, we would squash commits for one feature into one commit. There are 2 ways to do this: To rebase and squash based on the remote branch `git rebase -i <remote>/master` merge commits via `fixup`, etc Create a new branch and merge these commits into one `git checkout -b <some-branch-name> <remote>/master` `git merge --squash <current-feature-branch>` For commits, we adhere to the conventional commits format. For more details, refer to . When crafting commit messages, please adhere to the following conventions: if your commit addresses an existing issue, append "Fixes #XXX" to the end of the commit message (where XXX is the issue number).
Project: ClickHouse (App Definition and Development / Database)
File: where.md

slug: /en/sql-reference/statements/select/where sidebar_label: WHERE `WHERE` clause allows to filter the data that is coming from clause of `SELECT`. If there is a `WHERE` clause, it must contain an expression with the `UInt8` type. This is usually an expression with comparison and logical operators. Rows where this expression evaluates to `0` are excluded from further transformations or result. `WHERE` expression is evaluated on the ability to use indexes and partition pruning, if the underlying table engine supports that. :::note There is a filtering optimization called . ::: If you need to test a value for , use and operators or and functions. Otherwise an expression with `NULL` never passes. Example To find numbers that are multiples of 3 and are greater than 10 execute the following query on the : ``` sql SELECT number FROM numbers(20) WHERE (number > 10) AND (number % 3 == 0); ``` Result: ``` text number 12 15 18 ``` Queries with `NULL` values: ``` sql CREATE TABLE t_null(x Int8, y Nullable(Int8)) ENGINE=MergeTree() ORDER BY x; INSERT INTO t_null VALUES (1, NULL), (2, 3); SELECT * FROM t_null WHERE y IS NULL; SELECT * FROM t_null WHERE y != 0; ``` Result: ``` text xy 1 xy 2 3 ```
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: export-data.eg.md

```yaml apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: app-collect-service-endpoint-and-export spec: components: type: webservice name: busybox properties: image: busybox imagePullPolicy: IfNotPresent cmd: sleep '1000000' traits: type: expose properties: port: [8080] type: ClusterIP policies: type: topology name: local properties: clusters: ["local"] type: topology name: all properties: clusters: ["local", "cluster-worker"] workflow: steps: type: deploy name: deploy properties: policies: ["local"] type: collect-service-endpoints name: collect-service-endpoints outputs: name: host valueFrom: value.endpoint.host type: export-data name: export-data properties: topology: all inputs: from: host parameterKey: data.host ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.0-beta-4.md

layout: release date: 2021-02-22 tag: v0.5.0-beta-4 Revert "Bump billboard.js from 1.11.0 to 2.2.1 in /ui" @leecalcote (#2431) [mesheryctl] use current context endpoint when starting meshery @leecalcote (#2429) [Mesheryctl] Fix the meshery file path issues @hexxdump (#2427) Add Scoop instructions to docs site @alphaX86 (#2414) Added mesheryctl installation instructions using homebrew @metonymic-smokey (#2410) [DOCS] Change Database diagram to new one and rename database SVG file @alphaX86 (#2424)
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_target_https_proxy.md

+++ title = "googlecomputetargethttpsproxy resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputetargethttpsproxy" identifier = "inspec/resources/gcp/googlecomputetargethttpsproxy.md googlecomputetargethttpsproxy resource" parent = "inspec/resources/gcp" +++ A `googlecomputetargethttpsproxy` is used to test a Google TargetHttpsProxy resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputetargethttpsproxy(project: 'chef-gcp-inspec', name: 'inspec-gcp-https-proxy') do it { should exist } its('url_map') { should match /\/inspec-gcp-url-map$/ } its('description') { should eq 'A HTTPS target proxy' } end describe googlecomputetargethttpsproxy(project: 'chef-gcp-inspec', name: 'nonexistent') do it { should_not exist } end ``` Properties that can be accessed from the `googlecomputetargethttpsproxy` resource: `creation_timestamp` : Creation timestamp in RFC3339 text format. `description` : An optional description of this resource. `id` : The unique identifier for the resource. `name` : Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression `?` which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash. `quic_override` : Specifies the QUIC override policy for this resource. This determines whether the load balancer will attempt to negotiate QUIC with clients or not. Can specify one of NONE, ENABLE, or DISABLE. If NONE is specified, uses the QUIC policy with no user overrides, which is equivalent to DISABLE. Possible values: NONE ENABLE DISABLE `ssl_certificates` : A list of SslCertificate resources that are used to authenticate connections between users and the load balancer. At least one SSL certificate must be specified. `ssl_policy` : A reference to the SslPolicy resource that will be associated with the TargetHttpsProxy resource. If not set, the TargetHttpsProxy resource will not have any SSL policy configured. `url_map` : A reference to the UrlMap resource that defines the mapping from URL to the BackendService. Ensure the is enabled for the current project.
Project: The Update Framework (TUF) (Provisioning / Security & Compliance)
File: 0000-use-markdown-architectural-decision-records.md

Status: accepted Date: 2020-10-20 Technical Story: https://github.com/theupdateframework/python-tuf/issues/1141 We want to record architectural decisions made in this project. Which format and structure should these records follow? 2.1.2 The Markdown Architectural Decision Records Formless No conventions for file format and structure Chosen option: "MADR 2.1.2", because Implicit assumptions should be made explicit. Design documentation is important to enable people understanding the decisions later on. The MADR structure is comprehensible and facilitates usage & maintenance.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.157.md

layout: release date: 2023-10-13 tag: v0.6.157 [Docs] MeshSync @leecalcote (#9087) Include doc link in K8s component registration event @leecalcote (#9009) [meshmodel] Add Environment Component Def @theBeginner86 (#9070) Added-icon-for-meshmodel-prometheus-component-Alertmanager @Ayush9026 (#9069) Uploaded Icon for Kubernetes Component - Ingress @csengineer1990 (#9016) Added Flow Schema Icons @nwanduka (#9083) [UI]fix incorrect error message description @Shiva953 (#9071) Bump graphql from 16.6.0 to 16.8.1 in /ui @dependabot (#8862) chore: Remove lint-staged in package.json @nebula-aac (#9062) Disable edit and create action button in credential and fix all lint warning and errors @Yashsharma1911 (#9074) Bump fortio.org/fortio from 1.58.0 to 1.60.2 @dependabot (#8976) Bump graphql from 16.6.0 to 16.8.1 in /ui @dependabot (#8862) Bump golang.org/x/net from 0.15.0 to 0.17.0 in /scripts/component_generation @dependabot (#9079) [Docs] CSS removal and alert info background @leecalcote (#9092) Updated EKS Docs @aboobakersiddiqr63 (#9089) [Docs] MeshSync inclusion of component id label @leecalcote (#9090) Add docs for Bulk Operations and Metadata Renderers @ptdatta (#9086) Thank you to our contributors for making this release possible: @Aisuko, @Ayush9026, @MUzairS15, @Shiva953, @Yashsharma1911, @aabidsofi19, @aboobakersiddiqr63, @csengineer1990, @dependabot, @dependabot[bot], @l5io, @leecalcote, @nebula-aac, @nwanduka, @ptdatta, @theBeginner86 and l5io
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_plugin_bash_like.md

/ @kui-shell/plugin-bash-like doExecPipe(`argvs`, `repl`, `execOptions?`): `Promise`<`unknown`\> | Name | Type | | :- | : | | `argvs` | `string` | | `repl` | `default` | | `execOptions?` | `Pick`<`ExecOptions`, `"cwd"` \| `"env"` \| `"stderr"` \| `"stdout"`\> | `Promise`<`unknown`\> `Const` doExecWithPty(`namedParameters`): `Promise`<`any`\> Command handler that dispatches to an outer shell | Name | Type | | : | :-- | | `namedParameters` | `EvaluatorArgs`<`ParsedOptions`\> | `Promise`<`any`\> doExecWithStdoutViaPty<`O`\>(`args`): `Promise`<`string`\> Execute the given command using a pty, but return a string | Name | Type | | : | :- | | `O` | extends `ParsedOptions` = `ParsedOptions` | | Name | Type | | :-- | :-- | | `args` | `EvaluatorArgs`<`O`\> | `Promise`<`string`\> getSessionForTab(`tab`): `Promise`<`Channel`\> Return the session for the given tab | Name | Type | | :- | :- | | `tab` | `Tab` | `Promise`<`Channel`\> getTabState(`tab`, `key`): `any` | Name | Type | | :- | :-- | | `tab` | `default` | | `key` | `string` | `any` `Const` main(`N`, `server?`, `preexistingPort?`, `expectedCookie?`): `Promise`<`number` \| { `port`: `number` ; `wss`: `Server` }\> | Name | Type | | :-- | :-- | | `N` | `string` | | `server?` | `Server` | | `preexistingPort?` | `number` | | `expectedCookie?` | `SessionCookie` | `Promise`<`number` \| { `port`: `number` ; `wss`: `Server` }\>