Permalink
Browse files

Documentation bug for config_file_notify/require (#63)

* Documentation bug for config_file_notify/require

In the documentation the quoting was not correct.

* Documentation bug for config_file_notify/require

Quoting Problem in documentation
  • Loading branch information...
dagobert authored and alvagante committed Jan 11, 2019
1 parent 71248b6 commit 329603f8957f37438a669772fad28c7fb6f0131c
Showing with 4 additions and 4 deletions.
  1. +2 −2 README.md
  2. +2 −2 manifests/conf.pp
@@ -166,8 +166,8 @@ By default, configuration files managed by tp::conf automatically notify the ser
You can also set custom resource references to point to actual resources you declare in your manifests:

tp::conf { 'bind':
config_file_notify => Service['bind9'],
config_file_require => Package['bind9-server'],
config_file_notify => 'Service[bind9]',
config_file_require => 'Package[bind9-server]',
}

It's possible to manage files with different methods, for example directly providing its content:
@@ -105,8 +105,8 @@
# @example to customise notify and require dependencies
#
# tp::conf { 'nginx::nginx_fe.conf':
# config_file_notify => "Service['fe_nginx']",
# config_file_require => "Class['site::fe::nginx']",
# config_file_notify => 'Service[fe_nginx]',
# config_file_require => 'Class[site::fe::nginx]',
# }
#
# @example to disable validation for a configuration file

0 comments on commit 329603f

Please sign in to comment.