On Thu, Oct 3, 2013 at 5:54 AM, Julien Danjou <jul...@danjou.info> wrote:
> On Wed, Oct 02 2013, Thomas Maddox wrote: > > > I'm working to make the sample pipeline optional and I'm stuck at a > > decision point about whether I ought to use a collector config option > > (like 'enable_sample_pipelines'), or let it be driven by setup.cfg (i.e. > > the existence of sample plugin references). My favorite right now is the > > former, but I wanted to entertain the latter and learn in the process. > > What about having an empty pipeline.yml? > Modifying the pipeline's configuration file is the right way to go. If an empty file isn't valid, then a single pipeline that subscribes to no events may work. The other proposed solution isn't going to work. setup.cfg is not meant to be a deployer-facing configuration file. It's a packaging file that tells the system what files are part of the app or library. Doug
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
