cwielenb/CNCF-Dataset huggingface dataset:
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_migration_describe.md

title: kbcli migration describe Show details of a specific migration task. ``` kbcli migration describe NAME [flags] ``` ``` kbcli migration describe mytask ``` ``` -h, --help help for describe ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - Data migration between two data sources.
Project: Meshery (Provisioning / Automation & Configuration)
File: nocalhost.md

layout: integration title: Nocalhost subtitle: Collaborative and visual infrastructure as code for NGINX Service Mesh image: /assets/img/integrations/nocalhost/icons/color/nocalhost-color.svg permalink: extensibility/integrations/nocalhost docURL: https://docs.meshery.io/extensibility/integrations/nocalhost description: integrations-category: App Definition and Development integrations-subcategory: Application Definition & Image Build registrant: Artifact Hub components: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: Meshery (Provisioning / Automation & Configuration)
File: metrics-server.md

layout: integration title: Kubernetes Metrics Server subtitle: Collaborative and visual infrastructure as code for Kubernetes Metrics Server image: /assets/img/integrations/metrics-server/icons/color/metrics-server-color.svg permalink: extensibility/integrations/metrics-server docURL: https://docs.meshery.io/extensibility/integrations/metrics-server description: Metrics Server is a scalable, efficient source of container resource metrics for Kubernetes built-in autoscaling pipelines. integrations-category: Observability and Analysis integrations-subcategory: Monitoring registrant: GitHub components: featureList: [ "Fast autoscaling, collecting metrics every 15 seconds.", "Resource efficiency, using 1 mili core of CPU and 2 MB of memory for each node in a cluster.", "Scalable support up to 5,000 node clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_http_health_checks.md

+++ title = "googlecomputehttphealthchecks resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputehttphealthchecks" identifier = "inspec/resources/gcp/googlecomputehttphealthchecks.md googlecomputehttphealthchecks resource" parent = "inspec/resources/gcp" +++ A `googlecomputehttphealthchecks` is used to test a Google HttpHealthCheck resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecomputehttphealthchecks(project: 'chef-gcp-inspec') do its('names') { should include 'inspec-gcp-http-health-check' } its('timeout_secs') { should include '20' } its('checkintervalsecs') { should include '20' } end ``` Properties that can be accessed from the `googlecomputehttphealthchecks` resource: See the resource for more information. `checkintervalsecs` : an array of `googlecomputehttphealthcheck` checkintervalsec `creation_timestamps` : an array of `googlecomputehttphealthcheck` creation_timestamp `descriptions` : an array of `googlecomputehttphealthcheck` description `healthy_thresholds` : an array of `googlecomputehttphealthcheck` healthy_threshold `hosts` : an array of `googlecomputehttphealthcheck` host `ids` : an array of `googlecomputehttphealthcheck` id `names` : an array of `googlecomputehttphealthcheck` name `ports` : an array of `googlecomputehttphealthcheck` port `request_paths` : an array of `googlecomputehttphealthcheck` request_path `timeout_secs` : an array of `googlecomputehttphealthcheck` timeout_sec `unhealthy_thresholds` : an array of `googlecomputehttphealthcheck` unhealthy_threshold 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: Backstage (App Definition and Development / Application Definition & Image Build)
File: v1.16.0.md

id: v1.16.0 title: v1.16.0 description: Backstage Release v1.16.0 These are the release notes for the v1.16.0 release of . A huge thanks to the whole team of maintainers and contributors as well as the amazing Backstage Community for their hard work in getting this release developed and done. A little smaller release this time with the Summer Holidays, hope youre all having some deserved time off also! There have been some more tweaks here or there to types and the theme system to ensure a smooth future migration toward Material-UI version 5. This should be mostly transparent to adopters, but please let us know if you encounter any oddities around the theme system after upgrading to this release. Theres been some more plugins that have been ported across to using the new . They are as follows: `@backstage/plugin-adr-backend` - Contributed by in `@backstage/plugin-airbrake-backend` - Contributed by in `@backstage/plugin-azure-devops-backend` - Contributed by in `@backstage/plugin-badges-backend` - Contributed by in `@backstage/plugin-devtools-backend` - Contributed by in `@backstage/plugin-linguist-backend` - Contributed by in `@backstage/plugin-entity-feedback-backend` - Contributed by in `@backstage/plugin-lighthouse-backend` - Contributed by in Stay tuned for more updates on the future of the Backend System as we move to make this a stable API! Incremental event handlers are now async by default, and their response shape has been changed to allow further extension. Instead of returning `null` or `undefined` from an event handler to indicate no-oop, instead return the value `{ type: "ignored" }`. Contributed by in The configuration has been changed and the authentication property of `confluence.auth` is now an `object` instead to allow further evolution. Contributed by in Added more verbose component for when no audits for a website corresponding to the provided url were found. Contributed by in A reference to material-uis dependency has been updated from `@rjsf/material-ui` to `@rjsf/material-ui-v5`. Contributed by in It is now possible to customize the settings widget for different properties by using the`uiSchema` property. Contributed by in Fixed bug in `View Full Results` link of Search Modal that did not navigate to the full results page. Contributed by in This release does not contain any security fixes. We recommend that you keep your Backstage project up to date with this latest release. For more guidance on how to upgrade, check out the documentation for . Below you can find a list of links and references to help you learn about and start using this new release. , , and Backstage's for discussions and support Backstage , , and Sign up for our if you want to be informed about what is happening in the world of Backstage.
Project: ORY Hydra (Provisioning / Key Management)
File: OAuth2RedirectTo.md

Name | Type | Description | Notes | - | - | - RedirectTo | string | RedirectURL is the URL which you should redirect the user&#39;s browser to once the authentication process is completed. | `func NewOAuth2RedirectTo(redirectTo string, ) *OAuth2RedirectTo` NewOAuth2RedirectTo instantiates a new OAuth2RedirectTo object This constructor will assign default values to properties that have it defined, and makes sure properties required by API are set, but the set of arguments will change when the set of required properties is changed `func NewOAuth2RedirectToWithDefaults() *OAuth2RedirectTo` NewOAuth2RedirectToWithDefaults instantiates a new OAuth2RedirectTo object This constructor will only assign default values to properties that have it defined, but it doesn't guarantee that properties required by API are set `func (o *OAuth2RedirectTo) GetRedirectTo() string` GetRedirectTo returns the RedirectTo field if non-nil, zero value otherwise. `func (o OAuth2RedirectTo) GetRedirectToOk() (string, bool)` GetRedirectToOk returns a tuple with the RedirectTo field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *OAuth2RedirectTo) SetRedirectTo(v string)` SetRedirectTo sets RedirectTo field to given value.
Project: Meshery (Provisioning / Automation & Configuration)
File: integrations.md

layout: default title: "Extensibility: Meshery Integrations" permalink: extensibility/integrations type: Extensibility abstract: "Meshery architecture is extensible. Meshery provides several extension points for working with different cloud native projects via adapters, load generators and providers" language: en suggested-reading: false Meshery provides 220+ built-in integrations which refer to the supported connections and interactions between Meshery and various cloud native platforms, tools, and technologies. Meshery's approach is Kubernetes-native which means you can easily incorporate Meshery into your existing workflow without additional setup or integration effort. {% assign sorted_index = site.models | sort: "name" | alphabetical %} {% assign total = sorted_index | size %} {% capture totalled %} {% endcapture %} {{totalled}} Optionally, you can . <!-- UNCOMMENT WHEN INTEGRATIONS COLLECTION IS READY update: @vishalvivekm: integration collection is now models accessible via site.models and directory is docs/_models/ total: {{ site.models.size }} --> <ul> {% for item in sorted_index %} {% if item.type=="extensibility" and item.category=="integrations" and item.list=="include" and item.language == "en" -%} <li><a href="{{ site.baseurl }}{{ item.url }}">{{ item.title }}</a> {% if item.abstract %} {{ item.abstract }} {% endif %} </li> {% endif %} {% endfor %} </ul>
Project: userver (App Definition and Development / Streaming & Messaging)
File: json_to_yaml.md

