Expected behavior
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.
Detailed description of the problem and steps to reproduce it can be found here: https://github.com/michaelvl/kpt-test
Expected behavior
A
kpt pkg getfollowed by akpt pkg update --strategy force-delete-replaceresults in aKptfilethat has the git information as specified in thekpt pkg updatebut the pipeline section of theKptfileis from the initialkpt pkg getand 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
kptversion1.0.0-beta.38and1.0.0-beta.43.Detailed description of the problem and steps to reproduce it can be found here: https://github.com/michaelvl/kpt-test