cwielenb/CNCF-Dataset huggingface dataset:
Project: YugabyteDB (App Definition and Development / Database)
File: yba_provider_onprem_instance-types_add.md

Add an instance type to YugabyteDB Anywhere on-premises provider Add an instance type to YugabyteDB Anywhere on-premises provider ``` yba provider onprem instance-types add [flags] ``` ``` --instance-type-name string [Required] Instance type name. --volume stringArray [Required] Volumes associated per node of an instance type. Minimum number of required volumes = 1. Provide the following comma separated fields as key-value pairs:"type=<volume-type>,size=<volume-size>,mount-points="<quoted-comma-separated-mount-points>"". mount-points is a required key-value. Volume type (Defaults to SSD, Allowed values: EBS, SSD, HDD, NVME) and Volume size (Defaults to 100) are optional. Each volume needs to be added using a separate --volume flag. --mem-size float [Optional] Memory size of the node in GB. (default 8) --num-cores float [Optional] Number of cores per node. (default 4) --tenancy string [Optional] Tenancy of the nodes of this type. Allowed values (case sensitive): Shared, Dedicated, Host. -h, --help help for add ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -n, --name string [Optional] The name of the provider for the action. Required for create, delete, describe, instance-types and nodes. -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage YugabyteDB Anywhere onprem instance types
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.7.9.md

layout: release date: 2024-01-08 tag: v0.7.9 fix: broken 'Security' category @leecalcote (#9884) Remove schemas from `meshery/meshery`. @MUzairS15 (#9876) [Models] Update connection transitions and middleware. @MUzairS15 (#9881) Reuse tooltip @sudhanshutech (#9885) Bump @rjsf/utils from 5.8.1 to 5.15.1 in /ui @dependabot (#9803) Bump @rjsf/utils from 5.8.1 to 5.15.1 in /ui @dependabot (#9803) chore(deps): Bump github.com/cloudflare/circl from 1.3.3 to 1.3.7 @dependabot (#9878) docs: rearrange extensions @leecalcote (#9883) Thank you to our contributors for making this release possible: @MUzairS15, @Yashsharma1911, @dependabot, @leecalcote and @sudhanshutech
Project: Meshery (Provisioning / Automation & Configuration)
File: 02-07-2023-21-56-02_15bfb367.md

timestamp: "2023-02-07 21:42:13 UTC Tue" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "v0.6.50" k8s-distro: minikube k8s-version: "v1.24.7" service-mesh: Consul service-mesh-version: "v1.0.4" tests: consul-client: null consul-server: null overall-status: "failing"
Project: Pravega (App Definition and Development / Streaming & Messaging)
File: connectors.md

<!-- Copyright Pravega Authors. 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. --> Connectors allow integrating Pravega with different data sources and sinks. Currently, Pravega offers the following connectors: : The Flink Connector enables building end-to-end stream processing pipelines with Pravega in . This also allows reading and writing data to external data sources and sinks via Flink Connector. : Connector to read and write Pravega Streams with , a high-performance analytics engine for batch and streaming data. The connector can be used to build end-to-end stream processing pipelines that use Pravega as the stream storage and message bus, and Apache Spark for computation over the streams. : Implements both the input and the output format interfaces for . It leverages Pravega batch client to read existing events in parallel; and uses write API to write events to Pravega streams. : is a distributed SQL query engine for big data. Presto uses connectors to query storage from different storage sources. This connector allows Presto to query storage from Pravega streams. : A Pravega connector for the . : Connector to read and write Pravega streams with . In addition to the connectors provided by the Pravega organization, open-source contributors have also created connectors for external projects: : The project is an open source initiative to implement stream-aware, reactive, integration pipelines for Java and Scala. It is built on top of Akka Streams, and has been designed from the ground up to understand streaming natively and provide a DSL for reactive and stream-oriented programming, with built-in support for back-pressure. This Alpakka Pravega connector lets you connect Pravega to Akka Streams. : is a framework for building highly scalable event-driven microservices connected with shared messaging systems. The Pravega Binder connects Pravega to , which provides tools to create complex topologies for streaming and batch data pipelines. The data pipelines consist of Spring Boot apps, built using the Spring Cloud Stream or Spring Cloud Task microservice frameworks. : is an in-memory event-sourced ACID-transactional replicated object graph engine. The Pravega connector allows Memstate to use it as storage provider for persistence and global message ordering.
Project: Apache RocketMQ (App Definition and Development / Streaming & Messaging)
File: Debug_In_Idea.md

To download the Maven dependencies required for running RocketMQ, you can use the following command:`mvn clean install -Dmaven.test.skip=true` Ensure successful local compilation. The startup class for NameServer is located in `org.apache.rocketmq.namesrv.NamesrvStartup`. Add environment variable `ROCKETMQ_HOME=<rocketmq repository directory>` in `Idea-Edit Configurations`. Run NameServer and if the following log output is observed, it indicates successful startup. ```shell The Name Server boot success. serializeType=JSON, address 0.0.0.0:9876 ``` The startup class for Broker is located in`org.apache.rocketmq.broker.BrokerStartup` Create the `/rocketmq/conf/broker.conf` file or simply copy it from the official release package. ```shell brokerClusterName = DefaultCluster brokerName = broker-a brokerId = 0 deleteWhen = 04 fileReservedTime = 48 brokerRole = ASYNC_MASTER flushDiskType = ASYNC_FLUSH namesrvAddr = 127.0.0.1:9876 ``` Add the runtime parameter `-c /Users/xxx/rocketmq/conf/broker.conf` and the environment variable `ROCKETMQ_HOME=<rocketmq repository directory>` in `Idea-Edit Configurations`. Run the Broker and if the following log is observed, it indicates successful startup. ```shell The broker[broker-a,192.169.1.2:10911] boot success... ``` RocketMQ startup is now complete. You can use the examples provided in `/example` to send and consume messages. RocketMQ 5.x introduced the Proxy mode. Using the `LOCAL` mode eliminates the need for `Step2`. The startup class is located at `org.apache.rocketmq.proxy.ProxyStartup`. Add the environment variable `ROCKETMQ_HOME=<rocketmq repository directory>` in `Idea-Edit Configurations`. Create a new configuration file named `rmq-proxy.json` in the `/conf/` directory. ```json { "rocketMQClusterName": "DefaultCluster", "nameSrvAddr": "127.0.0.1:9876", "proxyMode": "local" } ``` Run the Proxy, and if the following log is observed, it indicates successful startup. ```shell Sat Aug 26 15:29:33 CST 2023 rocketmq-proxy startup successfully ```
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.0.23.5.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Major | hadoop.util.PureJavaCrc32 cache hit-ratio is low for static data* Speed up Crc32 by improving the cache hit-ratio of hadoop.util.PureJavaCrc32 | Major | Add a separate logger for block state change logs to enable turning off those logs* Add a separate logger "BlockStateChange" for block state change logs.
Project: ClickHouse (App Definition and Development / Database)
File: v21.7.2.7-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Allow to start clickhouse-client with unreadable working directory. (). Backported in : `CAST` from `Date` to `DateTime` (or `DateTime64`) was not using the timezone of the `DateTime` type. It can also affect the comparison between `Date` and `DateTime`. Inference of the common type for `Date` and `DateTime` also was not using the corresponding timezone. It affected the results of function `if` and array construction. Closes . (). Backported in : Fix assertion in PREWHERE with non-uint8 type, close . (). Backported in : Fix `ALTER MODIFY COLUMN` of columns, which participates in TTL expressions. (). Backported in : Fix rare bug with `DROP PART` query for `ReplicatedMergeTree` tables which can lead to error message `Unexpected merged part intersecting drop range`. (). Backported in : Fix ARM exception handling with non default page size. Fixes . Fixes . Fixes . Fixes . Fixes . Fixes . Fixes . Fixes . Fixes . Fixes . Fixes . (). Backported in : Fix extremely long backoff for background tasks when the background pool is full. Fixes . (). Backported in : Fix crash on call dictGet() with bad arguments. (). Backported in : Fix possible deadlock during query profiler stack unwinding. Fixes . (). Backported in : Fix formatting of type `Map` with integer keys to `JSON`. (). Backported in : Fix wrong thread estimation for right subquery join in some cases. Close . (). ExpressionCache destruction fix (). Proper fix of serialization of type Map to JSON ().
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.12.10.md

RabbitMQ `3.12.10` is a maintenance release in the `3.12.x` . Please refer to the upgrade section from the if upgrading from a version prior to 3.12.0. This release requires Erlang 25 and supports Erlang versions up to `26.1.x`. has more details on Erlang version requirements for RabbitMQ. As of 3.12.0, RabbitMQ requires Erlang 25. Nodes will fail to start on older Erlang releases. Users upgrading from 3.11.x (or older releases) on Erlang 25 to 3.12.x on Erlang 26 (both RabbitMQ and Erlang are upgraded at the same time) must consult the first. Release notes can be found on GitHub at . Avoids two Shovels being started after an upgrade from `3.12.6` or older versions. Two Shovels running concurrently would still transfer messages but because they act as competing consumers (and publishers), this affected message ordering in the target queue. Contributed by @gomoripeti (CloudAMQP). GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.12.10.tar.xz` instead of the source tarball produced by GitHub.
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.3.1.1.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Major | Flexible Visual Studio support* <!-- markdown --> This change updates the Microsoft Windows build directions to be more flexible with regards to Visual Studio compiler versions: Any version of Visual Studio 2010 Pro or higher may be used. MSBuild Solution files are converted to the version of VS at build time Example command file to set command paths prior to using maven so that conversion works Additionally, Snappy and ISA-L that use bin as the location of the DLL will now be recognized without having to set their respective lib paths if the prefix is set. Note to contributors: It is very important that solutions for any patches remain at the VS 2010-level. | Major | WASB: PageBlobInputStream.skip breaks HBASE replication* WASB: Bug fix to support non-sequential page blob reads. Required for HBASE replication. | Major | WASB: hflush() and hsync() regression* WASB: Bug fix for recent regression in hflush() and hsync(). | Major | Add dfsAdmin command to query if "upgrade" is finalized* New command is added to dfsadmin. hdfs dfsadmin [-upgrade [query \| finalize] -upgrade query gives the upgradeStatus -upgrade finalize is equivalent to -finalizeUpgrade. | Minor | Upgrade Azure Storage Sdk version to 7.0.0 and update corresponding code blocks* WASB: Fix Spark process hang at shutdown due to use of non-daemon threads by updating Azure Storage Java SDK to 7.0 | Major | hdfs mover -p /path times out after 20 min* Mover could have fail after 20+ minutes if a block move was enqueued for this long, between two DataNodes due to an internal constant that was introduced for Balancer, but affected Mover as well. The internal constant can be configured with the dfs.balancer.max-iteration-time parameter after the patch, and affects only the Balancer. Default is 20 minutes.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_project_alert_policies.md

+++ title = "googleprojectalert_policies resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleprojectalert_policies" identifier = "inspec/resources/gcp/googleprojectalertpolicies.md googleprojectalertpolicies resource" parent = "inspec/resources/gcp" +++ A `googleprojectalert_policies` is used to test a Google AlertPolicy resource ```ruby describe googleprojectalert_policies(project: 'chef-gcp-inspec') do it { should exist } its('policydisplaynames') { should include 'Display'} its('combiners') { should include 'OR'} end ``` describe googleprojectalert_policies(project: 'chef-inspec-gcp') do its('count') { should be <= 100} end describe googleprojectalert_policies(project: 'chef-inspec-gcp') do its('policy_names') { should include 'projects/spaterson-project/alertPolicies/9271751234503117449' } end describe googleprojectalert_policies(project: 'chef-inspec-gcp') do its('policydisplaynames') { should_not include 'banned policy' } end describe googleprojectalert_policies(project: 'chef-inspec-gcp') do its('policyenabledstates') { should_not include false } end Properties that can be accessed from the `googleprojectalert_policies` resource: See the resource for more information. `policy_names` : an array of `googleprojectalert_policy` name `policydisplaynames` : an array of `googleprojectalertpolicy` displayname `combiners` : an array of `googleprojectalert_policy` combiner `creation_records` : an array of `googleprojectalertpolicy` creationrecord `policyenabledstates` : an array of `googleprojectalert_policy` enabled `conditions` : an array of `googleprojectalert_policy` conditions `notification_channels` : an array of `googleprojectalertpolicy` notificationchannels `user_labels` : an array of `googleprojectalertpolicy` userlabels `documentations` : an array of `googleprojectalert_policy` documentation 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: KICS (Provisioning / Security & Compliance)
File: 5b6d53dd-3ba3-4269-b4d7-f82e880e43c3.md

title: Liveness Probe Is Not Defined hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 5b6d53dd-3ba3-4269-b4d7-f82e880e43c3 Query name: Liveness Probe Is Not Defined Platform: Terraform Severity: <span style="color:#5bc0de">Info</span> Category: Availability URL: In case of an unresponsive container, a Liveness Probe can help your application become more available since it restarts the container. However, it can lead to cascading failures. Define one if you really need it<br> ```tf title="Positive test num. 1 - tf file" hl_lines="7" resource "kubernetes_pod" "test" { metadata { name = "terraform-example" } spec { container { image = "nginx:1.7.9" name = "example" env { name = "environment" value = "test" } port { container_port = 8080 } } dns_config { nameservers = ["1.1.1.1", "8.8.8.8", "9.9.9.9"] searches = ["example.com"] option { name = "ndots" value = 1 } option { name = "use-vc" } } dns_policy = "None" } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="27" resource "kubernetes_deployment" "example" { metadata { name = "terraform-example" labels = { test = "MyExampleApp" } } spec { replicas = 3 selector { match_labels = { test = "MyExampleApp" } } template { metadata { labels = { test = "MyExampleApp" } } spec { container { image = "nginx:1.7.8" name = "example" resources { limits = { cpu = "0.5" memory = "512Mi" } requests = { cpu = "250m" memory = "50Mi" } } } } } } } ``` ```tf title="Negative test num. 1 - tf file" resource "kubernetes_pod" "test" { metadata { name = "terraform-example" } spec { container { image = "nginx:1.7.9" name = "example" env { name = "environment" value = "test" } port { container_port = 8080 } liveness_probe { http_get { path = "/nginx_status" port = 80 http_header { name = "X-Custom-Header" value = "Awesome" } } initialdelayseconds = 3 period_seconds = 3 } } dns_config { nameservers = ["1.1.1.1", "8.8.8.8", "9.9.9.9"] searches = ["example.com"] option { name = "ndots" value = 1 } option { name = "use-vc" } } dns_policy = "None" } } ``` ```tf title="Negative test num. 2 - tf file" resource "kubernetes_deployment" "example" { metadata { name = "terraform-example" labels = { test = "MyExampleApp" } } spec { replicas = 3 selector { match_labels = { test = "MyExampleApp" } } template { metadata { labels = { test = "MyExampleApp" } } spec { container { image = "nginx:1.7.8" name = "example" resources { limits = { cpu = "0.5" memory = "512Mi" } requests = { cpu = "250m" memory = "50Mi" } } liveness_probe { http_get { path = "/nginx_status" port = 80 http_header { name = "X-Custom-Header" value = "Awesome" } } initialdelayseconds = 3 period_seconds = 3 } } } } } } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: aws-applicationautoscaling-controller.md

layout: integration title: AWS Applilcation Autoscaling subtitle: Collaborative and visual infrastructure as code for AWS Applilcation Autoscaling image: /assets/img/integrations/aws-applicationautoscaling-controller/icons/color/aws-applicationautoscaling-controller-color.svg permalink: extensibility/integrations/aws-applicationautoscaling-controller docURL: https://docs.meshery.io/extensibility/integrations/aws-applicationautoscaling-controller description: integrations-category: Provisioning integrations-subcategory: Management Governance registrant: GitHub components: name: adopted-resource colorIcon: assets/img/integrations/aws-applicationautoscaling-controller/components/adopted-resource/icons/color/adopted-resource-color.svg whiteIcon: assets/img/integrations/aws-applicationautoscaling-controller/components/adopted-resource/icons/white/adopted-resource-white.svg description: name: scalable-target colorIcon: assets/img/integrations/aws-applicationautoscaling-controller/components/scalable-target/icons/color/scalable-target-color.svg whiteIcon: assets/img/integrations/aws-applicationautoscaling-controller/components/scalable-target/icons/white/scalable-target-white.svg description: name: field-export colorIcon: assets/img/integrations/aws-applicationautoscaling-controller/components/field-export/icons/color/field-export-color.svg whiteIcon: assets/img/integrations/aws-applicationautoscaling-controller/components/field-export/icons/white/field-export-white.svg description: name: scaling-target colorIcon: assets/img/integrations/aws-applicationautoscaling-controller/components/scaling-target/icons/color/scaling-target-color.svg whiteIcon: assets/img/integrations/aws-applicationautoscaling-controller/components/scaling-target/icons/white/scaling-target-white.svg description: name: scaling-policy colorIcon: assets/img/integrations/aws-applicationautoscaling-controller/components/scaling-policy/icons/color/scaling-policy-color.svg whiteIcon: assets/img/integrations/aws-applicationautoscaling-controller/components/scaling-policy/icons/white/scaling-policy-white.svg description: 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: ArangoDB (App Definition and Development / Database)
File: copy_file3.md

+++ title = "Auto-throwing filesystem_error" description = "" weight = 30 tags = ["default-actions", "value"] +++ Something not mentioned at all until now (and properly described in the next section, ) is that Outcome can be programmed take various actions when the user tries to observe `.value()` when there is no value, and so on for the other possible state observations. Seeing as we are replacing the throwing overload of `copy_file()` in the Filesystem TS with a `result` returning edition instead, it would make sense if an attempt to observe the value of an unsuccessful `fs_result` threw the exact same `filesystem_error` as the Filesystem TS does. Telling Outcome how to throw a `filesystem_error` with payload of the failing paths is easy: {{% snippet "outcomepayload.cpp" "filesystemapicustomthrow" %}} Reference documentation for the above functions: {{% api "void trythrowstdexceptionfromerror(std::errorcode ec, const std::string &msg = std::string{})" %}} Usage of our new "upgraded" Filesystem `copy_file()` might now be as follows: {{% snippet "outcomepayload.cpp" "filesystemapicustomthrow_demo" %}}