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
A kpt pkg get followed by a kpt pkg update --strategy force-delete-replace results in a Kptfile that has the git information as specified in the kpt pkg update but the pipeline section of the Kptfile is from the initial kpt pkg get and not the pipeline from the kpt pkg update. The consequence is that one cannot update the package pipeline.
The problem also applies to strategy fast-forward.
Tested using kpt version 1.0.0-beta.38 and 1.0.0-beta.43.
Expected behavior
A
kpt pkg get
followed by akpt pkg update --strategy force-delete-replace
results in aKptfile
that has the git information as specified in thekpt pkg update
but the pipeline section of theKptfile
is from the initialkpt pkg get
and not the pipeline from thekpt pkg update
. The consequence is that one cannot update the package pipeline.The problem also applies to strategy
fast-forward
.Tested using
kpt
version1.0.0-beta.38
and1.0.0-beta.43
.Detailed description of the problem and steps to reproduce it can be found here: https://github.com/michaelvl/kpt-test
The text was updated successfully, but these errors were encountered: