cwielenb/CNCF-Dataset huggingface dataset:
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_core.Events.NewTabRequestEvent.md

/ / / NewTabRequestEvent ..NewTabRequestEvent `Optional` background: `boolean` Optionally specify to create the new tab without switching to it tabs: { `cmdline?`: `string` ; `exec?`: `"pexec"` \| `"qexec"` ; `onClose?`: `string` ; `statusStripeDecoration?`: ; `title?`: `string` }[]
Project: YDB (App Definition and Development / Database)
File: byteat.md

Getting the byte value inside a string at an index counted from the beginning of the string. If an invalid index is specified, `NULL` is returned. Arguments: String: `String` or `Utf8`. Index: `Uint32`. Examples ```yql SELECT ByteAt("foo", 0), -- 102 ByteAt("foo", 1), -- 111 ByteAt("foo", 9); -- NULL ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: azurerm_webapps.md

+++ title = "azurerm_webapps resource" draft = false gh_repo = "inspec" platform = "azure" [menu] [menu.inspec] title = "azurerm_webapps" identifier = "inspec/resources/azure/azurermwebapps.md azurermwebapps resource" parent = "inspec/resources/azure" +++ {{< inspec/azurermdeprecated resource="azurewebapps" >}} Use the `azurerm_webapps` InSpec audit resource to enumerate Webapps. This resource interacts with version `2016-08-01` of the Azure Management API. For more information see the . At the moment, there doesn't appear to be a way to select the version of the Azure API docs. If you notice a newer version being referenced in the official documentation please open an issue or submit a pull request using the updated version. This resource is available in the `inspec-azure` [resource pack](/inspec/glossary/#resource-pack). To use it, add the following to your `inspec.yml` in your top-level profile: depends: inspec-azure: git: https://github.com/inspec/inspec-azure.git You'll also need to setup your Azure credentials; see the resource pack . An `azurerm_webapps` resource block identifies Webapps by Resource Group. describe azurermwebapps(resourcegroup: 'ExampleGroup') do ... end describe azurermwebapps(resourcegroup: 'ExampleGroup') do its('names') { should include('webapp_name') } end `names` The name of the Webapp its('names') { should include('webapp_name') } {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The control will pass if the resource returns a result. Use `should_not` if you expect zero matches. describe azurermwebapps(resourcegroup: 'ExampleGroup') do it { should exist } end describe azurermwebapps(resourcegroup: 'EmptyExampleGroup') do it { should_not exist } end Your [Service Principal](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal) must be setup with a `contributor` role on the subscription you wish to test.
Project: YugabyteDB (App Definition and Development / Database)
File: drop_domain.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="552" height="100" viewbox="0 0 552 100"><path class="connector" d="M0 52h15m53 0h10m70 0h30m32 0h10m64 0h20m-141 0q5 0 5 5v8q0 5 5 5h116q5 0 5-5v-8q0-5 5-5m5 0h30m-5 0q-5 0-5-5v-20q0-5 5-5h20m24 0h20q5 0 5 5v20q0 5-5 5m-5 0h50m77 0h22m-109 25q0 5 5 5h5m79 0h5q5 0 5-5m-104-25q5 0 5 5v33q0 5 5 5h89q5 0 5-5v-33q0-5 5-5m5 0h15"/><polygon points="0,59 5,52 0,45" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="35" width="53" height="25" rx="7"/><text class="text" x="25" y="52">DROP</text><rect class="literal" x="78" y="35" width="70" height="25" rx="7"/><text class="text" x="88" y="52">DOMAIN</text><rect class="literal" x="178" y="35" width="32" height="25" rx="7"/><text class="text" x="188" y="52">IF</text><rect class="literal" x="220" y="35" width="64" height="25" rx="7"/><text class="text" x="230" y="52">EXISTS</text><rect class="literal" x="349" y="5" width="24" height="25" rx="7"/><text class="text" x="359" y="22">,</text><a xlink:href="../../../syntaxresources/grammardiagrams#name"><rect class="rule" x="334" y="35" width="54" height="25"/><text class="text" x="344" y="52">name</text></a><rect class="literal" x="438" y="35" width="77" height="25" rx="7"/><text class="text" x="448" y="52">CASCADE</text><rect class="literal" x="438" y="65" width="79" height="25" rx="7"/><text class="text" x="448" y="82">RESTRICT</text><polygon points="548,59 552,59 552,45 548,45" style="fill:black;stroke-width:0"/></svg>
Project: KICS (Provisioning / Security & Compliance)
File: 2fc5ab5a-c5eb-4ae4-b687-0f16fe77c255.md

title: WAF Is Disabled For Azure Application Gateway hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 2fc5ab5a-c5eb-4ae4-b687-0f16fe77c255 Query name: WAF Is Disabled For Azure Application Gateway Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: Check if Web Application Firewall is disabled or not configured for Azure's Application Gateway.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="7" name: Create instance of Application Gateway azurermappgateway: resource_group: myResourceGroup name: myAppGateway sku: name: standard_small tier: standard capacity: 2 ``` ```yaml title="Negative test num. 1 - yaml file" name: Create instance of Application Gateway azurermappgateway: resource_group: myResourceGroup name: myAppGateway sku: name: waf_medium tier: waf capacity: 2 ```
Project: BigchainDB (App Definition and Development / Database)
File: ROADMAP.md

