Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 When upgrading catalogd to a revision that uses HTTPS, content URLs of existing Catalog objects remain unchanged. #270

Open
joelanford opened this issue May 15, 2024 · 1 comment

Comments

@joelanford
Copy link
Member

I believe this is because of this check:

// if ResolvedSource is not nil, it indicates that this is not the first time we're
// unpacking this catalog.
if catalog.Status.ResolvedSource != nil {
if !unpackAgain(catalog) {
return ctrl.Result{}, nil
}
}

I think there are two things to fix:

  1. We should not read our own status to assess state. The Catalog status is where we write state after reading from elsewhere. In this case, we should read the actual source of truth (the cache?) to see if we have something unpacked.
  2. Even if we don't need to unpack again, that doesn't mean there is nothing to do. For this bug, the thing we are missing is updating the content URL now that we're serving it via https.
@joelanford
Copy link
Member Author

Hmm. It seems there is no way for the LocalDir storage implementation to determine if what it has stored is actually up-to-date. Solving this problem may require a more invasive change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant