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

Establish behavior for installed content no longer present in the catalog #3122

Open
dtfranz opened this issue Nov 28, 2023 · 0 comments
Open
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@dtfranz
Copy link
Contributor

dtfranz commented Nov 28, 2023

Continuation of our discussion here.

We need to both capture existing behavior as well as decide on new behaviors for how we inform users that their installed content is no longer present in the catalog.

This is particularly relevant to any deprecated content, because users with deprecated content that miss a catalog update marking the content as such before a prune will not receive the "Deprecated" status updates.

What we've proposed so far is informing users in this situation that since their content is no longer in the catalog it may be deprecated. For instance:

entry, ok, err := entryForThisSubscription(sourceProvider, sub)
if err != nil {
   setDeprecationConditionsUnknown(sub, err)
} else if !ok {
   setDeprecationConditionsUnknown(sub, errors.New("could not find catalog entry matching subscription"))
} else {
   setDeprecationConditionsFromEntry(sub, entry)
}
@dtfranz dtfranz added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

1 participant