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

The following is a sample Lambda functions that are used for custom authentication with Cognito User Pools. These Lambda triggers issue and verify their own challenges as part of a user pool . Please see instructions for setting up the Cognito triggers at https://docs.aws.amazon.com/cognito/latest/developerguide/user-pool-lambda-challenge.html Define Auth Challenge Lambda Trigger: ```go package main import ( "fmt" "github.com/aws/aws-lambda-go/lambda" "github.com/aws/aws-lambda-go/events" ) func handler(event events.CognitoEventUserPoolsDefineAuthChallenge) (events.CognitoEventUserPoolsDefineAuthChallenge, error) { fmt.Printf("Define Auth Challenge: %+v\n", event) return event, nil } func main() { lambda.Start(handler) } ``` Create Auth Challenge Lambda Trigger: ```go package main import ( "fmt" "github.com/aws/aws-lambda-go/lambda" "github.com/aws/aws-lambda-go/events" ) func handler(event events.CognitoEventUserPoolsCreateAuthChallenge) (events.CognitoEventUserPoolsCreateAuthChallenge, error) { fmt.Printf("Create Auth Challenge: %+v\n", event) return event, nil } func main() { lambda.Start(handler) } ``` Verify Auth Challenge Response Lambda Trigger: ```go package main import ( "fmt" "github.com/aws/aws-lambda-go/lambda" "github.com/aws/aws-lambda-go/events" ) func handler(event events.CognitoEventUserPoolsVerifyAuthChallenge) (events.CognitoEventUserPoolsVerifyAuthChallenge, error) { fmt.Printf("Verify Auth Challenge: %+v\n", event) return event, nil } func main() { lambda.Start(handler) } ```
Project: Docker Compose (App Definition and Development / Application Definition & Image Build)
File: compose_events.md

<!MARKERGENSTART--> Receive real time events from containers | Name | Type | Default | Description | |:|:--|:--|:| | `--dry-run` | | | Execute command in dry run mode | | `--json` | | | Output events as a stream of json objects | <!MARKERGENEND--> Stream container events for every container in the project. With the `--json` flag, a json object is printed one per line with the format: ```json { "time": "2015-11-20T18:01:03.615550", "type": "container", "action": "create", "id": "213cf7...5fc39a", "service": "web", "attributes": { "name": "applicationweb1", "image": "alpine:edge" } } ``` The events that can be received using this can be seen .
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_access_context_manager_service_perimeters.md

+++ title = "googleaccesscontextmanagerservice_perimeters resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleaccesscontextmanagerservice_perimeters" identifier = "inspec/resources/gcp/googleaccesscontextmanagerserviceperimeters.md googleaccesscontextmanagerserviceperimeters resource" parent = "inspec/resources/gcp" +++ A `googleaccesscontextmanagerservice_perimeters` is used to test a Google ServicePerimeter resource ```ruby describe.one do googleaccesscontextmanageraccesspolicies(orgid: '190694428152').names.each do |policy_name| describe googleaccesscontextmanagerserviceperimeters(policyname: policy_name) do its('names') { should include 'restrict_all' } its('titles') { should include 'restrict_all' } end end end ``` Properties that can be accessed from the `googleaccesscontextmanagerservice_perimeters` resource: See the resource for more information. `titles` : an array of `googleaccesscontextmanagerservice_perimeter` title `descriptions` : an array of `googleaccesscontextmanagerservice_perimeter` description `create_times` : an array of `googleaccesscontextmanagerserviceperimeter` createtime `update_times` : an array of `googleaccesscontextmanagerserviceperimeter` updatetime `perimeter_types` : an array of `googleaccesscontextmanagerserviceperimeter` perimetertype `statuses` : an array of `googleaccesscontextmanagerservice_perimeter` status `specs` : an array of `googleaccesscontextmanagerservice_perimeter` spec `useexplicitdryrunspecs` : an array of `googleaccesscontextmanagerserviceperimeter` useexplicitdryrun_spec `parents` : an array of `googleaccesscontextmanagerservice_perimeter` parent `names` : an array of `googleaccesscontextmanagerservice_perimeter` name This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method.
Project: Meshery (Provisioning / Automation & Configuration)
File: latest-release.md

