[bug]: Repositories are not refreshed after switching repository source

[mcm1957]

No existing issues.

• [X] There is no existing issue for my problem.

Description

I see multiple reports at forum that user do not see the lastest Release even after switching the repository (at admin UI) from stable to latest. In all cases pressing "Check for updates" Button does the trick and the repostory data is correct / newest versions are ready to be installed.

I think there is no (working) refreh of repostory data when switching repositories. Please check / correct / add.

The goal should that after switching repository from stable to latest (or opposite) the functionality of "Check for Updates") is performed.

Note: As leaving the screen after switchiung repositories lasts a noticeable time, something is done there. Maybe the refresh is done using the old configuration ?

P.S: If this is considered a Feature Request, dfeel free to relabel it!

Reproduction instruction

• select stable rpository
• ensure that OLD LATEST repository data is loaded (do'nt k now how to do unless to wait some days ...)
• switch to latest repository
• check available version for an adapter updated shortly (after last loading latest repository data)

@copilot Please add the following functionality: After a user changes the active repository by selecting another repository execute the functionality which is normally performed when clicking the Button "search for Updates"

[foxriver76]

Isn't this an Admin issue?

[mcm1957]

Might be...

But does admin more than use the cli comman to set the repository? I did not check behavior if repo is changed using cli.

In general I do not expect thst there are two code paths changing the used repository. Und for sure clivdoes not call an admin function.

But feel free to move issue. But behavior using cli should be checked too.

[foxriver76]

@mcm1957

In general I do not expect thst there are two code paths changing the used repository. Und for sure clivdoes not call an admin function.

what do you mean? Admin needs to set repository then needs to perform update after repository has been set to obtain the new one. these are two different commands and maybe admin does not wait until first is finished or some might be the issue

[mcm1957]

I would expect that there is a command to set the active repository. (Sorry, I could not find it as iob --help. So either help is incomplete, the command is hidden on purpose or I need new glasses :-) ).

So I think that admin issues some command like

'iob set repository <name)'

I think that this command should do an update without waiting for an extra update command as updateing the data is part of setting an repository active in my oppinion.

But if the overall design is that adin should do the job its ok for me too. The primary problem at forum is always related to updates using UI. So please move the issue to admin so that it could be analyzed / improved there.

P.S. Is there any command to switch stabel /lates at commandline?

[foxriver76]

Please no additional magic in the the repo set command. Also in the system.repositories object you will have a separate key for stable and beta so if admin is still showing old updates (updates from the other repo), it is suuuupper unlikely that it is a controller issue because that would mean that controller has set content of one repo to the key of another.

[mcm1957]

Ok - could you please move the issue then?

[foxriver76]

Also re-validated it cli looks good to me