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

layout: release date: 2022-12-22 tag: v0.6.36 language: en Fix bug on /api/meshmodel/components/types @Revolyssup (#6763) [Server] MeshModel Updater Comments and Doc @leecalcote (#6748) Add "Kubernetes" in meshmodel components @Revolyssup (#6751) Fix APIVersion bug in Meshmodel components @Revolyssup (#6757) Move meshmodel components under "components" folder @leecalcote (#6745) Replace carriage return with newline @Revolyssup (#6743) Add meshmodel components in Dockerfile @Revolyssup (#6741) Replace "output" with "meshmodel_components" @Revolyssup (#6740) Add meshmodel components @Revolyssup (#6738) [MeshModel] Add support for `Relationships` @sudo-NithishKarthik (#6717) Change prettification logic @Revolyssup (#6727) Add apiVersion of a component in Design @Revolyssup (#6721) Move from draft-04 to draft-07 for k8s components @Revolyssup (#6723) Lowercase true/false in generated markdown @Revolyssup (#6720) Add configmap used to configure playground ingress @Revolyssup (#6676) Use helm chart name as dir @Revolyssup (#6716) Fix #6713 @Revolyssup (#6714) [Playground] Fix CORS issue during logout | CU-85zrgczty @theBeginner86 (#6730) [UI] Confirmation modal active tag background update @Chadha93 (#6759) cursor event & Delete Icon @harkiratsm (#6750) [UI] Fix style bug with Validation modal btn and Update spec verbiage @Chadha93 (#6753) fix: add tooltip on actions buttons @Udit-takkar (#6551) [UI] Add Sidebar Peek for Notification Center @theBeginner86 (#6737) [UI] Playground modal to Deploy Meshery locally | CU-333dqt2 @Chadha93 (#6729) [UI] Icon change for clearing the notification @suhail34 (#6579) [UI] ConfirmationModal - Changed the order of tabs @partik03 (#6725) Added Delete Modal in Grid view @hs05june (#6724) [UI] Change verify to validate and positions of button in card and table update @Chadha93 (#6718) Made settings consistent with the UI @partik03 (#6678) [UI] Update verbiage, format of snackbars(Meshery UI) and server logs(mesheryctl). @Chadha93 (#6702) [Playground] Fix CORS issue during logout | CU-85zrgczty @theBeginner86 (#6730) [UI] Add Sidebar Peek for Notification Center @theBeginner86 (#6737) Added Fossa Badge in Readme @hs05june (#6710) Update integrations updater workflow @Revolyssup (#6712) [docs] Recommended node versions for usage @Abhishek-kumar09 (#6744) docs: directions for meshery icons and static files in UI @Abhishek-kumar09 (#6726) Added Fossa Badge in Readme @hs05june (#6710) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Chadha93, @Revolyssup, @Udit-takkar, @XDRAGON2002, @harkiratsm, @hs05june, @l5io, @leecalcote, @partik03, @sudo-NithishKarthik, @suhail34, @theBeginner86 and l5io
Project: Shifu (Provisioning / Automation & Configuration)
File: use-shifu.md

Hello developers! This guide will help you control the virtual device `demo` locally using `Shifu`. ``` Ubuntu WSL on Windows 10 ``` If you have any problems using this guide and find any bugs, please don't hesitate to open an in GitHub. Use `kind` to deploy the cluster locally. Create a `k8s` cluster locally with the following command: ```sh kind create cluster ``` View all pods in the cluster. Run the following command to view all pods in the current cluster: ```sh kubectl get pods -A ``` Deploy `shifu` to the `k8s` cluster. Run the following command in `shifu` directory to deploy `shifu` to the cluster: ```shell kubectl apply -f pkg/k8s/crd/install/shifu_install.yml ``` Confirm that `shifu` has been added to the `k8s` cluster. Run the following command to view all pods in the current cluster and confirm that shifu has been deployed to the cluster: ```shell kubectl get pods -A ``` Generate a digital twin of the `demo` device. Run the following command in `shifu` directory to create a digital twin of the `demo` device: ```shell kubectl apply -f examples/deviceshifu/demo_device/edgedevice-agv/ ``` Deploy and run the `nginx` application. Run the `nginx` application with the following command: ```shell kubectl run nginx --image=nginx ``` Enter a command to return to the running state of the `demo` device. Run the following command to get the real-time coordinates of the `demo` device: ```shell kubectl exec -it nginx -- bash curl deviceshifu-agv.deviceshifu.svc.cluster.local/get_position;echo ```
Project: KICS (Provisioning / Security & Compliance)
File: d45330fd-f58d-45fb-a682-6481477a0f84.md

title: RBAC Roles with Attach Permission hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: d45330fd-f58d-45fb-a682-6481477a0f84 Query name: RBAC Roles with Attach Permission Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Roles or ClusterRoles with RBAC permissions to attach to containers via 'kubectl attach' could be abused by attackers to read log output (stdout, stderr) and send input data (stdin) to running processes. Additionally, it would allow a malicious user to attach to a privileged container resulting in a privilege escalation attack. To prevent this, the 'pods/attach' verb should not be used in production environments<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="8" apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: namespace: my-namespace name: allow-attach rules: apiGroups: [""] resources: ["pods", "pods/attach"] verbs: ["get", "list", "create"] apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: allow-attach namespace: my-namespace subjects: kind: User name: bob apiGroup: rbac.authorization.k8s.io roleRef: kind: Role name: allow-attach apiGroup: "" ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: namespace: my-namespace name: allow-attach-neg rules: apiGroups: [""] resources: ["pods"] verbs: ["get", "list", "create"] apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: allow-attach-neg namespace: my-namespace subjects: kind: User name: bob apiGroup: rbac.authorization.k8s.io roleRef: kind: Role name: allow-attach-neg apiGroup: "" ```
Project: Glasskube (App Definition and Development / Application Definition & Image Build)
File: SECURITY.md

At Glasskube, we take security seriously and appreciate the efforts of the security community in helping us maintain the integrity of our software. To report a security vulnerability, please follow these guidelines: Do Not Create GitHub Issues: Please refrain from creating GitHub issues to report security vulnerabilities. We do not want these issues to be publicly disclosed in our repositories. Contact Us Via Email: Instead, kindly send us an email at support@glasskube.eu to report the vulnerability. This allows us to keep the information confidential and take prompt action. Include Details: In your email, provide as much information as possible about the vulnerability, including a detailed description, potential impact, and any relevant steps to reproduce the issue. The more information you can provide, the better we can understand and address the problem. Response Time: We are committed to acknowledging your report as soon as possible. You can expect an initial response within 3 business days. Our team will investigate the issue and keep you informed of our progress. Vulnerability Handling: When we receive a security report, we will assess the severity of the vulnerability. If the vulnerability is accepted, we will work on a fix and keep you informed about the progress. If it is declined, we will provide a clear explanation of our decision. Responsible Disclosure: We greatly appreciate responsible disclosure, and we request that you refrain from disclosing the vulnerability publicly until we have had the opportunity to address the issue and provide a fix or mitigation. Your collaboration in helping us maintain a secure environment is invaluable. We thank you for your responsible reporting and dedication to improving the security of Glasskube. Note: Please adhere to our Responsible Disclosure Policy and guidelines when reporting vulnerabilities.
Project: EJBCA Community (Provisioning / Security & Compliance)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: '' labels: '' assignees: '' Is your feature request related to a problem or specific use case? Please describe. A clear and concise description of the problem or use case. 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. Product deployment Please complete the following information: Deployment format: [e.g. software, container] Version [e.g. 8.0.0] Additional context Add any other context or screenshots about the feature request here.
Project: Curiefense (Provisioning / Security & Compliance)
File: CODE_OF_CONDUCT.md

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at curiefense@reblaze.com. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. This Code of Conduct is adapted from the , version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: v5.0.11-en.md

Security enhancement for retained messages . The retained messages will not be published if the publisher client is banned. Security enhancement for the `subscribe` API . Enhance the `banned` feature . Now the corresponding session will be kicked when client is banned by `clientid`. Redesign `/gateways` API . Use `PUT /gateways/{name}` instead of `POST /gateways`, gateway gets 'loaded' automatically if needed. Use `PUT /gateways/{name}/enable/{true|false}` to enable or disable gateway. No more `DELETE /gateways/{name}`. Support `statsd {tags: {"user-defined-tag" = "tag-value"}` configure and improve stability of `emqx_statsd` . Improve node name generation rules to avoid potential atom table overflow risk . Set the default value for the maximum level of a topic to 128 . Keep MQTT v5 User-Property pairs from bridge ingested MQTT messsages to bridge target . Add a new config `quickdenyanonymous` to allow quick deny of anonymous clients (without username) so the auth backend checks can be skipped . Support message properties in `/publish` API . Optimize client query performance for HTTP APIs . Fix `ssl.existingName` option of helm chart not working . Fix create trace sometime failed by end_at time has already passed. Return 404 for status of unknown authenticator in `/authenticator/{id}/status` . Fix that JWT ACL rules are only applied if an `exp` claim is set . Fix that `/configs/global_zone` API cannot get the default value of the configuration . Fix mountpoint not working for will-msg . Fix that the obsolete SSL files aren't deleted after the bridge configuration update .
Project: ClickHouse (App Definition and Development / Database)
File: v20.10.4.1-stable.md

Workaround for use S3 with nginx server as proxy. Nginx currenty does not accept urls with empty path like http://domain.com?delete, but vanilla aws-sdk-cpp produces this kind of urls. This commit uses patched aws-sdk-cpp version, which makes urls with "/" as path in this cases, like http://domain.com/?delete. (). Backported in : Fix bug with MySQL database. When MySQL server used as database engine is down some queries raise Exception, because they try to get tables from disabled server, while it's unnecessary. For example, query `SELECT ... FROM system.parts` should work only with MergeTree tables and don't touch MySQL database at all. (). Backported in : Fixed the inconsistent behaviour when a part of return data could be dropped because the set for its filtration wasn't created. (). Backported in : Fix processing of very large entries in replication queue. Very large entries may appear in ALTER queries if table structure is extremely large (near 1 MB). This fixes . (). Backported in : Fix DROP TABLE for Distributed (racy with INSERT). (). Backported in : Fix rapid growth of metadata when using MySQL Master -> MySQL Slave -> ClickHouse MaterializeMySQL Engine, and `slaveparallelworker` enabled on MySQL Slave, by properly shrinking GTID sets. This fixes . (). Backported in : Now when parsing AVRO from input the LowCardinality is removed from type. Fixes . (). Backported in : Fixed . (). Backported in : This will fix optimizereadinorder/optimizeaggregationinorder with max_threads>0 and expression in ORDER BY. (). Backported in : Fix `IN` operator over several columns and tuples with enabled `transformnullin` setting. Fixes . (). Backported in : Fix rare silent crashes when query profiler is on and ClickHouse is installed on OS with glibc version that has (supposedly) broken asynchronous unwind tables for some functions. This fixes . This fixes . ().
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_connect_cluster.md

title: "Command - devspace connect cluster" sidebar_label: devspace connect cluster Connects an existing cluster to DevSpace Cloud ``` devspace connect cluster [flags] ``` ``` Connects an existing cluster to DevSpace Cloud. Examples: devspace connect cluster ``` ``` --admission-controller Deploy the admission controller (default true) --cert-manager Deploy a cert manager (default true) --context string The kube context to use --domain string The domain to use --gatekeeper Deploy the gatekeeper --gatekeeper-rules Deploy the gatekeeper default rules -h, --help help for cluster --ingress-controller Deploy an ingress controller (default true) --key string The encryption key to use --name string The cluster name to create --open-ui Opens the UI and displays the cluster overview --provider string The cloud provider to use --public Connects a new public cluster --use-domain Use an automatic domain for the cluster --use-hostnetwork Use the host network for the ingress controller instead of a loadbalancer ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile string The devspace profile to use (if there is any) --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) ```
Project: ArangoDB (App Definition and Development / Database)
File: PULL_REQUEST_TEMPLATE.md

(Please describe the changes in this PR for reviewers, motivation, rationale - mandatory) [ ] :hankey: Bugfix [ ] :pizza: New feature [ ] :fire: Performance improvement [ ] :hammer: Refactoring/simplification [ ] Tests [ ] Regression tests [ ] C++ Unit tests [ ] integration tests [ ] resilience tests [ ] :book: CHANGELOG entry made [ ] :books: documentation written (release notes, API changes, ...) [ ] Backports [ ] Backport for 3.12.0: (Please link PR) [ ] Backport for 3.11: (Please link PR) [ ] Backport for 3.10: (Please link PR) (Please reference tickets / specification / other PRs etc) [ ] Docs PR: [ ] Enterprise PR: [ ] GitHub issue / Jira ticket: [ ] Design document:
Project: KICS (Provisioning / Security & Compliance)
File: 1743f5f1-0bb0-4934-acef-c80baa5dadfa.md

title: User With Privilege Escalation By Actions 'iam:CreatePolicyVersion' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 1743f5f1-0bb0-4934-acef-c80baa5dadfa Query name: User With Privilege Escalation By Actions 'iam:CreatePolicyVersion' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: User with privilege escalation by actions 'iam:CreatePolicyVersion' 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 "awsiamuser" "cosmic" { name = "cosmic" } resource "awsiamuserpolicy" "testinline_policy" { name = "testinlinepolicy" user = awsiamuser.cosmic.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "iam:CreatePolicyVersion", ] Effect = "Allow" Resource = "*" }, ] }) } resource "awsiampolicy_attachment" "test-attach" { name = "test-attachment" users = [awsiamuser.cosmic.name] roles = [awsiamrole.role.name] groups = [awsiamgroup.group.name] } ``` ```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: Backstage (App Definition and Development / Application Definition & Image Build)
File: heroku.md

id: heroku title: Deploying with Heroku sidebar_label: Heroku description: How to deploy Backstage to Heroku Heroku is a Platform as a Service (PaaS) designed to handle application deployment in a hands-off way. Heroku supports container deployment of Docker images, a natural fit for Backstage. First, install the and login: ```shell $ heroku login ``` If you have not yet created a project through the Heroku interface, you can create it through the CLI. ```shell $ heroku create <your-app> ``` You might also need to set your Heroku app's stack to `container`: ```bash $ heroku stack:set container -a <your-app> ``` Configuring your `app-config.yaml`: ```yaml app: baseUrl: https://<your-app>.herokuapp.com backend: baseUrl: https://<your-app>.herokuapp.com listen: port: $env: PORT ``` Make sure your file is being copied into your container in the `Dockerfile`. Before building the Docker image, run the . They must be run whenever you are going to publish a new image. Heroku runs a container registry on `registry.heroku.com`. To push Backstage Docker images, log in to the container registry also: ```shell $ heroku container:login ``` Now we can push a Backstage to Heroku's container registry and release it to the `web` worker: ```bash $ docker image build . -f packages/backend/Dockerfile --tag registry.heroku.com/<your-app>/web $ docker push registry.heroku.com/<your-app>/web $ heroku container:release web -a <your-app> ``` Now you should have Backstage up and running!
Project: Meshery (Provisioning / Automation & Configuration)
File: 09-29-2022-17-41-09_8c17f987.md

timestamp: "2022-09-29 17:41:15 UTC Thu" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "v0.6.9" k8s-distro: minikube k8s-version: "v1.23.9" service-mesh: Consul service-mesh-version: "v0.48.0" tests: consul-client: null consul-server: null overall-status: "failing"
Project: Meshery (Provisioning / Automation & Configuration)
File: curiefense.md

layout: integration title: Curiefense subtitle: Collaborative and visual infrastructure as code for Curiefense image: /assets/img/integrations/curiefense/icons/color/curiefense-color.svg permalink: extensibility/integrations/curiefense docURL: https://docs.meshery.io/extensibility/integrations/curiefense description: integrations-category: Provisioning integrations-subcategory: Security & Compliance registrant: Artifact Hub components: featureList: [ "Protects all forms of web traffic, services, and APIs.", "Includes bot management, WAF, application-layer DDoS protection, session profiling, advanced rate limiting, and much more.", "It is integrated with NGINX and Envoy proxy." ] 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: KICS (Provisioning / Security & Compliance)
File: 704dadd3-54fc-48ac-b6a0-02f170011473.md

title: GuardDuty Detector Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 704dadd3-54fc-48ac-b6a0-02f170011473 Query name: GuardDuty Detector Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Make sure that Amazon GuardDuty is Enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="2" resource "awsguarddutydetector" "positive1" { enable = false } ``` ```tf title="Negative test num. 1 - tf file" resource "awsguarddutydetector" "negative1" { enable = true } ```
Project: KubeVirt (App Definition and Development / Application Definition & Image Build)
File: CONTRIBUTORS.md

Andrea Barberio (main author) Pablo Mazzini (tons of fixes and new options) Sean Karlage (BSDP package, and of tons of improvements to the DHCPv4 package) Owen Mooney (several option fixes and modifiers) Mikolaj Walczak (asynchronous DHCPv6 client) Chris Koch (tons of improvements in DHCPv4 and DHCPv6 internals and interface) Akshay Navale, Brandon Bennett and Chris Gorham (ZTPv6 and ZTPv4 packages) Anatole Denis (tons of fixes and new options)