cwielenb/CNCF-Dataset huggingface dataset:
Project: Apollo (Provisioning / Automation & Configuration)
File: portal-how-to-enable-session-store.md

Starting with version 1.9.0, apollo-portal adds session sharing support so that session sharing can be implemented in cluster deployments of apollo-portal. The default configuration is JDBC-based session sharing. So clear the session sharing related configuration and configure the database connection, the configuration to be cleared is as follows `spring.session.store-type` configuration in the external configuration file (properties/yml) Environment variables inside the `SPRINGSESSIONSTORE_TYPE` System Property inside `spring.session.store-type` There are several ways to set the database connection, from highest to lowest priority, as follows ```bash -Dspring.datasource.url=xxx -Dspring.datasource.username=xxx -Dspring.datasource.password=xxx ``` ```bash export SPRINGDATASOURCEURL="xxx" export SPRINGDATASOURCEUSERNAME="xxx" export SPRINGDATASOURCEPASSWORD="xxx" ``` For example `config/application-github.properties` ```properties spring.datasource.url=xxx spring.datasource.username=xxx spring.datasource.password=xxx ``` If you need to use other databases, you can refer to the other table creation sql provided by Please select the corresponding sql script according to the database you are using There are several ways to set this up, from highest to lowest priority, as follows Note: redis also supports cluster and sentry mode, configured in the standard `Spring Data Redis` mode (configuration items starting with `spring.redis`), please study the `Spring Data Redis` related documentation or consult the `Spring Data` Group for details ```bash -Dspring.session.store-type=redis -Dspring.redis.host=xxx -Dspring.redis.port=xxx -Dspring.redis.username=xxx -Dspring.redis.password=xxx ``` ```bash export SPRINGSESSIONSTORE_TYPE="redis" export SPRINGREDISHOST="xxx" export SPRINGREDISPORT="xxx" export SPRINGREDISUSERNAME="xxx" export SPRINGREDISPASSWORD="xxx" ``` For example ``config/application-github.properties`'' ```properties spring.session.store-type=redis spring.redis.host=xxx spring.redis.port=xxx spring.redis.username=xxx spring.redis.password=xxx ``` There are several ways to set this, in descending order of priority, as follows ```bash -Dspring.session.store-type=none ``` ```bash export SPRINGSESSIONSTORE_TYPE="none" ``` For example `config/application-github.properties` ```properties spring.session.store-type=none ```
Project: KICS (Provisioning / Security & Compliance)
File: ce60d060-efb8-4bfd-9cf7-ff8945d00d90.md

title: Misconfigured Password Policy Expiration hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ce60d060-efb8-4bfd-9cf7-ff8945d00d90 Query name: Misconfigured Password Policy Expiration Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: No password expiration policy<br> ```tf title="Positive test num. 1 - tf file" hl_lines="8 12" resource "awsiamaccountpasswordpolicy" "positive1" { minimumpasswordlength = 8 requirelowercasecharacters = true require_numbers = true requireuppercasecharacters = true require_symbols = true allowuserstochangepassword = true maxpasswordage = 180 } // comment resource "awsiamaccountpasswordpolicy" "positive2" { minimumpasswordlength = 8 requirelowercasecharacters = true require_numbers = true requireuppercasecharacters = true require_symbols = true allowuserstochangepassword = true } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamaccountpasswordpolicy" "negative1" { minimumpasswordlength = 8 requirelowercasecharacters = true require_numbers = true requireuppercasecharacters = true require_symbols = true allowuserstochangepassword = true maxpasswordage = 10 } ```
Project: YugabyteDB (App Definition and Development / Database)
File: reserved_names.md

title: Reserved names [YSQL] headerTitle: Reserved names linkTitle: Reserved names description: List of YSQL system column and database object names that are reserved for internal usage. summary: List of reserved names menu: v2.18: identifier: api-ysql-reserved-names parent: api-ysql weight: 100 type: docs YSQL reserves the following names for internal usage. Exception will be raised when these names are used even when they are double-quoted. | Names | Description | |-|-| | `oid` | System column | | `tableoid` | System column | | `xmin` | System column | | `cmin` | System column | | `xmax` | System column | | `cmax` | System column | | `ctid` | System column | | `ybctid` | Virtual column | | Prefixed with `pg_` | System database objects | | Prefixed with `yb_` | System database objects |
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: adr003-avoid-default-exports.md

