cwielenb/CNCF-Dataset huggingface dataset:
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.39.md

layout: release date: 2022-12-29 tag: v0.6.39 language: en Fix NoAuth logic with respect to provider enforcement @Revolyssup (#6808) Upgrade meshkit @Revolyssup (#6795) Continue MeshModel registeration ignoring failure @Revolyssup (#6796) Add "Application" to MeshModel components @Revolyssup (#6677) Fix Applications import bug @Revolyssup (#6793) Return source type with application update responsne @Revolyssup (#6789) Allow POST on /api/application @Revolyssup (#6787) Design Configurator : fonts, tooltips refractor @harkiratsm (#6755) Fix not able to upload JSON Board @MUzairS15 (#6802) fix: use optional chaining in /patterns @Udit-takkar (#6785) [cypress] migrate to cypress version 12 @Abhishek-kumar09 (#6681) [bug] Fix User profile update @theBeginner86 (#6778) added public content from the Meshery Catalog BookInfoForCatalogIstio @aryabyte21 (#6775) [cypress] migrate to cypress version 12 @Abhishek-kumar09 (#6681) Change updater workflow to mandate both flags @Revolyssup (#6791) Change updater workflow @Revolyssup (#6790) Add support for `component` level updation in MeshModels @Revolyssup (#6788) [Docs] Fixed Cilium calculation error on Compatibility Matrix @asubedy (#6801) [Docs] Changed calculation logic on the compatibility matrix @asubedy (#6786) Update README.md for better readability @chinu-anand (#6780) Each adapter page source their adapter-version-number dynamically @ayushthe1 (#6672) [Docs] Integrate Discussion Forum with Posts by Tag @leecalcote (#6773) fix: style for overview class @Udit-takkar (#6784) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Chadha93, @MUzairS15, @Revolyssup, @Udit-takkar, @UtkarshMishra12, @alphaX86, @aryabyte21, @asubedy, @ayushthe1, @chinu-anand, @harkiratsm, @l5io, @leecalcote, @theBeginner86 and l5io
Project: KICS (Provisioning / Security & Compliance)
File: e9817ad8-a8c9-4038-8a2f-db0e6e7b284b.md

title: Implicit Flow in OAuth2 (v2) hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: e9817ad8-a8c9-4038-8a2f-db0e6e7b284b Query name: Implicit Flow in OAuth2 (v2) Platform: OpenAPI Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: There is a 'securityDefinition' using implicit flow on OAuth2, which is deprecated<br> ```json title="Positive test num. 1 - json file" hl_lines="27" { "swagger": "2.0", "info": { "title": "Simple API overview", "version": "1.0.0" }, "schemes": [ "https" ], "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } } } } }, "securityDefinitions": { "oAuth2AuthCodeNeg2": { "type": "oauth2", "description": "For more information, see https://api.my.company.com/docs/oauth", "flow": "implicit", "authorizationUrl": "https://api.my.company.com/oauth/authorize", "scopes": { "write:api": "modify apis in your account", "read:api": "read your apis" } } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="19" swagger: "2.0" info: title: Simple API overview version: 1.0.0 schemes: https paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response securityDefinitions: oAuth2AuthCodeNeg2: type: oauth2 description: For more information, see https://api.my.company.com/docs/oauth flow: implicit authorizationUrl: https://api.my.company.com/oauth/authorize scopes: write:api: modify apis in your account read:api: read your apis ``` ```json title="Negative test num. 1 - json file" { "swagger": "2.0", "info": { "title": "Simple API overview", "version": "1.0.0" }, "schemes": [ "https" ], "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "200 response" } } } } }, "securityDefinitions": { "oAuth2AuthCodeNeg2": { "type": "oauth2", "description": "For more information, see https://api.my.company.com/docs/oauth", "flow": "accessCode", "authorizationUrl": "https://api.my.company.com/oauth/authorize", "tokenUrl": "https://api.my.company.com/oauth/token", "scopes": { "write:api": "modify apis in your account", "read:api": "read your apis" } } } } ``` ```yaml title="Negative test num. 2 - yaml file" swagger: "2.0" info: title: Simple API overview version: 1.0.0 schemes: https paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: "200": description: 200 response securityDefinitions: oAuth2AuthCodeNeg2: type: oauth2 description: For more information, see https://api.my.company.com/docs/oauth flow: accessCode authorizationUrl: https://api.my.company.com/oauth/authorize tokenUrl: https://api.my.company.com/oauth/token scopes: write:api: modify apis in your account read:api: read your apis ```
Project: Cyclops (App Definition and Development / Application Definition & Image Build)
File: template_storage.md

Version `v0.3.0` introduced a new tab to the sidebar: Templates. Here, you can find your "storage" of templates. Each entry references a Helm chart located in either a GitHub, Helm, or Oci repository. Each instance of Cyclops has a couple of templates to get you started. You can see how these charts look in our open . If you want to add your own templates, click the Add template reference. A modal will appear asking you for a pointer to your template. Here are some things to watch out for when connecting your templates. Let's take this repository for example: ``` -repository/ demo/ templates/ Chart.yaml values.schema.json values.yaml ``` If we wanted to connect the demo template: `Name` must follow the `Repository URL` must lead to `repository/` `Path` must be `demo` `Version` can be left empty / branch name / tag / commit hash Once you store a reference to your template, the next time you try to create a new module, it will be shown in the dropdown when selecting templates. Cyclops does not have storage of its own. It uses our CRD and the ETCD database of Kubernetes to store your template references. That is why the name of your templates has to adhere to the because it is a Kubernetes resource. Follow these rules when naming your templates: [x] contain no more than 63 characters [x] contain only lowercase alphanumeric characters or '-' [x] start with an alphanumeric character [x] end with an alphanumeric character You can edit yout template references by clicking on the blue pencil icon on your template. Everything except the name of the template is editable. If you find yourself with unwanted templates, you can easily delete them by clicking on the red trash can icon. A modal will open asking you to input the name of the template. Once written, the delete button will be enabled.
Project: Clair (Provisioning / Security & Compliance)
File: api_internal.md

Internal endpoints are underneath `/api/v1/internal` and are meant for communication between Clair microservices. If Clair is operating in combo mode, these endpoints may not exist. Any sort of API ingress should disallow clients to talk to these endpoints. We do not formally expose these APIs in our OpenAPI spec. Further information and usage is an effort left to the reader. The `update_diff/` endpoint exposes the api for diffing two update operations. This is used by the notifier to determine the added and removed vulnerabilities on security databsae update. The `update_operation` endpoint exposes the api for viewing updaters' activity. This is used by the notifier to determine if new updates have occurred and triggers an update diff to see what has changed. The `affected_manifest` endpoint exposes the api for retreiving affected manifests given a list of Vulnerabilities. This is used by the notifier to determine the manifests that need to have a notification generated.
Project: KICS (Provisioning / Security & Compliance)
File: b8a31292-509d-4b61-bc40-13b167db7e9c.md

title: Role With Privilege Escalation By Actions 'iam:AddUserToGroup' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: b8a31292-509d-4b61-bc40-13b167db7e9c Query name: Role With Privilege Escalation By Actions 'iam:AddUserToGroup' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Role with privilege escalation by actions 'iam:AddUserToGroup' 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 "awsiamrole" "cosmic" { name = "cosmic" } resource "awsiamrolepolicy" "testinline_policy" { name = "testinlinepolicy" role = awsiamrole.cosmic.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "iam:AddUserToGroup", ] 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: Kui (App Definition and Development / Application Definition & Image Build)
File: expandable-section.md

Sections starting with a `??? tip "Section name"` will be rendered as an expandable section, with the tab content indented by at least 4 spaces. ??? tip "Example Expandable Section" Warning: due to the vagaries of the Markdown syntax, make sure to have a newline separating the section start and section content. ???+ question "Example Question (default expanded)" With the added `+` (as in `???+`), the expandable section will be initially expanded. ???+ bug "Example Bug (default expanded)" You can choose from tip todo bug info note warning success question ??? info "Example Info" Informative content! ??? warning "Example Warning"
Project: Artifact Hub (App Definition and Development / Application Definition & Image Build)
File: argo_templates_repositories.md

Argo templates repositories are expected to be hosted in GitHub, GitLab or Bitbucket repos. When adding your repository to Artifact Hub, the url used must follow the following format: `https://github.com/user/repo[/path/to/packages]` `https://gitlab.com/user/repo[/path/to/packages]` `https://bitbucket.org/user/repo[/path/to/packages]` By default the `master` branch is used, but it's possible to specify a different one from the UI. Please NOTE that the repository URL used when adding the repository to Artifact Hub must NOT contain the git hosting platform specific parts, like tree/branch, just the path to your packages like it would show in the filesystem. The path/to/packages provided can contain metadata for one or more packages. Each package version must be on a separate folder, and it's up to you to decide if you want to publish one or multiple versions of your package. Each package must contain a file named `manifests.yaml` that includes the template content (like the ). The structure of a repository with multiple templates packages and versions could look something like this: ```sh $ tree path/to/packages path/to/packages artifacthub-repo.yml package1 1.0.0 README.md manifests.yaml artifacthub-pkg.yml 2.0.0 README.md manifests.yaml artifacthub-pkg.yml package2 1.0.0 README.md manifests.yaml artifacthub-pkg.yml ``` This structure is flexible, and in some cases it can be greatly simplified. In the case of a single package with a single version available at a time (the publisher doesn't want to make previous ones available, for example), the structure could look like this: ```sh $ tree path/to/packages path/to/packages artifacthub-repo.yml package1 README.md manifests.yaml artifacthub-pkg.yml ``` In the previous case, even the `package1` directory could be omitted. The reason is that both packages names and versions are read from the `artifacthub-pkg.yml` metadata file, so directories names are not used at all. Each package version needs an `artifacthub-pkg.yml` metadata file. Please see the file and the for more details. The repository metadata file shown above can be used to setup features like or . This file must be located at `/path/to/packages`. Once you have added your repository, you are all set up. As you add new versions of your templates packages or even new packages to your git repository, they'll be automatically indexed and listed in Artifact Hub.
Project: VoltDB (App Definition and Development / Database)
File: samples.md

If you're like us, you'd like to look at [googletest samples.](https://github.com/google/googletest/tree/master/googletest/samples) The sample directory has a number of well-commented samples showing how to use a variety of googletest features. Sample #1 shows the basic steps of using googletest to test C++ functions. Sample #2 shows a more complex unit test for a class with multiple member functions. Sample #3 uses a test fixture. Sample #4 teaches you how to use googletest and `googletest.h` together to get the best of both libraries. Sample #5 puts shared testing logic in a base test fixture, and reuses it in derived fixtures. Sample #6 demonstrates type-parameterized tests. Sample #7 teaches the basics of value-parameterized tests. Sample #8 shows using `Combine()` in value-parameterized tests. Sample #9 shows use of the listener API to modify Google Test's console output and the use of its reflection API to inspect test results. Sample #10 shows use of the listener API to implement a primitive memory leak checker.
Project: OpenSCAP (Provisioning / Security & Compliance)
File: issue_template.md

Is this an issue with SCAP Workbench? If so, report it here: https://github.com/OpenSCAP/scap-workbench/issues Is this an issue with SCAP Security Guide (i.e., related to the content of scans, not the scanner proper)? If so, report it here: https://github.com/OpenSCAP/scap-security-guide/issues Is this an issue during the OS installation process? If so, report it here: https://github.com/OpenSCAP/oscap-anaconda-addon/issues Thanks!
Project: YugabyteDB (App Definition and Development / Database)
File: 9-conclusion.md

``` { .run-postgres user=postgres } DROP EXTENSION anon CASCADE; ``` ``` { .run-postgres user=postgres dbname=postgres } REASSIGN OWNED BY jack TO postgres; REVOKE ALL ON SCHEMA public FROM jack; REASSIGN OWNED BY paul TO postgres; REASSIGN OWNED BY pierre TO postgres; ``` <! We can't use run-postgres here, because the pandoc-run-postgres filter is already connected to the "boutique" database. Therefore we can't remove it at this point of the document generation --> ``` { .run-postgres user=postgres dbname=postgres } DROP DATABASE IF EXISTS boutique; ``` ``` { .run-postgres user=postgres dbname=postgres } DROP ROLE IF EXISTS jack; DROP ROLE IF EXISTS paul; DROP ROLE IF EXISTS pierre; ``` [Static Masking](https://postgresql-anonymizer.readthedocs.io/en/stable/static_masking/) : perfect for \"once-and-for-all\" anonymization [Dynamic Masking](https://postgresql-anonymizer.readthedocs.io/en/stable/dynamic_masking/) : useful when one user is untrusted [Anonymous Dumps](https://postgresql-anonymizer.readthedocs.io/en/stable/anonymous_dumps/) : can be used in CI/CD workflows : good for statistics and data science Destruction and partial destruction Adding Noise Randomization Faking and Advanced Faking Pseudonymization Generic Hashing Custom masking RTFM -\> [Masking Functions](https://postgresql-anonymizer.readthedocs.io/en/latest/masking_functions/) Masking rules written in SQL Masking rules stored in the database schema No need for an external ETL Works with all current versions of PostgreSQL Multiple strategies, multiple functions Does not work with other databases (hence the name) Lack of feedback for huge tables (\> 10 TB) Other projects you may like : extract a small dataset from a larger PostgreSQL database : An advanced faking extension based on the python Faker lib This is a free and open project! Please send us feedback on how you use it, how it fits your needs (or not), etc. Sources are here: Download the [PDF Handout](https://dalibo.gitlab.io/postgresql_anonymizer/how-to.handout.pdf) ::: ::: {.cell .code} ``` python ``` :::
Project: Harbor (Provisioning / Container Registry)
File: 2-23-admin-delete-images.md

Test 2-23 - Admin User Delete Images (DB Mode) ======= To verify that an admin user can delete images owned by other users when users are managed locally by Harbor (DB mode). User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against a local database. ( auth_mode is set to db_auth* .) The user data is stored in a local database. A linux host with Docker CLI installed (Docker client). At least a non-admin user. NOTE: In below test, user A is non-admin user. User A and project X should be replaced by longer and meaningful names. Log in to UI as user A (non-admin). Create a project X so that the user has the project admin role. On a Docker client, log in as User A and run `docker push` to push an image to the project X, e.g. projectX/myimage:v1. Push an image with different name to project X, e.g. projectX/newimage:v1 . Run `docker pull` to verify images can be pulled successfully. In UI, log out user A's session. Log in as admin user. Under project X, delete the two images one by one. On a Docker client, log in as User A and run `docker pull` to pull the two deleted images of project X. Step 8, admin user can delete images of project X. Step 9, docker client should report errors. None
Project: KubeVirt (App Definition and Development / Application Definition & Image Build)
File: fossa.md

. Currently, FOSSA license scanning happens in two situations: on every push to a PR branch and on every push to the `kubevirt/kubevirt` default branch. Job definitions are located in `kubevirt/project-infra`: To view the scan results, you need to look at the job log file, where near the bottom of the file you'll find a direct link to the check results. To run the license scan you need a FOSSA API key stored in a file. Please have a look at the . This token you put into a file and start the analysis like this: ```bash export FOSSATOKENFILE=<path to your token file> ./hack/fossa.sh ``` for KubeVirt project is allowed for KubeVirt FOSSA team members. Please ask one of the maintainers for access in case you need it.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: ibmdb2_conf.md

+++ title = "ibmdb2_conf resource" draft = false gh_repo = "inspec" platform = "os" [menu] [menu.inspec] title = "ibmdb2_conf" identifier = "inspec/resources/os/ibmdb2conf.md ibmdb2conf resource" parent = "inspec/resources/os" +++ Use the `ibmdb2_conf` Chef InSpec audit resource to test the configuration settings. Make sure you are using the IBM Db2 database instance user credentials to run the InSpec test. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} A `ibmdb2conf` resource block declares db2executablefilepath, db_instance to connect and then runs command to get the configuration values and compares it to the value stated in the test: describe ibmdb2conf(db2executablefilepath: "/opt/ibm/db2/V11.5/bin/db2", db_instance: "db2inst1") do its("output") { shouldnot beempty } its("output") { should include("Audit buffer size (4KB) (AUDITBUFSZ) = 0")} end Windows describe ibmdb2_conf do its("output") { shouldnot beempty } its("output") { should include("Audit buffer size (4KB) (AUDITBUFSZ) = 0")} end where `ibmdb2session` declares a db2executablefilepath, dbinstance and dbname to connect. `db2executablefile_path` is the path of the db2 binary file. For Windows this is not required. `db_instance` is the name of the database instance. For Windows this is not required. `its("output") { should include("expected_settings")}` compares the results of the output against the expected result in the test. The following examples show how to use this Chef InSpec audit resource. describe ibmdb2conf(db2executablefilepath: "/opt/ibm/db2/V11.5/bin/db2", db_instance: "db2inst1") do its("output") { shouldnot beempty } its("output") { should include("Audit buffer size (4KB) (AUDITBUFSZ) = 1000")} end {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}}
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.68.md

layout: release date: 2023-03-27 tag: v0.6.68 Fix K8s Meshmodel component schema @Revolyssup (#7399) app sub-command suggestions added @gurpreet-legend (#7376) feat: rjsf upgrade, remove code @harkiratsm (#7395) Update Button in Storybook @acald-creator (#7391) Setup Storybook in `ui` @acald-creator (#7389) [bug] Fix: invalid memory address or nil pointer dereference @theBeginner86 (#7393) [CI] Change golang version to warning @leecalcote (#7398) Mark oam API endpoints as Deprecated @vishalvivekm (#7374) Anchorjs link bug fix and Search UI changes @VIKAS0264 (#7347) Fixed broken build-and-release link @adarshrajpathak (#7397) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Revolyssup, @VIKAS0264, @acald-creator, @adarshrajpathak, @gurpreet-legend, @harkiratsm, @l5io, @leecalcote, @theBeginner86 and @vishalvivekm
Project: Harbor (Provisioning / Container Registry)
File: 9-04-DB-user-pull-unsigned-images.md

Test 9-04 User pull unsigned images(DB mode) ======= To verify whether user can pull unsigned images with content trust enabled. User guide This test requires one Harbor instance is running and available. Harbor is set to authenticate against a local database.The user data is stored in a local database. A Linux host with Docker CLI(Docker client) installed. Login UI and create a project. On Docker client, unset DOCKERCONTENTTRUST and login Harbor. Push an image to the project created in step1. Reset DOCKERCONTENTTRUST to 1. Pull the unsigned image. User cannot pull unsigned images with content trust enabled. None