Bi-weekly call with the Porter maintainers, contributors and community. :::info Agenda: https://porter.sh/dev-meeting/ Zoom: https://porter.sh/zoom/dev/ passcode 77777 Calendar: Get the recurring calendar invite from https://porter.sh/calendar Time: Every other Thursday at 11am Central Time (17:00 UTC) Everyone is invited! 💖 Attendees can add agenda items before a meeting.

Do we care to make the test bundle realistic in any way? We can have a mega test bundle that does dependencies, separate from our main bundle if it causes performance problems Then have an example bundle or two in our examples repo that really walks through how to use the feature. Make a paired tutorial to explain how to use them. What should our test bundle(s) have so that we have exercise all of depsv2? More than one level deep of dependencies. So root -> A -> B Supports a range of bundle versions, e.g. mysql bundle has more than one available version Has a bundle interface specified as a bundle reference. This bundle could be a porter bundle or something handmade and published just to provide an interface

Outline https://github.com/cncf/toc/pull/951/files?short_path=bcaa7ab#diff-bcaa7ab661b159edfd0e192b68681fff7f6d95a07d69360cdff548b9f48d998b say what we did in 2022 (use the section from the annual review)maybe we can say how adoption of v1 is going so far using this link: https://hanadigital.github.io/grev/?user=getporter&repo=porter welcome new contributors and point out our contributing guide what is the operator, who would be interesting in using the operator, what's it used for. high level roadmap for the operator

Porter creates installers for cloud-native applications and their infrastructure. Package your application, client tools, configuration, and deployment logic into an installer that you can distribute and run with a single command. Metrics Metric Last Review Today Stars

Major features Porter Operator stable release, with tiny grpc service for outputs pep 003 advanced dependencies - "bundle workflow" run multiple bundles and pass data between them pep 005 mixins are bundles build, distribute and execute mixins using CNAB bundles

View slides from meeting Open Questions Can we use third party workflow engines? Which ones would work? Argo Brigade Cadence?

on the host porter client -> porter install inside the container invocation image -> porter run inside porter runtime binary parses the porter.yaml and makes Steps **FOR EACH STEP**

Good First Issue Link to the code (down tothe line) that needs to be changed Explain the desired solution, why it needs the change, and link to relevant docs Explain where to put in a test and what the test should contain Say which branch to make the change on Include reproduction steps Include this at the bottom (change based on which branch) See our [Contributing Tutorial](https://release-v1.porter.sh/contribute/tutorial) and [New Contributor Guide](https://github.com/getporter/porter/blob/release/v1/CONTRIBUTING.md) for help getting started contributing to Porter.

Permalink: https://hackmd.io/@porter/v1-release-planning Agenda Timeline and remaining issues https://github.com/getporter/porter/milestone/16 Yingrong has been vetting remaining bugs Possible errors users WILL see, we need docs ready to support these

We will get together occasionally and do a deep dive in various topics related to Porter and its tech. These are unscripted and unprepared, so join in to ask questions and watch us collaboratively figure stuff out live. Suggested topics [ ] Porter Code Structure [ ] Porter Operator [ ] How docker works how a container runs what's an image

Porter creates installers for cloud-native applications and their infrastructure. Package your application artifact, client tools, configuration and deployment logic together as a versioned bundle that you can distribute, and then install with a single command. Porter joined the CNCF Sandbox in September 2020. Metrics Metric 2020 Today

This document outlines a new structure for the porter docs website (https://porter.sh/docs). It identifies how the navigation should be grouped and what content we should include. Goals: Have a consistent doc structure where we can keep adding items without exploding the nav menu Right now we focus heavily on reference pages. We need more concept and task pages. ? If something is reference/concept/task focused should it be in a a separate location? I was thinking of grouping by doc type, and then use the next steps on each page to cross link to relevant things. For example the concept page for parameters would also link to a task page for parameters, and the reference. Getting Started

Cut a release Customize the release notes on GitHub Email porter@groups.io announcing the release and calling out key highlights. For major and minor releases (not patch), tweet and comment in the porter channel in Slack with a link to the release notes. If the release contains a new feature, write a blog post. Email Template Porter VERSION Release Notes

We have some BIG proposals outstanding for Porter that would push off a v1.0 if we tried to get all of them (and their breaking changes) in before cutting a v1. Since this could take the next year or more, we want to stabilize the current fucntionality and ship a v1 instead. A v1 would not include these recent propoals: Mixin Versioning. We may break this up and put some in v1.0, but reserve the larger changes which are related to mixins as bundles for later. Mixins as Bundles Advanced Dependencies Labels and Namespaces Log Sources and Levels

What is the state of signy now? not implemented from spec: in-toto root key (open signy PR) Moving signatures around, signed in acr, can pull and verify yay! But when I move to an on-prem registry (off network), or I archive a thick bundle to move across an airgap. Can't move the signature (due to notary v1 limitations). You have to re-sign. Can't export signature metadata to move it. If the registry is compatible and nothing changes, it's possible to get the same signature but not guaranteed. in-toto attestation that you pulled and verified and resigned. If someone wanted to do supply chain security what components are needed and what is the workflow? signy assumes that you used the in-toto toolchain, doesn't make assumptions about layout. https://in-toto.engineering.nyu.edu/ walk through to get a layout

PorterOps not only gives you a native, integrated experience for managing your bundles with Kubernetes but is the recommended way to automate your bundle pipeline with support for GitOps. Automate building and publishing bundles, when the bundle definition changes or new versions of images used by the bundle are available. Automatically deploy new versions of bundles. Isolated environments for running bundles in your organization, limiting access to secrets used by the bundles using namespaces and RBAC. Create and respond to events on your cluster to integrate bundles into your pipeline. Why Porter Operator and not CNAB Operator? PorterOps uses the Porter CLI, its configuration, storage, and accompanying ecosystem to manage bundles. It supports running any CNAB-compliant bundle, but this is not the CNAB Operator. It has features specific to the Porter ecosystem and you cannot swap from using Porter to another tool.

https://github.com/getporter/porter/issues/1335 https://github.com/getporter/porter/issues/1334 name: porter-hello version: v0.1.0 porter build && porter publish --registry carolynvs/ name: porter-hello # no version

Storage migrate credentials and/or claim storage, we decide based on schema.json porter storage migrate copy the named storage account contents (if not specified the source is the active store) to destination porter storage copy [NAME] --destination NAME