cwielenb/CNCF-Dataset huggingface dataset:
Project: ORY Hydra (Provisioning / Key Management)
File: CreateVerifiableCredentialRequestBody.md

Name | Type | Description | Notes | - | - | - Format | Pointer to string | | [optional] Proof | Pointer to | | [optional] Types | Pointer to []string | | [optional] `func NewCreateVerifiableCredentialRequestBody() *CreateVerifiableCredentialRequestBody` NewCreateVerifiableCredentialRequestBody instantiates a new CreateVerifiableCredentialRequestBody object This constructor will assign default values to properties that have it defined, and makes sure properties required by API are set, but the set of arguments will change when the set of required properties is changed `func NewCreateVerifiableCredentialRequestBodyWithDefaults() *CreateVerifiableCredentialRequestBody` NewCreateVerifiableCredentialRequestBodyWithDefaults instantiates a new CreateVerifiableCredentialRequestBody object This constructor will only assign default values to properties that have it defined, but it doesn't guarantee that properties required by API are set `func (o *CreateVerifiableCredentialRequestBody) GetFormat() string` GetFormat returns the Format field if non-nil, zero value otherwise. `func (o CreateVerifiableCredentialRequestBody) GetFormatOk() (string, bool)` GetFormatOk returns a tuple with the Format field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *CreateVerifiableCredentialRequestBody) SetFormat(v string)` SetFormat sets Format field to given value. `func (o *CreateVerifiableCredentialRequestBody) HasFormat() bool` HasFormat returns a boolean if a field has been set. `func (o *CreateVerifiableCredentialRequestBody) GetProof() VerifiableCredentialProof` GetProof returns the Proof field if non-nil, zero value otherwise. `func (o CreateVerifiableCredentialRequestBody) GetProofOk() (VerifiableCredentialProof, bool)` GetProofOk returns a tuple with the Proof field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *CreateVerifiableCredentialRequestBody) SetProof(v VerifiableCredentialProof)` SetProof sets Proof field to given value. `func (o *CreateVerifiableCredentialRequestBody) HasProof() bool` HasProof returns a boolean if a field has been set. `func (o *CreateVerifiableCredentialRequestBody) GetTypes() []string` GetTypes returns the Types field if non-nil, zero value otherwise. `func (o CreateVerifiableCredentialRequestBody) GetTypesOk() ([]string, bool)` GetTypesOk returns a tuple with the Types field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *CreateVerifiableCredentialRequestBody) SetTypes(v []string)` SetTypes sets Types field to given value. `func (o *CreateVerifiableCredentialRequestBody) HasTypes() bool` HasTypes returns a boolean if a field has been set.
Project: YugabyteDB (App Definition and Development / Database)
File: yba_provider_list.md

List YugabyteDB Anywhere providers List YugabyteDB Anywhere providers ``` yba provider list [flags] ``` ``` -n, --name string [Optional] Name of the provider. -c, --code string [Optional] Code of the provider, defaults to list all providers. Allowed values: aws, gcp, azu, onprem, kubernetes. -h, --help help for list ``` ``` -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") -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 providers
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_dataprotection_describe-backup-policy.md

title: kbcli dataprotection describe-backup-policy Describe a backup policy ``` kbcli dataprotection describe-backup-policy [flags] ``` ``` kbcli cluster describe-backup-policy mypolicy kbcli cluster describe-backup-policy --cluster mycluster ``` ``` --cluster strings The cluster name -h, --help help for describe-backup-policy ``` ``` --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 --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - Data protection command.
Project: KICS (Provisioning / Security & Compliance)
File: 7e4a6e76-568d-43ef-8c4e-36dea481bff1.md

