Christopher Fry

Porch returns a generic error when Kptfile validation fails on render

2

Porch always returns a generic error when a Kptfile validator function fails on render. ### Expected behavior Porch should return the fail message of the validator. ### Actual behavior Porch...

Update the [Config as Data UI Installation Guide](https://kpt.dev/guides/porch-ui-installation) with instructions on how to deploy the Config as Data UI to a [kind](https://kind.sigs.k8s.io/) cluster.

Add support to allow Porch to access authenticated container repositories for Kptfile function images. Currently Porch can only pull images from public repositories where no authentication is required, or from...

PackageRevision tasks continuously grows in size

2

With the PackageRevision tasks list (in `spec.tasks`) always being appended to anytime a package revision is updated, we'll need a way to compact this list after a number of tasks...

### Expected behavior You should always be able to create a new revision of a package using `kpt alpha rpkg copy` even if the package's upstream repository is unregistered. ###...

Slight differences in Kptfile upstream formatting with `kpt get` and `kpt alpha rpkg clone`

1

### Expected behavior The Kptfile `upstream(Lock).git.repo` is formatted the same when cloning the same package using `kpt get` and `kpt alpha rpkg clone`. ### Actual behavior The `repo` and `directory`...

Requesting kpt is updated to allow Kptfile pipeline functions to reference configs by resource name. Today, the [Kptfile Function spec](https://pkg.go.dev/github.com/GoogleContainerTools/skaffold/pkg/skaffold/render/kptfile#Function) allows configs to be either inline or referenced by config...

To improve the user experience, there's a request for the Config as Data UI to save and render more frequently when a user is actively updating a draft package. Advantages...

Porch allows duplicate package revisions to be created

2

### Expected behavior Porch should not allow a package revision to be created that matches the package name and revision of a package revision that already exists. In this scenario,...

Add first class fields to PackageRevision resource for upstream package name, revision, and repository name

2

Requesting first class fields are created in the `PackageRevision` resource for the upstream package name, upstream revision, and upstream repository name. Using first class fields eliminates the need of clients...