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

+++ title = "googlecontainernode_pools resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecontainernode_pools" identifier = "inspec/resources/gcp/googlecontainernodepools.md googlecontainernodepools resource" parent = "inspec/resources/gcp" +++ A `googlecontainernode_pools` is used to test a Google NodePool resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlecontainernodepools(project: 'chef-gcp-inspec', location: 'europe-west2-a', clustername: 'gcp-inspec-kube-cluster') do its('initialnodecounts') { should include '1'} end ``` describe googlecontainernode_pools(project: 'chef-inspec-gcp') do its('count') { should be <= 10} end describe googlecontainernode_pools(project: 'chef-inspec-gcp') do its('nodepoolnames') { should include "us-east1-b" } end googlecontainernodepools(project: 'chef-inspec-gcp', location: 'europe-west2-a', clustername: 'inspec-gcp-cluster').where(nodepoolname: /^mypool/).nodepoolnames.each do |nodepoolname| describe googlecontainernodepool(project: 'chef-inspec-gcp', location: 'europe-west2-a', clustername: 'inspec-gcp-cluster', nodepoolname: nodepool_name) do it { should exist } its('status') { should eq 'RUNNING' } end end Properties that can be accessed from the `googlecontainernode_pools` resource: See the resource for more information. `nodepoolnames` : an array of `googlecontainernode_pool` name `configs` : an array of `googlecontainernode_pool` config `initialnodecounts` : an array of `googlecontainernodepool` initialnode_count `nodepoolstatuses` : an array of `googlecontainernode_pool` status `status_messages` : an array of `googlecontainernodepool` statusmessage `versions` : an array of `googlecontainernode_pool` version `autoscalings` : an array of `googlecontainernode_pool` autoscaling `managements` : an array of `googlecontainernode_pool` management `maxpodsconstraints` : an array of `googlecontainernodepool` maxpods_constraint `conditions` : an array of `googlecontainernode_pool` conditions `podipv4cidr_sizes` : an array of `googlecontainernodepool` podipv4cidrsize `clusters` : an array of `googlecontainernode_pool` cluster `locations` : an array of `googlecontainernode_pool` location 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: Carvel (App Definition and Development / Application Definition & Image Build)
File: README_ApiGatewayEvent.md

API Gateway events consist of a request that was routed to a Lambda function by API Gateway. When this happens, API Gateway expects the result of the function to be the response that API Gateway should respond with. The following is a sample class and Lambda function that receives Amazon API Gateway event record data as an input, writes some of the record data to CloudWatch Logs, and responds with a 200 status and the same body as the request. (Note that anything written to stdout or stderr will be logged as CloudWatch Logs events.) ```go package main import ( "context" "fmt" "github.com/aws/aws-lambda-go/events" "github.com/aws/aws-lambda-go/lambda" ) func handleRequest(ctx context.Context, request events.APIGatewayProxyRequest) (events.APIGatewayProxyResponse, error) { fmt.Printf("Processing request data for request %s.\n", request.RequestContext.RequestID) fmt.Printf("Body size = %d.\n", len(request.Body)) fmt.Println("Headers:") for key, value := range request.Headers { fmt.Printf(" %s: %s\n", key, value) } return events.APIGatewayProxyResponse{Body: request.Body, StatusCode: 200}, nil } func main() { lambda.Start(handleRequest) } ```
Project: KusionStack (Provisioning / Automation & Configuration)
File: kusion_preview.md

Preview a series of resource changes within the stack Preview a series of resource changes within the stack. Create, update or delete resources according to the intent described in the stack. By default, Kusion will generate an execution preview and present it for your approval before taking any action. ``` kusion preview [flags] ``` ``` kusion preview -w /path/to/workdir kusion preview -D name=test -D age=18 kusion preview --intent-file intent.yaml kusion preview --ignore-fields="metadata.generation,metadata.managedFields kusion preview -o json kusion preview --no-style=true ``` ``` -a, --all --detail Automatically show all preview details, combined use with flag --detail -D, --argument stringToString Specify the top-level argument (default []) -C, --backend-config strings backend-config config state storage backend --backend-type string backend-type specify state storage backend -d, --detail Automatically show preview details with interactive options (default true) -h, --help help for preview --ignore-fields strings Ignore differences of target fields --intent-file string Specify the intent file path as input, and the intent file must be located in the working directory or its subdirectories --no-style no-style sets to RawOutput mode and disables all of styling --operator string Specify the operator -o, --output string Specify the output format -Y, --setting strings Specify the command line setting files -w, --workdir string Specify the work directory ``` ``` --profile string Name of profile to capture. One of (none|cpu|heap|goroutine|threadcreate|block|mutex) (default "none") --profile-output string Name of the file to write the profile to (default "profile.pprof") ``` - Kusion is the Platform Orchestrator of Internal Developer Platform
Project: Seata (App Definition and Development / Database)
File: CODE_OF_CONDUCT.md

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at dev-seata@googlegroups.com. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. This Code of Conduct is adapted from the , version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq
Project: SPIRE (Provisioning / Key Management)
File: migrating_registration_api_clients.md

