cwielenb/CNCF-Dataset huggingface dataset:
Project: ArangoDB (App Definition and Development / Database)
File: string_ref.md

+++ title = "String refs" weight = 40 +++ `<system_error2>` does not use `std::string` to return possibly statically or dynamically allocated strings, and thus avoids dragging in a lot of the standard library which impacts build times. Instead status code domains have a , which has a polymorphic implementation which may or may not [manage a dynamic memory allocation using an atomic reference counter](https://ned14.github.io/status-code/docstatuscodedomain.html#standardese-systemerror2status_code_domainatomicrefcountedstring_ref). Due to this polymorphism, you don't need to worry which implementation is actually in use under the bonnet when you pass around `string_ref` instances. `string_ref` provides the same member functions as a `span<const char>`, and so participates ordinarily in STL algorithms and containers. In particular, if you need to string search or slice it, you can construct a `string_view` on top easily. {{% snippet "experimentalstatuscode.cpp" "string_ref" %}} Now you understand what `string_ref` does, returning the name of the status code domain is self describing. Note we use the non-managing constructor of `string_ref`, as the string `"file i/o error domain"` is statically stored. We cache the returned value locally in static storage.
Project: Meshery (Provisioning / Automation & Configuration)
File: importing-design.md

layout: default title: Importing a Design abstract: Import your existing application definitions and infrastructure configuration into Meshery. permalink: extensions/importing-a-design language: en display-title: "false" list: include type: extensions category: meshmap You may bring your own design files or find them available through your chosen provider. Each design carries a unique identifier for reference. The designs in this repository serve in an educational capacity, facilitating learning, and also serve in an operational capacity, facilitating implementation and validation of your cloud native deployments adherence to a design. Step 1: Access the Extensions UI From Meshery Extension, designs can be imported from your local filesystem or imported from a remote URL. Step 2: Navigate to the Designs Tab and Select your Import Once you have accessed the Extension's UI, navigate to the Designs tab. In this tab you can see all your designs with their "<b>Name</b>" and "<b>Date Modified</b>". From the top right of the table click on import design which opens import modal. <a href="{{ site.baseurl }}/assets/img/meshmap/application-tab.png"><img style="border-radius: 0.5%;" alt="Import-Application" style="width:800px;height:auto;" src="{{ site.baseurl }}/assets/img/meshmap/design.png" /></a> Step 3: Import the Design You can import your design by clicking on the Browse button and selecting the file from your local machine or import in through URL Once you have selected the file, click on the Import button to import design into Meshery Extension. When you import a design into Extensions, it will create a Meshery Design based on definition. This Meshery design will include all of the configurations, and other parameters defined in the File. <a href="{{ site.baseurl }}/assets/img/meshmap/apps-modal.png"><img style="border-radius: 0.5%;" alt="Import-Application" style="width:800px;height:auto;" src="{{ site.baseurl }}/assets/img/meshmap/import-design.png" /></a> Once the Meshery Design has been created, you can use Meshery Extension to manage, operate and observe your cloud native infrastructure. You can also use Meshery Extension to deploy your Meshery Design to your infrastructure.
Project: Clair (Provisioning / Security & Compliance)
File: releases.md

Clair releases are cut roughly every three months and actively maintained for six. This means that bugfixes should be landed on `master` (if applicable) and then marked for backporting to a minor version's release branch. The process for doing this is not yet formalized. When cutting a new minor release, two things need to be done: creating a tag and creating a release branch. This can be done like so: ```sh git tag -as v4.x.0 HEAD git push upstream HEAD:release-4.x tag v4.x.0 ``` Then, a "release" needs to be created in the Github UI using the created tag. A patch release is just like a minor release with the caveat that minor version tags should only appear on release branches and a new branch does not need to be created. ```sh git checkout release-4.x git tag -as v4.x.1 HEAD git push upstream tag v4.x.1 ``` Then, a "release" needs to be created in the Github UI using the created tag. Clair's artifact release process is automated and driven off the releases in Github. Publishing a new release in the Github UI automatically triggers the creation of a complete source archive and a container. The archive is attached to the release, and the container is pushed to the repository. This is all powered by a Github Action in `.github/workflows/cut-release.yml`.
Project: Couler (Provisioning / Automation & Configuration)
File: examples.md

Let's start by running a very simple workflow template to echo "hello world" using the `docker/whalesay` container image from DockerHub. You can run this directly from your shell with a simple docker command: ``` $ docker run docker/whalesay cowsay "hello world" _ < hello world > \ \ \ /""""""""""""""""_/ === ~ { ~ ~ / ===- ~~~ \ o / \ \ / \\/ ``` With Couler, we can run the same container on a Kubernetes cluster using an Argo Workflows as the workflow engine. ```python --8<-- "examples/hello_world.py" ``` This example combines the use of a Python function result, along with conditionals, to take a dynamic path in the workflow. In this example, depending on the result of the first step defined in `flip_coin()`, the template will either run the `heads()` step or the `tails()` step. Steps can be defined via either `couler.run_script()` for Python functions or `couler.run_container()` for containers. In addition, the conditional logic to decide whether to flip the coin in this example is defined via the combined use of `couler.when()` and `couler.equal()`. ```python --8<-- "examples/coin_flip.py" ``` This example demonstrates different ways to define the workflow as a directed-acyclic graph (DAG) by specifying the dependencies of each task via `couler.set_dependencies()` and `couler.dag()`. Please see the code comments for the specific shape of DAG that we've defined in `linear()` and `diamond()`. ```python --8<-- "examples/dag.py" ``` Note that the current version only works with Argo Workflows but we are actively working on the design of the unified interface that is extensible to additional workflow engines. Please stay tuned for more updates and we welcome any feedback and contributions from the community.
Project: Checkov (Provisioning / Security & Compliance)
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 on our community slack. 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: ClickHouse (App Definition and Development / Database)
File: azureBlobStorage.md

slug: /en/sql-reference/table-functions/azureBlobStorage sidebar_position: 10 sidebar_label: azureBlobStorage keywords: [azure blob storage] Provides a table-like interface to select/insert files in . This table function is similar to the . Syntax ``` sql azureBlobStorage(- connectionstring|storageaccounturl, containername, blobpath, [accountname, accountkey, format, compression, structure]) ``` Arguments `connectionstring|storageaccounturl` connectionstring includes account name & key () or you could also provide the storage account url here and account name & account key as separate parameters (see parameters accountname & accountkey) `container_name` - Container name `blobpath` - file path. Supports following wildcards in readonly mode: ``, `*`, `?`, `{abc,def}` and `{N..M}` where `N`, `M` numbers, `'abc'`, `'def'` strings. `accountname` - if storageaccount_url is used, then account name can be specified here `accountkey` - if storageaccount_url is used, then account key can be specified here `format` The of the file. `compression` Supported values: `none`, `gzip/gz`, `brotli/br`, `xz/LZMA`, `zstd/zst`. By default, it will autodetect compression by file extension. (same as setting to `auto`). `structure` Structure of the table. Format `'column1name column1type, column2name column2type, ...'`. Returned value A table with the specified structure for reading or writing data in the specified file. Examples Write data into azure blob storage using the following : ```sql INSERT INTO TABLE FUNCTION azureBlobStorage('http://azurite1:10000/devstoreaccount1', 'testcontainer', 'test{partitionid}.csv', 'devstoreaccount1', 'Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==', 'CSV', 'auto', 'column1 UInt32, column2 UInt32, column3 UInt32') PARTITION BY column3 VALUES (1, 2, 3), (3, 2, 1), (78, 43, 3); ``` And then it can be read using ```sql SELECT * FROM azureBlobStorage('http://azurite1:10000/devstoreaccount1', 'testcontainer', 'test1.csv', 'devstoreaccount1', 'Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==', 'CSV', 'auto', 'column1 UInt32, column2 UInt32, column3 UInt32'); ``` ```response column1column2column3 3 2 1 ``` or using connection_string ```sql SELECT count(*) FROM azureBlobStorage('DefaultEndpointsProtocol=https;AccountName=devstoreaccount1;AccountKey=Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==;EndPointSuffix=core.windows.net', 'testcontainer', 'test3.csv', 'CSV', 'auto' , 'column1 UInt32, column2 UInt32, column3 UInt32'); ``` ``` text count() 2 ``` `_path` Path to the file. Type: `LowCardinalty(String)`. `_file` Name of the file. Type: `LowCardinalty(String)`. `_size` Size of the file in bytes. Type: `Nullable(UInt64)`. If the file size is unknown, the value is `NULL`. See Also
Project: ShardingSphere (App Definition and Development / Database)
File: issue.en.md

+++ title = "Issue of Conduct" weight = 1 chapter = true +++ Issue lists should be readable and retrievable, the author is obligated to summarize the title that is meaningful and convenient for retrieval, and to ensure the correctness and completeness of the content; Please confirm that there is no relevant existing Issue after sufficient search, and then submit a new Issue; The type of issue is divided into bug, new feature and problem. When you edit an issue, please select the correct template and fill in content according to the template; For problems caused by uncertain configuration, please submit the relevant reproducible code to GitHub, so that community contributors can locate and identify the problem more efficiently; Please reply to the Issue after it has been resolved to form a closed loop that will provide effective information for others who browse the Issue; Please pay attention to the submitted issues in time. Issues with no feedback for a long time will be closed regularly. Please use English for community diversity. For issues without clear title, the handler guides the submitter to revise and refine the title before dealing with it; For the issue with missing template information, the handler guides the submitter to provide the required information before processing; Issues related to code, such as bug fix and feature enhancement, will be marked with correct label and project version of the issue completed; The handler will regularly close the issue without feedback for a long time; Issues without reference or retrieval value will be marked as status:invalid and does not need attention.
Project: KICS (Provisioning / Security & Compliance)
File: e84eaf4d-2f45-47b2-abe8-e581b06deb66.md

title: Ensure Administrative Boundaries Between Resources hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: e84eaf4d-2f45-47b2-abe8-e581b06deb66 Query name: Ensure Administrative Boundaries Between Resources Platform: Kubernetes Severity: <span style="color:#5bc0de">Info</span> Category: Access Control URL: As a best practice, ensure that is made the correct use of namespaces to adequately administer your resources. Kubernetes Authorization plugins can also be used to create policies that segregate user access to namespaces.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="5" apiVersion: v1 kind: Pod metadata: name: frontend namespace: cosmic-namespace spec: containers: name: app image: images.my-company.example/app:v4 securityContext: allowPrivilegeEscalation: false resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" name: log-aggregator image: images.my-company.example/log-aggregator:v6 securityContext: allowPrivilegeEscalation: false resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" apiVersion: v1 kind: Pod metadata: name: frontend2 namespace: cosmic-namespace spec: containers: name: app image: images.my-company.example/app:v4 securityContext: allowPrivilegeEscalation: false resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" name: log-aggregator image: images.my-company.example/log-aggregator:v6 securityContext: allowPrivilegeEscalation: false resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" ``` ```yaml title="Negative test num. 1 - yaml file" ```
Project: Teleport (Provisioning / Security & Compliance)
File: 0007-rbac-oss.md

authors: Alexander Klizhentas (sasha@goteleport.com) state: draft Enable role based access control in open source. Provide better user experience for open source users. Unify user experience, testing and development for open source branches. The following features will become available starting 5.1 version. Role Based Access Control All RBAC features, except FedRamp feature flags. Access Workflow Plugins Some access workflows plugins will become available in the open source: Access Workflows Golang SDK and API Webhook Slack Gitlab Mattermost JIRA Plugin PagerDuty Plugin The following features will remain enterprise only. FedRamp Max connections AC control (and all future AC controls): ```yaml role: options: max_connections: 3 ``` Teleport fips mode flag ```bash $ teleport start --fips ``` Single Sign On OIDC and SAML connectors Extended access workflows New feature flags allowing waiting room and always requesting flow will be enterprise only. ```yaml role: options: request_access: 'note|always' ``` OSS users can request roles using `tsh login --request-roles` on demand. User interface with approval requests, waiting room remains in enterprise. Open Source Users Open source users will be assigned to a new `user` role. This role is almost backwards compatible with builtin OSS role `admin`, except it does not allow to modify resources. Otherwise all users will become admins after migration: ```yaml role: name: user spec: options: port_forwarding: true maxsessionttl: 30h forward_agent: true enhanced_recording: ['command', 'network'] allow: logins: ['{{internal.logins}}'] node_labels: '': '' ``` Another role, `admin` will be created. ```yaml kind: role metadata: name: admin spec: allow: logins: ['this-login-does-not-exist'] rules: resources: ['*'] verbs: ['*'] deny: {} ``` Migration tutorial will advice to promote designated local user to admin: ```bash $ tctl users update alice --set-roles=admin ``` Github Connector Github in open source mode will support both `teamstologins` and `teamstoroles` modes. Adding users in tctl Both OSS (legacy) user add will be supported to preserve backwards compatibility. ``` $ tctl users add joe joe,root,e2-user $ tctl users add joe --traits=internal.logins=joe,root,e2-user --roles=user $ tctl users add --roles=admin joe ``` Tsh status Tsh status loses `RBAC only` notice: ``` $ tsh status ... RBAC is only available in Teleport Enterprise https://gravitational.com/teleport/docs/enterprise ```
Project: KICS (Provisioning / Security & Compliance)
File: 268ca686-7fb7-4ae9-b129-955a2a89064e.md

title: No Drop Capabilities for Containers hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 268ca686-7fb7-4ae9-b129-955a2a89064e Query name: No Drop Capabilities for Containers Platform: Kubernetes Severity: <span style="color:#edd57e">Low</span> Category: Best Practices URL: Sees if Kubernetes Drop Capabilities exists to ensure containers security context<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="26 28 21" apiVersion: extensions/v1beta1 kind: Deployment metadata: name: nginx-deployment labels: app: nginx spec: replicas: 3 selector: matchLabels: app: nginx template: metadata: labels: app: nginx spec: containers: name: payment image: nginx securityContext: capabilities: add: NETBINDSERVICE name: payment2 image: nginx securityContext: allowPrivilegeEscalation: false name: payment3 image: nginx ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: extensions/v1beta1 kind: Deployment metadata: name: nginx-deployment labels: app: nginx spec: replicas: 3 selector: matchLabels: app: nginx template: metadata: labels: app: nginx spec: containers: name: payment image: nginx securityContext: capabilities: drop: all add: NETBINDSERVICE ```
Project: KICS (Provisioning / Security & Compliance)
File: ddfc4eaa-af23-409f-b96c-bf5c45dc4daa.md

title: HTTP Port Open To Internet hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: ddfc4eaa-af23-409f-b96c-bf5c45dc4daa Query name: HTTP Port Open To Internet Platform: CloudFormation Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: The HTTP port is open to the internet in a Security Group<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="10 11" Resources: InstanceSecurityGroup: Type: AWS::EC2::SecurityGroup Properties: GroupDescription: Allow http to client host VpcId: Ref: myVPC SecurityGroupIngress: IpProtocol: tcp FromPort: 80 ToPort: 80 CidrIp: 0.0.0.0/0 ``` ```json title="Positive test num. 2 - json file" hl_lines="13 14" { "Resources": { "InstanceSecurityGroup": { "Type": "AWS::EC2::SecurityGroup", "Properties": { "GroupDescription": "Allow http to client host", "VpcId": { "Ref": "myVPC" }, "SecurityGroupIngress": [ { "IpProtocol": "tcp", "FromPort": 80, "ToPort": 80, "CidrIp": "0.0.0.0/0" } ] } } } } ``` ```yaml title="Negative test num. 1 - yaml file" Resources: InstanceSecurityGroup: Type: AWS::EC2::SecurityGroup Properties: GroupDescription: Allow http to client host VpcId: Ref: myVPC SecurityGroupIngress: IpProtocol: tcp FromPort: 80 ToPort: 80 CidrIp: 192.168.0.0/16 ``` ```json title="Negative test num. 2 - json file" { "Resources": { "InstanceSecurityGroup": { "Type": "AWS::EC2::SecurityGroup", "Properties": { "GroupDescription": "Allow http to client host", "VpcId": { "Ref": "myVPC" }, "SecurityGroupIngress": [ { "IpProtocol": "tcp", "FromPort": 80, "ToPort": 80, "CidrIp": "192.168.0.0/16" } ] } } } } ```
Project: Meshery (Provisioning / Automation & Configuration)
File: notary.md

layout: integration title: Notary subtitle: Collaborative and visual infrastructure as code for NGINX Service Mesh image: /assets/img/integrations/notary/icons/color/notary-color.svg permalink: extensibility/integrations/notary docURL: https://docs.meshery.io/extensibility/integrations/notary description: integrations-category: Provisioning 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: FOSSA (Provisioning / Security & Compliance)
File: carthage.md

Find any folder which contains a file named `Cartfile.resolved`. Skip all subdirectories if one is found. The `Cartfile.resolved` file contains a list of direct dependencies, which should each represent subfolders in the `Carthage/Checkouts` directory. This structure is recursively scanned and combined into a single analysis. See below for an example: ``` myproject Cartfile.resolved # ref to "Quick/Nimble" Carthage/ Checkouts/ Nimble/ Cartfile.resolved # ref to "mattgallagher/CwlPreconditionTesting" Carthage/ Checkouts/ CwlPreconditionTesting/ # and so on... ```