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

Stop a node instance in YugabyteDB Anywhere universe Stop a node instance in YugabyteDB Anywhere universe. Stop the server processes running on the node. ``` yba universe node stop [flags] ``` ``` -h, --help help for stop ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -n, --name string [Required] The name of the universe for the corresponding node operations. --node-name string [Optional] The name of the universe node for the corresponding node operations. Required for add, reboot, release, remove, reprovision, start, stop. -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage YugabyteDB Anywhere universe nodes
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_update_config.md

title: "Command - devspace update config" sidebar_label: devspace update config Converts the active config to the current config version ``` devspace update config [flags] ``` ``` Updates the currently active config to the newest config version Note: This does not upgrade the overwrite configs ``` ``` -h, --help help for config ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile string The devspace profile to use (if there is any) --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) ```
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_core.ExecOptions.md

/ / ExecOptions .ExecOptions `Optional` alreadyWatching: `boolean` `Optional` block: `Optional` container: `Element` `Optional` contextChangeOK: `boolean` `Optional` createErrorStream: `StreamableFactory` `Optional` createOnly: `boolean` `Optional` createOutputStream: `StreamableFactory` `Optional` credentials: `Record`<`string`, `any`\> `Optional` custom: `any` `Optional` cwd: `string` cwd? `Optional` data: `string` \| `number` \| `Buffer` \| `Record`<`string`, `any`\> pass through uninterpreted data `Optional` delegationOk: `boolean` `Optional` echo: `boolean` `Optional` entity: `any` `Optional` env: `Record`<`string`, `string`\> environment variable map `Optional` exec: `"pexec"` \| `"qexec"` \| `"rexec"` `Optional` execUUID: `string` execution UUID `Optional` failWithUsage: `boolean` `Optional` filter: `any` `Optional` history: `number` `Optional` insertIdx: `number` `Optional` intentional: `boolean` `Optional` isDrilldown: `boolean` `Optional` isProxied: `boolean` `Optional` leaveBottomStripeAlone: `boolean` `Optional` nested: `boolean` `Optional` nextBlock: `HTMLElement` `Optional` noCoreRedirect: `boolean` `Optional` noDelegation: `boolean` `Optional` noHeader: `boolean` `Optional` noHistory: `boolean` `Optional` noRetry: `boolean` `Optional` noSidecarHeader: `boolean` `Optional` noStatus: `boolean` `Optional` parameters: `any` `Optional` pip: `Object` | Name | Type | | :- | :- | | `container` | `string` | | `returnTo` | `string` | `Optional` pipeStdin: `boolean` `Optional` placeholder: `string` `Optional` preserveBackButton: `boolean` `Optional` quiet: `boolean` `Optional` raw: `boolean` `Optional` rawResponse: `boolean` `Optional` render: `boolean` true, if you wish a qexec to return rendered HTML; default is false, meaning you get the model back on qexec `Optional` replSilence: `boolean` `Optional` reportErrors: `boolean` `Optional` rethrowErrors: `boolean` `Optional` showHeader: `boolean` `Optional` tab: force execution in a given tab? `Optional` type: `Optional` watch: `Object` pass watch state variables to subcommands being watched | Name | Type | | : | :- | | `accumulator` | `Record`<`string`, `any`\> | | `iteration` | `number` | `Optional` onExit(`exitCode`): `void` on job exit, pass the exitCode | Name | Type | | : | :- | | `exitCode` | `number` | `void` `Optional` onInit(`job`): \| `Promise`<\> on job init, pass the job, and get back a stdout; i.e. just before the PTY is brought up | Name | Type | | :- | :- | | `job` | | \| `Promise`<\> `Optional` onReady(`job`): `void` \| `Promise`<`void`\> on job ready, i.e. after the PTY is up, but before any data has been processed | Name | Type | | :- | :- | | `job` | | `void` \| `Promise`<`void`\> `Optional` stderr(`str`): `any` | Name | Type | | :- | :- | | `str` | `string` | `any` `Optional` stdout(`str`): `any` | Name | Type | | :- | : | | `str` | | `any`
Project: Pravega (App Definition and Development / Streaming & Messaging)
File: auth-plugin.md

<!-- Copyright Pravega Authors. 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. --> This guide describes in detail the Authentication/Authorization plugin model for Pravega. The custom implementation performs the implementation of the interface. Administrators and users are allowed to implement their own Authorization/Authentication plugins. Multiple plugins of such kind can exist together. The implementation of plugin follows the approach. The required Jars for the custom implementation needs to be located in the CLASSPATH to enable the access for Pravega Controller for implementation. Note: The custom implementation performs the implementation of the interface.
Project: YDB (App Definition and Development / Database)
File: ABSEIL_MANUAL.md

This document explains how to use Abseil throughout gRPC. Note that this isn't supposed to explain general usage of Abseil. gRPC intends to use the LTS versions of Abseil only because it simplifies dependency management. Abseil is being distributed via package distribution systems such as vcpkg and cocoapods. If gRPC depends on the certain version that aren't registered, gRPC in that system cannot get the right version of Abseil when being built, resulting in a build failure. Therefore, gRPC will use the LTS version only, preferably the latest one. Most of Abseil libraries are okay to use but there are some exceptions because they're not going well yet on some of our test machinaries or platforms it supports. The following is a list of targets that are NOT ready to use. `y_absl/synchronization:*`: Blocked by b/186685878. `y_absl/random`: . You can use Abseil in gRPC Core and gRPC C++. But you cannot use it in the public interface of gRPC C++ because i) it doesn't gurantee no breaking API changes like gRPC C++ does and ii) it may make users change their build system to address Abseil.
Project: ArangoDB (App Definition and Development / Database)
File: assume_value_lvalue.md

+++ title = "`valuetype &assumevalue() & noexcept`" description = "Narrow contract lvalue reference observer of any value present. Constexpr propagating, never throws." categories = ["observers"] weight = 600 +++ Narrow contract lvalue reference observer of any value present. `NoValuePolicy::narrowvaluecheck()` is first invoked, then the reference to the value is returned. The convention is that hard undefined behaviour occurs if no value is actually present, however `NoValuePolicy::narrowvaluecheck()` can do something to avoid that. Note that if `value_type` is `void`, only a `const` overload returning `void` is present. Requires: Always available. Complexity: Depends on `NoValuePolicy::narrowvaluecheck()`. Guarantees: An exception is never thrown.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: 163netease.md

title: "163 Net Ease" icon: /images/logos/powered-by/163netease.png hasLink: "https://www.163.com/" <!-- 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. -->
Project: KICS (Provisioning / Security & Compliance)
File: 4a8daf95-709d-4a36-9132-d3e19878fa34.md

title: API Gateway Endpoint Config is Not Private hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 4a8daf95-709d-4a36-9132-d3e19878fa34 Query name: API Gateway Endpoint Config is Not Private Platform: CloudFormation Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: The API Endpoint type in API Gateway should be set to PRIVATE so it's not exposed to the public internet<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="11 5" AWSTemplateFormatVersion: 2010-09-09 Resources: MyRestApi: Type: AWS::ApiGateway::RestApi Properties: Name: myRestApi MyRestApi2: Type: AWS::ApiGateway::RestApi Properties: EndpointConfiguration: Types: EDGE Name: myRestApi2 ``` ```json title="Positive test num. 2 - json file" hl_lines="6 14" { "AWSTemplateFormatVersion": "2010-09-09T00:00:00Z", "Resources": { "MyRestApi": { "Type": "AWS::ApiGateway::RestApi", "Properties": { "Name": "myRestApi" } }, "MyRestApi2": { "Type": "AWS::ApiGateway::RestApi", "Properties": { "EndpointConfiguration": { "Types": [ "EDGE" ] }, "Name": "myRestApi2" } } } } ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: 2010-09-09 Resources: MyRestApi: Type: AWS::ApiGateway::RestApi Properties: EndpointConfiguration: Types: PRIVATE Name: myRestApi ``` ```json title="Negative test num. 2 - json file" { "AWSTemplateFormatVersion": "2010-09-09T00:00:00Z", "Resources": { "MyRestApi": { "Type": "AWS::ApiGateway::RestApi", "Properties": { "EndpointConfiguration": { "Types": [ "PRIVATE" ] }, "Name": "myRestApi" } } } } ```
Project: VoltDB (App Definition and Development / Database)
File: KnownIssues.md

