[BUG] flytectl upgrade is broken after moving to the monorepo about flyte

[novahow]

#take

[runllm]

The issue with the flytectl upgrade command breaking after the monorepo migration is known. The error traces indicate issues with unexpected EOF and missing backups for rollback. This is likely due to changes in the repository structure and dependencies.

Would you like more details on potential fixes or workarounds?

Sources:

• #4305
• #1233
• https://discuss.flyte.org/t/16022712/hey-folks-i-m-trying-to-update-our-go-repositories-using-the/

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!

[eapolinario]

The work here has to do with how to list flytectl releases from the monorepo and use that list of releases as opposed to all releases.

More specifically, we use https://github.com/mouuff/go-rocket-update to provide this self-upgrade functionality, the issue is that when we check the releases this library ends up calling a github API that doesn't return the flytectl releases (which use git tags of the form flytectl/vX.Y.Z).

Resolving this issue will require some investigation. Here are some ideas:

1. implement a new provider that understands flytectl releases (similar to how we do in

   flyte/flytectl/pkg/github/githubutil.go

   Line 76 in 31802c7

   releases, _, err := g.ListReleases(context.Background(), owner, repoName, &github.ListOptions{

   )
2. use the zip provider (given that we download the new release separately).

[novahow]

@eapolinario Hi, I investigated the issue and implemented a new provider. I'm curious about how flytectl upgrade used to work before moving to monorepo? because according to

flyte/flytectl/cmd/upgrade/upgrade.go

Line 122 in 25c3596

if isGreater, err := util.IsVersionGreaterThan(latest, stdlibversion.Version); err != nil {

latest infers smth like "v0.8.20", and stdlibversion.Version is the version tag of flyte, which may be "v1.12.0" . How did this comparison work before the monorepo migration?

[eapolinario]

latest infers smth like "v0.8.20", and stdlibversion.Version is the version tag of flyte, which may be "v1.12.0" . How did this comparison work before the monorepo migration?

before the monorepo migration, stdlibVersion was the current version of flytectl as defined here. Notice that the before the move to the monorepo this referred to git tags of the flytectl repo.