layout: blank title: Latest Release permalink: project/releases/latest abstract: Return only the latest release of Meshery version information language: en type: project category: none list: exclude {% assign sorted_release = site.releases | sort: 'date' | reverse %} {%- for release in sorted_release limit:1 offset:0 -%} {{ release.tags }} {% endfor %}
Project: PolarDB (App Definition and Development / Database)
File: CONTRIBUTING.md

Contributors are welcome to submit their code and ideas. In a long run, we hope this project can be managed by developers from both inside and outside Alibaba. Sign CLA of PolarDB-X: Please download PolarDB-X . Follow the instructions to sign it. Here is a checklist to prepare and submit your PR (pull request). Create your own Github branch by forking PolarDB-X related repositories. Checkout for how to start PolarDB-X from source code. Push changes to your personal fork and make sure they follow our coding style (descriped in each repository) Create a PR with a detail description, if commit messages do not express themselves. Submit PR for review and address all feedbacks. Wait for merging (done by committers). Let's use an example to walk through the list. There are many PolarDB-X related repositories, take PolarDB-X SQL and PolarDB-X Glue for an example. On Github page of and , Click fork button to create your own polardbx-sql and polardbx-glue repository. ```bash git clone --recursive https://github.com/your_github/polardbx-sql.git ``` ```bash git branch yourgithubidfeaturename ``` ```bash git status git add files-to-change git commit -m "messages for your modifications" ``` ```bash git checkout develop git pull git checkout yourgithubidfeaturename git rebase develop -- resolve conflict, compile and test -- git push --recurse-submodules=on-demand origin yourgithubidfeaturename ``` Click New pull request or Compare & pull request button, choose to compare branches polardb/polardbx-sql/main and yourgithub/yourgithubidfeature_name, and write PR description. Resolve all problems raised by reviewers and update PR. It is done by PolarDB-X committers. _ Copyright Alibaba Group, Inc.
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: drush-9.md

description: >- Lagoon defaults to Drush 8. Drush 9 is used if you install Drush 9 into your Drupal site via Composer. Unfortunately, Drush 9 does not provide the ability to inject dynamic site aliases like Drush 8 did. We are working with the Drush team to implement this again. In the meantime, we have a workaround that allows you to use Drush 9 with Lagoon. Drush 9 provides a new command, `drush site:alias-convert` , which can convert Drush 8-style site aliases over to the Drush 9 YAML site alias style. This will create a on- time export of the site aliases currently existing in Lagoon, and save them in `/app/drush/sites` . These are then used when running a command like `drush sa`. In order to be able to use `drush site:alias-convert` , you need to do the following: Rename the `aliases.drushrc.php` inside the `drush` folder to `lagoon.aliases.drushrc.php`. You can now convert your Drush aliases by running the following command in your project using the `cli` container: ```bash title="Generate Site Aliases" docker-compose exec cli drush site:alias-convert /app/drush/sites --yes ``` It's good practice to commit the resulting YAML files into your Git repository, so that they are in place for your fellow developers. In Drush 9, all site aliases are prefixed with a group. In our case, this is `lagoon`. You can show all site aliases with their prefix via: ```bash title="Show all site aliases" drush sa --format=list ``` and to use them: ```bash title="Using Drush site alias" drush @lagoon.main ssh ``` If a new environment in Lagoon has been created, you can run `drush site:alias-convert` to update the site aliases file. If running this command does not update `lagoon.site.yml`, try deleting `lagoon.site.yml` first, and then re-run `drush site:alias-convert`. If you would like to sync files from a local environment to a remote environment, you need to pass additional parameters: ```bash title="Drush rsync" drush rsync @self:%files @lagoon.main:%files -- --omit-dir-times --no-perms --no-group --no-owner --chmod=ugo=rwX ``` This also applies to syncing one remote environment to another, if you're not using the Lagoon tasks UI to copy files between environments. For example, if you wanted to sync the files from `@lagoon.main` to `@lagoon.dev` , and ran `drush rsync @lagoon.main @lagoon.dev` locally, without the extra parameters, you would probably run into a "Cannot specify two remote aliases" error. To resolve this, you would first need to SSH into your destination environment `drush @lagoon.dev ssh`, and then execute the `rsync` command with parameters similar to the above: ```bash title="Drush rsync" drush rsync @lagoon.main:%files @self:%files -- --omit-dir-times --no-perms --no-group --no-owner --chmod=ugo=rwX ``` This is not necessary if you `rsync` from a remote to a local environment. Also, we're to find a way to inject this automatically.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: mac-address.md

