cwielenb/CNCF-Dataset huggingface dataset:
Project: KubeCarrier (App Definition and Development / Application Definition & Image Build)
File: PULL_REQUEST_TEMPLATE.md

What this PR does / why we need it: Which issue(s) this PR fixes (optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged): Fixes # Special notes for your reviewer: Documentation: <!-- Add links to the related documentation changes related to this pull request. --> Does this PR introduce a user-facing change?: <!-- Write your release note: Enter your extended release note in the below block. If the PR requires additional action from users switching to the new release, include the string "action required". If no release note is required, just write "NONE". --> ```release-note ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_storage_buckets.md

+++ title = "googlestoragebuckets resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlestoragebuckets" identifier = "inspec/resources/gcp/googlestoragebuckets.md googlestoragebuckets resource" parent = "inspec/resources/gcp" +++ A `googlestoragebuckets` is used to test a Google Bucket resource ```ruby describe googlestoragebuckets(project: 'chef-gcp-inspec') do its('bucket_names') { should include bucket-name } end ``` ```ruby describe googlestoragebuckets(project: 'chef-inspec-gcp') do its('count') { should be <= 100} end ``` ```ruby describe googlestoragebuckets do its('bucketnames'){ should include "myexpected_bucket" } end ``` ```ruby googlestoragebuckets(project: 'chef-inspec-gcp').bucketnames.each do |bucketname| describe googlestoragebucket(name: bucket_name) do it { should exist } its('project_number'){ should eq 1122334455 } end end ``` Properties that can be accessed from the `googlestoragebuckets` resource: See the resource for more information. `acls` : an array of `googlestoragebucket` acl `cors` : an array of `googlestoragebucket` cors `defaulteventbased_holds` : an array of `googlestoragebucket` defaulteventbased_hold `defaultobjectacls` : an array of `googlestoragebucket` defaultobjectacl `bucket_ids` : an array of `googlestoragebucket` id `lifecycles` : an array of `googlestoragebucket` lifecycle `bucket_locations` : an array of `googlestoragebucket` location `loggings` : an array of `googlestoragebucket` logging `metagenerations` : an array of `googlestoragebucket` metageneration `bucket_names` : an array of `googlestoragebucket` name `owners` : an array of `googlestoragebucket` owner `bucketprojectnumbers` : an array of `googlestoragebucket` project_number `storage_classes` : an array of `googlestoragebucket` storage_class `time_createds` : an array of `googlestoragebucket` time_created `updateds` : an array of `googlestoragebucket` updated `versionings` : an array of `googlestoragebucket` versioning `websites` : an array of `googlestoragebucket` website `labels` : an array of `googlestoragebucket` labels `encryptions` : an array of `googlestoragebucket` encryption `retention_policies` : an array of `googlestoragebucket` retention_policy `projects` : an array of `googlestoragebucket` project `predefineddefaultobject_acls` : an array of `googlestoragebucket` predefineddefaultobject_acl 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: ArangoDB (App Definition and Development / Database)
File: narrow_exception_check.md

