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
I've noticed that the re-arrangement of subpackages: sections introduces changes to the lock file that are more just clutter than anything else. On a recent update of Kubernetes, I spent quite a bit of time just tracking movements inside of the lock file.
It seems to me that we could just sort subpackages lexicographically, and that would lead to predictable ordering. The easiest way to do this would be in a marshaling hook in the cfg/lock.go and cfg/conf.go files.
The text was updated successfully, but these errors were encountered:
I've noticed that the re-arrangement of
subpackages:
sections introduces changes to the lock file that are more just clutter than anything else. On a recent update of Kubernetes, I spent quite a bit of time just tracking movements inside of the lock file.It seems to me that we could just sort subpackages lexicographically, and that would lead to predictable ordering. The easiest way to do this would be in a marshaling hook in the
cfg/lock.go
andcfg/conf.go
files.The text was updated successfully, but these errors were encountered: