cwielenb/CNCF-Dataset huggingface dataset:
Project: Meshery (Provisioning / Automation & Configuration)
File: aws-iam-controller.md

layout: integration title: AWS Identity and Access Management subtitle: Collaborative and visual infrastructure as code for AWS Identity and Access Management image: /assets/img/integrations/aws-iam-controller/icons/color/aws-iam-controller-color.svg permalink: extensibility/integrations/aws-iam-controller docURL: https://docs.meshery.io/extensibility/integrations/aws-iam-controller description: integrations-category: Security & Compliance integrations-subcategory: Security Identity Compliance registrant: GitHub components: name: field-export colorIcon: assets/img/integrations/aws-iam-controller/components/field-export/icons/color/field-export-color.svg whiteIcon: assets/img/integrations/aws-iam-controller/components/field-export/icons/white/field-export-white.svg description: name: adopted-resource colorIcon: assets/img/integrations/aws-iam-controller/components/adopted-resource/icons/color/adopted-resource-color.svg whiteIcon: assets/img/integrations/aws-iam-controller/components/adopted-resource/icons/white/adopted-resource-white.svg description: name: group colorIcon: assets/img/integrations/aws-iam-controller/components/group/icons/color/group-color.svg whiteIcon: assets/img/integrations/aws-iam-controller/components/group/icons/white/group-white.svg description: name: instance-profile colorIcon: assets/img/integrations/aws-iam-controller/components/instance-profile/icons/color/instance-profile-color.svg whiteIcon: assets/img/integrations/aws-iam-controller/components/instance-profile/icons/white/instance-profile-white.svg description: name: policy colorIcon: assets/img/integrations/aws-iam-controller/components/policy/icons/color/policy-color.svg whiteIcon: assets/img/integrations/aws-iam-controller/components/policy/icons/white/policy-white.svg description: name: role colorIcon: assets/img/integrations/aws-iam-controller/components/role/icons/color/role-color.svg whiteIcon: assets/img/integrations/aws-iam-controller/components/role/icons/white/role-white.svg description: name: user colorIcon: assets/img/integrations/aws-iam-controller/components/user/icons/color/user-color.svg whiteIcon: assets/img/integrations/aws-iam-controller/components/user/icons/white/user-white.svg description: name: open-id-connect-provider colorIcon: assets/img/integrations/aws-iam-controller/components/open-id-connect-provider/icons/color/open-id-connect-provider-color.svg whiteIcon: assets/img/integrations/aws-iam-controller/components/open-id-connect-provider/icons/white/open-id-connect-provider-white.svg description: featureList: [ "Manage per-account access or scale access across AWS accounts and applications", "Set, verify, and right-size permissions toward least privilege", "Establish organization-wide and preventative guardrails on AWS" ] 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: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: improvement-request.md

name: Improvement request about: Suggest an improvement idea for this project title: "[Improvement]" labels: kind/enhancement assignees: nayutah Is your improvement request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] If this is a new function, please describe the motivation and goals. A clear and concise description of why you want to happen, link the design doc if possible Describe the solution you'd like A clear and concise description of what you want to happen. Describe alternatives you've considered A clear and concise description of any alternative solutions or functions you've considered. Additional context Add any other context or screenshots about the improvement request here.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.0.4-en.md

