cwielenb/CNCF-Dataset huggingface dataset:
Project: ShardingSphere (App Definition and Development / Database)
File: syntaxhighlight.en.md

date: 2020-06-01T13:31:12+01:00 title: Code highlighting weight: 16 Learn theme uses to provide code syntax highlighting. Wrap the code block with three backticks and the name of the language. Highlight will try to auto detect the language if one is not provided. <!-- markdownlint-disable MD046 --> ```plaintext ```json [ { "title": "apples", "count": [12000, 20000], "description": {"text": "...", "sensitive": false} }, { "title": "oranges", "count": [17500, null], "description": {"text": "...", "sensitive": false} } ] ``` ``` <!-- markdownlint-disable MD046 --> Renders to: ```json [ { "title": "apples", "count": [12000, 20000], "description": {"text": "...", "sensitive": false} }, { "title": "oranges", "count": [17500, null], "description": {"text": "...", "sensitive": false} } ] ``` Learn theme ships with its own version of highlight.js to support offline browsing. The included package supports 38 common languages, as described on the . Highlight will write a warning to the browser console if a requested language was not found. For example, the following code block references an imaginary language `foo`. An error will be output to the console on this page. ```plaintext ```foo bar ``` ``` ```nohighlight Could not find the language 'foo', did you forget to load/include a language module?(anonymous) @ highlight.pack.js ``` To support languages other than the 38 common languages included in the default highlight.js you will need to download your own version of highlight.js and add it to your site content. Visit and select your desired language support. Note that more languages means greater package size. Inside the zip archive downloaded from highlight.js extract the file named `highlight.pack.js`. Move this file to the new location ```nohighlight static/js/highlight.pack.js ``` Do not replace the existing file at `themes/hugo-theme-learn/static/js/highlight.pack.js`. Including the file in the correct path will override the theme default highlight.pack.js and prevent issues caused in the future if the theme default file is updated. See
Project: Sonobuoy (Provisioning / Security & Compliance)
File: sonobuoy_gen_default-image-config.md

Generates the default image registry config for the e2e plugin ``` sonobuoy gen default-image-config [flags] ``` ``` --context string Context in the kubeconfig to use. -h, --help help for default-image-config --kubeconfig Kubeconfig Path to explicit kubeconfig file. ``` ``` --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) ``` - Generates a sonobuoy manifest for submission via kubectl
Project: Chef Infra (Provisioning / Automation & Configuration)
File: resource_before_notifications.md

Let users trigger another resource prior to an action happening. As a Chef user, I want to make one resource action a precondition for another, So that when two resources depend on each other, I can make an update succeed. As a Chef user, I want this action only to happen if the other resource does update, So that I don't unnecessarily run my preconditions on every single Chef run. As a Chef user, I want Chef to run an action if a resource updates, So that I don't have to implement the resource test logic in my recipe. We add a new `:before` timing which causes a notification to happen before the resource actually updates. If the resource will not actually update, this event does not fire. The events you can specify would become: `:before` - before the resource updates, but only if an update will occur. `:immediately` - after the resource updates, but only if an update occurred. `:delayed` - after the resource updates, at the end of the run. ```ruby package "foo" do action :upgrade notifies :stop, "service[blah]", :before end service "blah" do end ``` This will work for both `subscribes` and `notifies`. This will only affect resources, which have `:before` on them, and will not modify any existing resources or recipes. There is a tricky implementation detail here, because both the test part -- "is my package version lower than the latest?" -- and the set part -- "call rpm and update the package"-- of a resource are both part of the action. Chef only runs one action to run at a time, and it seems ill-advised to change that without a lot of extra thinking. To get around this without breaking the model, we propose that resources with an `:before` action run a why-run test of the action and trigger off of that, before running the action for real. The flow of this resource: ```ruby package "foo" do action :upgrade notifies :stop, "service[blah]", :before end ``` The execution of the package upgrade looks like this: If `:before` events are on the resource: a. raise an error if the resource does not support `why-run`. b. Turn on `why-run` temporarily. c. Run the action. d. Send the notification if `updatedbylast_action?` is true. e. Turn off `why-run`. Run the action (for real!). Send `:immediate` or `:delayed` notifications if `updatedbylast_action?` is true.
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: lifecycle.md

