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

+++ title = "googlecomputeinstance_group resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputeinstance_group" identifier = "inspec/resources/gcp/googlecomputeinstancegroup.md googlecomputeinstancegroup resource" parent = "inspec/resources/gcp" +++ A `googlecomputeinstance_group` is used to test a Google InstanceGroup resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputeinstance_group(project: 'chef-gcp-inspec', zone: 'zone', name: 'inspec-instance-group') do it { should exist } its('description') { should cmp 'My instance group for testing' } its('named_ports.count') { should cmp 1 } its('named_ports.first.name') { should cmp 'https' } its('named_ports.first.port') { should cmp '8080' } end describe googlecomputeinstance_group(project: 'chef-gcp-inspec', zone: 'zone', name: 'nonexistent') do it { should_not exist } end ``` describe googlecomputeinstance_group(project: 'chef-inspec-gcp', zone: 'europe-west2-a', name: 'gcp-inspec-test') do its('size') { should eq 2 } end describe googlecomputeinstance_group(project: 'chef-inspec-gcp', zone: 'europe-west2-a', name: 'gcp-inspec-test') do its('port_name') { should eq "http" } its('port_value') { should eq 80 } end Properties that can be accessed from the `googlecomputeinstance_group` resource: `creation_timestamp` : Creation timestamp in RFC3339 text format. `description` : An optional description of this resource. Provide this property when you create the resource. `id` : A unique identifier for this instance group. `name` : The name of the instance group. The name must be 1-63 characters long, and comply with RFC1035. `named_ports` : Assigns a name to a port number. For example: {name: "http", port: 80}. This allows the system to reference ports by the assigned name instead of a port number. Named ports can also contain multiple ports. For example: [{name: "http", port: 80},{name: "http", port: 8080}] Named ports apply to all instances in this instance group. `name` : The name for this named port. The name must be 1-63 characters long, and comply with RFC1035. `port` : The port number, which can be a value between 1 and 65535. `network` : The network to which all instances in the instance group belong. `region` : The region where the instance group is located (for regional resources). `subnetwork` : The subnetwork to which all instances in the instance group belong. `zone` : A reference to the zone where the instance group resides. Ensure the is enabled for the current project.
Project: Harbor (Provisioning / Container Registry)
File: 9-30-Project-level-content-trust.md

Test 9-30 Project enable content trust ======= To verify project level content trust works correctly. User guide This test requires one Harbor instance is running and available. A Linux host with Docker CLI installed (Docker client). NOTE: In below test, <harborip> should be replaced by your harbor's ip or FQDN. If you are using a self-signed certificate,make sure to copy the CA root cert into ```/etc/docker/certs.d/<harborip>``` and ```$HOME/.docker/tls/<harbor_ip>:4443/``` project a should be replaced by meaningful and longer name. Login UI and create a project a. Push an image to project a. On Docker client, run ```sh export DOCKERCONTENTTRUST=1 export DOCKERCONTENTTRUSTSERVER=https://<harborip>:4443 ``` and login Harbor. Push an image to project a. In project a configuration page, enabled project level content trust. Pull the image the first time pushed. Pull the image the second time pushed. In step6, the image can not be pulled. In step7, the image can be pulled. None
Project: Harbor (Provisioning / Container Registry)
File: 3-05-LDAP-user-manage-project-publicity.md

Test 3-05 - Manage Project Publicity (LDAP Mode) ======= To verify that a non system admin user can change project publicity of a project in LDAP mode. User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against an LDAP or AD server. ( auth_mode is set to ldap_auth* .) The user data is stored in an LDAP or AD server. A linux host with Docker CLI installed (Docker client). At least three non-admin users are in Harbor. NOTE: In below test, user A, B are non system admin users. User A, B and project X should be replaced by longer and meaningful names. MUST use two kinds of browsers at the same time to ensure independent sessions. For example, use Chrome and Firefox, or Chrome and Safari. DO NOT use the same browser to log in two users at the same time in different windows(tabs). Same as Test 3-02. Same as Test 3-02 None
Project: Chef InSpec (Provisioning / Security & Compliance)
File: azurerm_management_groups.md

