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

+++ title = "googleloggingproject_exclusion resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleloggingproject_exclusion" identifier = "inspec/resources/gcp/googleloggingprojectexclusion.md googleloggingprojectexclusion resource" parent = "inspec/resources/gcp" +++ A `googleloggingproject_exclusion` is used to test a Google ProjectExclusion resource ```ruby describe googleloggingproject_exclusion(project: 'chef-gcp-inspec', name: 'inspec-project-exclusion') do it { should exist } its('description'){ should cmp 'My project exclusion description' } its('filter'){ should cmp 'resource.type = gce_instance AND severity <= DEBUG' } end describe googleloggingproject_exclusion(project: 'chef-gcp-inspec', name: 'nonexistent') do it { should_not exist } end ``` describe googleloggingproject_exclusion(project: 'chef-inspec-gcp', exclusion: 'exclusion-name-abcd') do its('name') { should eq 'exclusion-name-abcd' } end describe googleloggingproject_exclusion(project: 'chef-inspec-gcp', exclusion: 'exclusion-name-abcd') do its('filter') { should eq 'resource.type = gce_instance AND severity <= DEBUG' } end describe googleloggingproject_exclusion(project: 'chef-inspec-gcp', exclusion: 'exclusion-name-abcd') do its('description') { should eq 'Exclude GCE instance debug logs' } end Properties that can be accessed from the `googleloggingproject_exclusion` resource: `project` : Id of the project that this exclusion applies to. `name` : Name of the exclusion, specified by the server during create. `description` : A user provided description of this exclusion. `filter` : An advanced logs filter. The only exported log entries are those that are in the resource owning the sink and that match the filter. `disabled` : If set to true then this exclusion is disabled and it does not exclude any log entries. Ensure the is enabled for the current project.
Project: YDB (App Definition and Development / Database)
File: grafana-dashboards.md

This page describes Grafana dashboards for {{ ydb-short-name }}. For information about how to install dashboards, see . General database dashboard. CPU utilization in an actor system. | Name | Description | ||| | CPU by execution pool (us) | CPU utilization in different execution pools across all nodes, microseconds per second (one million indicates utilization of a single core) | | Actor count | Number of actors (by actor type) | | CPU | CPU utilization in different execution pools (by actor type) | | Events | Actor system event handling metrics | gRPC layer metrics. | Name | Description | ||| | Requests | Number of requests received by a database per second (by gRPC method type) | | Request bytes | Size of database requests, bytes per second (by gRPC method type) | | Response bytes | Size of database responses, bytes per second (by gRPC method type) | | Dropped requests | Number of requests per second with processing terminated at the transport layer due to an error (by gRPC method type) | | Dropped responses | Number of responses per second with sending terminated at the transport layer due to an error (by gRPC method type) | | Requests in flight | Number of requests that a database is simultaneously handling (by gRPC method type) | | Request bytes in flight | Size of requests that a database is simultaneously handling (by gRPC method type) | Information about the query engine. | Name | Description | ||| | Requests | Number of incoming requests per second (by request type) | | Request bytes | Size of incoming requests, bytes per second (query, parameters, total) | | Responses | Number of responses per second (by response type) | | Response bytes | Response size, bytes per second (total, query result) | | Sessions | Information about running sessions | | Latencies | Request execution time histograms for different types of requests | Information about transactions from the DataShard transaction proxy layer. | Name | Description | ||| | Transactions | Datashard transaction metrics | | Latencies | Execution time histograms for different stages of datashard transactions | DataShard tablet metrics. | Name | Description | ||| | Operations | Datashard operation statistics for different types of operations | | Transactions | Information about datashard tablet transactions (by transaction type) | | Latencies | Execution time histograms for different stages of custom transactions | | Tablet latencies | Tablet transaction execution time histograms | | Compactions | Information about LSM compaction operations performed | | ReadSets | Information about ReadSets that are sent when executing a customer transaction | | Other | Other metrics |
Project: ArangoDB (App Definition and Development / Database)
File: in_place_type_t.md

