Morten Torkildsen

I'm not able to reproduce this situation. So just to clarify: * The package in question here (nephio-dev-deploy-0247f2adfd09fa113737ab033918095bdfaf16eb) is the result of running `rpkg clone` on a package created manually...

It looks like this removes the `message` column. How do we provide more information to users about why a resource isn't successfully reconciling? While ideally we should have everything based...

The issue that the error is not being printed seems like something we should fix in the regular command as well as in the alpha command.

This seems like a good use-case for bulk function execution: https://github.com/GoogleContainerTools/kpt/issues/3350

As mentioned in the issue, kpt used to rely on a ConfigMap to store the inventory list rather than the ResourceGroup type. We chose to change to use a CRD...

We only see very occasional flakes, so I think we can just wait for GitHub Action to do the upgrade.

So Porch already captures the author of each task (i.e. commit) in git. Porch gets this information from the kubernetes apiserver, so the author of each commit will be set...

So I think we want to implement this as CRD and controller rather than as a regular API on the aggregated APIserver. So we need to define what the CRD...

Updating a published packagerevision doesn't really make sense, so that will require creating a new packagerevision. I don't remember right now how this is handled in the update logic. But...

Yeah, so doing a merge update after doing replays should be fine. With the current task model and replay, there isn't any difference between a package created from `v1` and...