cwielenb/CNCF-Dataset huggingface dataset:
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_region_instance_group_managers.md

+++ title = "googlecomputeregioninstancegroup_managers resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputeregioninstancegroup_managers" identifier = "inspec/resources/gcp/googlecomputeregioninstancegroupmanagers.md googlecomputeregioninstancegroupmanagers resource" parent = "inspec/resources/gcp" +++ A `googlecomputeregioninstancegroup_managers` is used to test a Google RegionInstanceGroupManager resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ``` describe googlecomputeregioninstancegroup_managers(project: 'chef-gcp-inspec', region: 'europe-west2') do its('instancegroupmanager_names') { should include 'inspec-rigm' } its('baseinstancenames') { should include 'rigm1' } end ``` describe googlecomputeregioninstancegroup_managers(project: 'chef-inspec-gcp', region: 'europe-west2') do its('count') { should be <= 100} end describe googlecomputeregioninstancegroup_managers(project: 'chef-inspec-gcp', region: 'europe-west2') do its('instancegroupnames') { should include "my-instance-group-name" } end googlecomputeregioninstancegroupmanagers(project: 'chef-inspec-gcp', region: 'europe-west2').where(instancegroupname: /^mig/).instancegroupnames.each do |instancegroup_name| describe googlecomputeinstancegroup(project: 'chef-inspec-gcp', region: 'europe-west2', name: instancegroup_name) do it { should exist } its('target_size') { should be > 0 } end end Properties that can be accessed from the `googlecomputeregioninstancegroup_managers` resource: See the resource for more information. `baseinstancenames` : an array of `googlecomputeregioninstancegroupmanager` baseinstance_name `creation_timestamps` : an array of `googlecomputeregioninstancegroupmanager` creationtimestamp `current_actions` : an array of `googlecomputeregioninstancegroupmanager` currentactions `descriptions` : an array of `googlecomputeregioninstancegroup_manager` description `instancegroupmanager_ids` : an array of `googlecomputeregioninstancegroup_manager` id `instance_groups` : an array of `googlecomputeregioninstancegroupmanager` instancegroup `instance_templates` : an array of `googlecomputeregioninstancegroupmanager` instancetemplate `instancegroupmanager_names` : an array of `googlecomputeregioninstancegroup_manager` name `named_ports` : an array of `googlecomputeregioninstancegroupmanager` namedports `target_pools` : an array of `googlecomputeregioninstancegroupmanager` targetpools `target_sizes` : an array of `googlecomputeregioninstancegroupmanager` targetsize `autohealingpolicies` : an array of `googlecomputeregioninstancegroupmanager` autohealing_policies `regions` : an array of `googlecomputeregioninstancegroup_manager` region This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.
Project: secureCodeBox (Provisioning / Security & Compliance)
File: 2020-10-16-release-of-securecodebox-version-2.md

title: Release of Version 2 author: Sven Strittmatter author_title: Core Developer author_url: https://github.com/Weltraumschaf authorimageurl: https://www.gravatar.com/avatar/3fe213284598b5cb69009665902c77a1 tags: secureCodeBox release v2 description: Here we announce the release of secureCodeBox version 2.0! image: /img/blog/2020-10-16-firework.jpg (Photo by on ) We are very happy and proud to announce the of secureCodeBox. It is a better, faster and greater secureCodeBox since ever <!--truncate--> To get your hands on it you need a running cluster and . with enabled Kubernetes is sufficient for your first steps. We have worked really hard to provide you a comprehensive . There you find and how to . :::caution Please note that scanning random hosts may be illegal. Please scan only hosts you are responsible for and you are permitted to do this. Everything you do with the secureCodeBox is completely your responsibility. ::: If you miss something in our documentation or you think it is unclear or wrong described. Please feel free to file an . If you need any help with your brand new secureCodeBox don't hesitate to contact us via , (Channel `#project-securecodebox`), E-Mail (securecodebox at GitHub. The big changes we did in the architecture of secureCodeBox we we will discuss in a later post. For now I'll give you only a brief outline of the hottest key features: Kubernetes bases orchestration of scans: This means that we do not need the whole engine known from version 1. No UI anymore: In consequence, this means without the engine there is also no web UI anymore. Cascading scans: Now it is possible to feed the result of a scan into subsequent scans. Resource consumption: Massive reduction of consumed CPU and RAM because scanners only run when they scan. Stability and scalability: At we run approximately a thousand scans a day against our infrastructure Due to the fact of limited resources, we can't afford the maintenance for version 1. So we are forced to announce the for secureCodeBox version 1.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_plugin_install.md