The `registration` API has been deprecated and removed. The new API surface is a superset of the previous functionality and provides consistent semantics, batch, and paging support. This document outlines the replacement RPCs when migrating clients away from the old registration API. | Registration RPC | Replacement RPC | Notes | ||-|| | `CreateEntry` | `Entry.BatchCreateEntry` | | | `CreateEntryIfNotExists` | `Entry.BatchCreateEntry` | The result code for the entry is ALREADY_EXISTS when the entry is preexisting. | | `DeleteEntry` | `Entry.BatchDeleteEntry` | | | `FetchEntry` | `Entry.GetEntry` | | | `FetchEntries` | `Entry.ListEntries` | | | `UpdateEntry` | `Entry.BatchUpdateEntry` | | | `ListByParentID` | `Entry.ListEntries` | See the `byparentid` filter. | | `ListBySelector` | `Entry.ListEntries` | See the `by_selectors` filter. | | `ListBySelectors` | `Entry.ListEntries` | See the `by_selectors` filter. | | `ListBySpiffeID` | `Entry.ListEntries` | See the `byspiffeid` filter. | | `ListAllEntriesWithPages` | `Entry.ListEntries` | See the `pagesize` / `pagetoken` fields. | | `CreateFederatedBundle` | `Bundle.BatchCreateFederatedBundle` | Alternatively, `Bundle.BatchSetFederatedBundle` can be used to "upsert" the federated bundle. | | `FetchFederatedBundle` | `Bundle.GetFederatedBundle` | | | `ListFederatedBundles` | `Bundle.ListFederatedBundles` | | | `UpdateFederatedBundle` | `Bundle.BatchUpdateFederatedBundle` | Alternatively, `Bundle.BatchSetFederatedBundle` can be used to "upsert" the federated bundle. | | `DeleteFederatedBundle` | `Bundle.BatchDeleteFederatedBundle` | | | `CreateJoinToken` | `Agent.CreateJoinToken` | | | `FetchBundle` | `Bundle.GetBundle` | | | `EvictAgent` | `Agent.DeleteAgent` | See the `Agent.BanAgent` RPC for a similar but distinct operation. | | `ListAgents` | `Agent.ListAgents` | Implementors must assume the RPC can page results arbitrarily, as deemed necessary by the server. | | `MintX509SVID` | `SVID.MintX509SVID` | | | `MintJWTSVID` | `SVID.MintJWTSVID` | | | `GetNodeSelectors` | `Agent.GetAgent` | Selectors are included in the agent information, unless explicitly filtered. | Unlike the Registration API (with the exception of `ListAllEntriesWithPages`), the new APIs `List*` operations all support paging. If clients provide a page size, the server will page the response, using the page size as an upper bound. However, even if clients do not provide a page size, the server is free to page the results. As such, clients must always be prepared to handle a paged response. It is important to note that the batch RPCs will not return a non-OK status unless there was a problem encountered outside of application of a single batch operation. Instead, individual batch operation results are communicated via per-batch operation results. Migrators should be careful to do proper error checking of not only the RPC result code, but the individual batch operation result codes. See the individual RPC documentation for the batching semantics.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: set.md

