cwielenb/CNCF-Dataset huggingface dataset:
Project: ArangoDB (App Definition and Development / Database)
File: failure.md

+++ title = "`exception_type failure() const noexcept`" description = "Synthesising observer of the stored exception or error. Available if the traits `iserrorcodeavailable<T>` and `isexceptionptravailable<T>` are both true. Never throws." categories = ["observers"] weight = 790 +++ Synthesising observer of the stored exception or error. If an exception is available, returns a copy of that directly. If an error is available, and not an exception, an ADL discovered free function {{% api "auto basicoutcomefailureexceptionfrom_error(const EC &)" %}} is invoked. Default overloads for this function are defined in Outcome for {{% api "std::error_code" %}} and `boost::system::errorcode`, these return `std::makeexceptionptr(std::systemerror(ec))` and `boost::copyexception(boost::system::systemerror(ec))` respectively. Requires: Both the traits {{% api "iserrorcode_available<T>" %}} and {{% api "isexceptionptr_available<T>" %}} are true. Complexity: Depends on `basicoutcomefailureexceptionfrom_error(const EC &)`. Guarantees: Never throws. If an exception is thrown during the copy of the exception, that exception (from `std::current_exception()`) is returned instead.
Project: Ansible (Provisioning / Automation & Configuration)
File: pr_merged.md

Hi! This has been merged in, and will also be included in the next major release. For more info on our process see <https://docs.ansible.com/ansible/devel/referenceappendices/releaseand_maintenance.html#ansible-core-workflow> If you or anyone else has any further questions, please let us know by stopping by one of the mailing lists or chat channels, as appropriate. Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time. The mailing list and irc are great ways to ask questions, or post if you don't think this particular issue is resolved. See this page for a complete and up to date list of communication channels and their purposes: <https://docs.ansible.com/ansible/latest/community/communication.html> Thank you!
Project: Puppet (Provisioning / Automation & Configuration)
File: http_file_bucket_file.md

File Bucket File ============= The `filebucketfile` endpoint manages the contents of files in the file bucket. All access to files is managed with the md5 checksum of the file contents, represented as `:md5`. Where used, `:filename` means the full absolute path of the file on the client system. This is usually optional and used as an error check to make sure correct file is retrieved. The environment is required in all requests but ignored, as the file bucket does not distinguish between environments. Find Retrieve the contents of a file. GET /puppet/v3/filebucketfile/:md5?environment=:environment GET /puppet/v3/filebucketfile/:md5/:original_path?environment=:environment This will return the contents of the file if it's present. If `:original_path` is provided then the contents will only be sent if the file was uploaded with the same path at some point. Head Check if a file is present in the filebucket HEAD /puppet/v3/filebucketfile/:md5?environment=:environment HEAD /puppet/v3/filebucketfile/:md5/:original_path?environment=:environment This behaves identically to find, only returning headers. Save Save a file to the filebucket PUT /puppet/v3/filebucketfile/:md5?environment=:environment PUT /puppet/v3/filebucketfile/:md5/:original_path?environment=:environment The body should contain the file contents. This saves the file using the md5 sum of the file contents. If `:original_path` is provided, it adds the path to a list for the given file. If the md5 sum in the request is incorrect, the file will be instead saved under the correct checksum. GET, HEAD, PUT `application/octet-stream` None > PUT /puppet/v3/filebucketfile/md5/eb61eead90e3b899c6bcbe27ac581660//home/user/myfile.txt?environment=production HTTP/1.1 > Content-Type: application/octet-stream > Content-Length: 24 > This is the file content < HTTP/1.1 200 OK > GET /puppet/v3/filebucketfile/md5/4949e56d376cc80ce5387e8e89a75396//home/user/myfile.txt?environment=production HTTP/1.1 > Accept: application/octet-stream < HTTP/1.1 200 OK < Content-Length: 24 < This is the file content > GET /puppet/v3/filebucketfile/md5/4949e56d376cc80ce5387e8e89a75396//home/user/wrong_name?environment=production HTTP/1.1 > Accept: application/octet-stream < HTTP/1.1 404 Not Found < < Not Found: Could not find filebucketfile md5/4949e56d376cc80ce5387e8e89a75396/home/user/wrong_name Schema A `filebucketfile` response body is not structured data according to any standard scheme such as json/yaml, so no schema is applicable.
Project: KICS (Provisioning / Security & Compliance)
File: 229588ef-8fde-40c8-8756-f4f2b5825ded.md

title: Memory Requests Not Defined hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 229588ef-8fde-40c8-8756-f4f2b5825ded Query name: Memory Requests Not Defined Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Resource Management URL: Memory requests should be defined for each container. This allows the kubelet to reserve the requested amount of system resources and prevents over-provisioning on individual nodes<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="40 25 59 13" apiVersion: v1 kind: Pod metadata: name: memory-demo namespace: mem-example spec: containers: name: memory-demo-ctr-1 image: polinux/stress resources: limits: memory: "200Mi" requests: cpu: "0.5" command: ["stress"] args: ["--vm", "1", "--vm-bytes", "150M", "--vm-hang", "1"] apiVersion: v1 kind: Pod metadata: name: memory-demo-1 namespace: mem-example spec: containers: name: memory-demo-ctr-2 image: polinux/stress resources: limits: memory: "200Mi" command: ["stress"] args: ["--vm", "1", "--vm-bytes", "150M", "--vm-hang", "1"] apiVersion: v1 kind: Pod metadata: name: memory-demo-2 namespace: mem-example spec: containers: name: memory-demo-ctr-3 image: polinux/stress command: ["stress"] args: ["--vm", "1", "--vm-bytes", "150M", "--vm-hang", "1"] apiVersion: v1 kind: Pod metadata: name: memory-demo-3 namespace: mem-example spec: securityContext: runAsUser: 1000 runAsGroup: 3000 fsGroup: 2000 volumes: name: sec-ctx-vol emptyDir: { } containers: name: memory-demo-ctr-4 image: polinux/stress command: ["stress"] ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="18" apiVersion: apps/v1 kind: Deployment metadata: name: test-deployment2 labels: app: test2 spec: replicas: 3 selector: matchLabels: app: test2 template: metadata: labels: app: test2 spec: containers: name: pause image: k8s.gcr.io/pause resources: limits: cpu: 0.5 memory: 512Mi ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: memory-demo namespace: mem-example spec: containers: name: memory-demo-ctr image: polinux/stress resources: limits: memory: "200Mi" requests: memory: "100Mi" command: ["stress"] args: ["--vm", "1", "--vm-bytes", "150M", "--vm-hang", "1"] ``` ```yaml title="Negative test num. 2 - yaml file" apiVersion: apps/v1 kind: Deployment metadata: name: test-deployment-ctr-neg labels: app: test-neg spec: replicas: 3 selector: matchLabels: app: test-ctr-neg template: metadata: labels: app: test-ctr-neg spec: containers: name: pause image: k8s.gcr.io/pause resources: limits: cpu: 0.5 memory: 512Mi requests: cpu: 0.5 memory: 512Mi ```
Project: Open Application Model (App Definition and Development / Application Definition & Image Build)
File: network_scope.md

The network scope groups components together and links them to a network or SDN. The network itself must be defined and operated by the application operator. The network scope may also be queried by traffic management traits to determine discoverability boundaries for a service mesh or API boundaries for API gateways. If no network scope is assigned, the platform MUST join the application to a default network. Within that default network, all components in the application configuration MUST be able to communicate to each other, and health probes MUST be able to contact any components who define health checking rules. The network joined, however, is platform-dependent. For example, cluster-based environments (such as Kubernetes) declare cluster-wide networks. Conversely, a truly serverless implementation may join the components to a network that only includes the components and the health checking probes. | Attribute | Type | Required | Default Value | Description | |--||-||-| | `networkId` | `string` | Y | | The id of the network, e.g. vpc-id, VNet name. | | `subnetIds` | `array` | Y | | A comma separated list of IDs of the subnets within the network. For example, 'vsw-123' or 'vsw-123','vsw-456'. There could be more than one subnet because there is a limit in the number of IPs in a subnet. If IPs are taken up, operators need to add another subnet into this network. | | `internetGatewayType` | `string` | Y | | The type of the gateway, options are 'public', 'nat'. Empty string means no gateway. | For example, a network scope instance can be like below: ```yaml apiVersion: standard.oam.dev/v1alpha2 kind: NetworkScope metadata: name: example-vpc-network spec: allowComponentOverlap: true # can be skipped networkId: cool-vpc-network subnetIds: cool-subnetwork cooler-subnetwork coolest-subnetwork internetGatewayType: nat ``` An application could reference above scope instance as below: ```yaml kind: Application metadata: name: example-appconfig spec: components: componentName: example-component traits: ... scopes: networkscopes.standard.oam.dev: example-vpc-network ```
Project: KICS (Provisioning / Security & Compliance)
File: 591ade62-d6b0-4580-b1ae-209f80ba1cd9.md

title: Service Account Name Undefined Or Empty hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 591ade62-d6b0-4580-b1ae-209f80ba1cd9 Query name: Service Account Name Undefined Or Empty Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Defaults URL: A Kubernetes Pod should have a Service Account defined so to restrict Kubernetes API access, which means the attribute 'serviceAccountName' should be defined and not empty.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="58 28 6" apiVersion: v1 kind: Pod metadata: name: nginx.container spec: containers: image: nginx name: nginx volumeMounts: mountPath: /var/run/secrets/tokens name: vault-token volumes: name: vault-token projected: sources: serviceAccountToken: path: vault-token expirationSeconds: 7200 audience: vault apiVersion: v1 kind: Pod metadata: name: nginx2.container.group spec: containers: image: nginx2 name: nginx2 volumeMounts: mountPath: /var/run/secrets/tokens name: vault-token serviceAccountName: volumes: name: vault-token projected: sources: serviceAccountToken: path: vault-token expirationSeconds: 7200 audience: vault apiVersion: v1 kind: Pod metadata: name: nginx3 spec: containers: image: nginx3 name: nginx3 volumeMounts: mountPath: /var/run/secrets/tokens name: vault-token serviceAccountName: "" volumes: name: vault-token projected: sources: serviceAccountToken: path: vault-token expirationSeconds: 7200 audience: vault ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: nginx spec: containers: image: nginx name: nginx volumeMounts: mountPath: /var/run/secrets/tokens name: vault-token serviceAccountName: build-robot volumes: name: vault-token projected: sources: serviceAccountToken: path: vault-token expirationSeconds: 7200 audience: vault ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.15.md