id: adrs-adr003 title: 'ADR003: Avoid Default Exports and Prefer Named Exports' description: Architecture Decision Record (ADR) log on Avoid Default Exports and Prefer Named Exports When CommonJS was the primary authoring format, the best practice was to export only one thing from a module using the `module.exports = ...` format. This aligned with the of "Do one thing well". The module would be consumed (`const localName = require('the-module');`) without having to know the internal structure. Now, `ESModules` are the primary authoring format. They have numerous benefits, such as compile-time verification of exports, and standards-defined semantics. They have a similar mechanism known as "default exports", which allows for a consumer to `import localName from 'the-module';`. This is implicitly the same as `import { default as localName } from 'the-module';`. However, there are numerous reasons to avoid default exports, as documented by others before: https://humanwhocodes.com/blog/2019/01/stop-using-default-exports-javascript-module/ A summary: They add indirection by encouraging a developer to create local names for modules, increasing cognitive load and slowing down code comprehension: `import TheListThing from 'not-a-list-thing';`. They thwart tools, such as IDEs, that can automatically rename and refactor code. They promote typos and mistakes, as the imported member is completely up to the consuming developer to define. They are ugly in CommonJS interop, as the default property must be manually specified by the consumer. This is often hidden by Babel's module interop. They break re-exports due to name conflicts, forcing the developer to manually name each. Using named exports helps prevent needing to rename symbols, which has myriad benefits. A few are: IDE tools like "Find All References" and "Go To Definition" function Manual codebase searching ("grep", etc) is easier with a unique symbol We will stop using default exports except when absolutely necessary (such as modules). A workaround exists for those that would prefer to never use `default`: ```ts const Component = React.lazy(() => import('../path/to/Component').then(m => ({ default: m.Component })), ); ``` We will actively work to remove them from our codebases, being as explicit as possible. Have a connected component? `export const ConnectedComponent = connect(Component)`. We will add tools, such as lint rules, to help migrate away from default exports.
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_data_insert_redis.md

title: Kubectl-Dba Data Insert Redis menu: docs_{{ .version }}: identifier: kubectl-dba-data-insert-redis name: Kubectl-Dba Data Insert Redis parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Insert data to a redis database Use this cmd to insert data into a redis database ``` kubectl-dba data insert redis [flags] ``` ``` kubectl dba data insert redis -n demo sample-redis --rows 500 ``` ``` -h, --help help for redis -r, --rows int number of rows to insert (default 100) ``` ``` --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 ``` - Insert random data in a database
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_sourcerepo_repository.md

+++ title = "googlesourcereporepository resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlesourcereporepository" identifier = "inspec/resources/gcp/googlesourcereporepository.md googlesourcereporepository resource" parent = "inspec/resources/gcp" +++ A `googlesourcereporepository` is used to test a Google Repository resource ```ruby describe googlesourcereporepository(project: 'chef-gcp-inspec', name: 'inspec-gcp-repository') do it { should exist } end describe googlesourcereporepository(project: 'chef-gcp-inspec', name: 'nonexistent') do it { should_not exist } end ``` Properties that can be accessed from the `googlesourcereporepository` resource: `name` : Resource name of the repository, of the form projects/{{project}}/repos/{{repo}}. The repo name may contain slashes. E.g., projects/myproject/repos/name/with/slash `url` : URL to clone the repository from Google Cloud Source Repositories. `size` : The disk usage of the repo, in bytes. `pubsub_configs` : How this repository publishes a change in the repository through Cloud Pub/Sub. Keyed by the topic names. Ensure the is enabled for the current project.
Project: kube-bench (Provisioning / Security & Compliance)
File: bug_report.md

name: Bug report about: Tell us about a problem you are experiencing Overview [A clear and concise description of what the bug is] How did you run kube-bench? [Please specify exactly how you ran kube-bench, including details of command parameters and/or job file that you used to run it] What happened? [Please include output from the report to illustrate the problem. If possible please supply logs generated with the `-v 3` parameter.] What did you expect to happen: [Please describe what you expected to happen differently.] Environment [What is your version of kube-bench? (run `kube-bench version`)] [What is your version of Kubernetes? (run `kubectl version` or `oc version` on OpenShift.)] Running processes [Please include the output from running `ps -eaf | grep kube` on the affected node. This will allow us to check what Kubernetes processes are running, and how this compares to what kube-bench detected.] Configuration files [If kube-bench is reporting an issue related to the settings defined in a config file, please attach the file, or include an extract showing the settings that are being detected incorrectly.] Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Project: KubeArmor (Provisioning / Security & Compliance)
File: db-access.md

