hiera/vagrant.yaml - Issue 4810150141493248: Issue 122 - Puppet ENC via Hiera

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/vagrant.yaml

Issue 4810150141493248: Issue 122 - Puppet ENC via Hiera (Closed)

Patch Set: Created Sept. 8, 2014, 11:56 a.m.

Left:
Right:

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

Jump to:

OLD	NEW
(Empty)
	1 ---

	2 :backends:

	3 - yaml

	4 :yaml:

	5 :datadir: /vagrant/hiera

	6 :hierarchy:

	7 - "environments/development/base"

	8 - "environments/development/hosts"

	9 - "nodes/%{::hostname}"
	Wladimir Palant 2014/09/09 18:15:06 That's the wrong approach - we have YAML files per That's the wrong approach - we have YAML files per server type, not for individual servers. So for example server codereview1 has type codereview, meaning that nodes/codereview.yaml should be applied for it. Otherwise we would need a separate YAML file for each filter server. mathias 2014/10/08 03:02:33 Well, actually this is not wrong. Having separate Show quoted text On 2014/09/09 18:15:06, Wladimir Palant wrote: > That's the wrong approach - we have YAML files per server type, not for > individual servers. So for example server codereview1 has type codereview, > meaning that nodes/codereview.yaml should be applied for it. Otherwise we would > need a separate YAML file for each filter server. Well, actually this is not wrong. Having separate or linked specs per host is quite common, especially when adjusting to heterogeneous infrastructure. However, we where planning on integrating roles resp. types anyway (and have already done so, see next patch-set), so that host-specific stuff is still possible but not used if not required.
	10 - common

	11

OLD	NEW