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

displayed_sidebar: "English" Recovers a database, table, or partition that was dropped by using the DROP command. The dropped database, table, or partition can be recovered within the period specified by the FE parameter `catalogtrashexpire_second` (1 day by default). Data deleted by using cannot be recovered. Recover a database. ```sql RECOVER DATABASE <db_name> ``` Recover a table. ```sql RECOVER TABLE [<dbname>.]<tablename> ``` Recover a partition. ```sql RECOVER PARTITION <partitionname> FROM [<dbname>.]<table_name> ``` Note: This command can only recover metadata deleted some time ago (1 day by default). You can change the duration by adjusting the FE parameter `catalogtrashexpire_second`. If the metadata is deleted with identical metadata created, the previous one will not be recovered. Recover database `example_db`. ```sql RECOVER DATABASE example_db; ``` Recover table `example_tbl`. ```sql RECOVER TABLE exampledb.exampletbl; ``` Recover partition `p1` in the `example_tbl` table. ```sql RECOVER PARTITION p1 FROM example_tbl; ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: go-dependencies.md

type: languages title: "Go SDK Dependencies" <!-- 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. --> Beam Go uses for package management. Compile and runtime dependencies for your Beam SDK version are listed in `go.sum` in the Beam repository. This can be found at ``` https://raw.githubusercontent.com/apache/beam/v<VERSION_NUMBER>/sdks/go.sum ``` <p class="paragraph-wrap">Replace `&lt;VERSIONNUMBER&gt;` with the major.minor.patch version of the SDK. For example, <a href="https://raw.githubusercontent.com/apache/beam/v{{< param releaselatest >}}/sdks/go.sum" target="blank" rel="noopener noreferrer">https://raw.githubusercontent.com/apache/beam/v{{< param releaselatest >}}/sdks/go.sum</a> will provide the dependencies for the {{< param release_latest >}} release.</p> Note: To just view direct dependencies, you can view the `go.mod` file instead, direct dependencies are listed in the initial `require` statement. This can be found at `https://raw.githubusercontent.com/apache/beam/v<VERSION_NUMBER>/sdks/go.mod`
Project: YDB (App Definition and Development / Database)
File: substring.md

Returns a substring. Required arguments: Source string; Position: The offset from the beginning of the string in bytes (integer) or `NULL` meaning "from the beginning". Optional arguments: Substring length: The number of bytes starting from the specified position (an integer, or the default `NULL` meaning "up to the end of the source string"). Indexing starts from zero. If the specified position and length are beyond the string, returns an empty string. If the input string is optional, the result is also optional. Examples ```yql SELECT SUBSTRING("abcdefg", 3, 1); -- d ``` ```yql SELECT SUBSTRING("abcdefg", 3); -- defg ``` ```yql SELECT SUBSTRING("abcdefg", NULL, 3); -- abc ```
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: API-012-content-type.md

Accepted Not adding content-type to state store, pubsub and bindings. We will not add content-type since it is a persisted metadata and it can cause problems such as: Long term support since metadata persisted previously would need to be supported indefinitely. Added requirement for components to implement, leading to potentially hacky implementations to persist metadata side-by-side with data. Original issue and discussion: https://github.com/dapr/dapr/issues/2026 SDKs need to handle deserialization on their end, requiring enough context in the API to determine how to handle type deserialization.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.89.md

