Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update non-hiera usage (see #536) #669

Merged
merged 2 commits into from
Aug 11, 2015
Merged

Update non-hiera usage (see #536) #669

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
69aa880
Update hiera.md
Hufschmidt Aug 11, 2015
5fa8182
Update hiera.md
Hufschmidt Aug 11, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 17 additions & 7 deletions docs/hiera.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,23 +27,33 @@ Magically, it's all done! Work through these until the deprecation notices go aw

Maybe for some reason, Hiera isn't being used in your organization. Or, you like to keep a certain amount of composibilty in you modules. Or, hidden option #3! Regardless, the recommended path is to instantiate your own copy of Class[nginx::config] and move on with life. Let's do another example.

Assume the same code block as before:
Assume you have the following code block:

```ruby
class { 'nginx':
gzip => false,
class { 'nginx' :
manage_repo => false,
confd_purge => true,
vhost_purge => true,
}
```

Should become...
This should become...

```ruby
include nginx
class { 'nginx::config':
gzip => false,
Anchor['nginx::begin']
->
class { 'nginx::config' :
confd_purge => true,
vhost_purge => true,
}

class { 'nginx' :
manage_repo => false,
}
```

The order in which this commands are parsed is important, since nginx looks for nginx::config via a defined(nginx::config) statement, which as of puppet 3.x is still parse-order dependent.

# Why again are you doing this?

Well, the fact of the matter, the old Package/Config/Service pattern has served us well, but times are a-changin. Many users are starting to manage their packages and service seperately outside of the traditional pattern (Docker, anyone?). This means that in order to stay true to the goals of Configuration Management, it is becoming necessary to make less assumptions about how an organizations graph is composed, and allow the end-user additional flexibility. This is requring a re-think about how to best consume this module.
Expand Down