+++ title = "azurermmanagementgroups resource" draft = false gh_repo = "inspec" platform = "azure" [menu] [menu.inspec] title = "azurermmanagementgroups" identifier = "inspec/resources/azure/azurermmanagementgroups.md azurermmanagementgroups resource" parent = "inspec/resources/azure" +++ {{< inspec/azurermdeprecated resource="azuremanagement_groups" >}} Use the `azurermmanagementgroups` InSpec audit resource to test properties related to management groups. This resource interacts with version `2018-03-01-preview` of the Azure Management API. For more information see the . At the moment, there doesn't appear to be a way to select the version of the Azure API docs. If you notice a newer version being referenced in the official documentation please open an issue or submit a pull request using the updated version. This resource is available in the `inspec-azure` [resource pack](/inspec/glossary/#resource-pack). To use it, add the following to your `inspec.yml` in your top-level profile: depends: name: inspec-azure git: https://github.com/inspec/inspec-azure.git You'll also need to setup your Azure credentials; see the resource pack . describe azurermmanagementgroups do ... end ```ruby describe azurermmanagementgroups do its('ids') { should include "/providers/Microsoft.Management/managementGroups/mg_id" } its('names') { should include "parent_mg" } its('types') { should include '/providers/Microsoft.Management/managementGroups' } end ``` ```ruby describe azurermmanagementgroups.where(name: 'mg_parent').entries.first do its('properties') { should haveattributes(:tenantId => tenantid, :displayName => parent_dn)} end ``` N/A `ids` `types` `names` `properties` The management group ids. The management group types. The management group names. Additional properties relating to management groups. There are additional attributes that may be accessed that we have not documented. Please take a look at the . Any attribute in the response may be accessed with the key names separated by dots (`.`). The API may not always return keys that do not have any associated data. There may be cases where the deeply nested property may not have the desired attribute along your call chain. If you find yourself writing tests against properties that may be nil, fork this resource pack and add an accessor to the resource. Within that accessor you'll be able to guard against nil keys. Pull requests are always welcome. This InSpec audit resource has no special matchers. For a full list of available matchers, please visit our [Universal Matchers page](/inspec/matchers/). The control will pass if the filter returns at least one result. Use `should_not` if you expect zero matches. describe azurermmanagementgroups(name: 'my-mg') do it { should exist } end Your [Service Principal](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal) must be setup with a `Contributor` or `Management Group Contributor` role on the Tenant Root Group or the specific management group(s) you wish to test.
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_drop_role.md

title: DROP ROLE statement [YCQL] headerTitle: DROP ROLE linkTitle: DROP ROLE description: Use the DROP ROLE statement to delete an existing role. menu: v2.18: parent: api-cassandra weight: 1265 type: docs Use the `DROP ROLE` statement to delete an existing role. This statement is enabled by setting the YB-TServer flag to `true`. <svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="375" height="50" viewbox="0 0 375 50"><path class="connector" d="M0 22h5m53 0h10m52 0h30m32 0h10m64 0h20m-141 0q5 0 5 5v8q0 5 5 5h116q5 0 5-5v-8q0-5 5-5m5 0h10m84 0h5"/><rect class="literal" x="5" y="5" width="53" height="25" rx="7"/><text class="text" x="15" y="22">DROP</text><rect class="literal" x="68" y="5" width="52" height="25" rx="7"/><text class="text" x="78" y="22">ROLE</text><rect class="literal" x="150" y="5" width="32" height="25" rx="7"/><text class="text" x="160" y="22">IF</text><rect class="literal" x="192" y="5" width="64" height="25" rx="7"/><text class="text" x="202" y="22">EXISTS</text><a xlink:href="../grammardiagrams#role-name"><rect class="rule" x="286" y="5" width="84" height="25"/><text class="text" x="296" y="22">rolename</text></a></svg> ```ebnf droprole ::= DROP ROLE [ IF EXISTS ] rolename ``` Where `role_name` is a text identifier. An error is raised if `role_name` does not exist unless IF EXISTS option is present. Only a role with the `SUPERUSER` status can delete another `SUPERUSER` role. Only a client with the permission `DROP` on `ALL ROLES` or on the specified `role_name`, or with the `SUPERUSER` status can delete another role. You can do this as shown below. ```sql ycqlsh:example> DROP ROLE role1; ``` ```sql ycqlsh:example> DROP ROLE IF EXISTS role2; ```
Project: mirrord (App Definition and Development / Application Definition & Image Build)
File: README.md

To run the tests locally with the latest mirrord-agent image, run the following in the mirrord directory: `docker build -t test . --file mirrord/agent/Dockerfile` `minikube image load test` (you might have to specify `-p <PROFILE-NAME>` as well) `cargo test --package tests` The name `test` is hardcoded for the CI, and the tests will fail with an `Elapsed` error if the image named `test` is not found. To use a different image change the environment variable `MIRRORDAGENTIMAGE` at `testserverinit` in `tests/src/utils.rs`. To use the latest release of mirrord-agent, comment out the line adding the `MIRRORDAGENTIMAGE` environment. The Kubernetes resources created by the E2E tests are automatically deleted when the test exits. However, you can preserve resources from failed tests for debugging. To do this, set the `MIRRORDE2EPRESERVE_FAILED` variable to any value. ```bash MIRRORDE2EPRESERVE_FAILED=y cargo test --package tests ``` All test resources share a common label `mirrord-e2e-test-resource=true`. To delete them, simply run: ```bash kubectl delete namespaces,deployments,services -l mirrord-e2e-test-resource=true ```
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-provider-list.md

layout: default title: mesheryctl-system-provider-list permalink: reference/mesheryctl/system/provider/list redirect_from: reference/mesheryctl/system/provider/list/ type: reference display-title: "false" language: en command: system subcommand: provider list available providers List current provider and available providers <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system provider list [flags] </div> </pre> List all available providers <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system provider list </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for list </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -c, --context string (optional) temporarily change the current context. -v, --verbose verbose output -y, --yes (optional) assume yes for user interactive prompts. </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: KICS (Provisioning / Security & Compliance)
File: faa8fddf-c0aa-4b2d-84ff-e993e233ebe9.md

title: S3 Bucket Allows List Action From All Principals hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: faa8fddf-c0aa-4b2d-84ff-e993e233ebe9 Query name: S3 Bucket Allows List Action From All Principals Platform: CloudFormation Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: S3 Buckets must not allow List Action From All Principals, as to prevent leaking private information to the entire internet or allow unauthorized data tampering / deletion. This means the 'Effect' must not be 'Allow' when the 'Action' is List, for all Principals.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="22 7" Resources: SampleBucketPolicy3: Type: 'AWS::S3::BucketPolicy' Properties: Bucket: !Ref DOC-EXAMPLE-BUCKET PolicyDocument: Statement: Action: "ListObject" Effect: Allow Resource: "*" Principal: "*" Condition: StringLike: 'aws:Referer': 'http://www.example.com/*' 'http://example.net/*' SampleBucketPolicy4: Type: 'AWS::S3::BucketPolicy' Properties: Bucket: !Ref DOC-EXAMPLE-BUCKET PolicyDocument: Statement: Action: "ListObject" "GetObject" Effect: Allow Resource: "*" Principal: "*" Condition: StringLike: 'aws:Referer': 'http://www.example.com/*' 'http://example.net/*' ``` ```json title="Positive test num. 2 - json file" hl_lines="9 35" { "Resources": { "SampleBucketPolicy5": { "Type": "AWS::S3::BucketPolicy", "Properties": { "Bucket": { "Ref": "DOC-EXAMPLE-BUCKET" }, "PolicyDocument": { "Statement": [ { "Action": "ListObject", "Effect": "Allow", "Resource": "*", "Principal": "*", "Condition": { "StringLike": { "aws:Referer": [ "http://www.example.com/*", "http://example.net/*" ] } } } ] } } }, "SampleBucketPolicy6": { "Type": "AWS::S3::BucketPolicy", "Properties": { "Bucket": { "Ref": "DOC-EXAMPLE-BUCKET" }, "PolicyDocument": { "Statement": [ { "Action": [ "ListObject", "GetObject" ], "Effect": "Allow", "Resource": "*", "Principal": "*", "Condition": { "StringLike": { "aws:Referer": [ "http://www.example.com/*", "http://example.net/*" ] } } } ] } } } } } ``` ```yaml title="Negative test num. 1 - yaml file" Resources: SampleBucketPolicy1: Type: 'AWS::S3::BucketPolicy' Properties: Bucket: !Ref DOC-EXAMPLE-BUCKET PolicyDocument: Statement: Action: 's3:ListObject' Effect: Deny Resource: '*' Principal: '*' Condition: StringLike: 'aws:Referer': 'http://www.example.com/*' 'http://example.net/*' ``` ```json title="Negative test num. 2 - json file" { "Resources": { "SampleBucketPolicy2": { "Type": "AWS::S3::BucketPolicy", "Properties": { "Bucket": { "Ref": "DOC-EXAMPLE-BUCKET" }, "PolicyDocument": { "Statement": [ { "Action": [ "s3:ListObject" ], "Effect": "Deny", "Resource": "*", "Principal": "*", "Condition": { "StringLike": { "aws:Referer": [ "http://www.example.com/*", "http://example.net/*" ] } } } ] } } } } } ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-derivative-api.md

libpod today is a Golang library and a CLI. The choice of interface you make has advantages and disadvantages. Using the REST API Advantages: Stable, versioned API Language-agnostic API Disadvantages: Error handling is less verbose than Golang API May be slower Running as a subprocess Advantages: Many commands output JSON Works with languages other than Golang Easy to get started Disadvantages: Error handling is harder May be slower Can't hook into or control low-level things like how images are pulled Vendoring into a Go project Advantages: Significant power and control Disadvantages: You are now on the hook for container runtime security updates (partially, `runc`/`crun` are separate) Binary size Potential skew between multiple libpod versions operating on the same storage can cause problems Making the choice A good question to ask first is: Do you want users to be able to use `podman` to manipulate the containers created by your project? If so, that makes it more likely that you want to run `podman` as a subprocess or using the HTTP API. If you want a separate image store and a fundamentally different experience; if what you're doing with containers is quite different from those created by the `podman` CLI, that may drive you towards vendoring.
Project: Polaris (Provisioning / Security & Compliance)
File: admission-controller.md

meta: name: description content: "Fairwinds Polaris | Documentation: Polaris can be run as an admission controller that acts as a validating webhook." Want to manage the Admission Controller across multiple clusters? Check out Polaris can be run as an admission controller that acts as a validating webhook. This accepts the same configuration as the dashboard, and can run the same validations. The webhook will reject any workloads that trigger a danger-level check. This is indicative of the greater goal of Polaris, not just to encourage better configuration through dashboard visibility, but to actually enforce it with this webhook. Note that Polaris will not alter your workloads, only block workloads that don't conform to the configured policies. A valid TLS certificate is required for the Polaris Validating Webhook. If you have cert-manager installed in your cluster then the install methods below will work. If you don't use cert-manager, you'll need to: Supply a CA Bundle with the `webhook.caBundle` Create a TLS secret in your cluster with a valid certificate that uses that CA Pass the name of that secret with the webhook.secretName parameter. ```bash helm repo add fairwinds-stable https://charts.fairwinds.com/stable helm upgrade --install polaris fairwinds-stable/polaris --namespace polaris --create-namespace \ --set webhook.enable=true --set dashboard.enable=false ``` The webhook comes with built-in support for a handful of known controller types, such as Deployments, Jobs, and DaemonSets. To add new controller types, you can set `webhook.rules` in the Unfortunately we have not found a way to display warnings as part of `kubectl` output unless we are rejecting a workload altogether. This means that any checks with a severity of `warning` will still pass webhook validation, and the only evidence of that warning will either be in the Polaris dashboard or the Polaris webhook logs. This will change in a future version of Kubernetes. By default, the Admission Controller is just pass/fail, but Polaris can also operate as a mutating webhook for many of the issues it checks for. This means Polaris will remediate the issue it finds, rather than rejecting the deployment. To enable the mutating webhook, add `--set webhook.mutate=true` to your Helm installation command. The following default checks currently have mutation support enabled: `hostPIDSet` `hostNetworkSet` `hostIPCSet` `priorityClassNotSet` `hostPortSet` `pullPolicyNotAlways` `deploymentMissingReplicas` `dangerousCapabilities` `cpuLimitsMissing` `memoryLimitsMissing` `livenessProbeMissing` `memoryRequestsMissing` `cpuRequestsMissing` `runAsPrivileged` `readinessProbeMissing` `privilegeEscalationAllowed` `notReadOnlyRootFilesystem` `insecureCapabilities` `runAsRootAllowed` If you'd like to enable other mutations, you can set the `webhook.mutations` flag.
Project: Vitess (App Definition and Development / Database)
File: CONTRIBUTING.md

For all contributors, we recommend the standard based on . For significant changes, please to let everyone know what you're planning to work on, and to track progress and design decisions. Please read where we provide more information: How to make yourself familiar with Go and Vitess. How to go through the GitHub workflow. What to look for during code reviews. At this time, we will not be accepting contributions that only fix spelling, naming or grammatical errors in documentation, code, comments or elsewhere, from accounts created in the last 365 days. We appreciate your interest in contributing to Vitess, and we encourage you to contribute in other ways.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: max.md

title: "Max" <!-- 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. --> {{< localstorage language language-py >}} {{< button-pydoc path="apache_beam.transforms.core" class="CombineGlobally" >}} Gets the element with the maximum value within each aggregation. In the following example, we create a pipeline with a `PCollection`. Then, we get the element with the maximum value in different ways. We use `Combine.Globally()` to get the maximum element from the entire `PCollection`. {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHONMaxGlobally" show="maxglobally" >}} {{< /playground >}} We use `Combine.PerKey()` to get the maximum element for each unique key in a `PCollection` of key-values. {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHONMaxPerKey" show="maxper_key" >}} {{< /playground >}} {{< button-pydoc path="apache_beam.transforms.core" class="CombineGlobally" >}}
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.19.md

layout: release date: 2024-02-14 tag: v0.7.19 [Server] Fix connection `status` getting overriden during import of K8s connection. @MUzairS15 (#10303) Ripul handoo/relationships/pod template @RipulHandoo (#10271) add: Relationship between Replication Controller and other k8s resources @RipulHandoo (#10274) add: relationship between k8s lease and other k8s components[high-level] @RipulHandoo (#10244) run component updater @MUzairS15 (#10286) feat: Relationship between HPA and other k8s components. @RipulHandoo (#10126) add: Relationship between csi-driver and other k8s resources @RipulHandoo (#10262) feat: relationship between kubernetes secret and other resources @RipulHandoo (#9880) fix conflicts @MUzairS15 (#10285) Feature/exp components command @RipulHandoo (#9726) [Meshmodel] Update Components @aabidsofi19 (#10277) [fix] remove xstate/inspect @aabidsofi19 (#10302) fix hover of hyperlink @sudhanshutech (#10288) [Meshmodel] Update Components @aabidsofi19 (#10277) Fix the React Warnings in Meshery UI Build @MeenuyD (#10266) Testing small change @sudhanshutech (#10265) Bump github.com/onsi/ginkgo/v2 from 2.13.1 to 2.15.0 @dependabot (#10148) [Docs] Relationships and Policies @MUzairS15 (#10253) Fixed text color in swagger layout @iArchitSharma (#10279) error table liquid fix @iArchitSharma (#10283) Reference added to error table @iArchitSharma (#10281) [Docs] Remove deprecated adapters from toc sidebar @leecalcote (#10257) [Docs] Enhance enhanced layout with optional suggested-reading list @leecalcote (#10256) Fix missing list @iArchitSharma (#10260) Thank you to our contributors for making this release possible: @MUzairS15, @MeenuyD, @RipulHandoo, @aabidsofi19, @dependabot, @iArchitSharma, @l5io, @leecalcote, @sudhanshutech, @theBeginner86 and l5io
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.15.3.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | globPaths does not support {ab,cd} as it claims to | Blocker | fs | Hairong Kuang | Hairong Kuang | | | Empty blocks make fsck report corrupt, even when it isn't | Blocker | . | Allen Wittenauer | dhruba borthakur | | | streaming jobs fail after HADOOP-2227 | Blocker | . | Lohit Vijayarenu | Amareshwari Sriramadasu | | | bugs in mapred tutorial | Major | documentation | Doug Cutting | Arun C Murthy | | | bin/hadoop dfs -lsr / is broken | Minor | . | Mahadev konar | Mahadev konar |