title: EC2 Instance Using Default VPC hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 7e4a6e76-568d-43ef-8c4e-36dea481bff1 Query name: EC2 Instance Using Default VPC Platform: Terraform Severity: <span style="color:#edd57e">Low</span> Category: Networking and Firewall URL: EC2 Instances should not be configured under a default VPC network<br> ```tf title="Positive test num. 1 - tf file" hl_lines="6" resource "aws_instance" "positive1" { ami = "ami-003634241a8fcdec0" instance_type = "t2.micro" subnetid = awssubnet.my_subnet.id } resource "awssubnet" "mysubnet" { vpcid = awsvpc.default.id cidr_block = "10.0.1.0/24" tags = { Name = "Main" } } ``` ```tf title="Negative test num. 1 - tf file" resource "aws_instance" "negative1" { ami = "ami-003634241a8fcdec0" instance_type = "t2.micro" subnetid = awssubnet.my_subnet2.id } resource "awssubnet" "mysubnet2" { vpcid = awsvpc.main.id cidr_block = "10.0.1.0/24" tags = { Name = "Main" } } ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-network-disconnect.1.md

% podman-network-disconnect 1 podman\-network\-disconnect - Disconnect a container from a network podman network disconnect [options] network container Disconnects a container from a network. A container can be disconnected from a network by name or by ID. If all networks are disconnected from the container, it behaves like a container created with `--network=none` and it does not have network connectivity until a network is connected again. Force the container to disconnect from a network Disconnect container from specified network: ``` podman network disconnect test web ``` , , November 2020, Originally compiled by Brent Baude <bbaude@redhat.com>
Project: StarRocks (App Definition and Development / Database)
File: ceil.md

displayed_sidebar: "English" Returns values from the input `arg` rounded to the nearest equal or larger integer. ```Shell ceil(arg) ``` `arg` supports the DOUBLE data type. Returns a value of the BIGINT data type. ```Plain mysql> select ceil(3.14); ++ | ceil(3.14) | ++ | 4 | ++ 1 row in set (0.15 sec) ```
Project: StarRocks (App Definition and Development / Database)
File: materialized_views.md

displayed_sidebar: "English" `materialized_views` provides information about all asynchronous materialized views. The following fields are provided in `materialized_views`: | Field | Description | | | | | MATERIALIZEDVIEWID | ID of the materialized view. | | TABLE_SCHEMA | Database in which the materialized view resides. | | TABLE_NAME | Name of the materialized view. | | REFRESH_TYPE | Refresh type of the materialized view. Valid values: `ROLLUP`, `ASYNC`, and `MANUAL`. | | IS_ACTIVE | Indicates whether the materialized view is active. Inactive materialized views cannot be refreshed or queried. | | INACTIVE_REASON | The reason that the materialized view is inactive. | | PARTITION_TYPE | Type of partitioning strategy for the materialized view. | | TASK_ID | ID of the task responsible for refreshing the materialized view. | | TASK_NAME | Name of the task responsible for refreshing the materialized view. | | LASTREFRESHSTART_TIME | Start time of the most recent refresh task. | | LASTREFRESHFINISHED_TIME | End time of the most recent refresh task. | | LASTREFRESHDURATION | Duration of the most recent refresh task. | | LASTREFRESHSTATE | State of the most recent refresh task. | | LASTREFRESHFORCE_REFRESH | Indicates whether the most recent refresh task was a force refresh. | | LASTREFRESHSTART_PARTITION | Starting partition for the most recent refresh task. | | LASTREFRESHEND_PARTITION | Ending partition for the most recent refresh task. | | LASTREFRESHBASEREFRESHPARTITIONS | Base table partitions involved in the most recent refresh task. | | LASTREFRESHMVREFRESHPARTITIONS | Materialized view partitions refreshed in the most recent refresh task. | | LASTREFRESHERROR_CODE | Error code of the most recent refresh task. | | LASTREFRESHERROR_MESSAGE | Error message of the most recent refresh task. | | TABLE_ROWS | Number of data rows in the materialized view, based on approximate background statistics. | | MATERIALIZEDVIEWDEFINITION | SQL definition of the materialized view. |
Project: YugabyteDB (App Definition and Development / Database)
File: yba_yb-db-version_list.md

List YugabyteDB version releases List YugabyteDB version releases ``` yba yb-db-version list [flags] ``` ``` -h, --help help for list ``` ``` -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") -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 version release
Project: YugabyteDB (App Definition and Development / Database)
File: USERS.md

