You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original issue URL: kptdev/kpt#3269
Original issue user: https://github.com/mortent
Original issue created at: 2022-05-27T21:52:25Z
Original issue last updated at: 2022-05-27T21:52:25Z
Original issue body: Should we:
hide packages in main? (well, but they are there)
not merge them into main at all? (this will likely not match customer expectation of branching/tagging in Git)
or de-dupe identical packages? (in this case packages will pop up 'out of nowhere' when a duplicate blueprint is deleted but some of the dupes still remain)
We have already added functionality that tags the latest revision (kptdev/kpt#3015).
Original issue comments:
The text was updated successfully, but these errors were encountered:
tliron
transferred this issue from nephio-project/porch-issue-transfer
Apr 23, 2024
This is to do with a PackageRevision being created for main.
Blueprints:
When you approve, Porch commits the package to main and creates a tag. So there are two PackageRevision instances created, one for the tag and another for main.
We need to rethink how this works because this automatically created PackageRevision is confusing for users.
The discovery function should not rely on the main PackageRevision.
Deployment:
This PackageRevision is also used for deployment. The main PacakgeRevision may have been created for deployment.
Original issue URL: kptdev/kpt#3269
Original issue user: https://github.com/mortent
Original issue created at: 2022-05-27T21:52:25Z
Original issue last updated at: 2022-05-27T21:52:25Z
Original issue body: Should we:
We have already added functionality that tags the latest revision (kptdev/kpt#3015).
Original issue comments:
The text was updated successfully, but these errors were encountered: