cwielenb/CNCF-Dataset huggingface dataset:
Project: FOSSA (Provisioning / Security & Compliance)
File: nuspec.md

A `.nuspec` file is an XML manifest that contains package metadata for Nuget packages. This manifest is used both to build the package and to provide information to consumers. Walk the directory and find all files with a `.nuspec` suffix Depending on the version of Nuget in use, dependencies can be specified in two ways TODO: do we ONLY look at dependency groups???? The <dependencies> element within <metadata> contains any number of <dependency> elements that identify other packages upon which the top-level package depends. Example: ``` <?xml version="1.0"?> <package > <metadata> <id>GenericServices</id> <version>1.0.10</version> <title>GenericServices</title> <authors>Jon Smith</authors> <owners>Jon Smith</owners> <dependencies> <dependency id="GenericLibsBase" version="1.0.1" /> <dependency id="EntityFramework" version="6.1.3" /> <dependency id="AutoMapper" version="4.2.1" /> <dependency id="DelegateDecompiler.EntityFramework" version="0.18" /> </dependencies> </metadata> </package> ``` As an alternative to a single flat list, dependencies can be specified according to the framework profile of the target project using <group> elements within <dependencies>. ``` <?xml version="1.0"?> <package > <metadata> <id>GenericServices</id> <version>1.0.10</version> <title>GenericServices</title> <authors>Jon Smith</authors> <owners>Jon Smith</owners> <dependencies> <group> <dependency id="RouteMagic" version="1.1.0" /> </group> <group targetFramework=".NETFramework4.7.2"> <dependency id="jQuery" version="1.6.2" /> <dependency id="WebActivator" version="1.4.4" /> </group> </dependencies> </metadata> </package> ```
Project: KICS (Provisioning / Security & Compliance)
File: 0e5872b4-19a0-4165-8b2f-56d9e14b909f.md

title: IAM Managed Policy Applied to a User hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 0e5872b4-19a0-4165-8b2f-56d9e14b909f Query name: IAM Managed Policy Applied to a User Platform: CloudFormation Severity: <span style="color:#ff7213">Medium</span> Category: Best Practices URL: Make sure that any managed IAM policies are implemented in a group and not in a user.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="10" Resources: CreateTestDBPolicy: Type: 'AWS::IAM::ManagedPolicy' Properties: Description: Policy for creating a test database Path: / PolicyDocument: Version: 2012-10-17 Statement: [] Users: TestUser ``` ```json title="Positive test num. 2 - json file" hl_lines="11" { "Resources": { "CreateTestDBPolicy": { "Type": "AWS::IAM::ManagedPolicy", "Properties": { "Path": "/", "PolicyDocument": { "Statement": [], "Version": "2012-10-17T00:00:00Z" }, "Users": [ "TestUser" ], "Description": "Policy for creating a test database" } } } } ``` ```yaml title="Negative test num. 1 - yaml file" Resources: CreateTestDBPolicy: Type: 'AWS::IAM::ManagedPolicy' Properties: Description: Policy for creating a test database Path: / PolicyDocument: Version: 2012-10-17 Statement: [] Groups: TestGroup ``` ```json title="Negative test num. 2 - json file" { "Resources": { "CreateTestDBPolicy": { "Type": "AWS::IAM::ManagedPolicy", "Properties": { "Path": "/", "PolicyDocument": { "Statement": [], "Version": "2012-10-17T00:00:00Z" }, "Groups": [ "TestGroup" ], "Description": "Policy for creating a test database" } } } } ```
Project: KICS (Provisioning / Security & Compliance)
File: 9e8c89b3-7997-4d15-93e4-7911b9db99fd.md

title: Inline Policies Are Attached To ECS Service hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 9e8c89b3-7997-4d15-93e4-7911b9db99fd Query name: Inline Policies Are Attached To ECS Service Platform: CloudFormation Severity: <span style="color:#edd57e">Low</span> Category: Insecure Configurations URL: Check if any ECS service has inline policies attached, which are embedded directly into an entity (user, group,...), instead of the equivalent recommended managed policies.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="7" Resources: InlinePolicy: Type: AWS::ECS::Service DependsOn: Listener Properties: Role: Ref: IAMPolicy LoadBalancers: TargetGroupArn: Ref: TargetGroup ContainerPort: 80 ContainerName: sample-app Cluster: Ref: ECSCluster IAMPolicy: Type: 'AWS::IAM::Policy' Properties: PolicyName: root PolicyDocument: Version: 2012-10-17 Statement: Effect: Allow Action: '*' Resource: '*' ``` ```json title="Positive test num. 2 - json file" hl_lines="9" { "Resources": { "InlinePolicy": { "Type": "AWS::ECS::Service", "DependsOn": [ "Listener" ], "Properties": { "Role": { "Ref": "IAMPolicy" }, "LoadBalancers": [ { "TargetGroupArn": { "Ref": "TargetGroup" }, "ContainerPort": 80, "ContainerName": "sample-app" } ], "Cluster": { "Ref": "ECSCluster" } } }, "IAMPolicy": { "Type": "AWS::IAM::Policy", "Properties": { "PolicyName": "root", "PolicyDocument": { "Version": "2012-10-17T00:00:00Z", "Statement": [ { "Effect": "Allow", "Action": "*", "Resource": "*" } ] } } } } } ``` ```yaml title="Negative test num. 1 - yaml file" Resources: InlinePolicy: Type: AWS::ECS::Service DependsOn: Listener Properties: LoadBalancers: TargetGroupArn: Ref: TargetGroup ContainerPort: 80 ContainerName: sample-app Cluster: Ref: ECSCluster IAMPolicy: Type: 'AWS::IAM::Policy' Properties: PolicyName: root PolicyDocument: Version: 2012-10-17 Statement: Effect: Allow Action: '*' Resource: '*' ``` ```json title="Negative test num. 2 - json file" { "Resources": { "IAMPolicy": { "Properties": { "PolicyName": "root", "PolicyDocument": { "Version": "2012-10-17T00:00:00Z", "Statement": [ { "Effect": "Allow", "Action": "*", "Resource": "*" } ] } }, "Type": "AWS::IAM::Policy" }, "InlinePolicy": { "DependsOn": [ "Listener" ], "Properties": { "LoadBalancers": [ { "TargetGroupArn": { "Ref": "TargetGroup" }, "ContainerPort": 80, "ContainerName": "sample-app" } ], "Cluster": { "Ref": "ECSCluster" } }, "Type": "AWS::ECS::Service" } } } ```
Project: KubeDB by AppsCode (App Definition and Development / Database)
File: kubectl-dba_version.md

title: Kubectl-Dba Version menu: docs_{{ .version }}: identifier: kubectl-dba-version name: Kubectl-Dba Version parent: reference-cli menuname: docs{{ .version }} sectionmenuid: reference Prints binary version number. ``` kubectl-dba version [flags] ``` ``` --check string Check version constraint -h, --help help for version --short Print just the version number. ``` ``` --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 ``` - kubectl plugin for KubeDB
Project: KICS (Provisioning / Security & Compliance)
File: d5d1fe08-89db-440c-8725-b93223387309.md

title: Serverless API Without Content Encoding hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: d5d1fe08-89db-440c-8725-b93223387309 Query name: Serverless API Without Content Encoding Platform: ServerlessFW Severity: <span style="color:#edd57e">Low</span> Category: Encryption URL: Serverless should have API Gateway with Content Encoding enabled through the attribute 'minimumCompressionSize'. This value should be greater than -1 and smaller than 10485760<br> ```yml title="Positive test num. 1 - yml file" hl_lines="5" service: my-service frameworkVersion: '2' provider: name: aws apiGateway: ``` ```yml title="Positive test num. 2 - yml file" hl_lines="6" service: my-service frameworkVersion: '2' provider: name: aws apiGateway: minimumCompressionSize: 10485760 ``` ```yml title="Negative test num. 1 - yml file" service: my-service frameworkVersion: '2' provider: name: aws apiGateway: minimumCompressionSize: 1024 ```
Project: YugabyteDB (App Definition and Development / Database)
File: dcl_reassign_owned.md

title: REASSIGN OWNED statement [YSQL] headerTitle: REASSIGN OWNED linkTitle: REASSIGN OWNED description: Use the REASSIGN OWNED statement to change the ownership of database objects owned by any of the "oldroles" to "newrole". menu: v2.18: identifier: dclreassignowned parent: statements type: docs Use the `REASSIGN OWNED` statement to change the ownership of database objects owned by any of the `oldroles` to `newrole`. {{%ebnf%}} reassign_owned, role_specification {{%/ebnf%}} `REASSIGN OWNED` is typically used to prepare for the removal of a role. It requires membership on both the source roles and target role. Reassign all objects owned by john to yugabyte. ```plpgsql yugabyte=# reassign owned by john to yugabyte; ```
Project: JReleaser (App Definition and Development / Application Definition & Image Build)
File: PULL_REQUEST_TEMPLATE.md

<!-- The issue this PR addresses --> <!-- Please reference the issue this PR solves --> Fixes #? <!-- What problem does this change address? --> <!-- Link to relevant issues or discussions here --> . [ ] Make sure all contributed code can be distributed under the terms of the , e.g. the code was written by you or the original code is licensed under . when applicable.
Project: BOSH (Provisioning / Automation & Configuration)
File: director-console-debugging.md

For director version <= 265.x ```bash sudo su /var/vcap/jobs/director/bin/director_ctl console ``` For director version >= 266.x ```bash sudo su /var/vcap/jobs/director/bin/console ``` ```ruby Bosh::Director::Config.db.foreignkeylist(:instances) ``` ```ruby Bosh::Director::Config.db[:instances].where(variablesetid: nil).first ``` ```ruby Bosh::Director::Config.db[:schema_migrations].where(filename: "xxx").first ``` ```ruby Bosh::Director::Config.db[:schema_migrations].order(:filename).last ``` ```ruby Bosh::Director::Config.db[:schema_migrations] << {filename: "xxx"} ``` ```ruby Bosh::Director::Models::Instance.first.update(boostrap: false) ``` ```ruby Bosh::Director::Models::PersistentDisk.where(disk_cid: "...").all Bosh::Director::Models::PersistentDisk.where(disk_cid: "...").delete ``` ```ruby File.open("/tmp/my-temp-blob-file", 'wb') { |file| Bosh::Director::App.instance.blobstores.blobstore.get("some-blobstore-id", file) } ```
Project: ClickHouse (App Definition and Development / Database)
File: v21.8.15.7-lts.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fix usage of functions `array` and `tuple` with literal arguments in distributed queries. Previously it could lead to `Not found columns` exception. (). Backported in : Fix segfault while parsing ORC file with corrupted footer. Closes . ().
Project: Tinkerbell (Provisioning / Automation & Configuration)
File: DCO.md

All authors to the project retain copyright to their work. However, to ensure that they are only submitting work that they have rights to, we are requiring everyone to acknowledge this by signing their work. Since this signature indicates your rights to the contribution and certifies the statements below, it must contain your real name and email address. Various forms of noreply email address must not be used. Any copyright notices in this repository should specify the authors as "The project authors". To sign your work, just add a line like this at the end of your commit message: ```text Signed-off-by: Jess Owens <jowens@tinkerbell.org> ``` This can easily be done with the `--signoff` option to `git commit`. By doing this you state that you can certify the following (from ): ```text Developer Certificate of Origin Version 1.1 Copyright (C) 2004, 2006 The Linux Foundation and its contributors. 1 Letterman Drive Suite D4700 San Francisco, CA, 94129 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. ```
Project: FOSSA (Provisioning / Security & Compliance)
File: graph-hydration.md

To explain this feature, assume that red dependencies are Production, blue dependencies are Development, and yellow dependencies are Test. Here's our starting point after building a graph. When building the graph, we couldn't know that `ProdChild` should have been red. We only knew for sure that `TopProd` should be red. The same principle applies to `TopDev` being blue, and `TopIsolated` being yellow. In this graph, `MutualChild` and `MutualGrandChild` are connected (either directly or transitively) to both red and blue, so we want them to become both red and blue (we'll use purple to represent that). If we hydrate the graph, we can let all of the associated data (color) flow through the edges in the graph, recursively (we don't actually use recursion, because there may be cycles). Here's what the graph looks like after hydration: There are 4 things to note: In our case, we combine colors, though we could choose to just take the first color or latest color for any node. That's left to the user (read: author of the instance of the typeclass) to decide. In the main graph, with `TopDev` and `TopProd`, the results are predictable. Red and blue both flow downwards, creating purple when they join. In the yellow isolated graph, we have no trace of blue or red anywhere, meaning that graph hydration allows for isolation of subgraphs. In the cyclic graph, we ended up with all nodes being the same color. This is again due to combining the colors, but if we defined the behavior to overwrite existing colors (or to reject all colors after the first), we could end up with VERY different graphs. Graph hydration is handled through the `Hydrateable` typeclass, in the `Graphing.Hydrate` module. The tests, which can be found in `test/Graphing/HydrateSpec.hs`, should closely resemble these images.
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.0.18.2.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Blocker | Checksum verification is disabled for LocalFS* Checksum verification was mistakenly disabled for LocalFileSystem. | Blocker | Bug in FSInputChecker makes it possible to read from an invalid buffer* Checksum input stream can sometimes return invalid data to the user. | Blocker | TestReplication fails quite often* Simulated Datanodes should not include blocks that are still being written in their block report. | Blocker | dfs datanode metrics, bytes\_read, bytes\_written overflows due to incorrect type used.* Changed bytes\read, bytes\written to type long to prevent metrics overflow. | Blocker | SerializationFactory should use current context ClassLoader* SerializationFactory now uses the current context ClassLoader allowing for user supplied Serialization instances.
Project: CloudARK KubePlus (App Definition and Development / Application Definition & Image Build)
File: SECURITY.md

Join the [kubernetes-security-announce] group for security and vulnerability announcements. You can also subscribe to an RSS feed of the above using . Instructions for reporting a vulnerability can be found on the [Kubernetes Security and Disclosure Information] page. Information about supported Kubernetes versions can be found on the [Kubernetes version and version skew support policy] page on the Kubernetes website.
Project: ArangoDB (App Definition and Development / Database)
File: explicit_result_make_error_code_move_converting_constructor.md

+++ title = "`explicit basicoutcome(basicresult<A, B, C> &&)`" description = "Explicit converting move constructor from compatible `basicresult`. Available if `predicate::enablemakeerrorcodecompatibleconversion<A, B, void, C>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "explicit-constructors", "converting-constructors"] weight = 342 +++ Explicit converting move constructor from compatible `basicresult`. Calls {{% api "void onoutcomemoveconstruction(T *, U &&) noexcept" %}} with `this` and the input. Requires: `predicate::enablemakeerrorcodecompatible_conversion<A, B, void, C>` is true. Complexity: Same as for the move constructors of the underlying types. Constexpr, triviality and noexcept of underlying operations is propagated. Guarantees: If an exception is thrown during the operation, the object is left in a partially completed state, as per the normal rules for the same operation on a `struct`.
Project: CyberArk Conjur (Provisioning / Key Management)
File: solution_design.md

| Term | Description | |-|--| | | | | | | | Name | Link | |-|-| | Feature Doc | | | Issue | | Command: Input parameters: | Name | Description | Type | Default | Required? | |-|--|-|-|| | | | | | | Output parameters: | Name | Description | Type | |-|--|-| | | | | | Subject | Description | Issue Mitigation | |-|--|-| | | | | | Feature | OS | Version Number | |-|--|--| | | | | | Title | Given | When | Then | Comment | |--|--|-|-|-| | | | | | | | | | | | | | Title | Given | When | Then | Comment | |--|--|-|-|-| | | | | | | | | | | | | | Title | Given | When | Then | Comment | |--|--|-|-|-| | | | | | | | | | | | | | Scenario | Spec | Environment(s) | Comments | |--|-|--|--| | | | | | | Scenario | Log message | |--|--| | | | | | | | Security Issue | Description | Resolution | |--|--|-| | | | | | Name (ID) | Description | Issued On | ||--|| | | | | Solution designed is approved Test plan is reviewed Acceptance criteria have been met Tests are implemented according to test plan The behaviour is documented in Conjur Open Source and Enterprise Documentation has been validated by a manual UX walkthrough All relevant components are released | Persona | Name | |--|-| | Team leader | | | Product owner | | | System architect | | | Security architect | | | QA architect | |
Project: KICS (Provisioning / Security & Compliance)
File: 22c80725-e390-4055-8d14-a872230f6607.md

title: CloudFront Without WAF hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 22c80725-e390-4055-8d14-a872230f6607 Query name: CloudFront Without WAF Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: All AWS CloudFront distributions should be integrated with the Web Application Firewall (AWS WAF) service<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="2" name: create a basic distribution with defaults and tags community.aws.cloudfront_distribution: state: present defaultorigindomain_name: www.my-cloudfront-origin.com tags: Name: example distribution Project: example project Priority: '1' ``` ```yaml title="Negative test num. 1 - yaml file" name: create a basic distribution with defaults and tags community.aws.cloudfront_distribution: state: present defaultorigindomain_name: www.my-cloudfront-origin.com tags: Name: example distribution Project: example project Priority: '1' webaclid: my-web-acl-id ```
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.0.17.1.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Major | JavaSerialization can throw java.io.StreamCorruptedException* Change the Java serialization framework, which is not enabled by default, to correctly make the objects independent of the previous objects. | Minor | fsck on namenode without datanodes takes too much time* Improved performance of {{fsck}} by better management of the data stream on the client side.
Project: Veinmind Tools (Provisioning / Security & Compliance)
File: veinmind-runner_list_plugin.md

List plugin information ``` veinmind-runner list plugin [flags] ``` ``` -h, --help help for plugin -v, --verbose verbose mode ``` ``` -e, --exit-code int exit-code when veinmind-runner find security issues -g, --glob string specifies the pattern of plugin file to find -o, --output string output filepath of report --threads int threads for scan action (default 5) ``` - List relevant information
Project: YDB (App Definition and Development / Database)
File: state-storage-move.md

To decommission a {{ ydb-short-name }} cluster host that accommodates a part of a , you need to move the group to another host. {% include %} As an example, let's take a {{ ydb-short-name }} cluster with the following State Storage configuration: ```yaml ... domains_config: ... state_storage: ring: node: [1, 2, 3, 4, 5, 6, 7, 8, 9] nto_select: 9 ssid: 1 ... ... ``` The of the cluster that serves a part of State Storage is set up and running on the host with `node_id:1`. Suppose that you want to decommission this host. To replace `nodeid:1`, we to the cluster a new host with `nodeid:10` and a static node in it. To move State Storage from the `nodeid:1` host to the `nodeid:10` host: Stop the cluster's static nodes on the hosts with `nodeid:1` and `nodeid:10`. {% include %} In the `config.yaml` configuration file, change the `node` host list, replacing the ID of the removed host by the ID of the added host: ```yaml domains_config: ... state_storage: ring: node: [2, 3, 4, 5, 6, 7, 8, 9, 10] nto_select: 9 ssid: 1 ... ``` Update the `config.yaml` configuration files for all the cluster nodes, including dynamic nodes. Use the procedure to restart all the cluster nodes (including dynamic nodes but excluding static nodes on the hosts with `nodeid:1` and `nodeid:10`). Stop static cluster nodes on the hosts with `nodeid:1` and `nodeid:10`.