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

Set environment variables. This option allows arbitrary environment variables that are available for the process to be launched inside of the container. If an environment variable is specified without a value, Podman checks the host environment for a value and set the variable only if it is set on the host. As a special case, if an environment variable ending in * is specified without a value, Podman searches the host environment for variables starting with the prefix and adds those variables to the container.
Project: ClickHouse (App Definition and Development / Database)
File: quantiledeterministic.md

slug: /en/sql-reference/aggregate-functions/reference/quantiledeterministic sidebar_position: 206 Computes an approximate of a numeric data sequence. This function applies with a reservoir size up to 8192 and deterministic algorithm of sampling. The result is deterministic. To get an exact quantile, use the function. When using multiple `quantile*` functions with different levels in a query, the internal states are not combined (that is, the query works less efficiently than it could). In this case, use the function. Syntax ``` sql quantileDeterministic(level)(expr, determinator) ``` Alias: `medianDeterministic`. Arguments `level` Level of quantile. Optional parameter. Constant floating-point number from 0 to 1. We recommend using a `level` value in the range of `. `expr` Expression over the column values resulting in numeric , or . `determinator` Number whose hash is used instead of a random number generator in the reservoir sampling algorithm to make the result of sampling deterministic. As a determinator you can use any deterministic positive number, for example, a user id or an event id. If the same determinator value occurs too often, the function works incorrectly. Returned value Approximate quantile of the specified level. Type: for numeric data type input. if input values have the `Date` type. if input values have the `DateTime` type. Example Input table: ``` text val 1 1 2 3 ``` Query: ``` sql SELECT quantileDeterministic(val, 1) FROM t ``` Result: ``` text quantileDeterministic(val, 1) 1.5 ``` See Also
Project: KICS (Provisioning / Security & Compliance)
File: BADGE.md

To create a badge and update it the user should run KICS in their CI. This can be done differently for each . Let's assume a manual CLI process using docker: ```bash echo "running KICS in the current dir and writing results.json" docker run -t -v $PWD:/path checkmarx/kics:latest scan -p /path -o "/path/" ``` This will generate a results.json file under `path`. Parse the `results.json` and request a badge to img.shields.io. For this example, let's assume HIGH and MEDIUM results are bad: ```bash CRITICAL=$(jq '.severity_counters.CRITICAL' results.json) HIGH=$(jq '.severity_counters.HIGH' results.json) MEDIUM=$(jq '.severity_counters.MEDIUM' results.json) LOW=$(jq '.severity_counters.LOW' results.json) INFO=$(jq '.severity_counters.INFO' results.json) MESSAGE="passing" COLOR="green" if (( $HIGH > 0 )) || (( $MEDIUM > 0)); then MESSAGE="failing" COLOR="red" fi curl -sL "https://img.shields.io/badge/KICS-${MESSAGE}-${COLOR}.svg" > kics-status.svg ``` An example SVG produced: If you have github pages configured under `gh-pages` branch configured you can commit and push the badge to it and reference on your README.md, e.g: ``
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.90.md

layout: release date: 2023-06-01 tag: v0.6.90 [DevOps] Playground: Configure Nginx for Docker Deployment @0xt3j4s (#7748) Fix no-useful test case @Aisuko (#7751) added service for playground using metallb @anshuhtwt (#7583) [Server] Platform detect func improvement @Azanul (#7722) Remove no useful test cases and add new testcase @Aisuko (#7767) feat: Add test cases for closest_arg @Aisuko (#7760) feat: Add two test cases for meshery auth @Aisuko (#7759) add endpoint to download the application/designs with particular :id @harkiratsm (#7692) [bug] Fix user prefs API for google tag manager @theBeginner86 (#7758) Fixing the key spacing error again for the updated UI @0xt3j4s (#7755) Fixing the key-spacing error (in app.js file) occurring on 'RUN ESLint Meshery-UI' @0xt3j4s (#7749) Fix eslint typeof warning @8rxn (#7688) move dark mode under preferences menu @sudhanshutech (#7726) feat: add Beta badge on meshmap title @Udit-takkar (#7728) [Feature] - Search Functionality for MeshModel Browser and a Tab for Displaying Relationships @UsmanDev09 (#7736) [bug] Fix user prefs API for google tag manager @theBeginner86 (#7758) feat: Add test cases for closest_arg @Aisuko (#7760) Add Meshery Extensions Issue_Template @8rxn (#7745) meshsync update documented @Azanul (#7721) Thank you to our contributors for making this release possible: @0xt3j4s, @8rxn, @Abhishek-kumar09, @Aisuko, @Azanul, @Chadha93, @Udit-takkar, @UsmanDev09, @anshuhtwt, @harkiratsm, @l5io, @leecalcote, @muhammmadusman3211, @sudhanshutech, @theBeginner86 and l5io
Project: KICS (Provisioning / Security & Compliance)
File: c68b4e6d-4e01-4ca1-b256-1e18e875785c.md

title: Google Project IAM Member Service Account has Token Creator or Account User Role hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: c68b4e6d-4e01-4ca1-b256-1e18e875785c Query name: Google Project IAM Member Service Account has Token Creator or Account User Role Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: Verifies if Google Poject IAM Member Service Account doesn't have a Account User or Token Creator associated<br> ```tf title="Positive test num. 1 - tf file" hl_lines="9 3" resource "googleprojectiam_member" "positive1" { project = "your-project-id" role = "roles/iam.serviceAccountTokenCreator" member = "serviceAccount:my-other-app@appspot.gserviceacccount.com" } resource "googleprojectiam_member" "positive2" { project = "your-project-id" role = "roles/iam.serviceAccountUser" members = ["user:jane@example.com", "serviceAccount:my-other-app@appspot.gserviceacccount.com"] } ``` ```tf title="Negative test num. 1 - tf file" resource "googleprojectiam_member" "negative1" { project = "your-project-id" role = "roles/editor" members = "user:jane@example.com" } ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_compute_autoscalers.md