+++ title = "`inplacetype_t<T>`" description = "Either `std::inplacetypet<T>` or a local emulation, depending on the `BOOSTOUTCOMEUSESTDINPLACE_TYPE` macro." +++ Either `std::inplacetype_t<T>` or a local emulation, depending on the {{% api "BOOSTOUTCOMEUSESTDINPLACETYPE" %}} macro. Note that the templated variable `inplacetype` is also aliased or emulated locally. Requires: Nothing. Namespace: `BOOSTOUTCOMEV2_NAMESPACE` Header: `<boost/outcome/config.hpp>`
Project: secureCodeBox (Provisioning / Security & Compliance)
File: adr_0015.md

title: "ADR-0015: Kubernetes As Orchestration Engine for Scans" sidebar_label: "ADR-0015" | <!-- --> | <!-- --> | | -- | | | Status: | ACCEPTED | | Date: | 2022-09-13 | | Author(s): | Jannik Hollenbach , Sven Strittmatter | :::info This ADR should have been written prior to implementation. But we started documenting ADR later. This ADR has therefore been written retrospectively to record the decision made at that time. ::: secureCodeBox is merely an orchestration of various security scanners. is a platform to orchestrate resources. In first place designed to orchestrate data center resources, but extended its capabilities to define . This opens the possibility to define own resource types which will be orchestrated. Since we run all the integrated security scanners in containers anyway a secureCodeBox scanner is merely a image with a CLI scanner tool installed it seems to be a perfect match to define these scanners as custom resources and let Kubernetes orchestrate them, instead of implementing this orchestration (with all the consequences) by our own. We decided to use as underlying orchestration platform to manage the scan processes. secureCodeBox is hard coupled to and therefore can't be run w/o a cluster. We need to implement an own with our business logic. Therefore, we need to learn [Go]. We loose the web UI from version 1 and users need to use `kubectl` on command line to interact with secureCodeBox. No backward compatibility to version 1 installations, nor an easy upgrade path.
Project: KICS (Provisioning / Security & Compliance)
File: a659f3b5-9bf0-438a-bd9a-7d3a6427f1e3.md

title: Readiness Probe Is Not Configured hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: a659f3b5-9bf0-438a-bd9a-7d3a6427f1e3 Query name: Readiness Probe Is Not Configured Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Availability URL: Check if Readiness Probe is not configured.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="9" apiVersion: v1 kind: Pod metadata: name: goproxy labels: app: goproxy spec: containers: name: goproxy image: k8s.gcr.io/goproxy:0.1 ports: containerPort: 8080 livenessProbe: tcpSocket: port: 8080 initialDelaySeconds: 15 periodSeconds: 20 ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: goproxy labels: app: goproxy spec: containers: name: goproxy image: k8s.gcr.io/goproxy:0.1 ports: containerPort: 8080 readinessProbe: tcpSocket: port: 8080 initialDelaySeconds: 5 periodSeconds: 10 livenessProbe: tcpSocket: port: 8080 initialDelaySeconds: 15 periodSeconds: 20 ```
Project: KICS (Provisioning / Security & Compliance)
File: 7782d4b3-e23e-432b-9742-d9528432e771.md

title: Group With Privilege Escalation By Actions 'iam:SetDefaultPolicyVersion' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 7782d4b3-e23e-432b-9742-d9528432e771 Query name: Group With Privilege Escalation By Actions 'iam:SetDefaultPolicyVersion' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Group with privilege escalation by actions 'iam:SetDefaultPolicyVersion' and Resource set to '*'. For more information see https://rhinosecuritylabs.com/aws/aws-privilege-escalation-methods-mitigation/.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsiamgroup" "cosmic" { name = "cosmic" } resource "awsiamgrouppolicy" "testinline_policy" { name = "testinlinepolicy" group = awsiamgroup.cosmic.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "iam:SetDefaultPolicyVersion", ] Effect = "Allow" Resource = "*" }, ] }) } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamuser" "cosmic2" { name = "cosmic2" } resource "awsiamuserpolicy" "inlinepolicyruninstances2" { name = "inlinepolicyrun_instances" user = awsiamuser.cosmic2.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "ec2:Describe*", ] Effect = "Allow" Resource = "*" }, ] }) } ```
Project: Harbor (Provisioning / Container Registry)
File: 6-04-OVA-increase-volume.md

Test 6-04 - OVA Increase Volume Space ======= To verify that an OVA version of Harbor can be upgraded the volume to larger space. User guide, installation guide of Harbor OVA version. A running version of Harbor OVA version. A vCenter, at least an ESX host. A linux host with Docker CLI installed (Docker client). To-Do: Test attached 1 disk Test attached 2nd disk test attached 3rd disk reboot or not reboot? TBD None
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: feat-12326.en.md

Add session registration history. Setting config `broker.sessionhistoryretain` allows EMQX to keep track of expired sessions for the retained period. API `GET /api/v5/sessions_count?since=1705682238` can be called to count the cluster-wide sessions which were alive (unexpired) since the provided timestamp (UNIX epoch at seconds precision). A new gauge `cluster_sessions` is added to the metrics collection. Exposed to prometheus as ``` emqxclustersessions_count 1234 ``` NOTE: The counter can only be used for an approximate estimation as the collection and calculations are async.
Project: ClickHouse (App Definition and Development / Database)
File: processes.md

slug: /en/operations/system-tables/processes This system table is used for implementing the `SHOW PROCESSLIST` query. Columns: `user` (String) The user who made the query. Keep in mind that for distributed processing, queries are sent to remote servers under the `default` user. The field contains the username for a specific query, not for a query that this query initiated. `address` (String) The IP address the request was made from. The same for distributed processing. To track where a distributed query was originally made from, look at `system.processes` on the query requestor server. `elapsed` (Float64) The time in seconds since request execution started. `read_rows` (UInt64) The number of rows read from the table. For distributed processing, on the requestor server, this is the total for all remote servers. `read_bytes` (UInt64) The number of uncompressed bytes read from the table. For distributed processing, on the requestor server, this is the total for all remote servers. `totalrowsapprox` (UInt64) The approximation of the total number of rows that should be read. For distributed processing, on the requestor server, this is the total for all remote servers. It can be updated during request processing, when new sources to process become known. `memory_usage` (Int64) Amount of RAM the request uses. It might not include some types of dedicated memory. See the setting. `query` (String) The query text. For `INSERT`, it does not include the data to insert. `query_id` (String) Query ID, if defined. `is_cancelled` (UInt8) Was query cancelled. `isalldata_sent` (UInt8) Was all data sent to the client (in other words query had been finished on the server). ```sql SELECT * FROM system.processes LIMIT 10 FORMAT Vertical; ``` ```response Row 1: isinitialquery: 1 user: default query_id: 35a360fa-3743-441d-8e1f-228c938268da address: ::ffff:172.23.0.1 port: 47588 initial_user: default initialqueryid: 35a360fa-3743-441d-8e1f-228c938268da initial_address: ::ffff:172.23.0.1 initial_port: 47588 interface: 1 os_user: bharatnc client_hostname: tower client_name: ClickHouse client_revision: 54437 clientversionmajor: 20 clientversionminor: 7 clientversionpatch: 2 http_method: 0 httpuseragent: quota_key: elapsed: 0.000582537 is_cancelled: 0 isalldata_sent: 0 read_rows: 0 read_bytes: 0 totalrowsapprox: 0 written_rows: 0 written_bytes: 0 memory_usage: 0 peakmemoryusage: 0 query: SELECT * from system.processes LIMIT 10 FORMAT Vertical; thread_ids: [67] ProfileEvents: {'Query':1,'SelectQuery':1,'ReadCompressedBytes':36,'CompressedReadBufferBlocks':1,'CompressedReadBufferBytes':10,'IOBufferAllocs':1,'IOBufferAllocBytes':89,'ContextLock':15,'RWLockAcquiredReadLocks':1} Settings: {'backgroundpoolsize':'32','loadbalancing':'random','allowsuspiciouslowcardinalitytypes':'1','distributedaggregationmemoryefficient':'1','skipunavailableshards':'1','logqueries':'1','maxbytesbeforeexternalgroupby':'20000000000','maxbytesbeforeexternalsort':'20000000000','allowintrospectionfunctions':'1'} 1 rows in set. Elapsed: 0.002 sec. ```
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: operator-sdk_alpha.md

title: "operator-sdk alpha" Alpha-stage subcommands Alpha subcommands are for unstable features. Alpha subcommands are exploratory and may be removed without warning. No backwards compatibility is provided for any alpha subcommands. ``` -h, --help help for alpha ``` ``` --plugins strings plugin keys to be used for this subcommand execution --verbose Enable verbose logging ``` - - Convert your PROJECT config file from version 3-alpha to 3 - Re-scaffold an existing Kuberbuilder project
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.1.1.md

modify defaulthandlerfrom base => pre protocol by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/248 remove pipeline building for OPC UA mockdevice on linux/armv7 by @tomqin93 in https://github.com/Edgenesis/shifu/pull/250 fix mockdeviceName by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/252 revert ClusterRoleBinding and add docs by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/253 imeplement test and add into pipeline by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/244 add golangci-lint and github action by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/241 Update golangci-lint.yml by @tomqin93 in https://github.com/Edgenesis/shifu/pull/246 Update Azure Pipelines to split push into multiple jobs by @tomqin93 in https://github.com/Edgenesis/shifu/pull/247 add_telemetry by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/249 modify log => klog by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/251 Bump k8s.io/client-go from 0.25.0 to 0.25.1 by @dependabot in https://github.com/Edgenesis/shifu/pull/258 Bump k8s.io/klog/v2 from 2.70.1 to 2.80.1 by @dependabot in https://github.com/Edgenesis/shifu/pull/257 Fix shifu docs by @BtXin in https://github.com/Edgenesis/shifu/pull/243 update links in readme because shifu.run use en as default lang by @Yang-Xijie in https://github.com/Edgenesis/shifu/pull/242 docs: add badges just for fun by @yufeiminds in https://github.com/Edgenesis/shifu/pull/245 featTypo modification by @geffzhang in https://github.com/Edgenesis/shifu/pull/259 @yufeiminds made their first contribution in https://github.com/Edgenesis/shifu/pull/245 @geffzhang made their first contribution in https://github.com/Edgenesis/shifu/pull/259 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.1.0...v0.1.1
Project: external-secrets (Provisioning / Security & Compliance)
File: fortanix.md

Populate kubernetes secrets from OPAQUE or SECRET security objects in Fortanix. SDKMS ```yaml apiVersion: external-secrets.io/v1beta1 kind: SecretStore metadata: name: secret-store spec: provider: fortanix: apiUrl: <HOSTOFSDKMS_API> apiKey: secretRef: name: <NAMEOFKUBE_SECRET> key: <KEYINKUBE_SECRET> ``` ```yaml apiVersion: external-secrets.io/v1beta1 kind: ExternalSecret metadata: name: secret spec: refreshInterval: 1h secretStoreRef: kind: SecretStore name: secret-store data: secretKey: <KEYINKUBE_SECRET> remoteRef: key: <SDKMSSECURITYOBJECT_NAME> apiVersion: external-secrets.io/v1beta1 kind: ExternalSecret metadata: name: secret-from-property spec: refreshInterval: 1h secretStoreRef: kind: SecretStore name: secret-store data: secretKey: <KEYINKUBE_SECRET> remoteRef: key: <SDKMSSECURITYOBJECT_NAME> property: <SECURITYOBJECTVALUEINNERPROPERTY> apiVersion: external-secrets.io/v1beta1 kind: ExternalSecret metadata: name: secret-from-extract spec: refreshInterval: 1h secretStoreRef: kind: SecretStore name: secret-store dataFrom: extract: key: <SDKMSSECURITYOBJECT_NAME> ```
Project: ThreatMapper (Provisioning / Security & Compliance)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: "" labels: enhancement, needs-triage assignees: '' Additional context Add any other context about the problem here. Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] 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 features you've considered. Components/Services [ ] UI/Frontend [ ] API/Backend [ ] Agent [ ] Deployment/YAMLs [ ] CI/CD Integration [ ] Other (specify) Additional context Add any other context or screenshots about the feature request here.
Project: Meshery (Provisioning / Automation & Configuration)
File: flagger.md

