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

+++ title = "googlecomputeurl_maps resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputeurl_maps" identifier = "inspec/resources/gcp/googlecomputeurlmaps.md googlecomputeurlmaps resource" parent = "inspec/resources/gcp" +++ A `googlecomputeurl_maps` is used to test a Google UrlMap resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputeurl_maps(project: 'chef-gcp-inspec') do its('names') { should include 'inspec-gcp-url-map' } end ``` Properties that can be accessed from the `googlecomputeurl_maps` resource: See the resource for more information. `creation_timestamps` : an array of `googlecomputeurlmap` creationtimestamp `default_services` : an array of `googlecomputeurlmap` defaultservice `descriptions` : an array of `googlecomputeurl_map` description `ids` : an array of `googlecomputeurl_map` id `fingerprints` : an array of `googlecomputeurl_map` fingerprint `header_actions` : an array of `googlecomputeurlmap` headeraction `host_rules` : an array of `googlecomputeurlmap` hostrules `names` : an array of `googlecomputeurl_map` name `path_matchers` : an array of `googlecomputeurlmap` pathmatchers `tests` : an array of `googlecomputeurl_map` tests `defaulturlredirects` : an array of `googlecomputeurlmap` defaulturl_redirect This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_core.Icon.md

/ / Icon .Icon new Icon(`icon`) | Name | Type | | :-- | :- | | `icon` | | `Optional` balloon: `string` `Optional` balloonLength: `string` `Optional` balloonPos: `string` fontawesome: `string` `Optional` onclick: (`evt`: `Event`) => `void` (`evt`): `void` | Name | Type | | :- | : | | `evt` | `Event` | `void`
Project: kpt (Provisioning / Automation & Configuration)
File: drafts-repository.md

For easier orientation, an overview of the contents of the `drafts-repository.tar`. The repository in `drafts-repository.tar` has the following contents in `main` branch: ``` . basens Kptfile namespace.yaml package-context.yaml README.md empty Kptfile README.md istions istions.yaml Kptfile package-context.yaml README.md ``` The commit graph of the repository is: ``` | * 81d54c8aa3dd939fd36713f7074e9e1ad4f34612 (drafts/pkg-with-history/v1) Intermediate commit: eval | * 1c3f6bf69d579b544c6e60abbba2763987d2a019 Intermediate commit: patch | * 23371b72a0c5b5d7713030db1e9b89da402b91c4 Intermediate commit: eval | * dc1bde5e9044f76996664978fef79d88e01e8693 Intermediate commit: init |/ | * 487eaa0fe7652a313dcdb05790aa32034398593a (drafts/none/v1) Add none package with Kptfile marker |/ c7edca419782f88646f9572b0a829d686b2d91bd (HEAD -> main, tag: istions/v2) Add Istio Namespace Resource c93d417f1393ae5d7def978da70c42b62e645cda (tag: basens/v2) Add Base Namespace Resource | * 032c503a3921f322850e9bd49319346e0e0b129d (drafts/bucket/v1) Add Bucket Resource | * 1950b803f552e4c89ac17c528ec466c1a7375083 Add Bucket Package Context | * 5ea104c29951f3c3995ae15c4a367823794bd47d Empty Bucket Package |/ f8fb59f626182319ec78dd542afcce35f98811e2 (tag: istions/v1) Add Istio Namespace Package Context 740397bf8f594b785f6802755945bd58a5e94192 (tag: basens/v1) Add Base Namespace Package Context 3d21cf677b3afcca132e0b415144e83f1f2ca2a9 Empty Istio Namespace ca725b9cd90d5a3ee22101f0ea66f83e40217a6f Empty Base Namespace 7a6308e79524221d74f549bac53bf1ed771958f7 (tag: empty/v1) Empty Package ``` In addition to several published packages there are two drafts (`none` and `bucket`).
Project: YDB (App Definition and Development / Database)
File: detailed_distributed_storage.md

All information stored in BS_CONTROLLER can be grouped into: BS_CONTROLLER settings. Low-level configuration (PDisks, VDisks, and groups). Top-level configuration (Boxes and StoragePools). Runtime information (persistent disk and group metrics, the status of scrubbing of individual VDisks, information about node drive serial numbers). OperationLogs. The functional logic is built to load all table data (with the exception of OperationLog) into memory when the BS_CONTROLLER tablet starts and to keep them there for the entire time it is up. When executing transactions, the data is updated in tables and in memory. The tables are discussed in more detail below. The settings are stored in the State table. Low-level configuration includes information about the available cluster resources: PDisks, VDisks, and groups. These tables are interconnected via PK <-> FK links. Top-level configuration stores data necessary for linking Boxes and nodes where they are

Box | Column | ID | PK | Type | Default | Purpose | | | - | - | -- | -- | | | BoxId | 1 | * | Uint64 | | | | Name | 2 | | Utf8 | | | | Generation | 3 | | Uint64 | | | BoxHost | Column | ID | PK | Type | Default | Purpose | | -- | - | - | -- | -- | | | BoxId | 1 | * | Uint64 | | | | FQDN | 3 | * | Utf8 | | | | IcPort | 4 | * | Int32 | | | | HostConfigId | 5 | | Uint64 | | | BoxHostV2 | Column | ID | PK | Type | Default | Purpose | | -- | - | - | -- | -- | | | BoxId | 1 | * | Uint64 | | | | FQDN | 2 | * | Utf8 | | | | IcPort | 3 | * | Int32 | | | | HostConfigId | 4 | | Uint64 | | | BoxStoragePool | Column | ID | PK | Type | Default | Purpose | | - | - | - | -- | -- | | | BoxId | 1 | * | Uint64 | | | | StoragePoolId | 2 | * | Uint64 | | | | Name | 20 | | Utf8 | | | | ErasureSpecies | 3 | | Int32 | | | | RealmLevelBegin | 4 | | Int32 | | | | RealmLevelEnd | 5 | | Int32 | | | | DomainLevelBegin | 6 | | Int32 | | | | DomainLevelEnd | 7 | | Int32 | | | | NumFailRealms | 8 | | Int32 | | | | NumFailDomainsPerFailRealm | 9 | | Int32 | | | | NumVDisksPerFailDomain | 10 | | Int32 | | | | VDiskKind | 11 | | Int32 | | | | SpaceBytes | 12 | | Uint64 | | | | WriteIOPS | 13 | | Uint64 | | | | WriteBytesPerSecond | 14 | | Uint64 | | | | ReadIOPS | 15 | | Uint64 | | | | ReadBytesPerSecond | 16 | | Uint64 | | | | InMemCacheBytes | 17 | | Uint64 | | | | Kind | 18 | | Utf8 | | | | NumGroups | 19 | | Uint32 | | | | Generation | 21 | | Uint64 | | | | EncryptionMode | 22 | | Uint32 | 0 | | | SchemeshardId | 23 | | Uint64 | | | | PathItemId | 24 | | Uint64 | | | | RandomizeGroupMapping | 25 | | Bool | false | | BoxStoragePoolPDiskFilter | Column | ID | PK | Type | Default | Purpose | | | - | - | -- | -- | | | BoxId | 1 | * | Uint64 | | | | StoragePoolId | 2 | * | Uint64 | | | | Type | 3 | * | Int32 | | | | SharedWithOs | 4 | * | Bool | | | | ReadCentric | 5 | * | Bool | | | | Kind | 6 | * | Uint64 | | | BoxStoragePoolUser | Column | ID | PK | Type | Default | Purpose | | | - | - | -- | -- | | | BoxId | 1 | * | Uint64 | |
Project: Meshery (Provisioning / Automation & Configuration)
File: karpenter.md

layout: integration title: Karpenter subtitle: Collaborative and visual infrastructure as code for Karpenter image: /assets/img/integrations/karpenter/icons/color/karpenter-color.svg permalink: extensibility/integrations/karpenter docURL: https://docs.meshery.io/extensibility/integrations/karpenter description: integrations-category: Provisioning integrations-subcategory: Automation & Configuration registrant: Artifact Hub components: name: aws-node-template colorIcon: assets/img/integrations/karpenter/components/aws-node-template/icons/color/aws-node-template-color.svg whiteIcon: assets/img/integrations/karpenter/components/aws-node-template/icons/white/aws-node-template-white.svg description: name: provisioner colorIcon: assets/img/integrations/karpenter/components/provisioner/icons/color/provisioner-color.svg whiteIcon: assets/img/integrations/karpenter/components/provisioner/icons/white/provisioner-white.svg description: featureList: [ "Watching for pods that the Kubernetes scheduler has marked as unschedulable", "Evaluating scheduling constraints (resource requests, nodeselectors, affinities, tolerations, and topology spread constraints) requested by the pods", "Provisioning nodes that meet the requirements of the pods" ] howItWorks: "Using Meshery and Karpenter, once your Kubernetes cluster and the Karpenter controller are up and running" howItWorksDetails: "Set up provisioners: By applying a provisioner to Karpenter, you can configure constraints on node provisioning and set timeout values for node expiry or Kubelet configuration values. Deploy workloads: When deploying workloads, you can request that scheduling constraints be met to direct which nodes Karpenter provisions for those workloads. " language: en list: include type: extensibility category: integrations
Project: ThreatMapper (Provisioning / Security & Compliance)
File: jira.md

title: JIRA ThreatMapper can be configured to raise JIRA tickets for vulnerabilities and secrets. The minimum supported version of JIRA is 7.13. For authentication either password of a user account or an api token can be used. To generate an api token: Click settings icon and navigate to Atlassian account settings Once you navigate there, click security tab: Click Create API Token button, set label and create: On the Threatmapper Jira integrations page enter the jira site url, username, api token. The JIRA project key is the prefix of the issue numbers , e.g. issue "JRA-123" has "JRA" as project key Enter the type of ticket you would want ThreatMapper to create (Task / Bug etc.):
Project: ClickHouse (App Definition and Development / Database)
File: v22.12.6.22-stable.md

sidebar_position: 1 sidebar_label: 2023 Fix changing an expired role (). Fix bug in zero-copy replication disk choice during fetch (). Fix NOT_IMPLEMENTED error with CROSS JOIN and algorithm = auto (). Fix query parameters (). Hotfix for too verbose warnings in HTTP (). Better error messages in ReplicatedMergeTreeAttachThread (). Add a fuse for backport branches w/o a created PR (). Only valid Reviews.STATES overwrite existing reviews (). Place short return before big block, improve logging (). Artifacts s3 prefix (). Fix tsan error lock-order-inversion ().
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: user-defined-sinks.md

A `Pipeline` may have multiple Sinks, those sinks could either be a pre-defined sink such as `kafka`, `log`, etc., or a `user-defined sink`. A pre-defined sink vertex runs single-container pods, a user-defined sink runs two-container pods. You can build your own user-defined sinks in multiple languages. Check the links below to see the examples for different languages. A user-defined sink vertex looks like below. ```yaml spec: vertices: name: output sink: udsink: container: image: my-sink:latest ``` Some environment variables are available in the user-defined sink container: `NUMAFLOW_NAMESPACE` - Namespace. `NUMAFLOW_POD` - Pod name. `NUMAFLOW_REPLICA` - Replica index. `NUMAFLOWPIPELINENAME` - Name of the pipeline. `NUMAFLOWVERTEXNAME` - Name of the vertex. If you're looking for examples and usages contributed by the open source community, head over to . These user-defined sinks like AWS SQS, GCP Pub/Sub, provide valuable insights and guidance on how to use and write a user-defined sink.
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: vision.md

id: vision title: Vision description: Goal is to provide engineers with the best developer experience in the world Our goal is to provide engineers with the best developer experience in the world. A fantastic developer experience leads to happy, creative and productive engineers. Our belief is that engineers should not have to be experts in various infrastructure tools to be productive. Infrastructure should be abstracted away so that you can return to building and scaling, quickly and safely. We are working on making Backstage the trusted standard toolbox (read: UX layer) for the open source infrastructure landscape. Think of it like Kubernetes for developer experience. We realize this is an ambitious goal. We cant do it alone. If this sounds interesting or you'd like to help us shape our product vision, we'd love to talk. You can email us directly: .
Project: KICS (Provisioning / Security & Compliance)
File: 9513a694-aa0d-41d8-be61-3271e056f36b.md

title: Add Instead of Copy hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 9513a694-aa0d-41d8-be61-3271e056f36b Query name: Add Instead of Copy Platform: Dockerfile Severity: <span style="color:#ff7213">Medium</span> Category: Supply-Chain URL: Using ADD to load external installation scripts could lead to an evil web server leveraging this and loading a malicious script.<br> ```dockerfile title="Positive test num. 1 - dockerfile file" hl_lines="8" FROM openjdk:10-jdk VOLUME /tmp ADD http://source.file/package.file.tar.gz /temp RUN tar -xjf /temp/package.file.tar.gz \ && make -C /tmp/package.file \ && rm /tmp/ package.file.tar.gz ARG JAR_FILE ADD ${JAR_FILE} app.jar ENTRYPOINT ["java","-Djava.security.egd=file:/dev/./urandom","-jar","/app.jar"] ``` ```dockerfile title="Negative test num. 1 - dockerfile file" FROM openjdk:10-jdk VOLUME /tmp ARG JAR_FILE COPY ${JAR_FILE} app.jar ENTRYPOINT ["java","-Djava.security.egd=file:/dev/./urandom","-jar","/app.jar"] ADD http://source.file/package.file.tar.gz /temp RUN tar -xjf /temp/package.file.tar.gz \ && make -C /tmp/package.file \ && rm /tmp/ package.file.tar.gz ```
Project: SuperEdge (Provisioning / Automation & Configuration)
File: MAINTAINERS.md