+++ title = "`static void narrowexceptioncheck(Impl &&) noexcept`" description = "Observer policy performing hard UB if no exception is present. Constexpr, never throws." categories = ["observer-policies"] weight = 420 +++ Observer policy performing hard UB if no exception is present, by calling {{% api "static void _ub(Impl &&)" %}}. Constexpr where possible. Requires: Always available. Complexity: Constant time. Guarantees: Never throws an exception.
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.3.3.2.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Major | Add Available Space Rack Fault Tolerant BPP* Added a new BlockPlacementPolicy: "AvailableSpaceRackFaultTolerantBlockPlacementPolicy" which uses the same optimization logic as the AvailableSpaceBlockPlacementPolicy along with spreading the replicas across maximum number of racks, similar to BlockPlacementPolicyRackFaultTolerant. The BPP can be configured by setting the blockplacement policy class as org.apache.hadoop.hdfs.server.blockmanagement.AvailableSpaceRackFaultTolerantBlockPlacementPolicy | Major | Replace HTrace with No-Op tracer* Dependency on HTrace and TraceAdmin protocol/utility were removed. Tracing functionality is no-op until alternative tracer implementation is added. | Major | Make some parameters configurable for DataNodeDiskMetrics* WARNING: No release note provided for this change. | Major | Make GetClusterNodesRequestPBImpl thread safe* Added syncronization so that the "yarn node list" command does not fail intermittently | Minor | Encrypt S3A data client-side with AWS SDK (S3-CSE)* Adds support for client side encryption in AWS S3, with keys managed by AWS-KMS. Read the documentation in encryption.md very, very carefully before use and consider it unstable. S3-CSE is enabled in the existing configuration option "fs.s3a.server-side-encryption-algorithm": fs.s3a.server-side-encryption-algorithm=CSE-KMS fs.s3a.server-side-encryption.key=\<KMS\KEY\ID\> You cannot enable CSE and SSE in the same client, although you can still enable a default SSE option in the S3 console. \* Not compatible with S3Guard. \* Filesystem list/get status operations subtract 16 bytes from the length of all files \>= 16 bytes long to compensate for the padding which CSE adds. \* The SDK always warns about the specific algorithm chosen being deprecated. It is critical to use this algorithm for ranged GET requests to work (i.e. random IO). Ignore. \* Unencrypted files CANNOT BE READ. The entire bucket SHOULD be encrypted with S3-CSE. \* Uploading files may be a bit slower as blocks are now written sequentially. \* The Multipart Upload API is disabled when S3-CSE is active. | Critical | Improve RM system metrics publisher's performance by pushing events to timeline server in batch* When Timeline Service V1 or V1.5 is used, if "yarn.resourcemanager.system-metrics-publisher.timeline-server-v1.enable-batch" is set to true, ResourceManager sends timeline events in batch. The default value is false. If this functionality is enabled, the maximum number that events published in batch is configured by "yarn.resourcemanager.system-metrics-publisher.timeline-server-v1.batch-size". The default value is 1000. The interval of publishing events can be configured by "yarn.resourcemanager.system-metrics-publisher.timeline-server-v1.interval-seconds". By default, it is set to 60 seconds.
Project: Packer (App Definition and Development / Application Definition & Image Build)
File: question.md

name: Question about: If you have a question, please check out our other community resources instead of opening an issue. labels: question Issues on GitHub are intended to be related to bugs or feature requests, so we recommend using our other community resources instead of asking here if you have a question. Packer Guides: https://www.packer.io/guides Discussion List: https://groups.google.com/group/packer-tool Any other questions can be sent to the packer section of the HashiCorp forum: https://discuss.hashicorp.com/c/packer Packer community links: https://www.packer.io/community
Project: YugabyteDB (App Definition and Development / Database)
File: exists.md

title: EXISTS linkTitle: EXISTS description: EXISTS menu: preview: parent: api-yedis weight: 2060 aliases: /preview/api/redis/exist /preview/api/yedis/exist type: docs Single-key request only. Requests with multiple keys are not yet supported. `EXISTS key [key ...]` This command is a predicate to check whether or not the given `key` exists. Returns the number of existing keys. ```sh $ SET yuga1 "Africa" ``` ``` "OK" ``` ```sh $ SET yuga2 "America" ``` ``` "OK" ``` ```sh $ EXISTS yuga1 ``` ``` 1 ``` ```sh $ EXISTS yuga1 yuga2 notakey ``` ``` 2 ``` , , , , , , , , ,
Project: YDB (App Definition and Development / Database)
File: if.md

Checks the condition: `IF(conditionexpression, thenexpression, else_expression)`. It's a simplified alternative for . You may omit the `elseexpression` argument. In this case, if the condition is false (`conditionexpression` returned `false`), an empty value is returned with the type corresponding to `then_expression` and allowing for `NULL`. Hence, the result will have an . Examples ```yql SELECT IF(foo > 0, bar, baz) AS barorbaz, IF(foo > 0, foo) AS onlypositivefoo FROM my_table; ```
Project: KICS (Provisioning / Security & Compliance)
File: 2ab6de9a-0136-415c-be92-79d2e4fd750f.md

