rollouts: RSync naming schemes leads to failure for long git repo/org names.

Open droot opened this issue 2 years ago • 1 comments

Current implementation allows RSync names to be arbitrarily long (uses org/repo-name of the git repo) that fails whenever it hits the name limit. The task is to come up with a better naming scheme (probably using -<SHA(pkg attributes)>)

Mar 02 '23 21:03 droot

As part of this change https://github.com/GoogleContainerTools/kpt/pull/3853, remote-sync don't use orgname/repo-name, instead they use the prefix <gitlab|github>-<repo-id|project-id>-<dir-name>. So this should mitigate the problem to some extent. Though long nested directory paths can still lead to this problem.

But lowering the priority.

Mar 08 '23 19:03 droot