hiera/roles/logprocessor.yaml - Issue 29338675: Issue 3694 - Introduce class adblockplus::log::processor and role logprocessor

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments.

Keyboard Shortcuts

	File
u :	up to issue
m :	publish + mail comments
M :	edit review message
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line
<Enter> :	respond to / edit current comment
d :	mark current comment as done

	Issue
u :	up to list of issues
m :	publish + mail comments
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue
# :	close issue

	Comment/message editing
<Ctrl> + s or <Ctrl> + Enter :	save comment
<Esc> :	cancel edit

Side by Side Diff: hiera/roles/logprocessor.yaml

Issue 29338675: Issue 3694 - Introduce class adblockplus::log::processor and role logprocessor (Closed)

Patch Set: Created March 18, 2016, 6:08 p.m.

Left:
Right:

Use n/p to move between diff chunks; N/P to move between comments.

Jump to:

View unified diff | Download patch

OLD	NEW
(Empty)
	1 # This role is meant for development, testing and debugging purpose only

	2 classes:

	3 adblockplus::log::processor:

	4 fluent:

	5 package:

	6 ensure: "2.3.1-0"

	7 provider: "apt"

	8 user:

	9 managehome: true

	10 groups:

	11 - "adm"

	12 - "users"

	13 shell: "/bin/bash"

	14

	15 # modules/fluent/manifests/config.pp

	16 fluent::configs:

	17 debugging_example:

	18 content: \|

	19 <source>

	20 @type debug_agent

	21 bind 0.0.0.0

	22 port 24230

	23 </source>

	24 ensure: "absent"

	25 name: "20-debug"

	26 monitoring_example:

	27 content: \|

	28 <source>

	29 @type monitor_agent

	30 bind 0.0.0.0

	31 port 24220

	32 </source>

	33 ensure: "present"

	34 name: "20-monitor"

	35 output_example:

	36 content: \|

	37 <match **>

	38 @type file

	39 path /tmp/fluentd-example.log

	40 </match>

	41 ensure: "present"

	42 name: "80-output"

	43

	44 # modules/fluent/manifests/gem.pp

	45 fluent::gems:

	46 fluent-plugin-secure-forward:
	Fred 2016/03/21 16:33:35 Do we really need/want this plugin in the developm Do we really need/want this plugin in the development environment? mathias 2016/03/21 16:36:22 Actually I do not want any of these plugins in dev Show quoted text On 2016/03/21 16:33:35, Fred wrote: > Do we really need/want this plugin in the development environment? Actually I do not want any of these plugins in development, this file is merely meant as an example. I expect nobody to actually use the role as-is, but even if so, a plugin more or not should not matter. However, what about setting ensure to "absent" for this one, but keep the grep being "present"? That would serve the very same purpose, without the confusion about an unused plugin. Fred 2016/03/21 16:42:20 That suggestion sounds reasonable to me. That suggestion sounds reasonable to me.
	47 ensure: "present"

	48 fluent-plugin-grep:

	49 ensure: "present"

	50

OLD	NEW

« no previous file with comments | « no previous file | modules/adblockplus/manifests/log/processor.pp » ('j') | no next file with comments »