[katello-devel] purpose of --katello-configuration-files-only on katello-configure

Justin Sherrill jsherril at redhat.com
Tue Mar 26 15:00:24 UTC 2013


On 03/26/2013 10:39 AM, Justin Sherrill wrote:
> Hey Petr (or anyone else who can chime in),
>
> I have noticed that we added this functionality to katello configure 
> to update ONLY katello config files for the upgrade process.  Is there 
> any reason we don't want to upgrade all config files that we are 
> concerned with (pulp, candlepin, foreman, elasticsearch).    For 1.3 
> we do need to run through the pulp config files because they have all 
> changed, and this is not currently being done.  I can see obvious 
> reasons to run through all config files, as there might be other 
> changes in other config files.  What was the reason to just do the 
> katello ones?
>
Oh right so the full katello-configure get run later in the process, but 
after the db-migrate.  I'm curious why not go ahead and run 
katello-configure fully at that point (before the db:migrate).  I'll 
play around with it.

-Justin

> Thanks,
>
> -Justin
>
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel




More information about the katello-devel mailing list