layout: release date: 2024-02-02 tag: v0.7.15 Bump @babel/traverse from 7.23.6 to 7.23.9 in /ui @dependabot (#10159) replace icon in header @sudhanshutech (#10168) Start sourcing icons from Sistent (1st phase) @sudhanshutech (#10128) Bump @cypress/code-coverage from 3.12.17 to 3.12.19 in /provider-ui @dependabot (#10160) Bump @emotion/react from 11.10.8 to 11.11.3 in /ui @dependabot (#10155) Bump eslint-config-prettier from 9.0.0 to 9.1.0 in /ui @dependabot (#10157) Bump @mui/material from 5.15.2 to 5.15.7 in /provider-ui @dependabot (#10162) Bump eslint-config-next from 14.0.4 to 14.1.0 in /provider-ui @dependabot (#10163) Bump @babel/eslint-parser from 7.22.15 to 7.23.10 in /provider-ui @dependabot (#10161) Bump cypress from 13.6.2 to 13.6.4 in /provider-ui @dependabot (#10164) Bump @babel/traverse from 7.23.6 to 7.23.9 in /ui @dependabot (#10159) Bump @cypress/code-coverage from 3.12.17 to 3.12.19 in /provider-ui @dependabot (#10160) Bump @emotion/react from 11.10.8 to 11.11.3 in /ui @dependabot (#10155) Bump eslint-config-prettier from 9.0.0 to 9.1.0 in /ui @dependabot (#10157) Bump @mui/material from 5.15.2 to 5.15.7 in /provider-ui @dependabot (#10162) Bump eslint-config-next from 14.0.4 to 14.1.0 in /provider-ui @dependabot (#10163) Bump @babel/eslint-parser from 7.22.15 to 7.23.10 in /provider-ui @dependabot (#10161) Bump cypress from 13.6.2 to 13.6.4 in /provider-ui @dependabot (#10164) fix: remove direct link to the source code @RipulHandoo (#10166) Thank you to our contributors for making this release possible: @MUzairS15, @RipulHandoo, @dependabot, @dependabot[bot], @l5io, @leecalcote and @sudhanshutech
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: label.image.md

Add an image label (e.g. label=value) to the image metadata. Can be used multiple times. Users can set a special LABEL io.containers.capabilities=CAP1,CAP2,CAP3 in a Containerfile that specifies the list of Linux capabilities required for the container to run properly. This label specified in a container image tells Podman to run the container with just these capabilities. Podman launches the container with just the specified capabilities, as long as this list of capabilities is a subset of the default list. If the specified capabilities are not in the default set, Podman prints an error message and runs the container with the default capabilities.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.50.md

layout: release date: 2021-08-28 tag: v0.5.50 [UI]Reduce font padding and margin in RJSF tooltip @killbotXD (#4004) Update RJSF styling for tooltip. @Jashpatel1 (#3953) [UI] [Performance] Bulk delete bug fix @Chadha93 (#3993) fix error on onchange method @killbotXD (#4003) fix broken default config @navendu-pottekkat (#3999) Fix pattern capabilities registration - change port in docker-compose @utkarsh-pro (#3983) [mesheryctl] go-routine fixed for invalid platform flag @piyushsingariya (#3998) Changing version in manifests and meshconfig @metonymic-smokey (#3959) [mesheryctl] fixed default token location displayed twice @afzal442 (#3976) [UI] Adapter: Display NGINX Service Mesh @leecalcote (#3989) Added hover to Configuration and Conformance @warunicorn19 (#3964) [UI] add mapper to podname and version @bariqhibat (#3956) [UI] Bulk Delete in Filters + Patterns + Applications @Chadha93 (#3965) Metrics window @warunicorn19 (#3963) [UI] Import using URL added in filters @Meghana-12 (#3888) Fix page layout in case of hovering over carousel @yagarwal1307 (#3942) [UI] Dashboard: Added Hyperlink to Release Notes @CipherGirl (#3838) [WIP] Cached manifests for skip update flag in Kubernetes @metonymic-smokey (#3880) Patterns: Add OAM patterns with RJSF form on every pattern column @Abhishek-kumar09 (#3925) Fix user pref tabs UI @yagarwal1307 (#3943) [mesheryctl] Reworking of `filter apply` command. @piyushsingariya (#3857) Support minikube out of the box and multi k8s context support @utkarsh-pro (#3869) Reworking of component endpoints + Open API docs @piyushsingariya (#3872) Shifting `/filter/` endpoints out of experiment @piyushsingariya (#3924) [Dataplane] add dataplane to dashboard @bariqhibat (#3854) [Docs] Added Mesheryctl mesh deploy command @afzal442 (#3889) Updated helper.go to include meshery-nginx-sm @DanielLivingston32 (#3997) [UI] Added URL Uploader in Applications and Patterns @Meghana-12 (#3991) [UI] Handled requests made to `/provider` on Dev Server @sudhay23 (#4002) Fixed `subscriptions-transport-ws` error in cypress tests @dhruv0000 (#4000) Bump @babel/traverse from 7.14.7 to 7.15.0 in /ui @dependabot (#3811) [Docs] Added Mesheryctl mesh deploy command @afzal442 (#3889) [Docs] - Added New FAQ @The-Loony-Coder (#3837) Docs - Static and Dynamic Boards concept @suhaniii (#3950) removed installing mesheryctl from FAQ subheading @warunicorn19 (#3948) fixed the kuma-error-codes generation in docs @warunicorn19 (#3949) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Chadha93, @CipherGirl, @DanielLivingston32, @Jashpatel1, @Meghana-12, @The-Loony-Coder, @afzal442, @bariqhibat, @dependabot, @dependabot[bot], @dhruv0000, @killbotXD, @leecalcote, @metonymic-smokey, @navendu-pottekkat, @piyushsingariya, @sudhay23, @sudo-NithishKarthik, @suhaniii, @utkarsh-pro, @warunicorn19, @yagarwal1307 and l5io
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: environment-idling.md

Lagoon can utilize the , (installed in the `lagoon-remote`) to automatically idle environments if they have been unused for a defined period of time. This is done in order to reduce the load on the Kubernetes clusters and improve the overall performance of production environments and development environments that are actually in use. The environment idler has many different configuration capabilities. Here are the defaults of a standard Lagoon installation \(these could be quite different in your Lagoon, check with your Lagoon administrator!\) Idling is tried every 4 hours. Production environments are never idled. CLI pods are idled if they don't include a cron job and if there is no remote shell connection active. All other services and pods are idled if there was no traffic on the environment in the last 4 hours. If there is an active build happening, there will be no idling. Aergia will automatically un-idle an environment as soon as it is visited, therefore just visiting any URL of the environment will start the environment. Likewise, initiating an SSH session to the environment will also restart the services. The un-idling will take a couple of seconds, as the Kubernetes cluster needs to start all containers again. During this time there will be waiting screen shown to the visitor that their environment is currently started. Yes, there is a field `autoIdle` on the project \(impacts all environments\) and environment \(if you need to target just one environment\), as to whether idling is allowed to take place. A value of `1` indicates the project/environment is eligible for idling. If the project is set to `0` the environments will never be idled, even if the environment is set to `0` The default is always `1`\(idling is enabled\). Talk to your Lagoon administrator if you are unsure how to set these project/environment fields.
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.18.0.md

Fix misspelled words by @blazeout in https://github.com/Edgenesis/shifu/pull/591 @blazeout made their first contribution in https://github.com/Edgenesis/shifu/pull/591 Bump github.com/onsi/ginkgo/v2 from 2.9.2 to 2.9.4 by @dependabot in https://github.com/Edgenesis/shifu/pull/595 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.17.0...v0.18.0
Project: ArangoDB (App Definition and Development / Database)
File: error_lvalue.md

+++ title = "`error_type &error() &`" description = "Wide contract lvalue reference observer of the stored error. Constexpr propagating." categories = ["observers"] weight = 740 +++ Wide contract lvalue reference observer of the stored error. `NoValuePolicy::wideerrorcheck()` is first invoked, then the reference to the error is returned. As a valid default constructed error is always present, no undefined behaviour occurs if `NoValuePolicy::wideerrorcheck()` returns. Note that if `error_type` is `void`, only a `const` overload returning `void` is present. Requires: Always available. Complexity: Depends on `NoValuePolicy::wideerrorcheck()`. Guarantees: None.
Project: KICS (Provisioning / Security & Compliance)
File: 434945e5-4dfd-41b1-aba1-47075ccd9265.md

title: Serverless API X-Ray Tracing Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 434945e5-4dfd-41b1-aba1-47075ccd9265 Query name: Serverless API X-Ray Tracing Disabled Platform: ServerlessFW Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Serverless API Gateway should have X-Ray Tracing enabled<br> ```yml title="Positive test num. 1 - yml file" hl_lines="8" service: my-service frameworkVersion: '2' provider: name: aws apiGateway: minimumCompressionSize: 1024 tracing: apiGateway: false ``` ```yml title="Positive test num. 2 - yml file" hl_lines="7" service: my-service frameworkVersion: '2' provider: name: aws apiGateway: minimumCompressionSize: 1024 tracing: ``` ```yml title="Negative test num. 1 - yml file" service: my-service frameworkVersion: '2' provider: name: aws apiGateway: minimumCompressionSize: 1024 tracing: apiGateway: true ```