This document lists users of RocksDB and their use cases. If you are using RocksDB, please open a pull request and add yourself to the list. At Facebook, we use RocksDB as a backend for many different stateful services. We're also experimenting with running RocksDB as a storage engine for two databases: MyRocks -- https://github.com/MySQLOnRocksDB/mysql-5.6 MongoRocks -- https://github.com/mongodb-partners/mongo-rocks Two different use cases at Linkedin are using RocksDB as a storage engine: LinkedIn's follow feed for storing user's activities Apache Samza, open source framework for stream processing Learn more about those use cases in a Tech Talk by Ankit Gupta and Naveen Somasundaram: http://www.youtube.com/watch?v=plqVp_OnSzg Yahoo is using RocksDB as a storage engine for their biggest distributed data store Sherpa. Learn more about it here: http://yahooeng.tumblr.com/post/120730204806/sherpa-scales-new-heights CockroachDB is an open-source geo-replicated transactional database (still in development). They are using RocksDB as their storage engine. Check out their github: https://github.com/cockroachdb/cockroach DNANexus is using RocksDB to speed up processing of genomics data. You can learn more from this great blog post by Mike Lin: http://devblog.dnanexus.com/faster-bam-sorting-with-samtools-and-rocksdb/ Iron.io is using RocksDB as a storage engine for their distributed queuing system. Learn more from Tech Talk by Reed Allman: http://www.youtube.com/watch?v=HTjt6oj-RL4 Tango is using RocksDB as a graph storage to store all users' connection data and other social activity data. Turn is using RocksDB as a storage layer for their key/value store, serving at peak 2.4MM QPS out of different datacenters. Check out our RocksDB Protobuf merge operator at: https://github.com/vladb38/rocksdb_protobuf Check out their blog post: http://blog.cloudera.com/blog/2015/08/inside-santanders-near-real-time-data-ingest-architecture/ Airbnb is using RocksDB as a storage engine for their personalized search service. You can learn more about it here: https://www.youtube.com/watch?v=ASQ6XMtogMs Pinterest's Object Retrieval System uses RocksDB for storage: https://www.youtube.com/watch?v=MtFEVEs_2Vo uses RocksDB as the storage layer for their core key-value storage, high-performance counters and time-windowed HyperLogLog services. uses RocksDB as the disk cache layer for the real-time bidding service in their Performance DSP. Smart Code checker and URL helper uses RocksDB to store all the URLs where VWO's Smart Code is installed.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-network-inspect.1.md

% podman-network-inspect 1 podman\-network\-inspect - Display the network configuration for one or more networks podman network inspect [options] network [network ...] Display the (JSON format) network configuration. Pretty-print networks to JSON or using a Go template. | Placeholder | Description | |--|-| | .Containers ... | Running containers on this network. | | .Created ... | Timestamp when the network was created | | .DNSEnabled | Network has dns enabled (boolean) | | .Driver | Network driver | | .ID | Network ID | | .Internal | Network is internal (boolean) | | .IPAMOptions ... | Network ipam options | | .IPv6Enabled | Network has ipv6 subnet (boolean) | | .Labels ... | Network labels | | .Name | Network name | | .Network ... | Nested Network type | | .NetworkDNSServers | Array of DNS servers used in this network | | .NetworkInterface | Name of the network interface on the host | | .Options ... | Network options | | .Routes | List of static routes for this network | | .Subnets | List of subnets on this network | Inspect the default podman network. ``` $ podman network inspect podman [ { "name": "podman", "id": "2f259bab93aaaaa2542ba43ef33eb990d0999ee1b9924b557b7be53c0b7a1bb9", "driver": "bridge", "network_interface": "podman0", "created": "2021-06-03T12:04:33.088567413+02:00", "subnets": [ { "subnet": "10.88.0.0/16", "gateway": "10.88.0.1" } ], "ipv6_enabled": false, "internal": false, "dns_enabled": false, "ipam_options": { "driver": "host-local" } } ] ``` Show the subnet and gateway for a network. ``` $ podman network inspect podman --format "{{range .Subnets}}Subnet: {{.Subnet}} Gateway: {{.Gateway}}{{end}}" Subnet: 10.88.0.0/16 Gateway: 10.88.0.1 ``` , , , August 2021, Updated with the new network format by Paul Holzinger <pholzing@redhat.com> August 2019, Originally compiled by Brent Baude <bbaude@redhat.com>
Project: KICS (Provisioning / Security & Compliance)
File: 4766d3ea-241c-4ee6-93ff-c380c996bd1a.md

title: DOCDB Cluster Without KMS hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 4766d3ea-241c-4ee6-93ff-c380c996bd1a Query name: DOCDB Cluster Without KMS Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Encryption URL: AWS DOCDB Cluster should be encrypted with a KMS encryption key<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsdocdbcluster" "docdb" { cluster_identifier = "my-docdb-cluster" engine = "docdb" master_username = "foo" master_password = "mustbeeightchars" backupretentionperiod = 5 preferredbackupwindow = "07:00-09:00" skipfinalsnapshot = true } ``` ```tf title="Negative test num. 1 - tf file" resource "awsdocdbcluster" "docdb" { cluster_identifier = "my-docdb-cluster" engine = "docdb" master_username = "foo" master_password = "mustbeeightchars" backupretentionperiod = 5 preferredbackupwindow = "07:00-09:00" skipfinalsnapshot = true storage_encrypted = true kmskeyid = "arn:aws:kms:us-west-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab" } ```
Project: KICS (Provisioning / Security & Compliance)
File: 3b3b4411-ad1f-40e7-b257-a78a6bb9673a.md

title: VPC Without Attached Subnet hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 3b3b4411-ad1f-40e7-b257-a78a6bb9673a Query name: VPC Without Attached Subnet Platform: CloudFormation Severity: <span style="color:#edd57e">Low</span> Category: Resource Management URL: VPCs without attached subnets may indicate that they are not being used<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="3" AWSTemplateFormatVersion: '2010-09-09' Resources: myVPC_1: Type: AWS::EC2::VPC Properties: CidrBlock: 10.0.0.0/16 EnableDnsSupport: 'false' EnableDnsHostnames: 'false' InstanceTenancy: dedicated ``` ```json title="Positive test num. 2 - json file" hl_lines="4" { "AWSTemplateFormatVersion": "2010-09-09", "Resources": { "myVPC_1": { "Type": "AWS::EC2::VPC", "Properties": { "InstanceTenancy": "dedicated", "CidrBlock": "10.0.0.0/16", "EnableDnsSupport": "false", "EnableDnsHostnames": "false" } } } } ``` ```yaml title="Negative test num. 1 - yaml file" AWSTemplateFormatVersion: '2010-09-09' Resources: myVPC_2: Type: AWS::EC2::VPC Properties: CidrBlock: 10.0.0.0/16 EnableDnsSupport: 'false' EnableDnsHostnames: 'false' InstanceTenancy: dedicated mySubnet: Type: AWS::EC2::Subnet Properties: VpcId: Ref: myVPC_2 CidrBlock: 10.0.0.0/24 AvailabilityZone: "us-east-1a" ``` ```json title="Negative test num. 2 - json file" { "AWSTemplateFormatVersion": "2010-09-09", "Resources": { "myVPC_2": { "Type": "AWS::EC2::VPC", "Properties": { "CidrBlock": "10.0.0.0/16", "EnableDnsSupport": "false", "EnableDnsHostnames": "false", "InstanceTenancy": "dedicated" } }, "mySubnet": { "Type": "AWS::EC2::Subnet", "Properties": { "VpcId": { "Ref": "myVPC_2" }, "CidrBlock": "10.0.0.0/24", "AvailabilityZone": "us-east-1a" } } } } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: creating-a-meshery-design.md

layout: default title: Creating a Meshery Design abstract: Learn how to create a Meshery design from scratch or from a template. permalink: guides/configuration-management/creating-a-meshery-design redirect_from: guides/creating-a-meshery-design type: guides category: configuration language: en published: true suggested-reading: false abstract: Learn how to create a Meshery design from scratch or from a template. {% include alert.html type="info" title="Learn about Designs" content="Learn more about <a href='/concepts/logical/designs'>what a Meshery Design</a> is and how it fits into Meshery's approach to cloud native management." %} You can create a Meshery design in two ways: Click on the "Design" tab to start creating a new design. In the left panel, click "Components" and browse the type of component you want to add. Drag and drop the components onto the canvas. Click and drag from one component to another to create connections between components. You can customize the connections by adding labels or adjusting their properties. Once you're satisfied with your design, click the "Save" button on the toolbar. Your design will be saved as "Untitled design" by default. You can give your design a name to help identify and manage it later. Another way to create a Meshery design is to use an already curated template. You can either import designs that others have published and made available for public use or clone patterns from the Meshery Catalog. In the left panel of the designer mode, click "Designs". Select a design from the list that appears in the panel and it will appear on your canvas. If you already have a design that you'd like to build on, click on the import icon to import the design directly to your MeshMap canvas. A modal will pop-up where you'll then select the design type, choose the upload method (file upload or url import), enter the design file name, and choose the file to upload or enter the url link to import. In the left panel of the designer mode, click "Catalog". Select a design from the list that appears in the panel. A modal will pop up requesting you to clone (create a copy of) the design you've selected. Click "clone" and a copy of the design will appear on your MeshMap canvas. You can then configure the design to suit your purposes. {% include alert.html type="info" title="Learn about Patterns" content="Learn more about <a href='/concepts/logical/patterns'>what a Meshery Pattern</a> is and how it fits into Meshery's approach to cloud native management." %}
Project: SPIRE (Provisioning / Key Management)
File: changelog_guidelines.md

The following guidelines should be followed when updating the CHANGELOG: There should be an entry for every version, that includes the version number and release date. Entries should be focused on communicating user-facing changes, considering that the main consumers of the CHANGELOG are the end users of SPIRE. The types of changes should be grouped using the following categories: Added: New features that impact in the user experience. Should clearly communicate the new capability and why it is good. Changed: Changes in existing functionality. Should include information about the components affected and any behavioral changes. Deprecated: Features that will be removed in a future release. Should communicate any planned behavioral changes, including if the feature is deprecated in favor of a different feature. Removed: Features removed in this release. Should describe any behavioral changes, including if the feature has been removed in favor of a different feature. Fixed: Regular bug fixes. Should describe what the user would be experiencing if they were encountering the issue that is now fixed. Security: Security-related fixes. If there is a CVE assigned, it should be included. Categories that don't have an entry for the release are omitted in the CHANGELOG. The following is an example that includes all the categories: AWS PCA now has a configurable allowing operators to provide additional CA certificates for inclusion in the bundle (#1574) Envoy SDS support is now always on (#1579) The UpstreamCA plugin type is now marked as deprecated in favor of the UpstreamAuthority plugin type (#1406) The deprecated `upstream_bundle` server configurable has been removed. The server always uses the upstream bundle as the trust bundle (#1702) Issue in the Upstream Authority plugin that could result in a delay in the propagation of bundle updates/changes (#1917) Node API now ratelimits expensive calls (#577)