add new repo to content view, publish new version and promote it to our dev env. This kicks off a smart proxy but once finished the new repo does not getting seen by end client.
new repo available
Foreman and Proxy versions:
Current fix has been to change lifecycle env for that end client to one for a different content view, refresh on the client, then change LC again to the correct view and refresh. Cert gets replaced and it can then see the new repo.
Need to know why this isnt happening automatically.