Make sure that you can compile and run framework tests as described at @ref scripts/docs/en/userver/tutorial/build.md. The userver framework allows to use it's non-coroutine parts by using the `userver-universal` CMake target. It provides usefull utilities like utils::FastPimpl, utils::TrivialBiMap, @ref scripts/docs/en/userver/formats.md "JSON and YAML formats", utils::AnyMovable, cache::LruMap and many other utilities. See @ref userver_universal for a list of available functions and classes. Let's write a simple JSON to YAML converter with the help of `userver-universal`. The implementation is quite straightforward. Include the necessary C++ Standard library and userver headers: @snippet samples/json2yaml/json2yaml.cpp json2yaml - includes Write the logic for converting each of the JSON types to YAML type: @snippet samples/json2yaml/json2yaml.cpp json2yaml - convert Finally, read data from `std::cin`, parse it as JSON, convert to YAML and output it as text: @snippet samples/json2yaml/json2yaml.cpp json2yaml - main To build the sample, execute the following build steps at the userver root directory: ``` mkdir build_release cd build_release cmake -DCMAKEBUILDTYPE=Release .. make userver-samples-json2yaml ``` After that a tool is compiled an it could be used: ``` bash $ samples/json2yaml/userver-samples-json2yaml {"key": {"nested-key": [1, 2.0, "hello!", {"key-again": 42}]}} ^D key: nested-key: 1 2 hello! key-again: 42 ``` The code could be tested using any of the unit-testing frameworks, like Boost.Test, GTest, and so forth. However, to test the code with `pytest` some additional setup should be done: Inform CMake about the test and that it should be started by Python. Pass the path to the CMake built binary to Python: @snippet samples/json2yaml/CMakeLists.txt add_test Add a fixture to `conftest.py` to get the path to the CMake built binary: @snippet samples/json2yaml/tests/conftest.py pytest Write the test: @snippet samples/json2yaml/tests/test_basic.py pytest See the full example at: @ref samples/json2yaml/json2yaml.cpp @ref samples/json2yaml/CMakeLists.txt @ref samples/json2yaml/tests/conftest.py @ref samples/json2yaml/tests/test_basic.py @htmlonly <div class="bottom-nav"> @endhtmlonly @ref scripts/docs/en/userver/tutorial/multipartservice.md | @ref scripts/docs/en/userver/componentsystem.md @htmlonly </div> @endhtmlonly @example samples/json2yaml/json2yaml.cpp @example samples/json2yaml/CMakeLists.txt @example samples/json2yaml/tests/conftest.py @example samples/json2yaml/tests/test_basic.py
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: adr001-add-adr-log.md

id: adrs-adr001 title: 'ADR001: Architecture Decision Record (ADR) log' description: Architecture Decision Record (ADR) logs as a reference point for the team A decision was made to store ADRs in a log in the project repository There is a need to store big decisions made in a log as a reference point for the team, help with onboarding new members and give context to others interested in the project. People stop adding ADRs to the log and context gets lost
Project: YDB (App Definition and Development / Database)
File: folder.md

It's expressed as the `FOLDER` function in . Arguments: The path to the directory. An optional string with a list of meta attributes separated by a semicolon. The result is a table with three fixed columns: Path (`String`): The full name of the table. Type (`String`): The node type (table, map_node, file, document, and others). Attributes (`Yson`) is a Yson dictionary with meta attributes ordered in the second argument. Recommendations for use: To get only a list of tables, make sure to add `...WHERE Type == "table"`. Then, by optionally adding more conditions, you can use the aggregate function from the Path column to get only a list of paths and pass them to . Since the Path column is output in the same format as the result of the function , then they can be used to JOIN table attributes to its rows. We recommend that you work with the Attributes column using . {% note warning %} Use FOLDER with attributes containing large values with caution (`schema` could be one of those). A query with FOLDER applied to a folder with a large number of tables and a heavy attribute can create a heavy load on the YT wizard. {% endnote %} Examples: ```yql USE hahn; $table_paths = ( SELECT AGGREGATE_LIST(Path) FROM FOLDER("myfolder", "schema;rowcount") WHERE Type = "table" AND Yson::GetLength(Attributes.schema) > 0 AND Yson::LookupInt64(Attributes, "row_count") > 0 ); SELECT COUNT(*) FROM EACH($table_paths); ```
Project: KICS (Provisioning / Security & Compliance)
File: ee49557d-750c-4cc1-aa95-94ab36cbefde.md

title: Role With Privilege Escalation By Actions 'iam:CreatePolicyVersion' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ee49557d-750c-4cc1-aa95-94ab36cbefde Query name: Role With Privilege Escalation By Actions 'iam:CreatePolicyVersion' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Role with privilege escalation by actions 'iam:CreatePolicyVersion' and Resource set to '*'. For more information see https://rhinosecuritylabs.com/aws/aws-privilege-escalation-methods-mitigation/.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsiamrole" "cosmic" { name = "cosmic" } resource "awsiamrolepolicy" "testinline_policy" { name = "testinlinepolicy" role = awsiamrole.cosmic.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "iam:CreatePolicyVersion", ] Effect = "Allow" Resource = "*" }, ] }) } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamuser" "cosmic2" { name = "cosmic2" } resource "awsiamuserpolicy" "inlinepolicyruninstances2" { name = "inlinepolicyrun_instances" user = awsiamuser.cosmic2.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "ec2:Describe*", ] Effect = "Allow" Resource = "*" }, ] }) } ```
Project: Hexa (Provisioning / Security & Compliance)
File: CONTRIBUTING.md