```sh kubectl exec -it mysql-74775b4bf4-65nqf -n wordpress-mysql -- bash root@mysql-74775b4bf4-65nqf:/# cd var/lib/mysql root@mysql-74775b4bf4-65nqf:/var/lib/mysql# cat ib_logfile1 cat: ib_logfile1: Permission denied root@mysql-74775b4bf4-65nqf:/var/lib/mysql# ``` ``` { "ATags": [ "CIS", "CIS_Linux" ], "Action": "Block", "ClusterName": "aditya", "ContainerID": "b75628d4225b8071d5795da342cf2a5c03b1d67b22b40016697fcd17a0db20e4", "ContainerImage": "docker.io/library/mysql:5.6@sha256:20575ecebe6216036d25dab5903808211f1e9ba63dc7825ac20cb975e34cfcae", "ContainerName": "mysql", "Data": "syscall=SYSOPEN flags=ORDONLY", "Enforcer": "AppArmor", "HashID": "a7b7d91d52de395fe6cda698e89e0112e6f3ab818ea331cee60295a8ede358c8", "HostName": "aditya", "HostPID": 29898, "HostPPID": 29752, "Labels": "app=mysql", "Message": "Alert! Attempt to make changes to database detected", "NamespaceName": "wordpress-mysql", "Operation": "File", "Owner": { "Name": "mysql", "Namespace": "wordpress-mysql", "Ref": "Deployment" }, "PID": 230, "PPID": 223, "PodName": "mysql-74775b4bf4-65nqf", "PolicyName": "ksp-block-mysql-dir", "ProcessName": "/bin/cat", "Resource": "/var/lib/mysql/ib_logfile1", "Result": "Permission denied", "Severity": "1", "Source": "/bin/cat ib_logfile1", "Tags": "CIS,CIS_Linux", "Timestamp": 1696322555, "Type": "MatchedPolicy", "UID": 0, "UpdatedTime": "2023-10-03T08:42:35.618890Z", "cluster_id": "3896", "component_name": "kubearmor", "instanceGroup": "0", "instanceID": "0", "workload": "1" } ```
Project: YugabyteDB (App Definition and Development / Database)
File: docs-layout.md

title: Find the right page or section headerTitle: Find the right page or section linkTitle: Docs layout description: Find the right location in the YugabyteDB docs menu: preview: identifier: docs-layout parent: docs weight: 2912 type: docs The YugabyteDB docs are divided into several sections: is the overview documentation for YugabyteDB documents YugabyteDB Anywhere documents YugabyteDB Managed contains release notes and other information related to releases documents third-party integrations contains detailed reference and architecture information about functions, features, and interfaces contains frequently-asked questions on a variety of topics contains legal information and the (deprecated) YEDIS subsystem The are landing pages with overview and getting-started information. Pages in this section should have a high-level overview of a feature, what's supported, limitations, and a link to any roadmap GitHub issues. These docs pages can have "Further reading" sections, where you can add links to blogs or Reference section docs as appropriate. Think of the pages in the as a self-guided tour of YugabyteDB. When you're reading a page in this section, you should be able to get a good sense of how the feature works. The page may not answer every question you have, but should point you to the reference page where you can find that information. Reference docs should be comprehensive and, above all, accurate. This applies to other doc types, but is especially important for reference docs, as they should be the ultimate source of truth for users. Here are some examples of reference docs in our documentation: SQL reference sample: We also have design docs . These design docs should be referenced from the Reference section in the docs. Many of the illustrations in the docs use the following legend to represent tablet leaders and followers, cloud regions and zones, and applications. Now that you know where your page should go, locally and .
Project: secureCodeBox (Provisioning / Security & Compliance)
File: feature_request.md

name: " Feature request" about: "Suggest an idea for this project" labels: 'enhancement' <!-- Thank you for reporting an issue in our documentation Before opening a new issue, please make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead. --> <!-- Please describe a clear and concise description of what the problem is. Use commmon user story patterns like https://en.wikipedia.org/wiki/User_story: As a <role> I can <capability>, so that <receive benefit> In order to <receive benefit> as a <role>, I can <goal/desire> As <who> <when> <where>, I <want> because <why> For example... As a secureCodeBox user i'm always frustrated when [...] --> <!-- Please describe a clear and concise description of what you want to happen. --> <!-- Please describe a clear and concise description of any alternative solutions or features you've considered. --> <!-- Add any other context or screenshots about the feature request here. -->
Project: StarRocks (App Definition and Development / Database)
File: CREATE_FUNCTION.md