+++ title = "googlecomputeautoscalers resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlecomputeautoscalers" identifier = "inspec/resources/gcp/googlecomputeautoscalers.md googlecomputeautoscalers resource" parent = "inspec/resources/gcp" +++ A `googlecomputeautoscalers` is used to test a Google Autoscaler resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby autoscalers = googlecomputeautoscalers(project: 'chef-gcp-inspec', zone: 'zone') describe.one do autoscalers.autoscalingpolicies.each do |autoscalingpolicy| describe autoscaling_policy do its('maxnumreplicas') { should eq '5' } its('minnumreplicas') { should eq '1' } its('cooldownperiod_sec') { should eq '60' } its('cpuutilization.utilizationtarget') { should eq '0.5' } end end end ``` Properties that can be accessed from the `googlecomputeautoscalers` resource: See the resource for more information. `ids` : an array of `googlecomputeautoscaler` id `creation_timestamps` : an array of `googlecomputeautoscaler` creation_timestamp `names` : an array of `googlecomputeautoscaler` name `descriptions` : an array of `googlecomputeautoscaler` description `autoscaling_policies` : an array of `googlecomputeautoscaler` autoscaling_policy `targets` : an array of `googlecomputeautoscaler` target `zones` : an array of `googlecomputeautoscaler` zone 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: YugabyteDB (App Definition and Development / Database)
File: getrange.md

title: GETRANGE linkTitle: GETRANGE description: GETRANGE menu: preview: parent: api-yedis weight: 2080 aliases: /preview/api/redis/getrange /preview/api/yedis/getrange type: docs `GETRANGE key start end` This command fetches a substring of the string value that is associated with the given `key` between the two given offsets `start` and `end`. If an offset value is positive, it is counted from the beginning of the string. If an offset is negative, it is counted from the end. If an offset is out of range, it is limited to either the beginning or the end of the string. If `key` does not exist, (null) is returned. If `key` is associated with a non-string value, an error is raised. Returns a string value. ```sh $ SET yugakey "Yugabyte" ``` ``` "OK" ``` ```sh $ GETRANGE yugakey 0 3 ``` ``` "Yuga" ``` ```sh $ GETRANGE yugakey -4 -1 ``` ``` "Byte" ``` , , , , , , ,
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-system-connection-add.1.md

% podman-system-connection-add 1 podman\-system\-connection\-add - Record destination for the Podman service podman system connection add [options] name destination Record ssh destination for remote podman service(s). The ssh destination is given as one of: [user@]hostname[:port] ssh://[user@]hostname[:port] unix://path tcp://hostname:port The user is prompted for the remote ssh login password or key file passphrase as required. The `ssh-agent` is supported if it is running. Make the new destination the default for this user. The default is false. Path to ssh identity file. If the identity file has been encrypted, Podman prompts the user for the passphrase. If no identity file is provided and no user is given, Podman defaults to the user running the podman command. Podman prompts for the login password on the remote server. Port for ssh destination. The default value is `22`. Path to the Podman service unix domain socket on the ssh destination host Add a named system connection: ``` $ podman system connection add QA podman.example.com ``` Add a system connection using SSH data: ``` $ podman system connection add --identity ~/.ssh/dev_rsa production ssh://root@server.example.com:2222 ``` Add a named system connection to local Unix domain socket: ``` $ podman system connection add testing unix:///run/podman/podman.sock ``` Add a named system connection to local tcp socket: ``` $ podman system connection add debug tcp://localhost:8080 ``` , , June 2020, Originally compiled by Jhon Honce (jhonce at redhat dot com)
Project: Carvel (App Definition and Development / Application Definition & Image Build)
File: README_ALBTargetGroupEvents.md

ALB Target Group events consist of a request that was routed to a Lambda function which is a registered target of an Application Load Balancer Target Group. When this happens, ALB expects the result of the function to be the response that ALB should respond with. https://docs.aws.amazon.com/elasticloadbalancing/latest/application/lambda-functions.html The following is a sample class and Lambda function that receives an ALB Target Group event as an input, writes some of the incoming 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.ALBTargetGroupRequest) (events.ALBTargetGroupResponse, error) { fmt.Printf("Processing request data for traceId %s.\n", request.Headers["x-amzn-trace-id"]) 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.ALBTargetGroupResponse{Body: request.Body, StatusCode: 200, StatusDescription: "200 OK", IsBase64Encoded: false, Headers: map[string]string{}}, nil } func main() { lambda.Start(handleRequest) } ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: azurerm_network_watchers.md

+++ title = "azurermnetworkwatchers resource" draft = false gh_repo = "inspec" platform = "azure" [menu] [menu.inspec] title = "azurermnetworkwatchers" identifier = "inspec/resources/azure/azurermnetworkwatchers.md azurermnetworkwatchers resource" parent = "inspec/resources/azure" +++ {{< inspec/azurermdeprecated resource="azurenetwork_watchers" >}} Use the `azurermnetworkwatchers` InSpec audit resource to verify that a Network Watcher exists. This resource interacts with version `2018-02-01` of the Azure Management API. For more information see the [official Azure documentation](https://docs.microsoft.com/en-us/rest/api/network-watcher/networkwatchers/list). At the moment, there doesn't appear to be a way to select the version of the Azure API docs. If you notice a newer version being referenced in the official documentation please open an issue or submit a pull request using the updated version. This resource is available in the `inspec-azure` [resource pack](/inspec/glossary/#resource-pack). To use it, add the following to your `inspec.yml` in your top-level profile: depends: name: inspec-azure git: https://github.com/inspec/inspec-azure.git You'll also need to setup your Azure credentials; see the resource pack . An `azurermnetworkwatchers` resource block identifies Network Watchers by Resource Group. describe azurermnetworkwatchers(resourcegroup: 'examplegroup') do ... end describe azurermnetworkwatchers(resourcegroup: 'examplegroup') do its('names') { should include('ExampleNetworkWatcher') } end `names` The name of the Network Watcher its('names') { should include('ExampleNetworkWatcher') } {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The control will pass if the resource returns a result. Use `should_not` if you expect zero matches. describe azurermnetworkwatchers(resource_group: 'ExampleGroup') do it { should exist } end describe azurermnetworkwatchers(resource_group: 'MissingExampleGroup') do it { should_not exist } end Your [Service Principal](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal) must be setup with a `contributor` role on the subscription you wish to test.
Project: KubeVela (App Definition and Development / Application Definition & Image Build)
File: usage.md

You can use velaQL with a syntax similar to promeQL. The syntax format of velaQL is as follows: ```sql view{parameter1=value1}.statusKey ``` `view` represents different query views, we have built a few views: `component-pod-view`,`pod-view`,`resource-view` `parameter1=value1` represents query configuration items `statusKey` represents the aggregate result of the query, default is `status` List the pods created by specified component ``` parameter: { appName: string // application name appNs: string // application namespace name: string // component name cluster?: string // cluster name(Optional) clusterNs?: string // cluster namespace(Optional) } ``` `status` ``` // query successful status: { podList: [{ cluster: string worload: { apiVersion: string kind: string } metadata: { name: string namespace: string creationTime: string version: { revision: string publishVersion: string deployVersion: string } } status: { phase: "Pending" | "Running" | "Succeeded" | "Failed" | "Unknown" // if phase == "Pending" or "Unknown": podIP, hostIP, nodeName will be empty podIP: string hostIP: string nodeName: string } }] } // query failed status: { error: string } ``` ```sql component-pod-view{appName=demo,appNs=default,cluster=prod,clusterNs=default,name=web}.status ``` Query the pods detail information ``` parameter: { name: string // pod name namespace: string // pod namespace cluster?: string // cluster name(Optional) } ``` `status` ``` // query successful status: { containers: [{ name: string image: string resources: { limits: { cpu: string memory: string } requests: { cpu: string memory: string } usage: { cpu: string memory: string } } status: { // state holds a possible state of container. // only one of its members may be specified. state: { running: {...} waiting: {...} terminated: {...} } restartCount: string } }] events: [...v1.Event] } // query failed status: { error: string } ``` ``` pod-view{name=demo,namespace=default,cluster=prod}.status ``` List resources ``` parameter: { type: "ns" | "secret" | "configMap" | "pvc" | "storageClass" namespace: *"" | string // Optional cluster: *"" | string // Optional } ``` `status` ``` // query successful status: { list: [...k8sObject] } // query failed status: { error: string } ``` ``` resource-view{type=ns,cluster=prod}.status ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.119.md

layout: release date: 2023-08-08 tag: v0.6.119 update comp_updater script @MUzairS15 (#8411) Fix /api/integrations/connections/{connectionKind} @abdullah1308 (#8397) Update meshmodel search by name @abdullah1308 (#8249) fix relationships @MUzairS15 (#8409) fixed context switching abort @EraKin575 (#8392) Shortened the User ID in app list @gopivaibhav (#8395) Add load generator options flag to mesheryctl perf @abdullah1308 (#8403) Implement conditional rendering of Model Selector based on selected category @ShravaniAK (#8407) Bump tough-cookie and @cypress/request in /provider-ui @dependabot (#8404) [UI] - Handled configuration pages responsiveness @UsmanDev09 (#8408) Bump tough-cookie and @cypress/request in /ui @dependabot (#8405) Revert "[UI] Add Connection Stats Chart" @MUzairS15 (#8410) [UI] Add Connection Stats Chart @aabidsofi19 (#8171) Bump tough-cookie and @cypress/request in /provider-ui @dependabot (#8404) Bump tough-cookie and @cypress/request in /ui @dependabot (#8405) solved the issue of unresponsiveness of header @AdityaRaimec22 (#8352) Bump commonmarker from 0.23.9 to 0.23.10 in /docs @dependabot (#8413) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @AdityaRaimec22, @EraKin575, @MUzairS15, @ShravaniAK, @UsmanDev09, @aabidsofi19, @abdullah1308, @dependabot, @dependabot[bot], @gopivaibhav and @leecalcote
Project: StarRocks (App Definition and Development / Database)
File: aes_encrypt.md

displayed_sidebar: "English" Uses the AES128ECB algorithm to encrypt a string and returns a binary string. AES is short for advanced encryption standard and ECB is short for electronic code book. The key used to encrypt the string is a 128-bit string. ```Haskell aesencrypt(str,keystr); ``` `str`: the string to encrypt. It must be of the VARCHAR type. `key_str`: the key used to encrypt `str`. It must be of the VARCHAR type. Returns a value of the VARCHAR type. If the input is NULL, NULL is returned. Use this function to AES encrypt `starrocks` and convert the encrypted string into a Base64-encoded string. ```Plain Text mysql> select tobase64(AESENCRYPT('starrocks','F3229A0B371ED2D9441B830D21A390C3')); +-+ | tobase64(aesencrypt('starrocks', 'F3229A0B371ED2D9441B830D21A390C3')) | +-+ | uv/Lhzm74syo8JlfWarwKA== | +-+ 1 row in set (0.01 sec) ```
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: spinnaker-pipeline.md

title: Armory Policy Engine for Spinnaker labels: layer: cicd software: spinnaker blogs: https://blog.armory.io/deployment-policies-with-spinnaker/ tutorials: https://docs.armory.io/plugins/policy-engine/ inventors: armory Spinnaker is a Continuous Delivery and Deployment tool started by Netflix. The lets you configure policies that dictate what kinds of Spinnaker pipelines developers can create.
Project: Kyverno (Provisioning / Security & Compliance)
File: kyverno_completion_zsh.md

Generate the autocompletion script for zsh Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: echo "autoload -U compinit; compinit" >> ~/.zshrc To load completions in your current shell session: source <(kyverno completion zsh) To load completions for every new session, execute once: kyverno completion zsh > "${fpath[1]}/_kyverno" kyverno completion zsh > $(brew --prefix)/share/zsh/site-functions/_kyverno You will need to start a new shell for this setup to take effect. ``` kyverno completion zsh [flags] ``` ``` -h, --help help for zsh --no-descriptions disable completion descriptions ``` ``` --adddirheader If true, adds the file directory to the header of the log messages --alsologtostderr log to standard error as well as files (no effect when -logtostderr=true) --logbacktraceat traceLocation when logging hits line file:N, emit a stack trace (default :0) --log_dir string If non-empty, write log files in this directory (no effect when -logtostderr=true) --log_file string If non-empty, use this log file (no effect when -logtostderr=true) --logfilemax_size uint Defines the maximum size a log file can grow to (no effect when -logtostderr=true). Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800) --logtostderr log to standard error instead of files (default true) --one_output If true, only write logs to their native severity level (vs also writing to each lower severity level; no effect when -logtostderr=true) --skip_headers If true, avoid header prefixes in the log messages --skiplogheaders If true, avoid headers when opening log files (no effect when -logtostderr=true) --stderrthreshold severity logs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or -alsologtostderr=true) (default 2) -v, --v Level number for the log level verbosity --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging ``` - Generate the autocompletion script for the specified shell
Project: StarRocks (App Definition and Development / Database)
File: row.md

displayed_sidebar: "English" Creates a named STRUCT or ROW value from the given values. It supports unnamed struct. You do not need to specify the field names. StarRocks automatically generates column names, such as `col1, col2,...`. This function is supported from v3.1 onwards. struct() is the alias of row(). ```Haskell STRUCT row(ANY val, ...) ``` `val`: an expression of any supported type. This function is a variable argument function. You must pass at least one argument. `value` is nullable. Separate multiple values with a comma (`,`). Returns a STRUCT value which consists of the input values. ```Plaintext select row(1,"Apple","Pear"); +--+ | row(1, 'Apple', 'Pear') | +--+ | {"col1":1,"col2":"Apple","col3":"Pear"} | +--+ select row("Apple", NULL); ++ | row('Apple', NULL) | ++ | {"col1":"Apple","col2":null} | ++ select struct(1,2,3); ++ | row(1, 2, 3) | ++ | {"col1":1,"col2":2,"col3":3} | ++ ```