SuperEdge Maintainers are given in the list below, in no particular order. | Maintainer Name | Github Name | Company | | :-: | :-: | :: | | Gerald Wang | | Tencent | | Fighting Du | | Linklogis | | Attlee Wang | | Tencent | | Random Cheng | | Tsinghua Unigroup | | Kaiyue Chen | | Tencent | | Shubiao Yao | | Sina | | Fee Li | | Tencent | | Yiwei Chen | | Tencent | | Wenhu Wang | | ZTO | | Roy Liang | | Tencent |
Project: KubeEdge (Provisioning / Automation & Configuration)
File: README.md

](https://travis-ci.org/kubernetes-sigs/yaml) kubernetes-sigs/yaml is a permanent fork of . A wrapper around designed to enable a better way of handling YAML when marshaling to and from structs. In short, this library first converts YAML to JSON using go-yaml and then uses `json.Marshal` and `json.Unmarshal` to convert to or from the struct. This means that it effectively reuses the JSON struct tags as well as the custom JSON methods `MarshalJSON` and `UnmarshalJSON` unlike go-yaml. For a detailed overview of the rationale behind this method, . This package uses and therefore supports . Caveat #1: When using `yaml.Marshal` and `yaml.Unmarshal`, binary data should NOT be preceded with the `!!binary` YAML tag. If you do, go-yaml will convert the binary data from base64 to native binary data, which is not compatible with JSON. You can still use binary in your YAML files though - just store them without the `!!binary` tag and decode the base64 in your code (e.g. in the custom JSON methods `MarshalJSON` and `UnmarshalJSON`). This also has the benefit that your YAML and your JSON binary data will be decoded exactly the same way. As an example: ``` BAD: exampleKey: !!binary gIGC GOOD: exampleKey: gIGC ... and decode the base64 data in your code. ``` Caveat #2: When using `YAMLToJSON` directly, maps with keys that are maps will result in an error since this is not supported by JSON. This error will occur in `Unmarshal` as well since you can't unmarshal map keys anyways since struct fields can't be keys. To install, run: ``` $ go get sigs.k8s.io/yaml ``` And import using: ``` import "sigs.k8s.io/yaml" ``` Usage is very similar to the JSON library: ```go package main import ( "fmt" "sigs.k8s.io/yaml" ) type Person struct { Name string `json:"name"` // Affects YAML field names too. Age int `json:"age"` } func main() { // Marshal a Person struct to YAML. p := Person{"John", 30} y, err := yaml.Marshal(p) if err != nil { fmt.Printf("err: %v\n", err) return } fmt.Println(string(y)) /* Output: age: 30 name: John */ // Unmarshal the YAML back into a Person struct. var p2 Person err = yaml.Unmarshal(y, &p2) if err != nil { fmt.Printf("err: %v\n", err) return } fmt.Println(p2) /* Output: {John 30} */ } ``` `yaml.YAMLToJSON` and `yaml.JSONToYAML` methods are also available: ```go package main import ( "fmt" "sigs.k8s.io/yaml" ) func main() { j := []byte(`{"name": "John", "age": 30}`) y, err := yaml.JSONToYAML(j) if err != nil { fmt.Printf("err: %v\n", err) return } fmt.Println(string(y)) /* Output: age: 30 name: John */ j2, err := yaml.YAMLToJSON(y) if err != nil { fmt.Printf("err: %v\n", err) return } fmt.Println(string(j2)) /* Output: {"age":30,"name":"John"} */ } ```
Project: KICS (Provisioning / Security & Compliance)
File: c19779a9-5774-4d2f-a3a1-a99831730375.md

title: Components Link Definition Is Unused hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: c19779a9-5774-4d2f-a3a1-a99831730375 Query name: Components Link Definition Is Unused Platform: OpenAPI Severity: <span style="color:#5bc0de">Info</span> Category: Best Practices URL: Components links definitions should be referenced or removed from Open API definition<br> ```json title="Positive test num. 1 - json file" hl_lines="45" { "openapi": "3.0.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "success", "content": { "application/json": { "schema": { "type": "array", "items": { "$ref": "#/components/schemas/MyObject" } } } } } } } } }, "components": { "schemas": { "MyObject": { "type": "object", "properties": { "id": { "type": "string" }, "name": { "type": "string" } } } }, "links": { "APIRepository": { "operationId": "listVersionsv2" } } } } ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="29" openapi: 3.0.0 info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '200': description: success content: application/json: schema: type: array items: "$ref": "#/components/schemas/MyObject" components: schemas: MyObject: type: object properties: id: type: string name: type: string links: APIRepository: operationId: listVersionsv2 ``` ```json title="Negative test num. 1 - json file" { "openapi": "3.0.0", "info": { "title": "Simple API Overview", "version": "1.0.0" }, "paths": { "/": { "get": { "operationId": "listVersionsv2", "summary": "List API versions", "responses": { "200": { "description": "success", "content": { "application/json": { "schema": { "type": "array", "items": { "$ref": "#/components/schemas/MyObject" } } } }, "links": { "$ref": "#/components/links/APIRepository" } } } } } }, "components": { "schemas": { "MyObject": { "type": "object", "properties": { "id": { "type": "string" }, "name": { "type": "string" } } } }, "links": { "APIRepository": { "operationId": "listVersionsv2" } } } } ``` ```yaml title="Negative test num. 2 - yaml file" openapi: 3.0.0 info: title: Simple API Overview version: 1.0.0 paths: "/": get: operationId: listVersionsv2 summary: List API versions responses: '200': description: success content: application/json: schema: type: array items: "$ref": "#/components/schemas/MyObject" links: "$ref": "#/components/links/APIRepository" components: schemas: MyObject: type: object properties: id: type: string name: type: string links: APIRepository: operationId: listVersionsv2 ```
Project: ClickHouse (App Definition and Development / Database)
File: v21.2.9.41-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Make FQDN and other DNS related functions work correctly in alpine images. (). Backported in : If PODArray was instantiated with element size that is neither a fraction or a multiple of 16, buffer overflow was possible. No bugs in current releases exist. (). Backported in : Fix very rare bug when quorum insert with `quorum_parallel=1` is not really "quorum" because of deduplication. (). Backported in : Check if table function view is used as a column. This complements https://github.com/ClickHouse/ClickHouse/pull/20350. (). Backported in : Fix usage of function `map` in distributed queries. (). Backported in : Fix approx total rows accounting for reverse reading from MergeTree. (). Backported in : LIVE VIEW (experimental feature). Fix possible hanging in concurrent DROP/CREATE of TEMPORARY LIVE VIEW in `TemporaryLiveViewCleaner`, see https://gist.github.com/vzakaznikov/0c03195960fc86b56bfe2bc73a90019e. (). Backported in : Fixed a crash when using `mannWhitneyUTest` and `rankCorr` with window functions. This fixes . (). Backported in : Allow to start up with modified binary under gdb. In previous version if you set up breakpoint in gdb before start, server will refuse to start up due to failed integrity check. (). Check for EINTR in epoll_wait (). FileDictionarySource fix absolute file path ().
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.2.5.0.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Major | Extend UserGroupInformation to return a UGI given a preauthenticated kerberos Subject* Add getUGIFromSubject to leverage an external kerberos authentication | Major | Remove lsr in OfflineImageViewer* The offlineimageviewer no longer generates lsr-style outputs. The functionality has been superseded by a tool that takes the fsimage and exposes WebHDFS-like API for user queries. | Major | Remove deprecated methods in DistributedFileSystem* WARNING: No release note provided for this change. | Trivial | Remove unused field and imports from SaslRpcServer* SaslRpcServer.SASL\_PROPS is removed. Any use of this variable should be replaced with the following code: SaslPropertiesResolver saslPropsResolver = SaslPropertiesResolver.getInstance(conf); Map\<String, String\> sasl\_props = saslPropsResolver.getDefaultProperties(); | Minor | Document "fileId" and "childrenNum" fields in the FileStatus Json schema* WARNING: No release note provided for this change. | Major | Update hadoop-metrics2.properties examples to Yarn* Remove MRv1 settings from hadoop-metrics2.properties, add YARN settings instead. | Major | Config options to allow wildcard endpoints for namenode HTTP and HTTPS servers* HDFS-6273 introduces two new HDFS configuration keys: dfs.namenode.http-bind-host dfs.namenode.https-bind-host The most common use case for these keys is to have the NameNode HTTP (or HTTPS) endpoints listen on all interfaces on multi-homed systems by setting the keys to 0.0.0.0 i.e. INADDR\_ANY. For the systems background on this usage of INADDR\_ANY please refer to ip(7) in the Linux Programmer's Manual (web link: http://man7.org/linux/man-pages/man7/ip.7.html). These keys complement the existing NameNode options: dfs.namenode.rpc-bind-host dfs.namenode.servicerpc-bind-host | Major | Add s3 server-side encryption* s3 server-side encryption is now supported. To enable this feature, specify the following in your client-side configuration: name: fs.s3n.server-side-encryption-algorithm value: AES256 | Blocker | Issues with OIV processing PB-based fsimages* Set "dfs.namenode.legacy-oiv-image.dir" to an appropriate directory to make standby name node or secondary name node save its file system state in the old fsimage format during checkpointing. This image can be used for offline analysis using the OfflineImageViewer. Use the "hdfs oiv\_legacy" command to process the old fsimage format. | Major | adding more slow action log in critical write path* Log slow i/o. Set log thresholds in dfsclient and datanode via the below new configs: dfs.client.slow.io.warning.threshold.ms (Default 30 seconds) dfs.datanode.slow.io.warning.threshold.ms (Default 300ms) | Major | Refactor timeline classes into server.timeline package* WARNING: No release note provided for this change. | Major | Support utf-8 text with BOM (byte order marker)* WARNING: No release note provided for this change.