id: lifecycle title: Lifecycle Service sidebar_label: Lifecycle description: Documentation for the Lifecycle service This service allows your plugins to register hooks for cleaning up resources as the service is shutting down (e.g. when a pod is being torn down, or when pressing `Ctrl+C` during local development). Other core services also leverage this same mechanism internally to stop themselves cleanly. The following example shows how to get the lifecycle service in your `example` backend plugin to clean up a long running interval when the service is shutting down. ```ts import { coreServices, createBackendPlugin, } from '@backstage/backend-plugin-api'; createBackendPlugin({ pluginId: 'example', register(env) { env.registerInit({ deps: { lifecycle: coreServices.lifecycle, logger: coreServices.logger, }, async init({ lifecycle, logger }) { // some example work that we want to stop when shutting down const interval = setInterval(async () => { await fetch('http://google.com/keepalive').then(r => r.json()); // do some other stuff. }, 1000); lifecycle.addShutdownHook(() => clearInterval(interval)); }, }); }, }); ```
Project: StarRocks (App Definition and Development / Database)
File: years_add.md

displayed_sidebar: "English" ```Haskell DATETIME YEARS_ADD(DATETIME expr1,INT expr2) ``` Add a specified time interval to the date. Unit is year. The expr1 parameter is a valid datetime expression. The expr2 parameter is the years you want to add. ```Plain Text select years_add('2010-11-30 23:50:50', 2); +-+ | years_add('2010-11-30 23:50:50', 2) | +-+ | 2012-11-30 23:50:50 | +-+ select years_add('2010-11-30', 2); +-+ | years_add('2010-11-30', 2) | +-+ | 2012-11-30 00:00:00 | +-+ ``` YEARS_ADD,ADD
Project: Cyclops (App Definition and Development / Application Definition & Image Build)
File: configuration.md

Following are environment variables you can use to configure your instance of Cyclops. You can set those environment variables directly on the `cyclops-ui` Kubernetes deployment. | Name | Description | Default value | | : | : | :-- | | REACTAPPCYCLOPSCTRLHOST | Content | http://localhost:8080 | | REACTAPPDEFAULTTEMPLATEREPO | Default template repo (E.g. https://github.com/cyclops-ui/templates) | - | | REACTAPPDEFAULTTEMPLATEPATH | Default template path (E.g. `demo`) | - | | REACTAPPDEFAULTTEMPLATEVERSION | Default template version<br/>Can be a commit hash, a tag or a branch name | - |
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.10.1.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Implement the LzoCodec with support for the lzo compression algorithms | Major | io | Arun C Murthy | Arun C Murthy | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | IOException when running map reduce on S3 filesystem | Major | fs | Tom White | | | | MapTask prints info log message when the progress-reporting thread starts | Major | . | Devaraj Das | Devaraj Das | | | Investigate and fix the extremely large memory-footprint of JobTracker | Major | . | Arun C Murthy | Arun C Murthy | | | Race condition in JobTracker updating the task tracker's status while declaring it lost | Major | . | Owen O'Malley | Arun C Murthy | | | bin/hadoop jar throws file creation exception for temp files | Minor | . | Sanjay Dahiya | Sanjay Dahiya | | | dfs -get should remove existing crc file if -crc is not specified | Major | fs | Milind Bhandarkar | Milind Bhandarkar | | | java.library.path is wrongly initialized by bin/hadoop when only pre-built libs are present, but custom-built ones aren't | Major | . | Arun C Murthy | Arun C Murthy | | | Fix the merge method on Maps to limit the number of open files | Major | . | Devaraj Das | Devaraj Das | | | Files written to S3 but never closed can't be deleted | Major | fs | Bryan Pendleton | Tom White | | | native libraries aren't loaded unless the user specifies the java.library.path in the child jvm options | Major | util | Owen O'Malley | Owen O'Malley | | | Recursive delete for an S3 directory does not actually delete files or subdirectories | Major | fs | Tom White | Tom White | | | SequenceFileInputFormat can no longer read from data produced by MapFileOutputFormat | Major | . | Bryan Pendleton | Doug Cutting |
Project: ClickHouse (App Definition and Development / Database)
File: 50_build-issue.md

name: Build issue about: Report failed ClickHouse build from master title: '' labels: build assignees: '' Make sure that `git diff` result is empty and you've just pulled fresh master. Try cleaning up cmake cache. Just in case, official build instructions are published here: https://clickhouse.com/docs/en/development/build/ Operating system OS kind or distribution, specific version/release, non-standard kernel if any. If you are trying to build inside virtual machine, please mention it too. Cmake version Ninja version Compiler name and version Full cmake and/or ninja output
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.12.8.md