Improve the dashboard listener startup log, the listener name is no longer spliced with port information, and the colon(:) is no longer displayed when IP is not specified. Remove `/configs/listeners` API, use `/listeners/` instead. Optimize performance of builtin database operations in processes with long message queue Improve authentication tracing. Standardize the '/listeners' and `/gateway/<name>/listeners` API fields. It will introduce some incompatible updates, see Add option to perform GC on connection process after TLS/SSL handshake is performed. The `data/configs/cluster-override.conf` is cleared to 0KB if `hocon_pp:do/2` failed Improve the health_check for webhooks. Prior to this change, the webhook only checks the connectivity of the TCP port using `gen_tcp:connect/2`, so if it's a HTTPs server, we didn't check if TLS handshake was successful. The `created_at` field of rules is missing after emqx restarts. The rule engine's jq function now works even when the path to the EMQX install dir contains spaces Avoid applying any ACL checks on superusers Fix statistics related system topic name error Fix AuthN JWKS SSL schema. Using schema in `emqx_schema`. `sentinel` field should be required when AuthN/AuthZ Redis using sentinel mode. Fix bad swagger format. Fix `chars_limit` is not working when `formatter` is `json`. Ensuring that exhook dispatches the client events are sequential. Avoid using RocksDB backend for persistent sessions when such backend is unavailable. Fix AuthN `certsubject` and `certcommon_name` placeholder rendering failure. Support listen on an IPv6 address, e.g: GET '/rules' support for pagination and fuzzy search. Note : The previous API only returns array: `[RuleObj1,RuleObj2]`, after updating, it will become `{"data": [RuleObj1,RuleObj2], "meta":{"count":2, "limit":100, "page":1}`, which will carry the paging meta information. Fix the issue that webhook leaks TCP connections. ,
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.46.md

layout: release date: 2023-01-28 tag: v0.6.46 language: en Fix empty and duplicate outputs in MeshModel APIs @Revolyssup (#6941) Add K8s MeshModel components @Revolyssup (#6936) Fix SVG Bug and update fields @Revolyssup (#6933) [mesheryctl] Created 'mesheryctl system provider' @abdullah1308 (#6928) improved error message for system cmd - config, logs @kernelpanic77 (#6930) Minor changes on NPM packages @acald-creator (#6888) Ignore locally registered MeshModel package icons @leecalcote (#6945) rename public to published for catalog @MUzairS15 (#6938) [UI] Undeploy later button color update @Chadha93 (#6944) `provider-ui` MUI framework upgrade @acald-creator (#6911) Notification center consistently opens when clicked @deepakdinesh1123 (#6905) remove the description for additional fields @harkiratsm (#6861) [UI] MeshModel Summary in Meshery Settings @theBeginner86 (#6771) Changes made to Navigator Menu to remove some of the errors @deepakdinesh1123 (#6927) Made Toggle Buttons on customize addon synchronous @hs05june (#6925) Ignore locally registered MeshModel package icons @leecalcote (#6945) [chore] Upgrade Meshkit to v0.6.21 @theBeginner86 (#6942) Bump rack from 2.2.5 to 2.2.6.2 in /docs @dependabot (#6915) Bump globalid from 1.0.0 to 1.0.1 in /docs @dependabot (#6919) Bump commonmarker from 0.23.6 to 0.23.7 in /docs @dependabot (#6929) typographical error in quick-start.html @b0id (#6934) Resolving the Grammatical Mistake in README.md @ShivangShandilya (#6932) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Chadha93, @MUzairS15, @Revolyssup, @ShivangShandilya, @UtkarshMishra12, @abdullah1308, @acald-creator, @alphaX86, @b0id, @deepakdinesh1123, @dependabot, @dependabot[bot], @harkiratsm, @hs05june, @kernelpanic77, @l5io, @leecalcote, @theBeginner86 and l5io
Project: YugabyteDB (App Definition and Development / Database)
File: txn_commit.md

title: COMMIT statement [YSQL] headerTitle: COMMIT linkTitle: COMMIT description: Use the COMMIT statement to commit the current transaction. menu: v2.18: identifier: txn_commit parent: statements type: docs Use the `COMMIT` statement to commit the current transaction. All changes made by the transaction become visible to others and are guaranteed to be durable if a crash occurs. {{%ebnf%}} commit {{%/ebnf%}} ```sql COMMIT [ TRANSACTION | WORK ] ``` Add optional keyword has no effect. Add optional keyword has no effect. Create a sample table. ```plpgsql CREATE TABLE sample(k1 int, k2 int, v1 int, v2 text, PRIMARY KEY (k1, k2)); ``` Begin a transaction and insert some rows. ```plpgsql BEGIN TRANSACTION; SET TRANSACTION ISOLATION LEVEL REPEATABLE READ; ``` ```plpgsql INSERT INTO sample(k1, k2, v1, v2) VALUES (1, 2.0, 3, 'a'), (1, 3.0, 4, 'b'); ``` Start a new shell with `ysqlsh` and begin another transaction to insert some more rows. ```plpgsql yugabyte=# BEGIN TRANSACTION; SET TRANSACTION ISOLATION LEVEL REPEATABLE READ; ``` ```plpgsql INSERT INTO sample(k1, k2, v1, v2) VALUES (2, 2.0, 3, 'a'), (2, 3.0, 4, 'b'); ``` In each shell, check the only the rows from the current transaction are visible. 1st shell. ```plpgsql yugabyte=# SELECT * FROM sample; -- run in first shell ``` ``` k1 | k2 | v1 | v2 -+-+-+- 1 | 2 | 3 | a 1 | 3 | 4 | b (2 rows) ``` 2nd shell ```plpgsql yugabyte=# SELECT * FROM sample; -- run in second shell ``` ``` k1 | k2 | v1 | v2 -+-+-+- 2 | 2 | 3 | a 2 | 3 | 4 | b (2 rows) ``` Commit the first transaction and abort the second one. ```plpgsql COMMIT TRANSACTION; -- run in first shell. ``` Abort the current transaction (from the first shell). ```plpgsql ABORT TRANSACTION; -- run second shell. ``` In each shell check that only the rows from the committed transaction are visible. ```plpgsql yugabyte=# SELECT * FROM sample; -- run in first shell. ``` ``` k1 | k2 | v1 | v2 -+-+-+- 1 | 2 | 3 | a 1 | 3 | 4 | b (2 rows) ``` ```plpgsql yugabyte=# SELECT * FROM sample; -- run in second shell. ``` ``` k1 | k2 | v1 | v2 -+-+-+- 1 | 2 | 3 | a 1 | 3 | 4 | b (2 rows) ```
Project: Meshery (Provisioning / Automation & Configuration)
File: kubedb.md

layout: integration title: Kubedb subtitle: Collaborative and visual infrastructure as code for Kubedb image: /assets/img/integrations/kubedb/icons/color/kubedb-color.svg permalink: extensibility/integrations/kubedb docURL: https://docs.meshery.io/extensibility/integrations/kubedb description: integrations-category: App Definition and Development integrations-subcategory: Database registrant: Artifact Hub components: featureList: [ "KubeDB simplifies many of the difficult or tedious management tasks of running a production grade databases on private and public clouds. Maintain one stack for all your stateless and stateful applications and simplify the operational complexity.", "Standard Kubernetes is all you need. If you can run Kubernetes, you can provision and manage databases using KubeDB. Use standard Kubernetes CLI and API to provision and manage databases.", "KubeDB uses Persistent Volume Claims (PVC) to dynamically provision disks for database instances. Using appropriately defined StorageClasses, KubeDB provisioned database instances are designed to scale from small development workloads up to performance-intensive workloads on private and public cloud environments." ] 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: TDengine (App Definition and Development / Database)
File: 28-recovery.md

title: Error Recovery sidebar_label: Error Recovery description: This document describes the SQL statements related to error recovery in TDengine. In a complex environment, connections and query tasks may encounter errors or fail to return in a reasonable time. If this occurs, you can terminate the connection or task. ```sql KILL CONNECTION conn_id; ``` You can use the SHOW CONNECTIONS statement to find the conn_id. ```sql KILL QUERY 'kill_id'; ``` You can use the SHOW QUERIES statement to find the kill_id. ```sql KILL TRANSACTION trans_id ``` You can use the SHOW TRANSACTIONS statement to find the trans_id. ```sql RESET QUERY CACHE; ``` If metadata becomes desynchronized among multiple clients, you can use this command to clear the client-side cache. Clients then obtain the latest metadata from the server.
Project: Pulsar (App Definition and Development / Streaming & Messaging)
File: pip-275.md

As we can see from the that `numWorkerThreadsForNonPersistentTopic` is a configuration to specify the number of worker threads to serve non-persistent topic. Actually, `numWorkerThreadsForNonPersistentTopic` will specify the thread number of `BrokerService#topicOrderedExecutor`. Initially it was meant only for non-persistent topics, but now it is used for anything that needs to be done under strict order for a topic, like processing Subscriptions even for a persistent topic: There is only one place invoke `topicOrderedExecutor` for non-persistent topics. Other places will invoke `topicOrderedExecutor` for persistent-topic or persistent-dispatcher. Making this config has a better name and increase the ability of users to understand what they are configuring. Introduce `topicOrderedExecutorThreadNum` to deprecate `numWorkerThreadsForNonPersistentTopic`. Introduce `topicOrderedExecutorThreadNum` with default value `Runtime.getRuntime().availableProcessors()`: ``` private int topicOrderedExecutorThreadNum = Runtime.getRuntime().availableProcessors(); ``` deprecate `numWorkerThreadsForNonPersistentTopic` and change it's default value from `Runtime.getRuntime().availableProcessors()` to `-1`: ``` private int numWorkerThreadsForNonPersistentTopic = -1; ``` Overwrite method `ServiceConfiguration#getTopicOrderedExecutorThreadNum()` from lombok. ``` public int getTopicOrderedExecutorThreadNum() { return numWorkerThreadsForNonPersistentTopic > 0 ? numWorkerThreadsForNonPersistentTopic : topicOrderedExecutorThreadNum; } ``` And all places calling `ServiceConfiguration#getNumWorkerThreadsForNonPersistentTopic()` will call `ServiceConfiguration#getTopicOrderedExecutorThreadNum()` instead. Because we have overwritten method `getTopicOrderedExecutorThreadNum()` from lombok, so: if user doesn't set the `numWorkerThreadsForNonPersistentTopic`, the value of worker threads will keep `Runtime.getRuntime().availableProcessors()` If user has set the `numWorkerThreadsForNonPersistentTopic`, the value will keep what user set before. Mailing List discussion thread: https://lists.apache.org/thread/hx8v824v5wdoz3kn44s4t9pzgfnqkt1o Mailing List voting thread: https://lists.apache.org/thread/ywk6z440qt0vs32210799m508gbxfshm
Project: CDK for Kubernetes (CDK8s) (Provisioning / Automation & Configuration)
File: index.md

This section includes API reference for the various components of cdk8s. === "TypeScript" * Kubernetes v1.27.0 Kubernetes v1.28.0 Kubernetes v1.29.0 === "Python" * Kubernetes v1.27.0 Kubernetes v1.28.0 Kubernetes v1.29.0 === "Java" * Kubernetes v1.27.0 Kubernetes v1.28.0 Kubernetes v1.29.0 === "Go" * Kubernetes v1.27.0 Kubernetes v1.28.0 Kubernetes v1.29.0 !!! info The documentation here relates to version `2.x` of the cdk8s tool-chain, which is the latest. If you are still using version `1.x`, please refer to the *define* Kubernetes applications, they don't actually apply them to the cluster. When an app is executed, it synthesizes all the charts defined within the app into the `dist` directory, and then those charts can be applied to any Kubernetes cluster using `kubectl apply -f dist/chart.k8s.yaml` or a GitOps tool like . cdk8s is based on the design concepts and technologies behind the [AWS Cloud Development Kit](https://aws.amazon.com/cdk), and can interoperate with AWS CDK constructs to define cloud-native applications that include both Kubernetes resources and other CDK constructs as first class citizens.
Project: Nocalhost (App Definition and Development / Application Definition & Image Build)
File: CHANGESv2.md

A number of changes were made to Tcell for version two, and some of these are breaking. The import path for tcell has changed to `github.com/gdamore/tcell/v2` to reflect a new major version. The type `Style` has changed to a structure, to allow us to add additional data such as flags for color setting, more attribute bits, and so forth. Applications that relied on this being a number will need to be updated to use the accessor methods. The middle mouse button was reported as button 2 on Linux, but as button 3 on Windows, and the right mouse button was reported the reverse way. Tcell now always reports the right mouse button as button 2, and the middle button as button 3. To help make this clearer, new symbols `ButtonPrimary`, `ButtonSecondary`, and `ButtonMiddle` are provided. (Note that which button is right vs. left may be impacted by user preferences. Usually the left button will be considered the Primary, and the right will be the Secondary.) Applications may need to adjust their handling of mouse buttons 2 and 3 accordingly. A number of terminals have been removed. These are mostly ancient definitions unlikely to be used by anyone, such as `adm3a`. Historically terminfo reported function keys with modifiers set as a different function key altogether. For example, Shift-F1 was reported as F13 on XTerm. Tcell now prefers to report these using the base key (such as F1) with modifiers added. This works on XTerm and VTE based emulators, but some emulators may not support this. The new behavior more closely aligns with behavior on Windows platforms. These features are not breaking, but are introduced in version 2. For terminals that appear to behave like the venerable XTerm, tcell automatically adds modifier reporting for ALT, CTRL, SHIFT, and META keys when the terminal reports them. When using a color by its name or palette entry, Tcell now tries to use that palette entry as is; this should avoid some inconsistency and respect terminal themes correctly. When true fidelity to RGB values is needed, the new `TrueColor()` API can be used to create a direct color, which bypasses the palette altogether. For some terminals, if the `Tc` or `RGB` properties are present in terminfo, Tcell will automatically assume the terminal supports 24-bit color. A new color value, `ColorReset` can be used on the foreground or background to reset the color the default used by the terminal. Tcell now has improved support for tmux, when the `$TERM` variable is set to "tmux". Tcell has support for strikethrough when the terminal supports it, using the new `StrikeThrough()` API. Tcell provides the long requested capability to discriminate paste event by using the bracketed-paste capability present in some terminals. This is automatically available on terminals that support XTerm style mouse handling, but applications must opt-in to this by using the new `EnablePaste()` function. A new `EventPaste` type of event will be delivered when starting and finishing a paste operation.
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: flask-opa.md

title: Flask-OPA labels: category: flask layer: library software: flask code: https://github.com/EliuX/flask-opa blogs: https://github.com/EliuX/flask-opa/tree/master/examples Simple to use Flask extension that lets you secure your projects with OPA. It allows HTTP API Authorization and Policy Enforcement Point (AOP using decorators on methods).
Project: YDB (App Definition and Development / Database)
File: bulk-upsert.md

title: "Overview of the code recipe for bulk upsert of data in {{ ydb-short-name }}" description: "The article describes the code examples showing the {{ ydb-short-name }} SDK built-in tools for bulk upsert." {% include %} {{ ydb-short-name }} supports bulk upsert of many records without atomicity guarantees. The upsert process is split into multiple independent parallel transactions, each covering a single partition. For that reason, this approach is more effective than using `YQL`. If successful, the `BulkUpsert` method guarantees inserting all the data transmitted by the query. Below are code examples showing the {{ ydb-short-name }} SDK built-in tools for bulk upsert: {% list tabs %} Go (native) ```go package main import ( "context" "os" "github.com/ydb-platform/ydb-go-sdk/v3" "github.com/ydb-platform/ydb-go-sdk/v3/table" "github.com/ydb-platform/ydb-go-sdk/v3/table/types" ) func main() { ctx, cancel := context.WithCancel(context.Background()) defer cancel() db, err := ydb.Open(ctx, os.Getenv("YDBCONNECTIONSTRING"), ydb.WithAccessTokenCredentials(os.Getenv("YDB_TOKEN")), ) if err != nil { panic(err) } defer db.Close(ctx) type logMessage struct { App string Host string Timestamp time.Time HTTPCode uint32 Message string } // prepare native go data const batchSize = 10000 logs := make([]logMessage, 0, batchSize) for i := 0; i < batchSize; i++ { message := logMessage{ App: fmt.Sprintf("App_%d", i/256), Host: fmt.Sprintf("192.168.0.%d", i%256), Timestamp: time.Now().Add(time.Millisecond * time.Duration(i%1000)), HTTPCode: 200, } if i%2 == 0 { message.Message = "GET / HTTP/1.1" } else { message.Message = "GET /images/logo.png HTTP/1.1" } logs = append(logs, message) } // execute bulk upsert with native ydb data err = db.Table().Do( // Do retry operation on errors with best effort ctx, // context manage exiting from Do func(ctx context.Context, s table.Session) (err error) { // retry operation rows := make([]types.Value, 0, len(logs)) for _, msg := range logs { rows = append(rows, types.StructValue( types.StructFieldValue("App", types.UTF8Value(msg.App)), types.StructFieldValue("Host", types.UTF8Value(msg.Host)), types.StructFieldValue("Timestamp", types.TimestampValueFromTime(msg.Timestamp)), types.StructFieldValue("HTTPCode", types.Uint32Value(msg.HTTPCode)), types.StructFieldValue("Message", types.UTF8Value(msg.Message)), )) } return s.BulkUpsert(ctx, "/local/bulkupsertexample", types.ListValue(rows...)) }, ) if err != nil { fmt.Printf("unexpected error: %v", err) } } ``` Go (database/sql) The implementation of {{ ydb-short-name }} `database/sql` doesn't support bulk nontransactional upsert of data. For bulk upsert, use . {% endlist %}
Project: ShardingSphere (App Definition and Development / Database)
File: alter-migration-rule.en.md

+++ title = "ALTER MIGRATION RULE" weight = 2 +++ The `ALTER MIGRATION RULE` syntax is used to alter migration rule. {{< tabs >}} {{% tab name="Grammar" %}} ```sql AlterMigrationRule ::= 'ALTER' 'MIGRATION' 'RULE' ('(' (readConfiguration ',')? (writeConfiguration ',')? (dataChannel)? ')')? readConfiguration ::= 'READ' '(' ('WORKERTHREAD' '=' workerThreadPoolSize ',')? ('BATCHSIZE' '=' batchSize ',')? ('SHARDING_SIZE' '=' shardingSize ',')? (rateLimiter)? ')' writeConfiguration ::= 'WRITE' '(' ('WORKERTHREAD' '=' workerThreadPoolSize ',')? ('BATCHSIZE' '=' batchSize ',')? ('SHARDING_SIZE' '=' shardingSize ',')? (rateLimiter)? ')' dataChannel ::= 'STREAM_CHANNEL' '(' 'TYPE' '(' 'NAME' '=' algorithmName ',' propertiesDefinition ')' ')' workerThreadPoolSize ::= int batchSize ::= int shardingSize ::= int rateLimiter ::= 'RATE_LIMITER' '(' 'TYPE' '(' 'NAME' '=' algorithmName ',' propertiesDefinition ')' ')' algorithmName ::= string propertiesDefinition ::= 'PROPERTIES' '(' key '=' value (',' key '=' value)* ')' key ::= string value ::= literal ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} ```sql ALTER MIGRATION RULE ( READ( WORKERTHREAD=20, BATCHSIZE=1000, SHARDINGSIZE=10000000, RATELIMITER (TYPE(NAME='QPS',PROPERTIES('qps'='500')))), WRITE( WORKERTHREAD=20, BATCHSIZE=1000, RATE_LIMITER (TYPE(NAME='TPS',PROPERTIES('tps'='2000')))), STREAM_CHANNEL ( TYPE(NAME='MEMORY',PROPERTIES('block-queue-size'='2000'))) ); ``` `ALTER`, `MIGRATION`, `RULE`, `READ`, `WRITE`, `WORKERTHREAD`, `BATCHSIZE`, `SHARDINGSIZE`, `STREAMCHANNEL`, `TYPE`, `NAME`, `PROPERTIES`