layout: release date: 2023-05-25 tag: v0.6.89 Fix search and add counts to meshmodel APIs @abdullah1308 (#7685) [Meshsync Subsription Leak] Fix GrapqhQL subscription memory leak @Abhishek-kumar09 (#7714) [Playground] Deployment update for single node k8s cluster @leecalcote (#7718) Fixed import package @acald-creator (#7723) [Playground] NGINX container config @leecalcote (#7712) Add Playground host names and SSH @leecalcote (#7706) add network policy as a relationship @MUzairS15 (#7702) [cypress] Skip few e2e tests until fixed. @Abhishek-kumar09 (#7734) Fixing e2e test for user_spec @Freedisch (#7658) Meshmodel Browser phase 1 - Components and Models Summary @UsmanDev09 (#7672) save and delete designs in grid view @sudhanshutech (#7725) Migrate meshery-ui tracking to google tag manager @ayushthe1 (#7656) [Meshmap] Dark mode enhancements @Shivam-AfA (#7709) [UI] fixed dark mode issues in Meshery UI @Yashsharma1911 (#7413) [UI] Settings: Addressing inconsistencies between sections @UsmanDev09 (#7701) Fixed pagination issue in meshery design page @senali-d (#7698) [bug] Fix Meshery server crash on policy evaluation @theBeginner86 (#7729) Fixing e2e test for user_spec @Freedisch (#7658) [playground] Add missing restart policy to Meshery Docker Compose @theBeginner86 (#7731) [bug] Fix Meshery server crash on policy evaluation @theBeginner86 (#7729) [chore] Fix user search @theBeginner86 (#7711) Github Action to tweet when labeled with tag "issue/tweet" @gopivaibhav (#6770) Modify CLI guide for docs @alphaX86 (#7713) Feature Description Added Importing App Manifest @thisiskaransgit (#7704) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Chadha93, @Freedisch, @MUzairS15, @MarioArriaga92, @Shivam-AfA, @UsmanDev09, @Yashsharma1911, @abdullah1308, @acald-creator, @alphaX86, @ayushthe1, @gopivaibhav, @leecalcote, @muhammmadusman3211, @senali-d, @sudhanshutech, @theBeginner86, @thisiskaransgit and MUzairS15
Project: Meshery (Provisioning / Automation & Configuration)
File: cdk8s.md

layout: integration title: Cdk For Kubernetes (Cdk8S) subtitle: Collaborative and visual infrastructure as code for Cdk For Kubernetes (Cdk8S) image: /assets/img/integrations/cdk8s/icons/color/cdk8s-color.svg permalink: extensibility/integrations/cdk8s docURL: https://docs.meshery.io/extensibility/integrations/cdk8s description: integrations-category: Provisioning integrations-subcategory: Automation & Configuration registrant: Artifact Hub components: featureList: [ "Defines Kubernetes applications and reusable abstractions using familiar programming languages.", "Simplify application workflows.", "Compose and share reusable components through code libraries." ] howItWorks: "Deploy through GitOps" howItWorksDetails: "cdk8s is an open-source software development framework for defining Kubernetes applications and reusable abstractions using familiar programming languages and rich object-oriented APIs. cdk8s apps synthesize into standard Kubernetes manifests which can be applied to any Kubernetes cluster." language: en list: include type: extensibility category: integrations
Project: ShardingSphere (App Definition and Development / Database)
File: load-balance.en.md

+++ title = "Load Balance Algorithm" weight = 4 +++ ShardingSphere built-in provides a variety of load balancer algorithms, including polling algorithm, random access algorithm and weight access algorithm, which can meet users' needs in most business scenarios. Moreover, considering the complexity of the business scenario, the built-in algorithm also provides an extension mode. Users can implement the load balancer algorithm they need based on SPI interface. Type: ROUND_ROBIN Type: RANDOM Type: WEIGHT Attributes: | Name | DataType | Description | |--||--| | ${replica-name} | double | Attribute name uses the name of the replica, and the parameter fills in the weight value corresponding to the replica. Weight parameter range min > 0, total <= Double.MAX_VALUE. | Configure a load balancer algorithm for the loadBalancers attribute to use read/write splitting. ```yaml rules: !READWRITE_SPLITTING dataSourceGroups: readwrite_ds: writeDataSourceName: write_ds readDataSourceNames: readds0 readds1 transactionalReadQueryStrategy: PRIMARY loadBalancerName: random loadBalancers: random: type: RANDOM ```
Project: KICS (Provisioning / Security & Compliance)
File: 1819ac03-542b-4026-976b-f37addd59f3b.md

title: EBS Volume Not Attached To Instances hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 1819ac03-542b-4026-976b-f37addd59f3b Query name: EBS Volume Not Attached To Instances Platform: CloudFormation Severity: <span style="color:#edd57e">Low</span> Category: Availability URL: EBS Volumes that are unattached to instances may contain sensitive data<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="3" AWSTemplateFormatVersion: 2010-09-09 Resources: NewVolume: Type: AWS::EC2::Volume Properties: Size: 100 AvailabilityZone: us-west-1 ``` ```json title="Positive test num. 2 - json file" hl_lines="4" { "AWSTemplateFormatVersion": "2010-09-09T00:00:00Z", "Resources": { "NewVolume": { "Type": "AWS::EC2::Volume", "Properties": { "AvailabilityZone": "us-west-1", "Size": 100 } } } } ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: 2010-09-09 Resources: NewVolume: Type: AWS::EC2::Volume Properties: Size: 100 AvailabilityZone: us-west-1 MountPoint: Type: AWS::EC2::VolumeAttachment Properties: InstanceId: !Ref Ec2Instance VolumeId: !Ref NewVolume Device: /dev/sdh ``` ```json title="Negative test num. 2 - json file" { "AWSTemplateFormatVersion": "2010-09-09T00:00:00Z", "Resources": { "NewVolume": { "Type": "AWS::EC2::Volume", "Properties": { "Size": 100, "AvailabilityZone": "us-west-1" } }, "MountPoint": { "Type": "AWS::EC2::VolumeAttachment", "Properties": { "VolumeId": "NewVolume", "Device": "/dev/sdh", "InstanceId": "Ec2Instance" } } } } ```
Project: KICS (Provisioning / Security & Compliance)
File: b9c83569-459b-4110-8f79-6305aa33cb37.md

title: Using Kubernetes Native Secret Management hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b9c83569-459b-4110-8f79-6305aa33cb37 Query name: Using Kubernetes Native Secret Management Platform: Kubernetes Severity: <span style="color:#5bc0de">Info</span> Category: Secret Management URL: Kubernetes External Secret Storage and Management System usage should be considered if you have more complex secret management needs, rather than using Kubernetes Secrets directly. Additionally, ensure that access to secrets is carefully limited<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4" apiVersion: v1 kind: Secret metadata: name: cluster-secrets data: certificate-authority-data: Cg== stringData: bearerToken: "my-token" ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: secrets-store.csi.x-k8s.io/v1 kind: SecretProviderClass metadata: name: azure-kvname namespace: myNameSpace spec: provider: azure parameters: usePodIdentity: "true" keyvaultName: "<key Vault Name>" objects: | array: | objectName: secret1 objectType: secret | objectName: key1 objectType: key tenantId: "<tenant ID which the Key Vault sits under" secretObjects: secretName: appsecrets data: key: secret1 objectName: secret1 type: Opaque ``` ```yaml title="Negative test num. 2 - yaml file" apiVersion: v1 kind: Secret metadata: name: cluster-secrets data: certificate-authority-data: Cg== stringData: bearerToken: "my-token" apiVersion: secrets-store.csi.x-k8s.io/v1 kind: SecretProviderClass metadata: name: azure-kvname namespace: myNameSpace spec: provider: azure parameters: usePodIdentity: "true" keyvaultName: "<key Vault Name>" objects: array: {objectName: secret1, objectType: secret} {objectName: key1 , objectType: key} tenantId: "<tenant ID which the Key Vault sits under" secretObjects: secretName: appsecrets data: key: secret1 objectName: secret1 type: Opaque ```
Project: YugabyteDB (App Definition and Development / Database)
File: psetex.md

title: PSETEX linkTitle: PSETEX description: PSETEX menu: preview: parent: api-yedis weight: 2272 aliases: /preview/api/redis/psetex /preview/api/yedis/psetex type: docs `PSETEX key ttl_in_msec string_value` This command sets the value of `key` to be `stringvalue`, and sets the key to expire in `ttlin_msec` milli-seconds. Returns status string. ```sh $ PSETEX yugakey 1000 "Yugabyte" ``` ``` "OK" ``` ```sh $ GET yugakey ``` ``` "Yugabyte" ``` ```sh $ PTTL yugakey ``` ``` (integer) 900 ``` , , , , , , , , ,
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.151.md

layout: release date: 2023-09-28 tag: v0.6.151 comment out docker group check @leecalcote (#8958) equality changes @aabidsofi19 (#8959) Thank you to our contributors for making this release possible: @aabidsofi19 and @leecalcote
Project: ShardingSphere (App Definition and Development / Database)
File: README.md

Project uses template engine to generate example codes of ShardingSphere. Configure YAML file File: `src/main/resources/config.yaml` Generate code Run `org.apache.shardingsphere.example.generator.ExampleGeneratorMain` to generate example codes. Generated codes: `target/generated-sources/shardingsphere-${product}-sample` | Name | Description | Options | |:|-|:-| | mode | operating mode | cluster-zookeeper, cluster-etcd, standalone | | transaction | transaction type | local, xa-atomikos, xa-narayana | | features | feature set | sharding, readwrite-splitting, encrypt, shadow, mask | | frameworks | framework set | jdbc, spring-boot-starter-jdbc, spring-boot-starter-jpa, spring-boot-starter-mybatis, spring-namespace-jpa, spring-namespace-mybatis | | host | database host | | | port | database port | | | username | database username | | | password | database password | |
Project: Chef InSpec (Provisioning / Security & Compliance)
File: sysv_service.md

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

+++ title = "`boostchecked<T, E = boost::system::errorcode>`" description = "A type alias to a `basicresult` configured with `boost::system::errorcode` and `policy::throwbadresult_access<EC>`." +++ A type alias to a {{% api "basicresult<T, E, NoValuePolicy>" %}} configured with `boost::system::errorcode` and `policy::`{{% api "throwbadresult_access<EC>" %}}. This type alias always references the `boost` edition of things, unlike {{% api "checked<T, E = varies>" %}} which references either this alias or {{% api "stdchecked<T, E = std::errorcode>" %}}. Namespace: `BOOSTOUTCOMEV2_NAMESPACE` Header: `<boost/outcome/boost_result.hpp>`
Project: StarRocks (App Definition and Development / Database)
File: SHOW_ALTER.md

displayed_sidebar: "English" Shows the execution of the ongoing ALTER TABLE operations, including: Modify columns. Optimize table schema (from v3.2), including modifying the bucketing method and the number of buckets. Create and delete the rollup index. Show the execution of operations of modifying columns or optimizing table schema. ```sql SHOW ALTER TABLE { COLUMN | OPTIMIZE } [FROM db_name] [WHERE TableName|CreateTime|FinishTime|State] [ORDER BY] [LIMIT] ``` Show the execution of operations of adding or deleting the rollup index. ```sql SHOW ALTER TABLE ROLLUP [FROM db_name] ``` `{COLUMN OPTIMIZE | ROLLUP}`: If `COLUMN` is specified, this statement shows operations of modifying columns. If `OPTIMIZE` is specified, this statement shows operations of optimizing table structure. If `ROLLUP` is specified, this statement shows operations of adding or deleting the rollup index. `dbname`: optional. If `dbname` is not specified, the current database is used by default. Show the execution of operations of modifying columns, optimizing table schema, and creating or deleting the rollup index in the current database. ```sql SHOW ALTER TABLE COLUMN; SHOW ALTER TABLE OPTIMIZE; SHOW ALTER TABLE ROLLUP; ``` Show the execution of operations related to modifying columns, optimizing table schema, and creating or deleting the rollup index in a specified database. ```sql SHOW ALTER TABLE COLUMN FROM example_db; SHOW ALTER TABLE OPTIMIZE FROM example_db; SHOW ALTER TABLE ROLLUP FROM example_db; ``` Show the execution of the most recent operation of modifying columns or optimizing table schema in a specified table. ```sql SHOW ALTER TABLE COLUMN WHERE TableName = "table1" ORDER BY CreateTime DESC LIMIT 1; SHOW ALTER TABLE OPTIMIZE WHERE TableName = "table1" ORDER BY CreateTime DESC LIMIT 1; ```
Project: Carvel (App Definition and Development / Application Definition & Image Build)
File: apis.md

There are two strategies for integrating with ytt: invoke `ytt` out-of-process as an executable running as a separate process. construct, configure, execute, and inspect the results of a `ytt` command object, in-process. For most use-cases, the as-an-executable integration is more appropriate: decouples versioning of your tooling from `ytt` itself making it easier to upgrade "in the field." maintains well-defined integration interfaces making development and troubleshooting far easier. provides lots of safety checks to ensure that inputs are well-formed and valid. allows your tooling to be implemented in any language/platform that supports shelling out a process. Integrating with `ytt` as a Go module is more appropriate when: your use-case is narrow enough that few (if any) of the `ytt`-isms are useful to the end-user. your tooling must be distributed/integrated via a single binary (e.g. supplying a container image is undesirable) Performance is typically not a concern when deciding whether to go out-of-process or in-process: with reasonable computing resources and sources residing on-machine, `ytt` can execute over a reasonably complex library typically less than a second. By "integrate with `ytt` as an executable" we simply mean invoking the `ytt` binary, passing in the parameters required. How one does this depends largely on the platform from which you're integrating. Examples of how this can be done in Go: https://github.com/carvel-dev/kapp-controller/blob/develop/pkg/template/ytt.go https://github.com/carvel-dev/terraform-provider-carvel/blob/develop/pkg/ytt/ytt.go `ytt` does have a programmatic means of being invoked. However, there are no formal APIs: we can commit to backwards compatible behavior, but interfaces can and will change. Integrators need to be prepared to migrate with version bumps. add `ytt` as a dependency: ```go.mod ... require ( ... carvel.dev/ytt v0.40.0 ... ) ``` create and populate an instance of the template command: ```go opts := template.NewOptions() ``` invoke the command to evaluate: ```go output := opts.RunWithFiles(inputs, ui) ``` "Hello, world" with ytt. https://github.com/carvel-dev/kapp/blob/develop/pkg/kapp/yttresmod/overlaycontractv1_mod.go using `ytt` to overlay some existing YAML (here, a Kubernetes resource). We are always happy to support you in your use of `ytt`. You can: find us at (if your not yet in the workspace, get an ). or in our GitHub repo.
Project: Meshery (Provisioning / Automation & Configuration)
File: inclavare-containers.md

layout: integration title: Inclavare Containers subtitle: Collaborative and visual infrastructure as code for Inclavare Containers image: /assets/img/integrations/inclavare-containers/icons/color/inclavare-containers-color.svg permalink: extensibility/integrations/inclavare-containers docURL: https://docs.meshery.io/extensibility/integrations/inclavare containers description: integrations-category: Runtime integrations-subcategory: Container Runtime registrant: Artifact Hub components: 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