type: languages title: "Beam SQL extensions: SET and RESET Statement" aliases: /documentation/dsls/sql/set/ <!-- 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. --> Beam SQL's `SET` and `RESET` statements allow the user to [configure Pipeline Options](/documentation/programming-guide/#configuring-pipeline-options) via the SQL shell. These are the same Pipeline Options passed to other Beam applications on the command line in the `--<option>=<value>` format. ``` SET option = value ``` The SET command sets a Pipeline Option. `option`: The case sensitive name of the Pipeline Option, specified as an . `value`: The case sensitive value of the Pipeline Option, specified as an . For flag options that have no value on the command line, use `true`. ``` RESET option ``` The RESET command resets a Pipeline Option to its default value. `option`: The case sensitive name of the Pipeline Option, specified as an . ```SET project = `mygcpproject` ```: Sets the default GCP project to`mygcpproject`. `SET runner = DataflowRunner`: Sets the pipeline to run on Dataflow.
Project: ArangoDB (App Definition and Development / Database)
File: explicit_inplace_error_constructor_il.md

+++ title = "`explicit basicresult(inplacetypet<errortypeifenabled>, std::initializerlist<U>, Args ...)`" description = "Explicit inplace error constructor. Available if `predicate::enableinplaceerrorconstructor<std::initializerlist<U>, Args ...>` is true. Constexpr, triviality and noexcept propagating." categories = ["constructors", "explicit-constructors", "inplace-constructors"] weight = 430 +++ Explicit inplace error constructor. Calls {{% api "void onresultinplaceconstruction(T *, inplacetypet<U>, Args &&...) noexcept" %}} with `this`, `inplacetype<errortype>`, `std::initializer_list<U>` and `Args ...`. Requires: `predicate::enableinplaceerrorconstructor<std::initializerlist<U>, Args ...>` is true. Complexity: Same as for the `errortype` constructor which accepts `std::initializerlist<U>, Args ...`. Constexpr, triviality and noexcept of underlying operations is propagated. Guarantees: If an exception is thrown during the operation, the state of the Args is left indeterminate.
Project: ClickHouse (App Definition and Development / Database)
File: graphite_retentions.md

slug: /en/operations/system-tables/graphite_retentions Contains information about parameters which are used in tables with engines. Columns: `configname` (String) - `graphiterollup` parameter name. `regexp` (String) - A pattern for the metric name. `function` (String) - The name of the aggregating function. `age` (UInt64) - The minimum age of the data in seconds. `precision` (UInt64) - How precisely to define the age of the data in seconds. `priority` (UInt16) - Pattern priority. `is_default` (UInt8) - Whether the pattern is the default. `Tables.database` (Array(String)) - Array of names of database tables that use the `config_name` parameter. `Tables.table` (Array(String)) - Array of table names that use the `config_name` parameter.
Project: SPIFFE (Provisioning / Key Management)
File: BRANDON_LUM.md

Brandon Lum has many years under his belt in the authentication, authorization, and trusted computing spaces. As the CNCF Security TAG co-chair, he is also intimately familiar with the cloud native community, open source software, and broader infosec industry trends. Brandon is one of the founding maintainers of project Tornjak (a control plane and web UI for managing multiple SPIRE deployments), and given his experience in both the technical and social aspects of projects like SPIFFE/SPIRE, I feel he would be a great (and very effective) member of the SSC. GitHub Handle: @lumjjb Email Address: REDACTED LinkedIn Profile: https://www.linkedin.com/in/brandon-lum-a7b79418/ Current Affiliation: Google
Project: Pravega (App Definition and Development / Streaming & Messaging)
File: CONTRIBUTING.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. --> Happy hacking!
Project: external-secrets (Provisioning / Security & Compliance)
File: MAINTAINERS.md

