Morten Torkildsen
Morten Torkildsen
This updates kpt and porch to use go 1.18.
porch currently only supports basic authentication against git repositories. We need to support additional auth schemes such as ssh keys and GCP service accounts to enable integration with other git...
Currently the porch api doesn't expose a package resource. Instead, we expose package revisions with the grouping revisions that is part of the same package only available through the `PackageName`...
There are several issues with the package deletion flow that we want to address: * Currently every revision of a package has to be deleted individually. We should allow for...
Currently Porch doesn't expose any information about audit information about edits and approvals of packagerevisions through the API. We should capture who edited/proposed/approved a packagerevision and when it happened and...
Keeping in mind blast radius and permissions
If there is a conflicting inventory that can be resolved by the provided inventory policy, we currently just print an error message that there is a conflict. We should print...
We want to let users do operations on multiple packages at the same time, i.e. bulk. The most obvious use-case for this is letting users update all downstream packages in...
During updates we might encounter merge conflicts. kpt currently only supports a single automated conflict resolution strategy (take upstream), which isn't the right one in all cases. We should support...
We are currently discussing two different alternatives for doing updates in porch. It is the current merge behavior from kpt (which is roughly equivalent to how we can do a...