This fixes an issue where catalog/charts were stale after a repo was updated

[codyrancher]

Summary

The catalog.cattle.io.clusterrepos/{repo} resource doesn't subscribe to updates. We now force a full request in the areas where it's appropriate to do so.

fixes #7668

Testing

If you want me to modify the repo for you just let me know. If you want to test it yourself the following notes should be helpful.

To test this you'll need a chart repo that you can modify. I created a simple repo at https://github.com/CodyrancherTest/charts/tree/master.
To modify do the following:

• fork that repo
• modify the values.yaml (I just change the logLevel)
• run helm package . within the root of the directory
• Add, commit and push all of the changes to your github repo

[AndrewHoffmanQA]

@codyrancher I will gladly take you up on the offer to modify the repro, would you be interested in walking through it on a call?

I have a couple questions about the order of operations for this bug and repro steps on this work item vs the actual ticket and would benefit from the KT in general.

[catherineluse]

@codyrancher I'm working on a related issue and have a question. Since we are now force fetching all chart repos on most chart pages, does that make the "Refresh" button redundant? (The button in the linked issue on the git repositories list page) I'm thinking either the button should be removed, or we should do less force-fetching elsewhere to justify the existence of the button and improve performance for setups with a huge number of helm chart apps.

[codyrancher]

@codyrancher I'm working on a related issue and have a question. Since we are now force fetching all chart repos on most chart pages, does that make the "Refresh" button redundant? (The button in the linked issue on the git repositories list page) I'm thinking either the button should be removed, or we should do less force-fetching elsewhere to justify the existence of the button and improve performance for setups with a huge number of helm chart apps.

@catherineluse I don't think the refresh button is redundant. I'm having to force refresh the data because the resource doesn't receive automatic updates over the socket. If you want to do less force fetching for performance reasons I think that's a reasonable goal but I think it will technically be wrong since the data could be stale.