describes governance guidelines and maintainer responsibilities. | Maintainer | GitHub ID | Affiliation | | | | -- | | RealName Here | | | | RealName Here | | | | RealName Here | | | | RealName Here | | | | RealName Here | | | | RealName Here | | | | ESO Feature Area | Lead | | -- | :: | | Technical Lead | | | Chief Architects | | | Webhooks | | | Setup, Installation, Upgrade Experience | | | Helm Chart & HA | | | Operator & Day 2 Operations | | | Security | TBD | | User Interface/Usability/User Experience | Meina Zhou (zhoumeina) | | Scale & Performance | | | Documentation | | | Releases | | | QA, Test Automation | | | Community Management | | | Product Management | | RealName Here, RealName Here, RealName Here, RealName Here, RealName Here,
Project: Meshery (Provisioning / Automation & Configuration)
File: parsec.md

layout: integration title: Parsec subtitle: Collaborative and visual infrastructure as code for Parsec image: /assets/img/integrations/parsec/icons/color/parsec-color.svg permalink: extensibility/integrations/parsec docURL: https://docs.meshery.io/extensibility/integrations/parsec description: integrations-category: Security & Compliance integrations-subcategory: Security & Compliance 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: Monokle (App Definition and Development / Application Definition & Image Build)
File: faq.md

You will need to install the following two prerequisites to successfully run Monokle Desktop: - Required for functionality. - Required for and functionality. Monokle Desktop supports Windows, MacOS and Linux. Get the latest installers for MacOS and Windows on . For running Monokle Desktop on Linux, run it from the source, following the steps as outlined in the documentation. While adding new clusters, a valid kubeconfig file is required. Please check that all the needed configuration settings are present in your kubeconfig file are valid. For more detail read the documentation. You need to install and configure kubectl for previewing files. It helps to debug your configurations before you deploy them to your cluster. Yes, Monokle Desktop allows you to navigate and preview the output of a Helm chart for an existing values files. Read more at . You can launch multiple project windows using the option. It allows you to work on multiple folders or clusters simultaneously; thus visual navigation for the multiple pages becomes simpler and faster. Yes, Monokle Desktop can be used for creating / editing / debugging manifests before they are deployed to a cluster using a CD tool like ArgoCD or Flux. You can navigate to the resources created by Kustomize or Helm in the navigator. Hover over the resources and hit the button to perform the preview and see the generated resources in the navigator. The source editor provides an autocomplete option for only native Kubernetes resources. Therefore, the autocomplete feature is not available for any other resources except the resources in the YAML manifests. The source editor automatically saves the current changes in your resource manifests as long as they are valid YAML files.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: fix-11798.en.md

Fixed the issue where the node could not start after executing `./bin/emqx data import [FILE]`. And strongly bind apikey's `apikeykey` to `apikeyname`. `apikeykey` will generate a unique value from the given human-readable `apikeyname` when generating an apikey using dashboard. `apikeyname` will be a unique value generated by `apikeykey` when using bootstrap file to generate apikey, .
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_cluster_hscale.md

title: kbcli cluster hscale Horizontally scale the specified components in the cluster. ``` kbcli cluster hscale NAME [flags] ``` ``` kbcli cluster hscale mycluster --components=mysql --replicas=3 ``` ``` --auto-approve Skip interactive approval before horizontally scaling the cluster --components strings Component names to this operations --dry-run string[="unchanged"] Must be "client", or "server". If with client strategy, only print the object that would be sent, and no data is actually sent. If with server strategy, submit the server-side request, but no data is persistent. (default "none") -h, --help help for hscale --name string OpsRequest name. if not specified, it will be randomly generated -o, --output format Prints the output in the specified format. Allowed values: JSON and YAML (default yaml) --replicas int Replicas with the specified components --ttlSecondsAfterSucceed int Time to live after the OpsRequest succeed ``` ``` --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 ``` - Cluster command.