title: SQL Server Predictable Admin Account Name hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 2ab6de9a-0136-415c-be92-79d2e4fd750f Query name: SQL Server Predictable Admin Account Name Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: Azure SQL Server's Admin account login must avoid using names like 'Admin', that are too predictable, which means the attribute 'administrator_login' must be set to a name that is not easy to predict<br> ```tf title="Positive test num. 1 - tf file" hl_lines="40 20" resource "azurermresourcegroup" "positive1" { name = "database-rg" location = "West US" } resource "azurermstorageaccount" "positive2" { name = "examplesa" resourcegroupname = azurermresourcegroup.example.name location = azurermresourcegroup.example.location account_tier = "Standard" accountreplicationtype = "LRS" } resource "azurermsqlserver" "positive3" { name = "mssqlserver" resourcegroupname = azurermresourcegroup.example.name location = azurermresourcegroup.example.location version = "12.0" administrator_login = "" administratorloginpassword = "thisIsDog11" extendedauditingpolicy { storageendpoint = azurermstorageaccount.example.primaryblob_endpoint storageaccountaccesskey = azurermstorageaccount.example.primaryaccess_key storageaccountaccesskeyis_secondary = true retentionindays = 6 } tags = { environment = "production" } } resource "azurermsqlserver" "positive4" { name = "mssqlserver" resourcegroupname = azurermresourcegroup.example.name location = azurermresourcegroup.example.location version = "12.0" administrator_login = "Admin" administratorloginpassword = "thisIsDog11" extendedauditingpolicy { storageendpoint = azurermstorageaccount.example.primaryblob_endpoint storageaccountaccesskey = azurermstorageaccount.example.primaryaccess_key storageaccountaccesskeyis_secondary = true retentionindays = 6 } tags = { environment = "production" } } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermresourcegroup" "negative1" { name = "database-rg" location = "West US" } resource "azurermstorageaccount" "negative2" { name = "examplesa" resourcegroupname = azurermresourcegroup.example.name location = azurermresourcegroup.example.location account_tier = "Standard" accountreplicationtype = "LRS" } resource "azurermsqlserver" "negative3" { name = "mssqlserver" resourcegroupname = azurermresourcegroup.example.name location = azurermresourcegroup.example.location version = "12.0" administrator_login = "UnpredictableAdminLogin" administratorloginpassword = "thisIsDog11" extendedauditingpolicy { storageendpoint = azurermstorageaccount.example.primaryblob_endpoint storageaccountaccesskey = azurermstorageaccount.example.primaryaccess_key storageaccountaccesskeyis_secondary = true retentionindays = 6 } tags = { environment = "production" } } ```
Project: YDB (App Definition and Development / Database)
File: basic.md

{% include %} {% include %} {% include %} {% include %} {% include %} {% include %} {% include %} {% include %} {% include %} {% include %} {% include %} {% include %} {% include %} {% include %} {% include %} {% include %} {% include %} {% include %} {% if featurebulktables %} {% include %} {% endif %} {% include %} {% if feature_mapreduce %} {% include %} {% include %} {% endif %} {% include %} {% include %} {% include %} {% if feature_codegen %} {% include %} {% endif %} {% include %} {% if feature_webui %} {% include %} {% endif %} {% include %} {% include %} {% include %} {% include %} {% include %} {% include %} {% include %} {% include %} {% include %} {% include %} {% include %} {% if tech %} {% include %} {% endif %}
Project: Harbor (Provisioning / Container Registry)
File: proposal.md

name: Proposal about: Suggest an idea for this project Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Describe the solution you'd like A clear and concise description of what you want to happen. Describe the main design/architecture of your solution A clear and concise description of what does your solution look like. Rich text and diagrams are preferred. Describe the development plan you've considered A clear and concise description of the plan to make the solution ready. It can include a development timeline, resource estimation, and other related things. Additional context Add any other context or screenshots about the feature request here.
Project: Devfile (App Definition and Development / Application Definition & Image Build)
File: CONDUCT.md