As any non-trivial software system, Google Mock has some known limitations and problems. We are working on improving it, and welcome your help! The follow is a list of issues we know about. The `README` file in release 1.1.0 still says that Google Mock only works with Google Test. Actually, you can configure Google Mock to work with any testing framework you choose. `gmockoutputtest` and `gmock-printers_test` are known to fail with Power PC CPUs. This is due to portability issues with these tests, and is not an indication of problems in Google Mock itself. You can safely ignore them. This only applies if you manually built and installed Google Test, and then built a Google Mock against it (either explicitly, or because gtest-config was in your path post-install). In this situation, Libtool has a known issue with certain systems' ldconfig setup: http://article.gmane.org/gmane.comp.sysutils.automake.general/9025 This requires a manual run of "sudo ldconfig" after the "sudo make install" for Google Test before any binaries which link against it can be executed. This isn't a bug in our install, but we should at least have documented it or hacked a work-around into our install. We should have one of these solutions in our next release.
Project: KICS (Provisioning / Security & Compliance)
File: b2ea2367-8dc9-4231-a035-d0b28bfa3dde.md

title: Nifcloud Computing Has Public Ingress Security Group Rule hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b2ea2367-8dc9-4231-a035-d0b28bfa3dde Query name: Nifcloud Computing Has Public Ingress Security Group Rule Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Networking and Firewall URL: An ingress security group rule allows traffic from /0<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "nifcloudsecuritygroup_rule" "positive" { securitygroupnames = ["http"] type = "IN" description = "HTTP from VPC" from_port = 80 to_port = 80 protocol = "TCP" cidr_ip = "0.0.0.0/0" } ``` ```tf title="Negative test num. 1 - tf file" resource "nifcloudsecuritygroup_rule" "negative" { securitygroupnames = ["http"] type = "IN" description = "HTTP from VPC" from_port = 80 to_port = 80 protocol = "TCP" cidr_ip = "10.0.0.0/16" } ```
Project: KICS (Provisioning / Security & Compliance)
File: 7f65be75-90ab-4036-8c2a-410aef7bb650.md

title: Kinesis SSE Not Configured hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 7f65be75-90ab-4036-8c2a-410aef7bb650 Query name: Kinesis SSE Not Configured Platform: CloudFormation Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: AWS Kinesis Stream should have SSE (Server Side Encryption) defined<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="8 26 19" Resources: EventStream1: Type: AWS::Kinesis::Stream Properties: Name: EventStream RetentionPeriodHours: 24 ShardCount: 1 StreamEncryption: EncryptionType: KMS Tags: Key: Name Value: !Sub ${EnvironmentName}-EventStream-${AWS::Region} EventStream2: Type: AWS::Kinesis::Stream Properties: Name: EventStream RetentionPeriodHours: 24 ShardCount: 1 StreamEncryption: KeyId: !Ref myKey Tags: Key: Name Value: !Sub ${EnvironmentName}-EventStream-${AWS::Region} EventStream3: Type: AWS::Kinesis::Stream Properties: Name: EventStream RetentionPeriodHours: 24 ShardCount: 1 Tags: Key: Name Value: !Sub ${EnvironmentName}-EventStream-${AWS::Region} ``` ```json title="Positive test num. 2 - json file" hl_lines="9 26 39" { "Resources": { "EventStream1": { "Type": "AWS::Kinesis::Stream", "Properties": { "Name": "EventStream", "RetentionPeriodHours": 24, "ShardCount": 1, "StreamEncryption": { "EncryptionType": "KMS" }, "Tags": [ { "Key": "Name", "Value": "${EnvironmentName}-EventStream-${AWS::Region}" } ] } }, "EventStream2": { "Type": "AWS::Kinesis::Stream", "Properties": { "Name": "EventStream", "RetentionPeriodHours": 24, "ShardCount": 1, "StreamEncryption": { "KeyId": "myKey" }, "Tags": [ { "Key": "Name", "Value": "${EnvironmentName}-EventStream-${AWS::Region}" } ] } }, "EventStream3": { "Type": "AWS::Kinesis::Stream", "Properties": { "Name": "EventStream", "RetentionPeriodHours": 24, "ShardCount": 1, "Tags": [ { "Key": "Name", "Value": "${EnvironmentName}-EventStream-${AWS::Region}" } ] } } } } ``` ```yaml title="Negative test num. 1 - yaml file" Resources: EventStream: Type: AWS::Kinesis::Stream Properties: Name: EventStream RetentionPeriodHours: 24 ShardCount: 1 StreamEncryption: EncryptionType: KMS KeyId: !Ref myKey Tags: Key: Name Value: !Sub ${EnvironmentName}-EventStream-${AWS::Region} ``` ```json title="Negative test num. 2 - json file" { "Resources": { "EventStream": { "Type": "AWS::Kinesis::Stream", "Properties": { "Tags": [ { "Key": "Name", "Value": "${EnvironmentName}-EventStream-${AWS::Region}" } ], "Name": "EventStream", "RetentionPeriodHours": 24, "ShardCount": 1, "StreamEncryption": { "EncryptionType": "KMS", "KeyId": "myKey" } } } } } ```
Project: Flink (App Definition and Development / Streaming & Messaging)
File: hadoop.md