<! Copyright 2020 Interplanetary Database Association e.V., BigchainDB and IPDB software contributors. SPDX-License-Identifier: (Apache-2.0 AND CC-BY-4.0) Code is Apache-2.0 and docs are CC-BY-4.0 > We moved the BigchainDB Roadmap to the bigchaindb/org repository; see: (We kept this file here to avoid breaking some links.)
Project: KICS (Provisioning / Security & Compliance)
File: 559439b2-3e9c-4739-ac46-17e3b24ec215.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: 559439b2-3e9c-4739-ac46-17e3b24ec215 Query name: API Gateway Endpoint Config is Not Private Platform: Ansible 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="8" name: Setup AWS API Gateway setup on AWS and deploy API definition community.aws.awsapigateway: swaggerfile: myapi.yml stage: production cache_enabled: true cache_size: '1.6' tracing_enabled: true endpoint_type: EDGE state: present ``` ```yaml title="Negative test num. 1 - yaml file" name: Setup AWS API Gateway setup on AWS and deploy API definition community.aws.awsapigateway: swaggerfile: myapi.yml stage: production cache_enabled: true cache_size: '1.6' tracing_enabled: true endpoint_type: PRIVATE state: present ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.0-rc.5w.md

layout: release date: 2022-06-11 tag: v0.6.0-rc.5w language: en Fix failing save context for incluster @Revolyssup (#5601) [dde] UI Change to adapt to the exposed server version @sudo-NithishKarthik (#5596) fix: Service mesh provisioning @sudo-NithishKarthik (#5595) exposed meshery server version in dde @warunicorn19 (#5591) Fix panic @Revolyssup (#5593) Fix NATS connectivity test @MUzairS15 (#5583) Multi context refactor @Revolyssup (#5528) Ci/marioarriaga92/5592 fix cypress v10 legacy config file error @MarioArriaga92 (#5597) [UI] Pattern file bug fixes @Chadha93 (#5587) [UI] Settings button style fix for lifecycle @Chadha93 (#5588) material-ui/core from 4.12.3 to 4.12.4 @Harshit-Dandriyal (#5585) [UI] Pattern file bug fixes @Chadha93 (#5587) Bump google.golang.org/grpc from 1.46.0 to 1.47.0 @dependabot (#5560) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Chadha93, @Harshit-Dandriyal, @MUzairS15, @MarioArriaga92, @Revolyssup, @dependabot, @l5io, @leecalcote, @sudo-NithishKarthik, @warunicorn19 and Nithish
Project: Druid (App Definition and Development / Database)
File: cla.md

title: Druid Contributor License Agreement layout: simple_page canonical: 'https://druid.apache.org/community/cla' <!-- 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. --> Edit this page in the repo. To see your changes, navigate to them from the .
Project: Meshery (Provisioning / Automation & Configuration)
File: flyte-sandbox.md

layout: integration title: Flyte Sandbox subtitle: Collaborative and visual infrastructure as code for Flyte Sandbox image: /assets/img/integrations/flyte-sandbox/icons/color/flyte-sandbox-color.svg permalink: extensibility/integrations/flyte-sandbox docURL: https://docs.meshery.io/extensibility/integrations/flyte-sandbox description: integrations-category: Provisioning integrations-subcategory: Security & Compliance registrant: Artifact Hub components: name: scheduled-spark-application colorIcon: assets/img/integrations/flyte-sandbox/components/scheduled-spark-application/icons/color/scheduled-spark-application-color.svg whiteIcon: assets/img/integrations/flyte-sandbox/components/scheduled-spark-application/icons/white/scheduled-spark-application-white.svg description: name: spark-application colorIcon: assets/img/integrations/flyte-sandbox/components/spark-application/icons/color/spark-application-color.svg whiteIcon: assets/img/integrations/flyte-sandbox/components/spark-application/icons/white/spark-application-white.svg description: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: KICS (Provisioning / Security & Compliance)
File: f34508b9-f574-4330-b42d-88c44cced645.md

title: Hardcoded AWS Access Key In Lambda hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: f34508b9-f574-4330-b42d-88c44cced645 Query name: Hardcoded AWS Access Key In Lambda Platform: Ansible Severity: <span style="color:#bb2124">High</span> Category: Secret Management URL: Lambda access/secret keys should not be hardcoded<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="32 3" name: looped creation community.aws.lambda: awsaccesskey: 'wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY' name: '{{ item.name }}' state: present zipfile: '{{ item.zipfile }}' runtime: 'python2.7' role: 'arn:aws:iam::987654321012:role/lambdabasicexecution' handler: 'hellopython.myhandler' vpcsubnetids: subnet-123abcde subnet-edcba321 vpcsecuritygroup_ids: sg-123abcde sg-edcba321 environmentvariables: '{{ item.envvars }}' tags: key1: 'value1' loop: name: HelloWorld zip_file: hello-code.zip env_vars: key1: "first" key2: "second" name: ByeBye zip_file: bye-code.zip env_vars: key1: "1" key2: "2" name: remove tags community.aws.lambda: awsaccesskey: 'wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY' name: 'Lambda function' state: present zip_file: 'code.zip' runtime: 'python2.7' role: 'arn:aws:iam::987654321012:role/lambdabasicexecution' handler: 'hellopython.myhandler' tags: {} name: Delete Lambda functions HelloWorld and ByeBye community.aws.lambda: name: '{{ item }}' state: absent loop: HelloWorld ByeBye ``` ```yaml title="Negative test num. 1 - yaml file" name: looped creation community.aws.lambda: name: '{{ item.name }}' state: present zipfile: '{{ item.zipfile }}' runtime: python2.7 role: arn:aws:iam::987654321012:role/lambdabasicexecution handler: hellopython.myhandler vpcsubnetids: subnet-123abcde subnet-edcba321 vpcsecuritygroup_ids: sg-123abcde sg-edcba321 environmentvariables: '{{ item.envvars }}' tags: key1: value1 loop: name: HelloWorld zip_file: hello-code.zip env_vars: key1: first key2: second name: ByeBye zip_file: bye-code.zip env_vars: key1: '1' key2: '2' name: remove tags community.aws.lambda: name: Lambda function state: present zip_file: code.zip runtime: python2.7 role: arn:aws:iam::987654321012:role/lambdabasicexecution handler: hellopython.myhandler tags: {} name: Delete Lambda functions HelloWorld and ByeBye community.aws.lambda: name: '{{ item }}' state: absent loop: HelloWorld ByeBye ```
Project: KICS (Provisioning / Security & Compliance)
File: f4e9ff70-0f3b-4c50-a713-26cbe7ec4039.md

title: SQLServer Ingress From Any IP hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: f4e9ff70-0f3b-4c50-a713-26cbe7ec4039 Query name: SQLServer Ingress From Any IP Platform: Ansible Severity: <span style="color:#ff0000">Critical</span> Category: Networking and Firewall URL: Check if all IPs are allowed, check from start 0.0.0.0 to end 255.255.255.255.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="8" name: Create (or update) Firewall Rule azure.azcollection.azurermsqlfirewallrule: resource_group: myResourceGroup server_name: firewallrulecrudtest-6285 name: firewallrulecrudtest-5370 startipaddress: 0.0.0.0 endipaddress: 255.255.255.255 ``` ```yaml title="Negative test num. 1 - yaml file" name: Create (or update) Firewall Rule azure.azcollection.azurermsqlfirewallrule: resource_group: myResourceGroup server_name: firewallrulecrudtest-6285 name: firewallrulecrudtest-5370 startipaddress: 172.28.10.136 endipaddress: 172.28.10.138 name: Create (or update) Firewall Rule2 azure.azcollection.azurermsqlfirewallrule: resource_group: myResourceGroup server_name: firewallrulecrudtest-6285 name: firewallrulecrudtest-5370 startipaddress: 0.0.0.0 endipaddress: 0.0.0.3 name: Create (or update) Firewall Rule3 azure.azcollection.azurermsqlfirewallrule: resource_group: myResourceGroup server_name: firewallrulecrudtest-6285 name: firewallrulecrudtest-5370 startipaddress: 255.255.255.250 endipaddress: 255.255.255.255 ```
Project: TiDB (App Definition and Development / Database)
File: TEMPLATE.md

Author(s): , , ... Discussion PR: https://github.com/pingcap/tidb/pull/XXX Tracking Issue: https://github.com/pingcap/tidb/issues/XXX * * One para explanation of the proposal that helps others get the brief info of this design doc. What's the background and the problem being solved by this design doc? What use cases does it support? Please pay attention to this section. When a design is under review, the reviewers usually do not rush into details, but try to figure out the motivation or background of it. In other words, who wants the feature or what problem the feature solves. Explain the design in enough detail that: it is reasonably clear how the feature would be implemented, corner cases are dissected by example, how the feature is used, etc. It's better to describe the pseudo-code of the key algorithm, API interfaces, the UML graph, what components are needed to be changed in this section. Compatibility is important, please also take into consideration, a checklist: Compatibility with other features, like partition table, security&privilege, collation&charset, clustered index, async commit, etc. Compatibility with other internal components, like parser, DDL, planner, statistics, executor, etc. Compatibility with other external components, like PD, TiKV, TiFlash, BR, TiCDC, Dumpling, TiUP, K8s, etc. Upgrade compatibility Downgrade compatibility A brief description of how the implementation will be tested. Both the integration test and the unit test should be considered. It's used to ensure the basic feature function works as expected. Both the integration test and the unit test should be considered. It's used to ensure this feature works as expected in some common scenarios. A checklist to test compatibility: Compatibility with other features, like partition table, security & privilege, charset & collation, clustered index, async commit, etc. Compatibility with other internal components, like parser, DDL, planner, statistics, executor, etc. Compatibility with other external components, like PD, TiKV, TiFlash, BR, TiCDC, Dumpling, TiUP, K8s, etc. Upgrade compatibility Downgrade compatibility The following two parts need to be measured: The performance of this feature under different parameters The performance influence on the online workload Describe the potential impacts & risks of the design on overall performance, security, k8s, and other aspects. List all the risks or unknowns by far. Please describe impacts and risks in two sections: Impacts could be positive or negative, and intentional. Risks are usually negative, unintentional, and may or may not happen. E.g., for performance, we might expect a new feature to improve latency by 10% (expected impact), there is a risk that latency in scenarios X and Y could degrade by 50%. How do other systems solve this issue? What other designs have been considered and what is the rationale for not choosing them? What parts of the design are still to be determined?
Project: LinuxKit (Provisioning / Automation & Configuration)
File: platform-hyperv.md

LinuxKit supports running LinuxKit created VMs on Hyper-V on Microsoft Windows. `linuxkit` must be run from an elevated command prompt, typically a elevated Powershell and utilises Powershell scripting to manage the Hyper-V VMs. Example: ```sh linuxkit.exe run --disk size=1 linuxkit-efi.iso ``` The Hyper-V VM, by default, is named after the prefix of the ISO, ie with `.iso` and `-efi` stripped. Note, You may only have one VM for a given name. You can specify an alternative name using the `-name` command-line option. Currently, the Hyper-V backend only supports booting EFI ISO images created with LinuxKit. `linuxkit` create a Generation 2 VM and disables secure EFI boot for booting. In the future, we may add support for legacy BIOS ISOs, booting from disks, and enable secure boot. The serial port of the VM is configured to redirect to a Named Pipe, and when the `linuxkit` command is executed an interactive console is provided in the same window. The serial console may also be redirected to a file. Note: The connection to the Named Pipe sometimes seems to be a bit racey, though the code itself should be fine. You may have to try again if the connection to the serial console fails. If the main console is configured within the VM, one can also connect to it using the Hyper-V manager, or from the command-line: ```sh vmconnect.exe localhost linuxkit ``` The Hyper-V backend supports multiple disks to be attached to the VM using the standard `linuxkit` `-disk` syntax. While Hyper-V typically stores disk images under a default location, if the VM is created with `linuxkit`, by default, new disks are created in the current directory. By default, the Hyper-V backend will try to find an external switch configured by the user and use this for network connectivity for the VM. This means that DHCP will be provided by the normal DHCP server on your network. Depending on your firewall settings, you may be able to access the VM directly via its IP address. Alternatively, you can specify a Hyper-V switch to use using the `-switch` command-line option. In this case it is the user's responsibility to provide a DHCP server or to configure the VM's IP address by some other means. LinuxKit does not yet have packages for Hyper-V integration agents (KVP and VSS daemons). We plan to add them soon. The Hyper-V backend currently does not support passing metadata/userdata to the VM.
Project: ShardingSphere (App Definition and Development / Database)
File: show-shadow-rule.en.md

+++ title = "SHOW SHADOW RULE" weight = 1 +++ The `SHOW SHADOW RULE` syntax is used to query shadow rules for specified database. {{< tabs >}} {{% tab name="Grammar" %}} ```sql ShowEncryptRule::= 'SHOW' 'SHADOW' ('RULES' | 'RULE' shadowRuleName) ('FROM' databaseName)? shadowRuleName ::= identifier databaseName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} When `databaseName` is not specified, the default is the currently used `DATABASE`. If `DATABASE` is not used, `No database selected` will be prompted. | Column | Description | |--|-| | rule_name | Shadow rule name | | source_name | Data source name | | shadow_name | Shadow data source name | | shadow_table | Shadow table | Query specified shadow rule in specified database. ```sql SHOW SHADOW RULE shadowrule FROM shadowdb; ``` ```sql mysql> SHOW SHADOW RULE shadowrule FROM shadowdb; +-+-+-+-+ | rulename | sourcename | shadowname | shadowtable | +-+-+-+-+ | shadowrule | ds0 | ds1 | torderitem,torder | +-+-+-+-+ 1 row in set (0.00 sec) ``` Query specified shadow rule in current database. ```sql SHOW SHADOW RULE shadow_rule; ``` ```sql mysql> SHOW SHADOW RULE shadow_rule; +-+-+-+-+ | rulename | sourcename | shadowname | shadowtable | +-+-+-+-+ | shadowrule | ds0 | ds1 | torderitem,torder | +-+-+-+-+ 1 row in set (0.01 sec) ``` Query shadow rules for specified database. ```sql SHOW SHADOW RULES FROM shadow_db; ``` ```sql mysql> SHOW SHADOW RULES FROM shadow_db; +-+-+-+-+ | rulename | sourcename | shadowname | shadowtable | +-+-+-+-+ | shadowrule | ds0 | ds1 | torderitem,torder | +-+-+-+-+ 1 row in set (0.00 sec) ``` Query shadow rules for current database. ```sql SHOW SHADOW RULES; ``` ```sql mysql> SHOW SHADOW RULES; +-+-+-+-+ | rulename | sourcename | shadowname | shadowtable | +-+-+-+-+ | shadowrule | ds0 | ds1 | torderitem,torder | +-+-+-+-+ 1 row in set (0.00 sec) ``` `SHOW`, `SHADOW`, `RULE`, `RULES`, `FROM`
Project: Beam (App Definition and Development / Streaming & Messaging)
File: 28_io_jdbc.md

Prompt: Is Oracle Java Database Connectivity (JDBC) supported in Apache Beam? Response: The is a Java API for connecting to relational databases. Apache Beam supports reading and writing data with JDBC using the `ReadFromJdbc` and `WriteToJdbc` transforms in the `JdbcIO` module. For more information, see the JdbcIO connector documentation for the following languages: To get started with JDBC and Apache Beam, refer to the . Here is an example of Apache Beam pipeline code for reading data with JDBC: ```python class ExampleRow(NamedTuple): id: int name: str class ReadJdbcOptions(PipelineOptions): @classmethod def addargparse_args(cls, parser): parser.add_argument( "--driverClassName", help="JDBC driver class name") parser.add_argument( "--url", help="JDBC URL") parser.add_argument( "--username", help="JDBC username") parser.add_argument( "--password", help="JDBC password") parser.add_argument( "--query", default="SELECT * FROM users", help="JDBC query") options = ReadJdbcOptions() with beam.Pipeline(options=options) as p: (p | "Read from JDBC" >> ReadFromJdbc( driverClassName=options.driverClassName, url=options.url, username=options.username, password=options.password, query=options.query) | Map(logging.info)) ```