RabbitMQ `3.12.8` is a maintenance release in the `3.12.x` . Please refer to the upgrade section from the if upgrading from a version prior to 3.12.0. This release requires Erlang 25 and supports Erlang versions up to `26.1.x`. has more details on Erlang version requirements for RabbitMQ. As of 3.12.0, RabbitMQ requires Erlang 25. Nodes will fail to start on older Erlang releases. Users upgrading from 3.11.x (or older releases) on Erlang 25 to 3.12.x on Erlang 26 (both RabbitMQ and Erlang are upgraded at the same time) must consult the first. Release notes can be found on GitHub at . Avoids a potential exception in the `autoheal` partition handler. Contributed by @Ayanda-D. GitHub issue: `raft.segmentmaxentries` is now validated to prevent the value from overflowing its 16-bit segment file field. Maximum supported value is now `65535`. GitHub issue: Significantly faster Shovel startup in environments where there are many of them (one thousand or more). GitHub issue: User-provided credentials are now obfuscated using an one-off key pair generated on node boot. This keeps sensitive client state information from being logged by the runtime exception logger. GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.12.8.tar.xz` instead of the source tarball produced by GitHub.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_cluster_list-instances.md

title: kbcli cluster list-instances List cluster instances. ``` kbcli cluster list-instances [flags] ``` ``` kbcli cluster list-instances kbcli cluster list-instances mycluster ``` ``` -A, --all-namespaces If present, list the requested object(s) across all namespaces. Namespace in current context is ignored even if specified with --namespace. -h, --help help for list-instances -l, --selector string Selector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. ``` ``` --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/.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 --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 --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 ``` - Cluster command.
Project: YugabyteDB (App Definition and Development / Database)
File: dcl_alter_default_privileges.md

title: ALTER DEFAULT PRIVILEGES statement [YSQL] headerTitle: ALTER DEFAULT PRIVILEGES linkTitle: ALTER DEFAULT PRIVILEGES description: Use the ALTER DEFAULT PRIVILEGES statement to define the default access privileges. menu: v2.18: identifier: dclalterdefault_privileges parent: statements type: docs Use the `ALTER DEFAULT PRIVILEGES` statement to define the default access privileges. {{%ebnf%}} alterdefaultpriv, abbrgrantor_revoke, agranttable, agrantseq, agrantfunc, agranttype, agrantschema, arevoketable, arevokeseq, arevokefunc, arevoketype, arevokeschema, granttablepriv, grantseqpriv, grantee_role {{%/ebnf%}} `ALTER DEFAULT PRIVILEGES` defines the privileges for objects created in future. It does not affect objects that are already created. Users can change default privileges only for objects that are created by them or by roles that they are a member of. Grant SELECT privilege to all tables that are created in schema marketing to all users. ```plpgsql yugabyte=# ALTER DEFAULT PRIVILEGES IN SCHEMA marketing GRANT SELECT ON TABLES TO PUBLIC; ``` Revoke INSERT privilege on all tables from user john. ```plpgsql yugabyte=# ALTER DEFAULT PRIVILEGES REVOKE INSERT ON TABLES FROM john; ```
Project: Meshery (Provisioning / Automation & Configuration)
File: gitlab-controller.md

layout: integration title: Gitlab Controller subtitle: Collaborative and visual infrastructure as code for Gitlab Controller image: /assets/img/integrations/gitlab-controller/icons/color/gitlab-controller-color.svg permalink: extensibility/integrations/gitlab-controller docURL: https://docs.meshery.io/extensibility/integrations/gitlab-controller description: integrations-category: App Definition and Development integrations-subcategory: Source Version Control 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
Project: Chef Habitat (App Definition and Development / Application Definition & Image Build)
File: plan_quickstart.md