title: "Hadoop" weight: 4 type: docs aliases: /dev/connectors/formats/hadoop.html /apis/streaming/connectors/formats/hadoop.html <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you 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. --> Support for Hadoop is contained in the `flink-hadoop-compatibility` Maven module. Add the following dependency to your `pom.xml` to use hadoop ```xml <dependency> <groupId>org.apache.flink</groupId> <artifactId>flink-hadoop-compatibility{{< scala_version >}}</artifactId> <version>{{< version >}}</version> </dependency> ``` If you want to run your Flink application locally (e.g. from your IDE), you also need to add a `hadoop-client` dependency such as: ```xml <dependency> <groupId>org.apache.hadoop</groupId> <artifactId>hadoop-client</artifactId> <version>2.10.2</version> <scope>provided</scope> </dependency> ``` To use Hadoop `InputFormats` with Flink the format must first be wrapped using either `readHadoopFile` or `createHadoopInput` of the `HadoopInputs` utility class. The former is used for input formats derived from `FileInputFormat` while the latter has to be used for general purpose input formats. The resulting `InputFormat` can be used to create a data source by using `ExecutionEnvironment#createInput`. The resulting `DataStream` contains 2-tuples where the first field is the key and the second field is the value retrieved from the Hadoop InputFormat. The following example shows how to use Hadoop's `TextInputFormat`. {{< tabs "baa59ec9-046e-4fe3-a2db-db5ee09d0635" >}} {{< tab "Java" >}} ```java StreamExecutionEnvironment env = StreamExecutionEnvironment.getExecutionEnvironment(); KeyValueTextInputFormat textInputFormat = new KeyValueTextInputFormat(); DataStream<Tuple2<Text, Text>> input = env.createInput(HadoopInputs.readHadoopFile( textInputFormat, Text.class, Text.class, textPath)); // Do something with the data. [...] ``` {{< /tab >}} {{< tab "Scala" >}} ```scala val env = StreamExecutionEnvironment.getExecutionEnvironment val textInputFormat = new KeyValueTextInputFormat val input: DataStream[(Text, Text)] = env.createInput(HadoopInputs.readHadoopFile( textInputFormat, classOf[Text], classOf[Text], textPath)) // Do something with the data. [...] ``` {{< /tab >}} {{< /tabs >}} {{< top >}}
Project: StarRocks (App Definition and Development / Database)
File: load_tracking_logs.md