Welcome to the Hexa community! This guide explains the various ways you can participate in and contribute to the work of policy orchestration. to stay up-to-date with the project and contribute. Before you can contribute, please sign the Please make sure to read and observe our Additional development information can be found . Contributors* are anyone that engages on a regular basis with the Hexa-IDQL project by updating documentation, doing code reviews, creating or responding to issues, contributing code, and so on. Maintainers* are the team responsible for overall project governance and project direction. Maintainers have final approval over PRs and setting priority within the project backlog. Please the current list of maintainers. The project backlog is maintained at this . Here you can see work in progress as well as the list of items in our backlog. If you want to be assigned to a user story, contact the maintainers. Intentions should be clear We encourage real-time linting environments such as Functions should not be documented with comments unless describing why; described why, not what Ignoring errors should be rare but explicit and marked with an underscore; `db.Exec(` versus `, = db.Exec(` Favor passing structs by value not reference; favor immutability Avoid locking or sleeping Avoid short, ambiguous names; favor clarity Support package names should end in `support`; common pkgs that support your application code, replaceable by an open source framework or library We use for building containers Ensure everything runs locally via `docker compose` Favor a single repository; to move quickly Favor replace-ability aka low coupling high cohesion; cmds, pkgs, support pkgs could be replaced with something better over time Ensure all code is tested Tests should be in their own package `package metricssupport_test` - with no access to private functions Test package names should include `_test` Avoid mocking database tests Avoid mocking HTTP tests Local unit, integration, and acceptance tests should run within a few seconds, not minutes Refactor ruthlessly Use "query" for non-database generated identifier fields, use "queryRow" for database generated or expected identifier fields (pk, fk, etc) The Hexa project has several providers for integrating with different cloud platforms or systems (Google, Microsoft, Amazon, etc.). If you would like to extend Hexa and build a new integration - go for it! We will be here to support your effort along the way. New providers can be added to our existing repo or, we can create a separate repo if that makes sense.
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: Cassandra.md

Cassandra source connector Read data from Apache Cassandra. | name | type | required | default value | |-|--|-|| | host | String | Yes | - | | keyspace | String | Yes | - | | cql | String | Yes | - | | username | String | No | - | | password | String | No | - | | datacenter | String | No | datacenter1 | | consistencylevel | String | No | LOCALONE | `Cassandra` cluster address, the format is `host:port` , allowing multiple `hosts` to be specified. Such as `"cassandra1:9042,cassandra2:9042"`. The `Cassandra` keyspace. The query cql used to search data though Cassandra session. `Cassandra` user username. `Cassandra` user password. The `Cassandra` datacenter, default is `datacenter1`. The `Cassandra` write consistency level, default is `LOCAL_ONE`. ```hocon source { Cassandra { host = "localhost:9042" username = "cassandra" password = "cassandra" datacenter = "datacenter1" keyspace = "test" cql = "select * from source_table" resulttablename = "source_table" } } ``` Add Cassandra Source Connector
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.0.18.1.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Blocker | renameTo(src, dst) does not restore src name in case of quota failure.* In case of quota failure on HDFS, rename does not restore source filename. | Blocker | [HOD] Make HOD to roll log files on the client* HOD client was modified to roll over client logs being written to the cluster directory. A new configuration parameter, hod.log-rollover-count, was introduced to specify how many rollover log files to retain.
Project: Docker Compose (App Definition and Development / Application Definition & Image Build)
File: compose_build.md

<!MARKERGENSTART--> Build or rebuild services | Name | Type | Default | Description | |:-|:--|:--|:| | `--build-arg` | `stringArray` | | Set build-time variables for services | | `--builder` | `string` | | Set builder to use | | `--dry-run` | | | Execute command in dry run mode | | `-m`, `--memory` | `bytes` | `0` | Set memory limit for the build container. Not supported by BuildKit. | | `--no-cache` | | | Do not use cache when building the image | | `--pull` | | | Always attempt to pull a newer version of the image | | `--push` | | | Push service images | | `-q`, `--quiet` | | | Don't print anything to STDOUT | | `--ssh` | `string` | | Set SSH authentications used when building service images. (use 'default' for using your default SSH Agent) | | `--with-dependencies` | | | Also build dependencies (transitively) | <!MARKERGENEND--> Services are built once and then tagged, by default as `project-service`. If the Compose file specifies an name, the image is tagged with that name, substituting any variables beforehand. See . If you change a service's `Dockerfile` or the contents of its build directory, run `docker compose build` to rebuild it.