Configuration file as a command line argument

Bug #1101180 reported by Javier Collado
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
UTAH
Fix Released
Wishlist
Javier Collado

Bug Description

Currently, it's possible to use a json configuration file to overwrite some of
the values provided by default. This is useful to configure some parameters
(for example, log file names) that don't have its own command line option, but
that are needed in some environments.

However, it turns out, that the way to pass such a configuration file name
is through an environment variable. To make things user friendlier, it would
be desirable to have a command line option to pass that configuration file.

Related branches

Changed in utah:
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
Javier Collado (javier.collado) wrote :

This is related to bug#1173124

Changed in utah:
assignee: nobody → Javier Collado (javier.collado)
Changed in utah:
status: Triaged → In Progress
milestone: none → 0.13
Revision history for this message
Javier Collado (javier.collado) wrote :

The fix that has been committed, doesn't really add an option to specify a
configuration file, but adds a logpath option that so that the configuration
file is no longer needed.

If a need arises in the future to pass the configuration file path as a command
line option, this bug can be reopened.

Changed in utah:
status: In Progress → Fix Committed
Changed in utah:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.