Cobra will follow a steady release cadence. Non breaking changes will be released as minor versions quarterly. Patch bug releases are at the discretion of the maintainers. Users can expect security patch fixes to be released within relatively short order of a CVE becoming known. For more information on security patch fixes see the CVE section below. Releases will follow . Users tracking the Master branch should expect unpredictable breaking changes as the project continues to move forward. For stability, it is highly recommended to use a release. We will maintain two major releases in a moving window. The N-1 release will only receive bug fixes and security updates and will be dropped once N+1 is released. Deprecation of Go versions or dependent packages will only occur in major releases. To reduce the change of this taking users by surprise, any large deprecation will be preceded by an announcement in the and an Issue on Github. Maintainers will make every effort to release security patches in the case of a medium to high severity CVE directly impacting the library. The speed in which these patches reach a release is up to the discretion of the maintainers. A low severity CVE may be a lower priority than a high severity one. Cobra maintainers will use GitHub issues and the as the primary means of communication with the community. This is to foster open communication with all users and contributors. Breaking changes are generally allowed in the master branch, as this is the branch used to develop the next release of Cobra. There may be times, however, when master is closed for breaking changes. This is likely to happen as we near the release of a new version. Breaking changes are not allowed in release branches, as these represent minor versions that have already been released. These version have consumers who expect the APIs, behaviors, etc, to remain stable during the lifetime of the patch stream for the minor release. Examples of breaking changes include: Removing or renaming exported constant, variable, type, or function. Updating the version of critical libraries such as `spf13/pflag`, `spf13/viper` etc... Some version updates may be acceptable for picking up bug fixes, but maintainers must exercise caution when reviewing. There may, at times, need to be exceptions where breaking changes are allowed in release branches. These are at the discretion of the project's maintainers, and must be carefully considered before merging. Maintainers will ensure the Cobra test suite utilizes the current supported versions of Golang. Changes to this document and the contents therein are at the discretion of the maintainers. None of the contents of this document are legally binding in any way to the maintainers or the users.
Project: CloudNativePG (App Definition and Development / Database)
File: declarative_hibernation.md

CloudNativePG is designed to keep PostgreSQL clusters up, running and available anytime. There are some kinds of workloads that require the database to be up only when the workload is active. Batch-driven solutions are one such case. In batch-driven solutions, the database needs to be up only when the batch process is running. The declarative hibernation feature enables saving CPU power by removing the database Pods, while keeping the database PVCs. !!! Note Declarative hibernation is different from the existing implementation of . Imperative hibernation shuts down all Postgres instances in the High Availability cluster, and keeps a static copy of the PVCs of the primary that contain `PGDATA` and WALs. The plugin enables to exit the hibernation phase, by resuming the primary and then recreating all the replicas - if they exist. To hibernate a cluster, set the `cnpg.io/hibernation=on` annotation: ``` sh $ kubectl annotate cluster <cluster-name> --overwrite cnpg.io/hibernation=on ``` A hibernated cluster won't have any running Pods, while the PVCs are retained so that the cluster can be rehydrated at a later time. Replica PVCs will be kept in addition to the primary's PVC. The hibernation procedure will delete the primary Pod and then the replica Pods, avoiding switchover, to ensure the replicas are kept in sync. The hibernation status can be monitored by looking for the `cnpg.io/hibernation` condition: ``` sh $ kubectl get cluster <cluster-name> -o "jsonpath={.status.conditions[?(.type==\"cnpg.io/hibernation\")]}" { "lastTransitionTime":"2023-03-05T16:43:35Z", "message":"Cluster has been hibernated", "reason":"Hibernated", "status":"True", "type":"cnpg.io/hibernation" } ``` The hibernation status can also be read with the `status` sub-command of the `cnpg` plugin for `kubectl`: ``` sh $ kubectl cnpg status <cluster-name> Cluster Summary Name: cluster-example Namespace: default PostgreSQL Image: ghcr.io/cloudnative-pg/postgresql:16.3 Primary instance: cluster-example-2 Status: Cluster in healthy state Instances: 3 Ready instances: 0 Hibernation Status Hibernated Message Cluster has been hibernated Time 2023-03-05 16:43:35 +0000 UTC [..] ``` To rehydrate a cluster, either set the `cnpg.io/hibernation` annotation to `off`: ``` $ kubectl annotate cluster <cluster-name> --overwrite cnpg.io/hibernation=off ``` Or, just unset it altogether: ``` $ kubectl annotate cluster <cluster-name> cnpg.io/hibernation- ``` The Pods will be recreated and the cluster will resume operation.
Project: ClickHouse (App Definition and Development / Database)
File: comparison-functions.md