layout: integration title: Flagger subtitle: Collaborative and visual infrastructure as code for Flagger image: /assets/img/integrations/flagger/icons/color/flagger-color.svg permalink: extensibility/integrations/flagger docURL: https://docs.meshery.io/extensibility/integrations/flagger description: integrations-category: App Definition and Development integrations-subcategory: Continuous Integration & Delivery registrant: Artifact Hub components: name: canary colorIcon: assets/img/integrations/flagger/components/canary/icons/color/canary-color.svg whiteIcon: assets/img/integrations/flagger/components/canary/icons/white/canary-white.svg description: name: metric-template colorIcon: assets/img/integrations/flagger/components/metric-template/icons/color/metric-template-color.svg whiteIcon: assets/img/integrations/flagger/components/metric-template/icons/white/metric-template-white.svg description: name: alert-provider colorIcon: assets/img/integrations/flagger/components/alert-provider/icons/color/alert-provider-color.svg whiteIcon: assets/img/integrations/flagger/components/alert-provider/icons/white/alert-provider-white.svg description: featureList: [ "Canary (progressive traffic shifting), A/B Testing (HTTP headers and cookies traffic routing), Blue/Green (traffic switching and mirroring)", "Flagger was designed to give developers confidence in automating production releases with progressive delivery techniques.", "Reduce the risk of introducing a new software version in production by gradually shifting traffic to the new version while measuring metrics like HTTP/gRPC request success rate and latency." ] 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: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: operator-sdk_completion_zsh.md

title: "operator-sdk completion zsh" Load zsh completions ``` operator-sdk completion zsh [flags] ``` ``` $ echo "autoload -U compinit; compinit" >> ~/.zshrc $ operator-sdk completion zsh > "${fpath[1]}/_operator-sdk" ``` ``` -h, --help help for zsh ``` ``` --plugins strings plugin keys to be used for this subcommand execution --verbose Enable verbose logging ``` - Load completions for the specified shell
Project: external-secrets (Provisioning / Security & Compliance)
File: secretstore.md

The `SecretStore` is namespaced and specifies how to access the external API. The SecretStore maps to exactly one instance of an external API. By design, SecretStores are bound to a namespace and can not reference resources across namespaces. If you want to design cross-namespace SecretStores you must use which do not have this limitation. For a full list of supported fields see or dig into our . ``` yaml {% include 'full-secret-store.yaml' %} ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: accenture.md

title: "Accenture" icon: /images/logos/powered-by/accenture.png hasLink: "https://www.accenture.com/us-en/services/ai-artificial-intelligence-index" <!-- Licensed 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. -->
Project: external-secrets (Provisioning / Security & Compliance)
File: scaleway.md

External Secrets Operator integrates with . You need an api key (access key + secret key) to authenticate with the secret manager. Both access and secret keys can be specified either directly in the config, or by referencing a kubernetes secret. ```yaml apiVersion: external-secrets.io/v1beta1 kind: SecretStore metadata: name: secret-store spec: provider: scaleway: region: <REGION> projectId: <PROJECT_UUID> accessKey: value: <ACCESS_KEY> secretKey: secretRef: name: <NAMEOFKUBE_SECRET> key: <KEYINKUBE_SECRET> ``` Secrets can be referenced by name, id or path, using the prefixes `"name:"`, `"id:"` and `"path:"` respectively. A PushSecret resource can only use a name reference. ```yaml apiVersion: external-secrets.io/v1beta1 kind: ExternalSecret metadata: name: secret spec: refreshInterval: 20s secretStoreRef: kind: SecretStore name: secret-store data: secretKey: <KEYINKUBE_SECRET> remoteRef: key: id:<SECRET_UUID> version: latest_enabled ```