displayed_sidebar: "English" `loadtrackinglogs` provides error logs of load jobs. This view is supported from StarRocks v3.0 onwards. The following fields are provided in `loadtrackinglogs`: | Field | Description | | - | | | JOB_ID | The ID of the load job. | | LABEL | The label of the load job. | | DATABASE_NAME | The database that the load job belongs to. | | TRACKING_LOG | Errors (if any) of the load job. | :::tip To query the view `loadtrackinglogs` you will need to filter on either a `JOB_ID` or a `LABEL`. You can retrieve the `JOBID` or `LABEL` of a load job from the view `informationschema.loads`. Example: ```sql SELECT * from informationschema.loadtrackinglogs WHERE label ='userbehavior'\G row * JOB_ID: 10141 LABEL: user_behavior DATABASE_NAME: mydatabase TRACKING_LOG: NULL TYPE: BROKER 1 row in set (0.02 sec) ``` :::
Project: ArangoDB (App Definition and Development / Database)
File: is_error_type_enum.md

+++ title = "`iserrortype_enum<E, Enum>`" description = "A customisable integral constant type true for `E` types constructible from `Enum` types which are to receive error throwing no-value policies." +++ A customisable integral constant type true for `E` types constructible from `Enum` types which are to receive error throwing no-value policies Overridable: By template specialisation into the `trait` namespace. Default: False. Specialisations exist for: `<boost/outcome/boost_result.hpp>` `boost::system::errorcode` to `boost::system::iserrorconditionenum<Enum>::value`. `<boost/outcome/std_result.hpp>` `std::errorcode` to `std::iserrorconditionenum<Enum>::value`. Namespace: `BOOSTOUTCOMEV2_NAMESPACE::trait` Header: `<boost/outcome/trait.hpp>`
Project: KICS (Provisioning / Security & Compliance)
File: d0c13053-d2c8-44a6-95da-d592996e9e67.md

