On 18 August 2017 at 12:58, Andrew Schofield <[email protected]> wrote:
> Activation keys are good for the initial host registration only. If you > assign new products to a content view then you need to : > > a) Add these to the activation key (so newly provisioned servers get the > new repos) > b) Either manually / automatically subscribe servers to the new products > from the host (command line / scripts / puppet etc) or use the web ui / > hammer / api todo this > > Subscription manager (from memory I'm probably wrong on timings) will > auto-refresh every 4 hrs or so. > Ah! This answers a question of mine from another thread. Can someone give an example of the hammer command to update the /etc/yum.repos.d/redhat.repo from the server? Neither hammer repository nor hammer repository-set seem quite right. Alternatively - and probably preferably (so that it can be scripted to run via ansible) - the puppet command that would pull updates to the repo file? cheers L. ------ "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics is the insistence that we cannot ignore the truth, nor should we panic about it. It is a shared consciousness that our institutions have failed and our ecosystem is collapsing, yet we are still here — and we are creative agents who can shape our destinies. Apocalyptic civics is the conviction that the only way out is through, and the only way through is together. " *Greg Bloom* @greggish https://twitter.com/greggish/status/873177525903609857 -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