title: kbcli plugin install Install kbcli or kubectl plugins ``` kbcli plugin install [flags] ``` ``` kbcli plugin install [PLUGIN] kbcli plugin install [INDEX/PLUGIN] ``` ``` -h, --help help for install ``` ``` --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 ``` - Provides utilities for interacting with plugins.
Project: KICS (Provisioning / Security & Compliance)
File: 87554eef-154d-411d-bdce-9dbd91e56851.md

title: PSP Allows Privilege Escalation hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 87554eef-154d-411d-bdce-9dbd91e56851 Query name: PSP Allows Privilege Escalation Platform: Kubernetes Severity: <span style="color:#bb2124">High</span> Category: Insecure Configurations URL: PodSecurityPolicy should not allow privilege escalation<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="32 9" apiVersion: policy/v1beta1 kind: PodSecurityPolicy metadata: name: privileged annotations: seccomp.security.alpha.kubernetes.io/allowedProfileNames: '*' spec: privileged: true allowPrivilegeEscalation: true hostNetwork: true hostPorts: min: 0 max: 65535 hostIPC: true hostPID: true runAsUser: rule: 'RunAsAny' seLinux: rule: 'RunAsAny' supplementalGroups: rule: 'RunAsAny' fsGroup: rule: 'RunAsAny' apiVersion: policy/v1beta1 kind: PodSecurityPolicy metadata: name: privileged2 annotations: seccomp.security.alpha.kubernetes.io/allowedProfileNames: '*' spec: privileged: true hostNetwork: true hostPorts: min: 0 max: 65535 hostIPC: true hostPID: true runAsUser: rule: 'RunAsAny' seLinux: rule: 'RunAsAny' supplementalGroups: rule: 'RunAsAny' fsGroup: rule: 'RunAsAny' ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: policy/v1beta1 kind: PodSecurityPolicy metadata: name: privileged annotations: seccomp.security.alpha.kubernetes.io/allowedProfileNames: '*' spec: privileged: true allowPrivilegeEscalation: false volumes: '*' hostNetwork: true hostPorts: min: 0 max: 65535 hostIPC: true hostPID: true runAsUser: rule: 'RunAsAny' seLinux: rule: 'RunAsAny' supplementalGroups: rule: 'RunAsAny' fsGroup: rule: 'RunAsAny' ```
Project: ArangoDB (App Definition and Development / Database)
File: assume_exception_rvalue_const.md

+++ title = "`const exceptiontype &&assumeexception() const && noexcept`" description = "Narrow contract const rvalue reference observer of the stored exception. Constexpr propagating, never throws." categories = ["observers"] weight = 782 +++ Narrow contract const rvalue reference observer of the stored exception. `NoValuePolicy::narrowexceptioncheck()` is first invoked, then the reference to the exception is returned. As a valid default constructed exception is always present, no undefined behaviour occurs unless `NoValuePolicy::narrowexceptioncheck()` does that. Note that if `exception_type` is `void`, only a `const` overload returning `void` is present. Requires: Always available. Complexity: Depends on `NoValuePolicy::narrowexceptioncheck()`. Guarantees: An exception is never thrown.
Project: NeuVector (Provisioning / Security & Compliance)
File: HACKING.md

HACKING ======= Assuming you already have a Go environment set up. go get github.com/socketplane/libovsdb cd $GOPATH/src/github.com/socketplane/libovsdb You can use to fork the repo hub fork ... or alternatively, fork socketplane/libovsdb on GitHub and add your fork as a remote git remote add <github-user> git@github.com:<github-user>/libovsdb Pull a local branch before you start developing. Convention for branches is `bug/1234` for a branch that addresses a specific bug `feature/awesome` for a branch that implements an awesome feature If your work is a minor, you can call the branch whatever you like (within reason). Before you submit code, you must agree to the Developer Certificate of Origin Version 1.1 Copyright (C) 2004, 2006 The Linux Foundation and its contributors. 660 York Street, Suite 102, San Francisco, CA 94110 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Developer's Certificate of Origin 1.1 By making a contribution to this project, I certify that: (a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it. (d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved. To verify that you agree, you must sign-off your commits. git commit -s This adds the following to the bottom of you commit message Signed-off-by: John Doe <john@doe.io> The name and email address used in the sign off are taken from your `user.name` and `user.email` settings in `git`. You can change these globally or locally using `git config` or from your `~/.gitconfig` file fig up -d make test-all go fmt git push <github-user> <branch-name> hub pull-request ... or if you still aren't using `hub` (which you should be by now) you can head over to and create a PR using the web interface Once your patch has been submitted it will be scrutinized by your peers. To make changes in response to comments... git push <github-user> --force This will update the pull request, retrigger CI etc... We hope you find this guide helpful and are looking forward to your pull requests!
Project: YugabyteDB (App Definition and Development / Database)
File: metabase.md

title: Metabase linkTitle: Metabase description: Metabase menu: stable: identifier: metabase parent: tools weight: 70 type: docs is a Business Intelligence (BI) tool. This document shows how to set up Metabase to integrate with YugabyteDB's PostgreSQL-compatible API. Follow instructions to run a local YugabyteDB cluster. ```sh $ wget https://raw.githubusercontent.com/yugabyte/yb-sql-workshop/master/query-using-bi-tools/schema.sql ``` ```sh $ wget https://github.com/yugabyte/yb-sql-workshop/raw/master/query-using-bi-tools/sample-data.tgz ``` ```sh $ tar zxvf sample-data.tgz ``` ```sh $ ls data/ ``` ```output orders.sql products.sql reviews.sql users.sql ``` Run the following command to connect to YugabyteDB using the YSQL shell: ```sh $ ./bin/ysqlsh ``` ```output ysqlsh (11.2) Type "help" for help. yugabyte=# ``` ```sql yugabyte=# CREATE DATABASE yb-demo; yugabyte=# GRANT ALL ON DATABASE yb-demo to yugabyte; yugabyte=# \c yb-demo; ``` First create the 4 tables necessary to store the data: ```sql yugabyte=# \i 'schema.sql'; ``` Now load the data into the tables: ```sql yugabyte=# \i 'data/products.sql' yugabyte=# \i 'data/users.sql' yugabyte=# \i 'data/orders.sql' yugabyte=# \i 'data/reviews.sql' ``` Detailed steps for setting up Metabase are available in the . The following are the minimal steps for getting started: ```sh $ wget http://downloads.metabase.com/v0.30.4/metabase.jar ``` ```sh $ java -jar metabase.jar ``` Go to <http://localhost:3000> to configure your Metabase server and point it to the YSQL API endpoint at `localhost:5433`. Detailed steps on how to use Metabase are available in the . For this doc, you will specifically focus on asking questions that require RDBMS capabilities. Filter data using WHERE clauses Join data between tables Perform data aggregation using GROUP BY Use built-in functions such as SUM, MIN, MAX, and so on Click Ask a Question > Custom Query. Choose the database you just set up, and enter the SQL queries noted in the section.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: docker_service.md

