cwielenb/CNCF-Dataset huggingface dataset:
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_connect_mariadb.md

title: Kubectl-Dba Connect Mariadb menu: docs_{{ .version }}: identifier: kubectl-dba-connect-mariadb name: Kubectl-Dba Connect Mariadb parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Connect to a mariadb object Use this command to connect to a mariadb object's primary pod. ``` kubectl-dba connect mariadb [flags] ``` ``` -h, --help help for mariadb ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "/home/runner/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --default-seccomp-profile-type string Default seccomp profile --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --password string Password for basic authentication to the API server --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use --username string Username for basic authentication to the API server ``` - Connect to a database.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.109.md

layout: release date: 2023-07-20 tag: v0.6.109 [chore] Fix missing remote provider prefs @theBeginner86 (#8234) [chore] bump meshkit to `v0.6.49` @MUzairS15 (#8233) Update go.mod @theBeginner86 (#8231) Use meshkit function @MUzairS15 (#8215) Bump word-wrap from 1.2.3 to 1.2.4 in /install/docker-extension/ui @dependabot (#8218) Add duplicate count for meshmodel model, component @abdullah1308 (#8168) Changed server request for Publishing Catalog Content @Player256 (#8197) Bump meshery-operator version to the latest(v0.6.10) @Aisuko (#8187) [Playground] Use Nginx daemon not container @leecalcote (#8201) Fix core component not getting updated by `component_updater` script. @MUzairS15 (#8192) Common search view for grid and data-table @sudhanshutech (#8157) [mesheryctl] Pattern Subcommand dysfunctional @suhail34 (#8177) [CI] Adding a make target for mesheryctl docs and add in the worflow file @suhail34 (#8185) [CI] fix eslint @theBeginner86 (#8232) Fix visibility bug in catalog @sudhanshutech (#8214) Apply default icon style to all the mui icons @Abhishek-kumar09 (#8229) [chore] fix the checkboxes label capitalization in dark mode @harkiratsm (#8222) [RJSF] UI enhancement in publish to catalog modal @Yashsharma1911 (#8141) Common search view for grid and data-table @sudhanshutech (#8157) Updated Performance icon in Meshery UI @vednp (#8189) [Deps]ui and provider ui @leecalcote (#8186) [chore] fix the usage of publish modal @harkiratsm (#8180) [CI] fix eslint @theBeginner86 (#8232) [CI] Send out email in case of meshmodel component generation/updater failure. @suhail34 (#8216) [CI] Update playground-cleanup.sh script @theBeginner86 (#8209) [CI] Job to update REST and GraphQL docs #7956 @suhail34 (#8076) [CI] Adding a make target for mesheryctl docs and add in the worflow file @suhail34 (#8185) [Docs] Minor MeshModel Changes @Boombag0607 (#8183) Added Build and Release Meeting time and minutes link @ranjanmangla1 (#8114) Update meshmodel docs @abdullah1308 (#8206) Bring search bar back @vishalvivekm (#8210) [Docs] Kubernetes installations @leecalcote (#8190) Add Concept Docs for MeshModel @Boombag0607 (#8182) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Aisuko, @Boombag0607, @MUzairS15, @Player256, @Yashsharma1911, @abdullah1308, @dependabot, @dependabot[bot], @harkiratsm, @l5io, @leecalcote, @nebula-aac, @ranjanmangla1, @sudhanshutech, @suhail34, @theBeginner86, @vednp, @vishalvivekm and Ved Pahune
Project: BigchainDB (App Definition and Development / Database)
File: node-security-and-privacy.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 > Here are some references about how to secure an Ubuntu 18.04 server: Also, here are some recommendations a node operator can follow to enhance the privacy of the data coming to, stored on, and leaving their node: Ensure that all data stored on a node is encrypted at rest, e.g. using full disk encryption. This can be provided as a service by the operating system, transparently to BigchainDB, MongoDB and Tendermint. Ensure that all data is encrypted in transit, i.e. enforce using HTTPS for the HTTP API and the Websocket API. This can be done using NGINX or similar, as we do with the IPDB Testnet.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: 41_ai_model_refresh.md

Prompt: How can I make sure my Apache Beam pipeline uses the latest version of the ML model? Response: Production ML workflows often involve updating the ML model with new data. You can ensure that your Apache Beam pipeline uses the latest version of the ML model by leveraging the RunInference API alongside Apache Beam's feature. Side inputs are additional inputs that can be provided to a transform, in addition to the main input . The `RunInference` transform accepts an optional input parameter `modelmetadatapcoll`, which is a side input `PCollection` emitting `ModelMetadata`. `ModelMetadata` is a `NamedTuple` object containing `modelid` and `modelname`, used to load the model for inference and identify it in the metrics generated by the `RunInference` transform. The URL or path to the model should be compatible with the respective . If the main collection emits inputs before the `modelmetadatapcoll` side input is available, the main `PCollection` will be buffered until the `modelmetadatapcoll` side input is emitted. For more information on `ModelMetadata`, refer to the . A common approach to model updates in production is to use a `FileWatchPattern` as a side input: ```python import apache_beam as beam from apache_beam.ml.inference.utils import WatchFilePattern from apache_beam.ml.inference.base import RunInference tfmodelhandler = ... # model handler for the model with beam.Pipeline() as pipeline: filepattern = '<pathtomodelfile>' sideinputpcoll = ( pipeline | "FilePatternUpdates" >> WatchFilePattern(filepattern=filepattern)) maininputpcoll = ... # main input PCollection inference_pcoll = ( maininputpcoll | "RunInference" >> RunInference( modelhandler=modelhandler, modelmetadatapcoll=sideinputpcoll)) ``` In the provided example, the `modelmetadatapcoll` parameter expects a `PCollection` of `ModelMetadata` compatible with the `AsSingleton` marker. Given that the pipeline employs the `WatchFilePattern` class as a side input, it automatically manages windowing and encapsulates the output into `ModelMetadata`. For more information, refer to the section in the Apache Beam documentation.
Project: Meshery (Provisioning / Automation & Configuration)
File: aws-secretsmanager-controller.md

layout: integration title: AWS Secrets Manager subtitle: Collaborative and visual infrastructure as code for AWS Secrets Manager image: /assets/img/integrations/aws-secretsmanager-controller/icons/color/aws-secretsmanager-controller-color.svg permalink: extensibility/integrations/aws-secretsmanager-controller docURL: https://docs.meshery.io/extensibility/integrations/aws-secretsmanager-controller description: integrations-category: Security & Compliance integrations-subcategory: Security Identity Compliance registrant: GitHub components: name: field-export colorIcon: assets/img/integrations/aws-secretsmanager-controller/components/field-export/icons/color/field-export-color.svg whiteIcon: assets/img/integrations/aws-secretsmanager-controller/components/field-export/icons/white/field-export-white.svg description: name: adopted-resource colorIcon: assets/img/integrations/aws-secretsmanager-controller/components/adopted-resource/icons/color/adopted-resource-color.svg whiteIcon: assets/img/integrations/aws-secretsmanager-controller/components/adopted-resource/icons/white/adopted-resource-white.svg description: name: secret colorIcon: assets/img/integrations/aws-secretsmanager-controller/components/secret/icons/color/secret-color.svg whiteIcon: assets/img/integrations/aws-secretsmanager-controller/components/secret/icons/white/secret-white.svg description: featureList: [ "Centrally store and manage credentials, API keys, and other secrets.", "Use AWS Identity and Access Management (IAM) permissions policies to manage access to your secrets.", "Rotate secrets on demand or on a schedule, without redeploying or disrupting active applications." ] 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: YugabyteDB (App Definition and Development / Database)
File: postgresql-compatibility.md

title: PostgreSQL compatibility linkTitle: PostgreSQL compatibility description: Summary of YugabyteDB's PostgreSQL compatibility menu: v2.18: identifier: explore-ysql-postgresql-compatibility parent: explore-ysql-language-features weight: 70 type: docs YugabyteDB is a distributed database that supports the majority of PostgreSQL syntax. This means that existing applications built on PostgreSQL can often be migrated to YugabyteDB without changing application code. Because YugabyteDB is PostgreSQL compatible, it works with the majority of PostgreSQL database tools such as various language drivers, ORM tools, schema migration tools, and many more third-party database tools. Because YugabyteDB is a distributed database, supporting all PostgreSQL features easily in a distributed system is not always feasible. This page documents the known list of differences between PostgreSQL and YugabyteDB. You need to consider these differences while porting an existing application to YugabyteDB. The following PostgreSQL features are not supported in YugabyteDB: | Unsupported PostgreSQL feature | Track feature request GitHub issue | | -- | -- | | LOCK TABLE to obtain a table-level lock | | | Table inheritance | | | Exclusion constraints | | | Deferrable constraints | | | GiST indexes | | | Events (Listen/Notify) | | | XML Functions | | | XA syntax | | | ALTER TYPE | | | CREATE CONVERSION | | | Primary/Foreign key constraints on foreign tables | , | | GENERATED ALWAYS AS STORED columns | | | Multicolumn GIN indexes| | | CREATE ACCESS METHOD | | | DESC/HASH on GIN indexes (ASC supported) | | | CREATE SCHEMA with elements | | | Index on citext column | | | ABSTIME type | | | transaction ids (xid) <br/> YugabyteDB uses instead of transaction ids. | | | DDL operations within transaction| | | Some ALTER TABLE variants| |
Project: YugabyteDB (App Definition and Development / Database)
File: 05-natural-join.md

title: "NATURAL JOINs" In this exercise we will query the products table using a NATURAL INNER JOIN with the order\details_ table. ``` SELECT DISTINCT products.product_id, products.product_name, orderdetails.unitprice FROM products NATURAL INNER JOIN order_details ORDER BY products.product_id; ``` The query should return 76 rows. In this exercise we will query the customers table using a NATURAL LEFT JOIN with the orders table. ``` SELECT DISTINCT customers.customer_id, customers.contact_name, orders.ship_region FROM customers NATURAL LEFT JOIN orders ORDER BY customers.customer_id DESC; ``` The query should return 91 rows. In this exercise we will query the customers table using a NATURAL RIGHT JOIN with the orders table. ``` SELECT DISTINCT customers.company_name, customers.contact_name, orders.ship_region FROM customers NATURAL RIGHT JOIN orders ORDER BY company_name DESC; ``` The query should return 89 rows.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.11.16.md

RabbitMQ `3.11.16` is a maintenance release in the `3.11.x` . Please refer to the upgrade section from if upgrading from a version prior to 3.11.0. This release requires Erlang 25 and supports Erlang versions up to `25.3.x`. has more details on Erlang version requirements for RabbitMQ. As of 3.11.0, RabbitMQ requires Erlang 25. Nodes will fail to start on older Erlang releases. Erlang 25 as our new baseline means much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation available to all RabbitMQ 3.11 users. Release notes can be found on GitHub at . now will from the node before removing it from the cluster. Contributed by @SimonUnge (AWS). GitHub issue: A new boolean setting, `quorumqueue.propertyequivalence.relaxedcheckson_redeclaration`, makes it possible to relax queue property equivalence checks for quorum queues. Specifically, when a quorum queue is redeclared and the client-provided type is set to "classic", this setting will help avoid a channel exception, making it easier to migrate to quorum queues step by step, without upgrading all applications in a short period of time. Contributed by @SimonUnge (AWS). GitHub issue: `rabbitmq-queues grow` and `rabbitmq-queues add_member` now verify cluster membership of the node new quorum queue replicas should be placed on. GitHub issue: URI parser incorrectly used the `password` query parameter to override the password value in authority (user info) part. The `password` query parameter can be used to specify private key password for upstream connections that use TLS. GitHub issue: URI parser incorrectly used the `password` query parameter to override the password value in authority (user info) part. The `password` query parameter can be used to specify private key password for Shovels that use TLS. GitHub issue: was upgraded To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.16.tar.xz` instead of the source tarball produced by GitHub.
Project: Stolon (App Definition and Development / Database)
File: pitr_wal-e.md

This example shows how to do point in time recovery with stolon using correctly suggests to not put environment variables containing secret data (like aws secret keys) inside the `archive_command` since every user connected to postgres could read them. In its examples wal-e suggests to use the `envdir` command to set the wal-e required environment variables or (since some distribution don't have it) just use a custom script that sets them. Take the base backups using the `wal-e backup-push` command. For doing this you should set at least the `archivemode` and the `archivecommand` pgParameters in the cluster spec. Wal-e will be used as the archive command: ``` stolonctl update --patch '{ "pgParameters" : { "archivemode": "on", "archivecommand": "envdir /etc/wal-e.d/env wal-e wal-push %p" } }' ``` Note: looks like wal-e doesn't backups various config files like `postgresql.conf`, `pghba.conf`. While `pghba.conf` is currently generated by stolon, you'd like to keep the previous postgres parameters after the restore. For doing this there're two different ways: if you want to backup the `postgresql.conf` you should do this outside `wal-e`. To restore it you have to create a `dataRestoreCommand` that will restore it after the `wal-e backup fetch` command. if you don't want to backup/restore it than you can just set all the `pgParameters` inside the ``` stolonctl init '{ "initMode": "pitr", "pitrConfig": { "dataRestoreCommand": "envdir /etc/wal-e.d/env wal-e backup-fetch %d LATEST" , "archiveRecoverySettings": { "restoreCommand": "envdir /etc/wal-e.d/env wal-e wal-fetch \"%f\" \"%p\"" } } }' ```
Project: StarRocks (App Definition and Development / Database)
File: minutes_diff.md

displayed_sidebar: "English" Returns the minute difference between two date expressions (`expr1` `expr2`), accurate to the minute. ```Haskell BIGINT minutes_diff(DATETIME expr1,DATETIME expr2); ``` `expr1`: the end time. It must be of the DATETIME type. `expr2`: the start time. It must be of the DATETIME type. Returns a BIGINT value. NULL is returned if the date does not exist, for example, 2022-02-29. ```Plain select minutes_diff('2010-11-30 23:59:59', '2010-11-30 20:58:59'); ++ | minutes_diff('2010-11-30 23:59:59', '2010-11-30 20:58:59') | ++ | 181 | ++ ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: login_defs.md

+++ title = "login_defs resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "login_defs" identifier = "inspec/resources/os/logindefs.md logindefs resource" parent = "inspec/resources/os" +++ Use the `login_defs` Chef InSpec audit resource to test configuration settings in the `/etc/login.defs` file. The `logins.defs` file defines site-specific configuration for the shadow password suite on Linux and Unix platforms, such as password expiration ranges, minimum/maximum values for automatic selection of user and group identifiers, or the method with which passwords are encrypted. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.0.0 of InSpec. A `login_defs` resource block declares the `login.defs` configuration data to be tested: describe login_defs do its('name') { should include('foo') } end where `name` is a configuration setting in `login.defs` `{ should include('foo') }` tests the value of `name` as read from `login.defs` versus the value declared in the test This resource supports the properties found in the `login.defs` configuration settings. The following examples show how to use this Chef InSpec audit resource. The `name` matcher tests the value of `name` as read from `login.defs` versus the value declared in the test: its('name') { should eq 'foo' } describe login_defs do its('PASSMAXDAYS') { should eq '180' } its('PASSMINDAYS') { should eq '1' } its('PASSMINLEN') { should eq '15' } its('PASSWARNAGE') { should eq '30' } end describe login_defs do its('ENCRYPT_METHOD') { should eq 'SHA512' } end describe login_defs do its('UMASK') { should eq '077' } its('PASSMAXDAYS') { should eq '90' } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}}
Project: userver (App Definition and Development / Streaming & Messaging)
File: stability.md

Userver is used by hundreds of microservices only in our code base. Manual application of modifications to the whole code-base is a burden. Rule of the thumb: we endeavor to change things only if the migration path is simple or there is a script to automate it. Userver follows the two-part versioning since version `2.0`: `major.minor` Examples: `2.0`, `2.1_rc` We attempt to keep the API stable as long as it does not stand in the way of new features or better safety. Note that framework internals located in `::impl::` and `::detail::` namespaces have no stability guarantees. You should not use those in your code directly. Transitive includes could not be relied on. Even a change in patch version could remove some `#include` from header and break code that relies on transitive includes. However, we provide script `./scripts/add-missing-include.sh` that helps to add missing includes in big code bases. Avoid adding your own forward declarations for the framework types as the type could change to an alias or vice versa during the userver development process. Userver is meant for usage mostly as a static library that is linked with the application. Because of that userver has no Application Binary Interface (ABI) stability guarantees. Binary interface may change on any commit. However, you could redefine cmake options `USERVERNAMESPACE`, `USERVERNAMESPACEBEGIN` and `USERVERNAMESPACE_END` to place all the entities of the userver into versioned inline namespace. That would to allow you mixing different versions of userver in a single binary without ODR-violations. @anchor QUALITY_TIERS userver consists of multiple drivers and technologies. Some of those are well tested on large scale of hundreds and thousands of services, some are less popular. There are tiers to differentiate technologies: Platinum Tier* - driver is known to be used in multiple high load critical to uptime services in huge companies. Golden Tier* - driver that has not enought usage feedback from huge companies. Still fine for production usage. Silver Tier* - early days of the driver. It passes all the tests and works fine, but more feedback/time required to become a Golden Tier driver. Fine for prototyping and production usage with some caution. @htmlonly <div class="bottom-nav"> @endhtmlonly @ref clickhousedriver | @ref scripts/docs/en/userver/driverguide.md @htmlonly </div> @endhtmlonly