<<Container|Pod>> network interface MAC address (e.g. 92:d0:c6:0a:29:33) This option can only be used if the <<container|pod>> is joined to only a single network - i.e., --network=_network-name_ is used at most once - and if the <<container|pod>> is not joining another container's network namespace via --network=container:_id_. Remember that the MAC address in an Ethernet network must be unique. The IPv6 link-local address is based on the device's MAC address according to RFC4862. To specify multiple static MAC addresses per <<container|pod>>, set multiple networks using the --network option with a static MAC address specified for each using the `mac` mode for that option.
Project: Harbor (Provisioning / Container Registry)
File: 5-01-OVA-networking.md

Test 5-01 - OVA Networking Settings During Deployment ======= To verify that an OVA version of Harbor can be configured to obtain IP address from DHCP or static IP. User guide, installation guide of Harbor OVA version. This test requires an OVA binary of Harbor. A vCenter, at least an ESX host, and a network that supports DHCP. A linux host with Docker CLI installed (Docker client). From vSphere Web Client, import Harbor's OVA onto an ESX host. In the deployment wizard, enter different passwords of Linux root user, Harbor admin user and MySQL root user. Leave the networking settings blank. Power on the imported OVA. Wait a few minutes for the VM's booting and its IP address comes up in vCenter. (may need to refresh in Web Client) Open a browser and enter http://VMIPaddress. Log in as admin user of Harbor. Create a new project. On a Docker client host, use `docker login <harbor_host>` command to log in as the admin user. Run some `docker push` and `docker pull` commands to push images to the project and pull from the project. On vSphere, open the console of Harbor's VM, log in as root user using the password entered during deployment. Check the network IP address of the VM. From vSphere Web Client, import a new Harbor's OVA onto an ESX host. Repeat Step 2-12, except in Step 3, enter static network settings of the OVA, such as static IP, DNS, gateway, hostname. In Step 1-11, everything should work without errors. The passwords entered during deployment should work in Step 7, 9 and 11. In Step 14, basically is to test if static networking works for the OVA. The outcome should be the same as Step 1-12, except the networking settings are from the deployment wizard. Verify the IP address, hostname, DNS are correctly set inside the VM. None
Project: StarRocks (App Definition and Development / Database)
File: strright.md

displayed_sidebar: "English" This function extracts a number of characters from a string with specified length (starting from right). The unit for length: utf-8 character. Note: This function is also named as . ```SQL VARCHAR strright(VARCHAR str,INT len) ``` ```SQL MySQL > select strright("Hello starrocks",9); +--+ | strright('Hello starrocks', 9) | +--+ | starrocks | +--+ ``` STRRIGHT
Project: YDB (App Definition and Development / Database)
File: auth-anonymous.md

{% include %} Below are examples of the code for anonymous authentication in different {{ ydb-short-name }} SDKs. {% list tabs %} Go (native) By default, anonymous authentication is used. You can explicitly enable anonymous authentication as follows: ```go package main import ( "context" "github.com/ydb-platform/ydb-go-sdk/v3" ) func main() { ctx, cancel := context.WithCancel(context.Background()) defer cancel() db, err := ydb.Open(ctx, os.Getenv("YDBCONNECTIONSTRING"), ydb.WithAnonymousCredentials(), ) if err != nil { panic(err) } defer db.Close(ctx) ... } ``` Go (database/sql) By default, anonymous authentication is used. You can explicitly enable anonymous authentication as follows: ```go package main import ( "context" "database/sql" "os" "github.com/ydb-platform/ydb-go-sdk/v3" ) func main() { ctx, cancel := context.WithCancel(context.Background()) defer cancel() nativeDriver, err := ydb.Open(ctx, os.Getenv("YDBCONNECTIONSTRING"), ydb.WithAnonymousCredentials(), ) if err != nil { panic(err) } defer nativeDriver.Close(ctx) connector, err := ydb.Connector(nativeDriver) if err != nil { panic(err) } db := sql.OpenDB(connector) defer db.Close() ... } ``` Java ```java public void work(String connectionString) { AuthProvider authProvider = NopAuthProvider.INSTANCE; GrpcTransport transport = GrpcTransport.forConnectionString(connectionString) .withAuthProvider(authProvider) .build()); TableClient tableClient = TableClient.newClient(transport).build(); doWork(tableClient); tableClient.close(); transport.close(); } ``` Node.js {% include %} Python {% include %} Python (asyncio) {% include %} C# (.NET) ```C# using Ydb.Sdk; using Ydb.Sdk.Auth; const string endpoint = "grpc://localhost:2136"; const string database = "/local"; var config = new DriverConfig( endpoint: endpoint, database: database, credentials: new AnonymousProvider() ); await using var driver = await Driver.CreateInitialized(config); ``` PHP ```php <?php use YdbPlatform\Ydb\Ydb; use YdbPlatform\Ydb\Auth\Implement\AnonymousAuthentication; $config = [ // Database path 'database' => '/local', // Database endpoint 'endpoint' => 'localhost:2136', // Auto discovery (dedicated server only) 'discovery' => false, // IAM config 'iam_config' => [ 'insecure' => true, // 'rootcertfile' => './CA.pem', // Root CA file (uncomment for dedicated server) ], 'credentials' => new AnonymousAuthentication() ]; $ydb = new Ydb($config); ``` {% endlist %}
Project: Kapitan (Provisioning / Automation & Configuration)
File: copy.md

This input type simply copies the input templates to the output directory without any rendering/processing. For Copy, `inputpaths` can be either a file or a directory: in case of a directory, all the templates in the directory will be copied and outputted to `outputpath`. Supported output types: N/A (no need to specify `output_type`) Example ```yaml kapitan: compile: input_type: copy ignore_missing: true # Do not error if path is missing. Defaults to False input_paths: resources/state/${target_name}/.terraform.lock.hcl output_path: terraform/ ```
Project: Sonobuoy (Provisioning / Security & Compliance)
File: sonobuoy_retrieve.md

Retrieves the results of a sonobuoy run to a specified path ``` sonobuoy retrieve [path] [flags] ``` ``` --context string Context in the kubeconfig to use. -x, --extract If true, extracts the results instead of just downloading the results tarball. -f, --filename string Specify the name of the downloaded file. If empty, defaults to the name of the tarball in the pod. -h, --help help for retrieve --kubeconfig Kubeconfig Path to explicit kubeconfig file. -n, --namespace string The namespace to run Sonobuoy in. Only one Sonobuoy run can exist per namespace simultaneously. (default "sonobuoy") --retrieve-path string Specify the path to retrieve from the aggregator pod. (default "/tmp/sonobuoy") ``` ``` --level level Log level. One of {panic, fatal, error, warn, info, debug, trace} (default info) ``` - Generate reports on your Kubernetes cluster by running plugins
Project: Docker Compose (App Definition and Development / Application Definition & Image Build)
File: compose_down.md

<!MARKERGENSTART--> Stop and remove containers, networks | Name | Type | Default | Description | |:-|:|:--|:| | `--dry-run` | | | Execute command in dry run mode | | `--remove-orphans` | | | Remove containers for services not defined in the Compose file | | `--rmi` | `string` | | Remove images used by services. "local" remove only images that don't have a custom tag ("local"\|"all") | | `-t`, `--timeout` | `int` | `0` | Specify a shutdown timeout in seconds | | `-v`, `--volumes` | | | Remove named volumes declared in the "volumes" section of the Compose file and anonymous volumes attached to containers | <!MARKERGENEND--> Stops containers and removes containers, networks, volumes, and images created by `up`. By default, the only things removed are: Containers for services defined in the Compose file. Networks defined in the networks section of the Compose file. The default network, if one is used. Networks and volumes defined as external are never removed. Anonymous volumes are not removed by default. However, as they dont have a stable name, they are not automatically mounted by a subsequent `up`. For data that needs to persist between updates, use explicit paths as bind mounts or named volumes.
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: operator-sdk_cleanup.md

title: "operator-sdk cleanup" Clean up an Operator deployed with the 'run' subcommand This command has subcommands that will destroy an Operator deployed with OLM. ``` operator-sdk cleanup <operatorPackageName> [flags] ``` ``` --delete-all If set to true, all other delete options will be enabled (default true) --delete-crds If set to true, owned CRDs and CRs will be deleted --delete-operator-groups If set to true, operator groups will be deleted -h, --help help for cleanup --kubeconfig string Path to the kubeconfig file to use for CLI requests. -n, --namespace string If present, namespace scope for this CLI request --timeout duration Duration to wait for the command to complete before failing (default 2m0s) ``` ``` --plugins strings plugin keys to be used for this subcommand execution --verbose Enable verbose logging ``` -
Project: Beam (App Definition and Development / Streaming & Messaging)
File: create.md

title: "Create" <!-- 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. --> <table align="left"> <a target="_blank" class="button" href="https://beam.apache.org/releases/pydoc/current/apachebeam.transforms.core.html#apachebeam.transforms.core.Create"> <img src="/images/logos/sdks/python.png" width="20px" height="20px" alt="Pydoc" /> Pydoc </a> </table> <br><br> Creates a collection containing a specified set of elements. This is useful for testing, as well as creating an initial input to process in parallel. For example, a single element to execute a one-time `ParDo` or a list of filenames to be read. {{< playground height="700px" >}} {{< playgroundsnippet language="py" path="SDKPYTHON_Create" show="create" >}} {{< /playground >}}
Project: ArangoDB (App Definition and Development / Database)
File: implicit_failure_move_constructor.md

+++ title = "`basicresult(failuretype<T> &&)`" description = "Implicit error-from-failure-type-sugar move constructor. Available if `predicate::enablecompatibleconversion<void, T, void>` is true, or `T` is `void`. Constexpr, triviality and noexcept propagating." categories = ["constructors", "implicit-constructors", "tagged-constructors"] weight = 530 +++ Implicit error-from-failure-type-sugar move constructor used to disambiguate the construction of the error type. Note that if `T = void`, `errortype` will be default constructed. Calls {{% api "void onresultmoveconstruction(T *, U &&) noexcept" %}} with `this` and `failure_type<T> &&`. Requires: `predicate::enablecompatibleconversion<void, T, void>` is true, or `T` is `void`. Complexity: Same as for the `errortype` constructor which accepts `T`, or the `errortype` default constructor if `T` is `void`. Constexpr, triviality and noexcept of underlying operations is propagated.
Project: NebulaGraph (App Definition and Development / Database)
File: Security.md

NebulaGraph is dedicated to offering stable and secure data services. We recognize the importance of community contributions to our security posture and invite you to report any vulnerabilities you may discover. Should you identify a potential security vulnerability within NebulaGraph or encounter a security incident, we urge you to get in touch with our team. For efficient communication, please send your findings to (security@vesoft.com) with the following details: Vulnerability name (): Provide a clear, concise title. Include a CVE identifier if available. Description of the security issue (): Elaborate on the security concern. Impacted Components (): Specify affected modules and their version numbers. Reproduction Steps (): Detail the process to verify the vulnerability. Suggested Remediation: Offer potential solutions if possible. Contact information (): Name Email Organization Consent for Identity Disclosure > Fields marked with an asterisk `(*)` are mandatory. The NebulaGraph security team pledges to acknowledge receipt of your report via email within one working day. Post-resolution, we will promptly notify you and extend our gratitude for your invaluable assistance in enhancing NebulaGraph's security. Disclosure of the vulnerability will be withheld until an official patch is released. We appreciate your discretion and cooperation. We thank you for your attention to these guidelines and look forward to your participation in securing NebulaGraph.
Project: Meshery (Provisioning / Automation & Configuration)
File: nginx.md

layout: integration title: NGINX subtitle: Collaborative and visual infrastructure as code for NGINX image: /assets/img/integrations/nginx/icons/color/nginx-color.svg permalink: extensibility/integrations/nginx docURL: https://docs.meshery.io/extensibility/integrations/nginx description: integrations-category: Cloud Native Network integrations-subcategory: Service Proxy 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