+++ title = "docker_service resource" draft = false gh_repo = "inspec" platform = "linux" [menu] [menu.inspec] title = "docker_service" identifier = "inspec/resources/os/dockerservice.md dockerservice resource" parent = "inspec/resources/os" +++ Use the `docker_service` Chef InSpec audit resource to verify a docker swarm service. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.51.0 of InSpec. A `docker_service` resource block declares the service by name: describe docker_service('foo') do it { should exist } its('id') { should eq 'docker-service-id' } its('repo') { should eq 'alpine' } its('tag') { should eq 'latest' } end The resource allows you to pass in a service id: describe docker_service(id: 'docker-service-id') do ... end You can also pass in the fully-qualified image: describe docker_service(image: 'localhost:5000/alpine:latest') do ... end The following examples show how to use Chef InSpec `docker_service` resource. The `id` property returns the service id: its('id') { should eq 'docker-service-id' } The `image` property is a combination of `repository:tag` it tests the value of the image: its('image') { should eq 'alpine:latest' } The `mode` property tests the value of the service mode: its('mode') { should eq 'replicated' } The `name` property tests the value of the service name: its('name') { should eq 'foo' } The `ports` property tests the value of the service's published ports: its('ports') { should include '*:8000->8000/tcp' } The `repo` property tests the value of the repository name: its('repo') { should eq 'alpine' } The `replicas` property tests the value of the service's replica count: its('replicas') { should eq '3/3' } The `tag` property tests the value of image tag: its('tag') { should eq 'latest' } describe docker_service('foo') do it { should exist } its('id') { should eq 'docker-service-id' } its('repo') { should eq 'alpine' } its('tag') { should eq 'latest' } end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The `exist` matcher tests if the image is available on the node: it { should exist }
Project: YugabyteDB (App Definition and Development / Database)
File: ldap-issues.md

title: Troubleshoot LDAP issues headerTitle: linkTitle: LDAP issues description: Troubleshoot LDAP issues menu: stable_yugabyte-platform: identifier: ldap-issues parent: troubleshoot-yp weight: 40 type: docs Laboratory machines sometimes lack an appropriate intermediate certificate in order to trust the LDAP server certificate. You can prepend the environment variable `LDAPTLS_REQCERT=never` to test connectivity with ldapsearch: ```sh LDAPTLS_REQCERT=never ldapsearch -x -H ldaps://ldapserver.example.org -b dc=example,dc=org 'uid=adam' -D "cn=admin,dc=example,dc=org" -w adminpassword ``` There are two cases where explicit intermediate CA configuration is needed: ldapsearch works correctly with `LDAPTLS_REQCERT=never` but fails otherwise. ldapsearch works correctly, but database authentication still fails with a PostgreSQL error message such as "LDAP diagnostics: error:1416F086:SSL routines:tlsprocessserver_certificate:certificate verify failed". In either case, you need to define the intermediate CA in `$HOME/ldaprc` or `$HOME/.ldaprc` for the `yugabyte` user. The following example file `/home/yugabyte/ldaprc` shows the `TLS_CACERT` option pointing to the CA certificate used by the LDAP server. You need to obtain this CA file and place it locally on each client machine. ```output TLS_CACERT /etc/ssl/certs/ca-bundle.trust.crt ``` If the `TLS_CACERT` option is not set in `$HOME/ldaprc`, it will not work in the system-wide OpenLDAP configuration file `/etc/openldap/ldap.conf`.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.49.md

