cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: c01d10de-c468-4790-b3a0-fc887a56f289.md

title: OSS Buckets Secure Transport Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: c01d10de-c468-4790-b3a0-fc887a56f289 Query name: OSS Buckets Secure Transport Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: OSS Buckets should have secure transport enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="2" resource "alicloudossbucket" "bucket-securetransport1"{ policy = <<POLICY { "Version": "1", "Statement": [ { "Effect": "Allow", "Action": [ "oss:RestoreObject", "oss:ListObjects", "oss:AbortMultipartUpload", "oss:PutObjectAcl", "oss:GetObjectAcl", "oss:ListParts", "oss:DeleteObject", "oss:PutObject", "oss:GetObject", "oss:GetVodPlaylist", "oss:PostVodPlaylist", "oss:PublishRtmpStream", "oss:ListObjectVersions", "oss:GetObjectVersion", "oss:GetObjectVersionAcl", "oss:RestoreObjectVersion" ], "Principal": [ "*" ], "Resource": [ "acs:oss::0000111122223334:af/" ], "Condition": { "Bool": { "acs:SecureTransport": [ "false" ] } } } ] } POLICY } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="5" resource "alicloudossbucket" "bucket-securetransport3" { bucket = "bucket-170309-policy" acl = "private" policy = <<POLICY {"Statement": [{"Action": ["oss:PutObject", "oss:GetObject", "oss:DeleteBucket"], "Effect":"Allow", "Resource": ["acs:oss:::*"]}], "Version":"1"} POLICY } ``` ```tf title="Negative test num. 1 - tf file" resource "alicloudossbucket" "bucket-securetransport2"{ policy = <<POLICY { "Version": "1", "Statement": [ { "Effect": "Deny", "Action": [ "oss:RestoreObject", "oss:ListObjects", "oss:AbortMultipartUpload", "oss:PutObjectAcl", "oss:GetObjectAcl", "oss:ListParts", "oss:DeleteObject", "oss:PutObject", "oss:GetObject", "oss:GetVodPlaylist", "oss:PostVodPlaylist", "oss:PublishRtmpStream", "oss:ListObjectVersions", "oss:GetObjectVersion", "oss:GetObjectVersionAcl", "oss:RestoreObjectVersion" ], "Principal": [ "*" ], "Resource": [ "acs:oss::0000111122223334:af/" ], "Condition": { "Bool": { "acs:SecureTransport": [ "false" ] } } } ] } POLICY } ``` ```tf title="Negative test num. 2 - tf file" resource "alicloudossbucket" "bucket-securetransport4"{ policy = <<POLICY { "Version": "1", "Statement": [ { "Effect": "Allow", "Action": [ "oss:RestoreObject", "oss:ListObjects", "oss:AbortMultipartUpload", "oss:PutObjectAcl", "oss:GetObjectAcl", "oss:ListParts", "oss:DeleteObject", "oss:PutObject", "oss:GetObject", "oss:GetVodPlaylist", "oss:PostVodPlaylist", "oss:PublishRtmpStream", "oss:ListObjectVersions", "oss:GetObjectVersion", "oss:GetObjectVersionAcl", "oss:RestoreObjectVersion" ], "Principal": [ "*" ], "Resource": [ "acs:oss::0000111122223334:af/" ], "Condition": { "Bool": { "acs:SecureTransport": [ "true" ] } } } ] } POLICY } ```
Project: ArangoDB (App Definition and Development / Database)
File: index.md

<!-- Copyright 2018 Paul Fultz II Distributed under the Boost Software License, Version 1.0. (http://www.boost.org/LICENSE10.txt) --> About ===== HigherOrderFunctions is a header-only C++11/C++14 library that provides utilities for functions and function objects, which can solve many problems with much simpler constructs than whats traditionally been done with metaprogramming. HigherOrderFunctions is: Modern: HigherOrderFunctions takes advantages of modern C++11/C++14 features. It support both `constexpr` initialization and `constexpr` evaluation of functions. It takes advantage of type deduction, varidiac templates, and perfect forwarding to provide a simple and modern interface. Relevant: HigherOrderFunctions provides utilities for functions and does not try to implement a functional language in C++. As such, HigherOrderFunctions solves many problems relevant to C++ programmers, including initialization of function objects and lambdas, overloading with ordering, improved return type deduction, and much more. Lightweight: HigherOrderFunctions builds simple lightweight abstraction on top of function objects. It does not require subscribing to an entire framework. Just use the parts you need. HigherOrderFunctions is divided into three components: Function Adaptors and Decorators: These enhance functions with additional capability. Functions: These return functions that achieve a specific purpose. Utilities: These are general utilities that are useful when defining or using functions Github: Documentation: Motivation ========== Improve the expressiveness and capabilities of functions, including first-class citzens for function overload set, extension methods, infix operators and much more. Simplify constructs in C++ that have generally required metaprogramming Enable point-free style programming Workaround the limitations of lambdas in C++14 Requirements ============ This requires a C++11 compiler. There are no third-party dependencies. This has been tested on clang 3.5-3.8, gcc 4.6-7, and Visual Studio 2015 and 2017. Contexpr support Both MSVC and gcc 4.6 have limited constexpr support due to many bugs in the implementation of constexpr. However, constexpr initialization of functions is supported when using the and constructs. Noexcept support On older compilers such as gcc 4.6 and gcc 4.7, `noexcept` is not used due to many bugs in the implementation. Also, most compilers don't support deducing `noexcept` with member function pointers. Only newer versions of gcc(4.9 and later) support this.
Project: Tetragon (Provisioning / Security & Compliance)
File: documentation.md

title: "Documentation" weight: 4 description: "Learn how to contribute to the documentation" Thank you for taking the time to improve Tetragon's documentation. All the Tetragon documentation content can be found under . {{< note >}} The main page served from a directory path is named `_index.md`. For example is available under . {{< /note >}} We generally follow the Kubernetes docs style guide . To preview the documentation locally, use one of the method below. Then browse to , the default port used by Hugo to listen. {{< note >}} When submitting a docs related pull request, a Netlify job will automatically build a preview of your changes and post the link in a PR comment, it is often a good idea to edit your initial PR message and link to the precise location of your changes within the preview to help the reviewer's job. {{< /note >}} With a Docker service available, from the root of the repository, use: ```shell make docs ``` You can also use `make` from the Makefile at the `/docs` folder level. To cleanup the container image built in the process, you can use: ```shell make -C docs clean ``` The documentation is a using the . Please refer to dedicated guides on how to install Hugo+extended and how to tweak Docsy, but generally, to preview your work, from the `/docs` folder: ```shell hugo server ```
Project: StarRocks (App Definition and Development / Database)
File: minute.md

displayed_sidebar: "English" Returns the minute for a given date. The return value ranges from 0 to 59. The `date` parameter must be of the DATE or DATETIME type. ```Haskell INT MINUTE(DATETIME|DATE date) ``` ```Plain Text MySQL > select minute('2018-12-31 23:59:59'); +--+ |minute('2018-12-31 23:59:59')| +--+ | 59 | +--+ ``` MINUTE
Project: Beam (App Definition and Development / Streaming & Messaging)
File: withtimestamps.md

title: "WithTimestamps" <!-- Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> {{< localstorage language language-py >}} Assigns timestamps to all the elements of a collection. In the following examples, we create a pipeline with a `PCollection` and attach a timestamp value to each of its elements. When windowing and late data play an important role in streaming pipelines, timestamps are especially useful. The elements themselves often already contain a timestamp field. `beam.window.TimestampedValue` takes a value and a in the form of seconds. {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHONWithTimestampsEventTime" show="withtimestampsevent_time" >}} {{< /playground >}} To convert from a to `unix_time` you can use . For more information on time formatting options, see . {{< highlight >}} {{< codesample "sdks/python/apachebeam/examples/snippets/transforms/elementwise/withtimestamps.py" timetuple2unixtime >}} {{< /highlight >}} To convert from a to `unixtime` you can use convert it to a `time.structtime` first with . {{< highlight >}} {{< codesample "sdks/python/apachebeam/examples/snippets/transforms/elementwise/withtimestamps.py" datetime2unix_time >}} {{< /highlight >}} If each element has a chronological number, these numbers can be used as a . These numbers have to be converted to a "seconds" equivalent, which can be especially important depending on your windowing and late data rules. {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHONWithTimestampsLogicalClock" show="withtimestampslogical_clock" >}} {{< /playground >}} If the elements do not have any time data available, you can also use the current processing time for each element. Note that this grabs the local time of the worker that is processing each element. Workers might have time deltas, so using this method is not a reliable way to do precise ordering. By using processing time, there is no way of knowing if data is arriving late because the timestamp is attached when the element enters into the pipeline. {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHONWithTimestampsProcessingTime" show="withtimestampsprocessing_time" >}} {{< /playground >}} converts between explicit and implicit forms of Beam values.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.6.md

layout: release date: 2021-05-02 tag: v0.5.6 Fix build and release workflow @ramrodo (#2770) Remote Pattern Imports @utkarsh-pro (#2724) [mesheryctl] perf should not require a running Docker process #2763 @Naimaoye (#2776) [mesheryctl] fix gloabl help message @fallmor (#2772) Updated README.MD @JoyNwaiwu (#2773) Bump cypress from 6.8.0 to 7.2.0 in /provider-ui @dependabot (#2788) Bump @babel/types from 7.13.0 to 7.14.0 in /ui @dependabot (#2792) Bump github.com/prometheus/common from 0.20.0 to 0.23.0 @dependabot (#2796) Bump gonum.org/v1/gonum from 0.8.2 to 0.9.1 @dependabot (#2798) Bump mui-datatables from 3.7.6 to 3.7.7 in /ui @dependabot (#2782) Bump notistack from 1.0.5 to 1.0.6 in /ui @dependabot (#2787) Bump start-server-and-test from 1.12.0 to 1.12.1 in /ui @dependabot (#2781) Bump redux from 4.0.5 to 4.1.0 in /ui @dependabot (#2784) Bump classnames from 2.2.6 to 2.3.1 in /ui @dependabot (#2794) Bump github.com/lib/pq from 1.10.0 to 1.10.1 @dependabot (#2799) Bump next from 10.1.2 to 10.2.0 in /provider-ui @dependabot (#2783) Bump @fortawesome/fontawesome-svg-core from 1.2.34 to 1.2.35 in /ui @dependabot (#2793) Bump @material-ui/pickers from 3.2.10 to 3.3.10 in /ui @dependabot (#2780) Bump babel-plugin-relay from 11.0.1 to 11.0.2 in /ui @dependabot (#2790) Bump eslint-plugin-react from 7.23.1 to 7.23.2 in /provider-ui @dependabot (#2791) Bump eslint from 7.23.0 to 7.25.0 in /provider-ui @dependabot (#2789) Bump github.com/sirupsen/logrus from 1.8.0 to 1.8.1 @dependabot (#2797) Bump gorm.io/gorm from 1.20.10 to 1.21.9 @dependabot (#2795)
Project: Chef Infra (Provisioning / Automation & Configuration)
File: client_release_cadence.md

Chef Infra Client follows for releases. Major versions (eg. 16.x -> 17.x) will include backwards-incompatible changes. Minor versions (eg 16.7 -> 16.8) will include new features and bug fixes, but will be backwards-compatible to the best of our ability. Patch releases will contain bug and security fixes only. Chef Infra Client feature releases are promoted to the stable channel once per month. It is expected that this occur during the second week of the month unless circumstances intervene. Additional patch releases for a given feature release may be promoted if critical issues are found. Chef Workstation is released once per month in order to pull in the latest Chef Infra Client. It is expected that this occur during the fourth week of the month unless circumstances intervene. The Chef release in April of each year is a major version release, which will contain backwards-incompatible changes. A reminder notice will be sent via Discourse and Slack in March that will summarize the changes slated for the release. Monthly releases help ensure we get new features and minor bug fixes out to Chef Infra users in a timely fashion while not overloading the maintainer teams. Similarly, offsetting the Chef Infra Client and Chef Workstation releases allows Workstation to ship with current Chef Infra Client releases. Major releases in April avoids releasing during winter holidays, summer vacations, ChefConf, and Chef Summits.
Project: Gradle Build Tool (App Definition and Development / Application Definition & Image Build)
File: notes.md

The Gradle team is excited to announce Gradle @version@. This release features , , ... , and more. <!-- Include only their name, impactful features should be called out separately below. THIS LIST SHOULD BE ALPHABETIZED BY [PERSON NAME] - the docs:updateContributorsInReleaseNotes task will enforce this ordering, which is case-insensitive. --> We would like to thank the following community members for their contributions to this release of Gradle: Be sure to check out the for insight into what's planned for future releases. Switch your build to use Gradle @version@ by updating your wrapper: `./gradlew wrapper --gradle-version=@version@` See the to learn about deprecations, breaking changes, and other considerations when upgrading to Gradle @version@. For Java, Groovy, Kotlin, and Android compatibility, see the . <!-- Do not add breaking changes or deprecations here! Add them to the upgrade guide instead. --> <!-- ================== TEMPLATE ============================== <a name="FILL-IN-KEY-AREA"></a> <<<FILL IN CONTEXT FOR KEY AREA>>> Example: The improves build performance by caching the result of the configuration phase. Using the configuration cache, Gradle can skip the configuration phase entirely when nothing that affects the build configuration has changed. HIGHLIGHT the use case or existing problem the feature solves EXPLAIN how the new release addresses that problem or use case PROVIDE a screenshot or snippet illustrating the new feature, if applicable LINK to the full documentation for more details ================== END TEMPLATE ========================== ========================================================== ADD RELEASE FEATURES BELOW vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv --> <!-- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ADD RELEASE FEATURES ABOVE ========================================================== --> Promoted features are features that were incubating in previous versions of Gradle but are now supported and subject to backward compatibility. See the User Manual section on the for more information. The following are the features that have been promoted in this Gradle release. <!-- --> <!-- This section will be populated automatically --> Known issues are problems that were discovered post-release that are directly related to changes made in this release. <!-- This section will be populated automatically --> We love getting contributions from the Gradle community. For information on contributing, please see . If you find a problem with this release, please file a bug on adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the . We hope you will build happiness with Gradle, and we look forward to your feedback via or on .
Project: MySQL (App Definition and Development / Database)
File: CONTRIBUTING.md

libcbor is maintained by in his spare time on a best-effort basis. Community contributions are welcome as long as they align with the and and follow the guidelines described belows. Bug reports and questions: Bug reports and specific technical questions are always welcome. Feel free to open an . Incremental improvements: Bug fixes (including build scripts, examples, test, typos, CI/CD config, etc.) and documentation improvements (fixes of typos, inaccuracies, out of date content, etc.) are always welcome. Feel free to open a . New features: I am looking to keep the scope of libcbor small. If you would like to add a feature, please open an issue with your proposal (or reach out to me privately) to discuss if the feature fits into libcbor before opening a PR. Major changes: Please open an issue with your proposal (or reach out to me privately) to discuss if the improvement fits into cbor before opening a PR. Ensure that all CI checks pass Check that the PR is complete and of good quality Include a descriptive summary of the change. If the PR addresses an open issue, please link it. Code changes: Add tests If necessary: Update documentation, including any links Code changes: Update . Do not change the version number. I work on libcbor on a best effort basis. The typical response time is a few days. If you do not receive a response in a few weeks, feel free to ping the PR or issue.
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.30.0.md

Fix Telemetry Service SQL Server pipeline flaky test by @Yunxe in https://github.com/Edgenesis/shifu/pull/734 Fix: Bump github.com/gopcua/opcua from 0.4.0 to 0.5.2 by @cool-wangtongzhou in https://github.com/Edgenesis/shifu/pull/735 Bump sigs.k8s.io/controller-runtime from 0.15.1 to 0.16.3 by @tomqin93 in https://github.com/Edgenesis/shifu/pull/738 @cool-wangtongzhou made their first contribution in https://github.com/Edgenesis/shifu/pull/735 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.29.0...v0.30.0
Project: Chef InSpec (Provisioning / Security & Compliance)
File: groups.md

+++ title = "groups resource" draft = false gh_repo = "inspec" platform = "os" [menu] [menu.inspec] title = "groups" identifier = "inspec/resources/os/groups.md groups resource" parent = "inspec/resources/os" +++ Use the `groups` Chef InSpec audit resource to test multiple groups on the system. The `groups` resource uses the following system groups: On non-Windows systems the group resource tests local groups defined in the`/etc/group` file. On Windows systems the group resource tests local groups defined by Local Users and Groups. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} This resource first became available in v1.0.0 of InSpec. A `groups` resource block uses `where` to filter entries from the systems groups. If `where` is omitted, all entries are selected. describe groups do its('names') { should eq ['wheel', 'daemon', 'sys', 'adm'] } its('names') { should include 'wheel' } end describe groups.where { members =~ /root/ } do its('names') { should eq ['wheel', 'daemon', 'sys', 'adm'] } end The following examples show how to use this Chef InSpec audit resource. describe groups.where { name == 'wheel' } do it { should exist } its('members') { should include 'root' } end The `gids` property tests the named group identifier: its('gids') { should eq 1234 } The `names` property tests the name field on a Windows group: its('names') { should include 'Power Users' } The `domains` property tests the domain on a Windows group: its('domains') { should include 'WIN-CIV7VMLVHLD' } The `members` property tests the members that belong to a group: its('members') { should include 'root' } its('members') { should include 'Administrator' } where `members` returns: an array of group members for Windows Platform. Example: `["member1", "member2"]` a single element array that contains a CSV string of group members for Non-Windows Platforms. Example: `["member1,member2"]` The `members_array` property tests the group members just like the `members` property, but the value returned by this property is always an array of group members. its('members_array') { should include 'root' } its('members_array') { should include 'Administrator' } {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The `exist` matcher tests if the named user exists: it { should exist }
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.1.0.md

Refactored shifu into monorepo by @BtXin in https://github.com/Edgenesis/shifu/pull/217 OPC UA example update by @tomqin93 in https://github.com/Edgenesis/shifu/pull/233 fix demo link in README by @Yang-Xijie in https://github.com/Edgenesis/shifu/pull/229 fix some error in telemetry YAML and sample device YAML by @tomqin93 in https://github.com/Edgenesis/shifu/pull/235 [Issue #234] MQTT and other telemetrySetting fixes by @tomqin93 in https://github.com/Edgenesis/shifu/pull/236 fix http and socket if defaulttimeoutSeconds<0 by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/237 Create codecov.yml by @tomqin93 in https://github.com/Edgenesis/shifu/pull/216 bump up mockdevice version by @tomqin93 in https://github.com/Edgenesis/shifu/pull/222 Add CodeCov and star chart in README by @tomqin93 in https://github.com/Edgenesis/shifu/pull/226 Refactored shifu into monorepo by @BtXin in https://github.com/Edgenesis/shifu/pull/217 attempt to fix CI by @tomqin93 in https://github.com/Edgenesis/shifu/pull/228 Bump k8s.io/client-go from 0.24.4 to 0.25.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/220 Bump github.com/onsi/gomega from 1.18.1 to 1.20.1 by @dependabot in https://github.com/Edgenesis/shifu/pull/227 Bump github.com/onsi/gomega from 1.20.1 to 1.20.2 by @dependabot in https://github.com/Edgenesis/shifu/pull/232 Use gcr distroless instead of edgehub's image by @BtXin in https://github.com/Edgenesis/shifu/pull/231 Bump sigs.k8s.io/controller-runtime from 0.12.3 to 0.13.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/238 Update issue templates by @tomqin93 in https://github.com/Edgenesis/shifu/pull/213 Fix changelog v0.0.6 name by @BtXin in https://github.com/Edgenesis/shifu/pull/214 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.0.6...v0.1.0