displayed_sidebar: "English" Creates a user-defined function (UDF). Currently, you can only create Java UDFs, including Scalar functions, user-defined aggregate functions (UDAFs), user-defined window functions (UDWFs), and user-defined table functions (UDTFs). For details about how to compile, create, and use a Java UDF, see . NOTE To create a global UDF, you must have the SYSTEM-level CREATE GLOBAL FUNCTION privilege. To create a database-wide UDF, you must have the DATABASE-level CREATE FUNCTION privilege. ```sql CREATE FUNCTION function_name (arg_type [, ...]) RETURNS return_type PROPERTIES ("key" = "value" [, ...]) ``` | Parameter | Required | Description | | - | -- | | | GLOBAL | No | Whether to create a global UDF, supported from v3.0. | | AGGREGATE | No | Whether to create a UDAF or UDWF. | | TABLE | No | Whether to create a UDTF. If both `AGGREGATE` and `TABLE` are not specified, a Scalar function is created. | | functionname | Yes | The name of the function you want to create. You can include the name of the database in this parameter, for example,`db1.myfunc`. If `function_name` includes the database name, the UDF is created in that database. Otherwise, the UDF is created in the current database. The name of the new function and its parameters cannot be the same as an existing name in the destination database. Otherwise, the function cannot be created. The creation succeeds if the function name is the same but the parameters are different. | | arg_type | Yes | Argument type of the function. The added argument can be represented by `, ...`. For the supported data types, see .| | return_type | Yes | The return type of the function. For the supported data types, see . | | PROPERTIES | Yes | Properties of the function, which vary depending on the type of the UDF to create. For details, see . |
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.12.1.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Make Record I/O functionally modular from the rest of Hadoop | Major | record | Milind Bhandarkar | Milind Bhandarkar | | | Rename InputArchive and OutputArchive and make them public | Major | record | Milind Bhandarkar | Milind Bhandarkar | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | StackOverflowError in FSDataSet | Blocker | . | Philippe Gassmann | Raghu Angadi | | | Compile fails if Checkstyle jar is present in lib directory | Major | build | Tom White | Tom White | | | IndexOutOfBoundsException in JobInProgress.updateTaskStatus leads to hung jobs | Blocker | . | Arun C Murthy | Arun C Murthy | | | Race condition in fetching map outputs (might lead to hung reduces) | Blocker | . | Devaraj Das | Devaraj Das | | | Replication not occuring after cluster restart when datanodes missing | Blocker | . | Nigel Daley | Hairong Kuang | | | NullpointerException in ChecksumFileSystem$FSInputChecker.seek | Blocker | . | Hairong Kuang | Hairong Kuang | | | Csv and Xml serialization for buffers do not work for byte value of -1 | Blocker | record | Milind Bhandarkar | Milind Bhandarkar | | | Cygwin path translation should occur earlier in bin/hadoop | Major | scripts | Andrzej Bialecki | | | | NPE from Simon in JT stdout | Major | . | David Bowen | David Bowen | | | NullPointerException in HeartbeatMonitor thread | Blocker | . | Nigel Daley | Hairong Kuang | | | Race condition in Hadoop metrics | Major | . | David Bowen | | | | Checksumed file system should retry reading if a different replica is found when handle ChecksumException | Blocker | . | dhruba borthakur | Hairong Kuang | | | Number of racks and datanode double temporarily when upgrading from 0.10.1 to 0.11.2 | Blocker | . | Nigel Daley | Konstantin Shvachko | | | NullPointerException in JobInProgress.getTaskInProgress | Major | . | Nigel Daley | Gautam Kowshik | | | copyToLocal doesn't copy directories | Blocker | . | Nigel Daley | | | | Streaming, NPE when reading sequencefile | Major | . | Koji Noguchi | | | | DFS Scalability: When the namenode is restarted it consumes 80% CPU | Blocker | . | dhruba borthakur | dhruba borthakur | | | The c++ version of write and read v-int don't agree with the java versions | Major | record | Owen O'Malley | Milind Bhandarkar | | | Missing progress information in map tasks | Major | . | Andrzej Bialecki | Andrzej Bialecki | | | The DFSClient hides IOExceptions in flush | Major | . | Owen O'Malley | Hairong Kuang | | | Optimize CPU usage when cluster restarts | Major | . | dhruba borthakur | Hairong Kuang |
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: alluxio.md

title: Alluxio labels: category: authorization type: poweredbyopa tutorials: https://docs.alluxio.io/ee/user/2.10.0/en/security/OpenPolicyAgent-Integration.html inventors: alluxio Alluxio is an open source data orchestration technology for analytics and AI for the cloud. Alluxio can integrate with OPA and delegate all permission checks to OPA.
Project: Meshery (Provisioning / Automation & Configuration)
File: pravega.md

layout: integration title: Pravega subtitle: Collaborative and visual infrastructure as code for Pravega image: /assets/img/integrations/pravega/icons/color/pravega-color.svg permalink: extensibility/integrations/pravega docURL: https://docs.meshery.io/extensibility/integrations/pravega description: integrations-category: Cloud Native Storage integrations-subcategory: Streaming & Messaging 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