layout: release date: 2024-04-19 tag: v0.7.49 Disable permission check for now @dragon-slayer875 (#10749) Fix wrong key in permission constant file for preferences @Yashsharma1911 (#10748) Thank you to our contributors for making this release possible: @MUzairS15, @Yashsharma1911, @aabidsofi19, @dragon-slayer875, @leecalcote and l5io
Project: YugabyteDB (App Definition and Development / Database)
File: drop_database.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="458" height="50" viewbox="0 0 458 50"><path class="connector" d="M0 22h15m53 0h10m84 0h30m32 0h10m64 0h20m-141 0q5 0 5 5v8q0 5 5 5h116q5 0 5-5v-8q0-5 5-5m5 0h10m115 0h15"/><polygon points="0,29 5,22 0,15" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="5" width="53" height="25" rx="7"/><text class="text" x="25" y="22">DROP</text><rect class="literal" x="78" y="5" width="84" height="25" rx="7"/><text class="text" x="88" y="22">DATABASE</text><rect class="literal" x="192" y="5" width="32" height="25" rx="7"/><text class="text" x="202" y="22">IF</text><rect class="literal" x="234" y="5" width="64" height="25" rx="7"/><text class="text" x="244" y="22">EXISTS</text><a xlink:href="../../../syntaxresources/grammardiagrams#database-name"><rect class="rule" x="328" y="5" width="115" height="25"/><text class="text" x="338" y="22">database_name</text></a><polygon points="454,29 458,29 458,15 454,15" style="fill:black;stroke-width:0"/></svg>
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-system-connection-rename.1.md

% podman-system-connection-rename 1 podman\-system\-connection\-rename - Rename the destination for Podman service podman system connection rename old new Rename ssh destination from old to new. Rename the specified connection: ``` $ podman system connection rename laptop devel ``` , , July 2020, Originally compiled by Jhon Honce (jhonce at redhat dot com)
Project: ArangoDB (App Definition and Development / Database)
File: version.md

+++ title = "Version macros" +++ Overridable: None of the following macros are overridable. Header: `<boost/outcome/config.hpp>` <a name="version-major"></a>`BOOSTOUTCOMEVERSION_MAJOR <number>` Major version for cmake and DLL version stamping. <a name="version-minor"></a>`BOOSTOUTCOMEVERSION_MINOR <number>` Minor version for cmake and DLL version stamping. <a name="version-patch"></a>`BOOSTOUTCOMEVERSION_PATCH <number>` Patch version for cmake and DLL version stamping. <a name="version-revision"></a>`BOOSTOUTCOMEVERSION_REVISION <number>` Revision version for cmake and DLL version stamping. <a name="unstable-version"></a>`BOOSTOUTCOMEUNSTABLE_VERSION <number>` Defined between stable releases of Outcome. It means the inline namespace will be permuted per-commit to ensure ABI uniqueness such that multiple versions of Outcome in a single process space cannot collide. <a name="v2"></a>`BOOSTOUTCOMEV2 <tokens>` The namespace configuration of this Outcome v2. Consists of a sequence of bracketed tokens later fused by the preprocessor into namespace and C++ module names. <a name="v2-namespace"></a>`BOOSTOUTCOMEV2_NAMESPACE <identifier>` The Outcome namespace, which may be permuted per SHA commit. This is not fully qualified. <a name="v2-namespace-begin"></a>`BOOSTOUTCOMEV2NAMESPACEBEGIN <keywords and identifiers>` Expands into the appropriate namespace markup to enter the Outcome v2 namespace. <a name="v2-namespace-export-begin"></a>`BOOSTOUTCOMEV2NAMESPACEEXPORT_BEGIN <keywords and identifiers>` Expands into the appropriate namespace markup to enter the C++ module exported Outcome v2 namespace. <a name="v2-namespace-end"></a>`BOOSTOUTCOMEV2NAMESPACEEND <keywords and identifiers>` Expands into the appropriate namespace markup to exit the Outcome v2 namespace.