+++ title = "Plan Quickstart" draft = false gh_repo = "habitat" [menu] [menu.habitat] title = "Plan Quickstart" identifier = "habitat/plans/plan-quickstart Plan Quickstart" parent = "habitat/plans" weight = 20 +++ All plans must have a `plan.sh` or `plan.ps1` at the root of the plan context. They may even include both if a package is targeting both Windows and Linux platforms. This file will be used by the `hab-plan-build` command to build your package. To create a plan, do the following: If you haven't done so already, and install it per the instructions on the download page. Run `hab cli setup` and follow the instructions in the setup script. The easiest way to create a plan is to use the `hab plan init` subcommand. This subcommand will create a directory, known as the plan context, that contains your plan file and any runtime hooks and/or templated configuration data. To use `hab plan init` as part of your project repo, navigate to the root of your project repo and run `hab plan init`. It will create a new `habitat` sub-directory with a plan.sh (or plan.ps1 on Windows) based on the name of the parent directory, and include a `default.toml` file as well as `config` and `hooks` directories for you to populate as needed. For example: ```bash cd /path/to/<reponame> hab plan init ``` will result in a new `habitat` directory located at `/path/to/<reponame>/habitat`. A plan file will be created and the `pkgname` variable will be set to \<reponame\>. Also, any environment variables that you have previously set (such as `HABORIGIN`) will be used to populate the respective `pkg_*` variables. If you want to auto-populate more of the `pkg_*` variables, you also have the option of setting them when calling `hab plan init`, as shown in the following example: ```bash env pkgsvcuser=someuser pkg_deps="(core/make core/coreutils)" \ pkglicense="('MIT' 'Apache-2.0')" pkgbin_dirs="(bin sbin)" \ pkgversion=1.0.0 pkgdescription="foo" pkg_maintainer="you" \ hab plan init yourplan ``` See for more information on how to use this subcommand. Now that you have stubbed out your plan file in your plan context, open it and begin modifying it to suit your needs. When writing a plan, it's important to understand that you are defining both how the package is built and the actions Chef Habitat will take when the Supervisor starts and manages the child processes in the package. The following sections explain what you need to do for each phase.
Project: ThreatMapper (Provisioning / Security & Compliance)
File: managed-database.md

title: Managed Database For production deployment of Deepfence Management Console, we recommend using cloud/vendor managed PostgreSQL and Neo4j services. Please use the following settings to configure the Neo4j AuraDB Professional / Enterprise service | Option | Recommended Value | ||-| | Memory | 8GB | | CPU | 2 CPU | | Storage | 16GB | In docker-compose.yml, set the values for postgresql accordingly. ```yaml x-service-variables: &common-creds DEEPFENCENEO4JUSER: neo4j DEEPFENCENEO4JPASSWORD: <password> NEO4J_AUTH: neo4j/<password> DEEPFENCENEO4JBOLT_PORT: 7687 DEEPFENCENEO4JHOST: abcdefgh.databases.neo4j.io ``` Please use the following settings to configure the Elasticsearch service | Option | Recommended Value | |-|| | Engine | PostgreSQL | | Version | 13.7-R1 or above | | Availability | Single DB instance / Multi-AZ DB instance | | Credentials | Set username and password | | DB instance class | db.m6i.large / db.t3.medium or better | | Storage type | Provisioned IOPS SSD | | Allocated storage | >= 100 | | Provisioned IOPS | >= 3000 | | Public access | No (provide access only to management console nodes) | | Database authentication | Password authentication | | Initial database name | deepfence | In docker-compose.yml, set the values for postgresql accordingly. ```yaml x-service-variables: &common-creds DEEPFENCEPOSTGRESUSERDBUSER: postgres DEEPFENCEPOSTGRESUSERDBPASSWORD: <password> DEEPFENCEPOSTGRESUSERDBHOST: pg-db-1.aaaaaa.us-east-1.rds.amazonaws.com DEEPFENCEPOSTGRESUSERDBNAME: deepfence DEEPFENCEPOSTGRESUSERDBPORT: 5432 DEEPFENCEPOSTGRESUSERDBSSLMODE: disable ```
Project: Druid (App Definition and Development / Database)
File: peons.md

id: peons title: "Peon service" sidebar_label: "Peon" <!-- ~ 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. --> The Peon service is a task execution engine spawned by the MiddleManager. Each Peon runs a separate JVM and is responsible for executing a single task. Peons always run on the same host as the MiddleManager that spawned them. For Apache Druid Peon configuration, see and . For basic tuning guidance for MiddleManager tasks, see . Peons run a single task in a single JVM. The MiddleManager is responsible for creating Peons for running tasks. Peons should rarely run on their own. The Peon should seldom run separately from the MiddleManager, except for development purposes. ``` org.apache.druid.cli.Main internal peon <taskfile> <statusfile> ``` The task file contains the task JSON object. The status file indicates where the task status will be output.