title: CloudFront Without Minimum Protocol TLS 1.2 hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: d0c13053-d2c8-44a6-95da-d592996e9e67 Query name: CloudFront Without Minimum Protocol TLS 1.2 Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: CloudFront Minimum Protocol version should be at least TLS 1.2<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="40 18 37" name: create a distribution with an origin and logging community.aws.cloudfront_distribution: state: present caller_reference: unique test distribution ID origins: id: 'my test origin-000111' domain_name: www.example.com origin_path: /production custom_headers: header_name: MyCustomHeaderName header_value: MyCustomHeaderValue logging: enabled: true include_cookies: false bucket: mylogbucket.s3.amazonaws.com prefix: myprefix/ viewer_certificate: minimumprotocolversion: TLSv1 comment: this is a CloudFront distribution with logging name: create another distribution with an origin and logging community.aws.cloudfront_distribution: state: present caller_reference: unique test distribution ID origins: id: 'my test origin-000111' domain_name: www.example.com origin_path: /production custom_headers: header_name: MyCustomHeaderName header_value: MyCustomHeaderValue logging: enabled: true include_cookies: false bucket: mylogbucket.s3.amazonaws.com prefix: myprefix/ viewer_certificate: minimumprotocolversion: TLSv1.1_2016 comment: this is a CloudFront distribution with logging name: create a third distribution community.aws.cloudfront_distribution: state: present caller_reference: unique test distribution ID origins: id: 'my test origin-000111' domain_name: www.example.com origin_path: /production custom_headers: header_name: MyCustomHeaderName header_value: MyCustomHeaderValue logging: enabled: true include_cookies: false bucket: mylogbucket.s3.amazonaws.com prefix: myprefix/ comment: this is a CloudFront distribution with logging ``` ```yaml title="Negative test num. 1 - yaml file" name: create a distribution with an origin and logging community.aws.cloudfront_distribution: state: present caller_reference: unique test distribution ID origins: id: 'my test origin-000111' domain_name: www.example.com origin_path: /production custom_headers: header_name: MyCustomHeaderName header_value: MyCustomHeaderValue logging: enabled: true include_cookies: false bucket: mylogbucket.s3.amazonaws.com prefix: myprefix/ viewer_certificate: minimumprotocolversion: TLSv1.2_2018 comment: this is a CloudFront distribution with logging ```