slug: /en/sql-reference/functions/comparison-functions sidebar_position: 35 sidebar_label: Comparison Below comparison functions return 0 or 1 as Uint8. The following types can be compared: numbers strings and fixed strings dates dates with times Only values within the same group can be compared (e.g. UInt16 and UInt64) but not across groups (e.g. UInt16 and DateTime). Strings are compared byte-by-byte. Note that this may lead to unexpected results if one of the strings contains UTF-8 encoded multi-byte characters. A string S1 which has another string S2 as prefix is considered longer than S2. Syntax ```sql equals(a, b) ``` Alias: `a = b` (operator) `a == b` (operator) Syntax ```sql notEquals(a, b) ``` Alias: `a != b` (operator) `a <> b` (operator) Syntax ```sql less(a, b) ``` Alias: `a < b` (operator) Syntax ```sql greater(a, b) ``` Alias: `a > b` (operator) Syntax ```sql lessOrEquals(a, b) ``` Alias: `a <= b` (operator) Syntax ```sql greaterOrEquals(a, b) ``` Alias: `a >= b` (operator)
Project: StarRocks (App Definition and Development / Database)
File: DROP_FUNCTION.md

displayed_sidebar: "English" Deletes a custom function. The function can only be deleted when its name and parameter type are consistent. Only the owner of the custom function have the permissions to delete the function. ```sql DROP FUNCTION functionname(argtype [, ...]) ``` `function_name`: the name of function to be dropped. `arg_type`: the argument type of function to be dropped. Drop a function. ```sql DROP FUNCTION my_add(INT, INT) ```
Project: YDB (App Definition and Development / Database)
File: datatypes_primitive_string.md

| Type | Description | Notes | | -- | -- | -- | | `String` | A string that can contain any binary data | | `Utf8` | Text encoded in | | `Json` | represented as text | Doesn't support matching{% if featuremaptables %}, can't be used in the primary key{% endif %} | | `JsonDocument` | in an indexed binary representation | Doesn't support matching{% if featuremaptables %}, can't be used in the primary key{% endif %} | | `Yson` | in a textual or binary representation. | Doesn't support matching{% if featuremaptables %}, can't be used in the primary key{% endif %} | | `Uuid` | Universally unique identifier | Not supported for table columns | {% note info "Cell size restrictions" %} The maximum value size for a {% if featuremaptables %}non-key {% endif %} column cell with any string data type is 8 MB. {% endnote %} Unlike the `JSON` data type that stores the original text representation passed by the user, `JsonDocument` uses an indexed binary representation. An important difference from the point of view of semantics is that `JsonDocument` doesn't preserve formatting, the order of keys in objects, or their duplicates. Thanks to the indexed view, `JsonDocument` lets you bypass the document model using `JsonPath` without the need to parse the full content. This helps efficiently perform operations from the , reducing delays and cost of user queries. Execution of `JsonDocument` queries can be up to several times more efficient depending on the type of load. Due to the added redundancy, `JsonDocument` is less effective in storage. The additional storage overhead depends on the specific content, but is 20-30% of the original volume on average. Saving data in `JsonDocument` format requires additional conversion from the textual representation, which makes writing it less efficient. However, for most read-intensive scenarios that involve processing data from JSON, this data type is preferred and recommended. {% note warning %} To store numbers (JSON Number) in `JsonDocument`, as well as for arithmetic operations on them in the , the type is used. Precision might be lost when non-standard representations of numbers are used in the source JSON document. {% endnote %}
Project: Harbor (Provisioning / Container Registry)
File: 2-16-LDAP-user-delete-projects.md

Test 2-16 - User Delete Projects (LDAP Mode) ======= To verify that a non-admin user can delete projects in (LDAP mode). User guide This test requires that two(2) Harbor instances are running and available. Harbor is set to authenticate against an LDAP or AD server. ( auth_mode is set to ldap_auth* .) The user data is stored in an LDAP or AD server. A linux host with Docker CLI installed (Docker client). At least a non-admin user. Same as Test 2-06 except that users are from LDAP/AD. Same as Test 2-06. None