Noissue - Generate content on provision

modules/web/manifests/server.pp

Index: modules/web/manifests/server.pp
===================================================================
--- a/modules/web/manifests/server.pp
+++ b/modules/web/manifests/server.pp
@@ -12,6 +12,8 @@
 
   include sitescripts
 
+  $PYTHONPATH = 'PYTHONPATH=/opt/cms:/opt/sitescripts'
+
   # Ensure there is at least one character in the respective strings;
   # see https://codereview.adblockplus.org/29329028/#msg3
   validate_re($vhost, '.+')
@@ -25,7 +27,7 @@
 
   Cron {
     environment => concat(hiera('cron::environment', []), [
-      'PYTHONPATH=/opt/cms:/opt/sitescripts',
+      $PYTHONPATH,
     ]),
   }
 
@@ -114,6 +116,21 @@
     creates => "/home/www/${repository}/.hg/hgrc",
   }
 
+  $initialize_content_exec = [
+    'python', '-m', 'cms.bin.generate_static_pages',
+    "/home/www/${repository}", "/var/www/${vhost}",
+  ]
+
+  if $::environment == 'development' {

[mathias, 2017/05/12 16:42:12]

If you'd used refreshonly => $::environment != "development" on the exec
resource you would not only minimize complexity and have a resource definition
available irregardless of whether it runs (which eases ordering when necessary),
but also ensure a newly provisioned server in production would be able to serve
content right after provisioning.

[f.lopez, 2017/05/12 17:43:39]

You are right.

+    exec {"initialize_content":
+      command => shellquote($initialize_content_exec),
+      path => ["/usr/bin/", "/bin/"],
+      user => www,
+      require => [Exec["fetch_repo"], Exec["fetch_cms"]],
+      environment => $PYTHONPATH,
+    }
+  }
+
   file {'/var/www':
     ensure => directory,
     mode => 755,
@@ -137,7 +154,7 @@
 
   cron {'update_repo':
     ensure => present,
-    command => "hg pull -q -R /home/www/${repository} && python -m cms.bin.generate_static_pages /home/www/${repository} /var/www/${vhost}",
+    command => "hg pull -q -R /home/www/${repository} && ${initialize_content_exec} /home/www/${repository} /var/www/${vhost}",

[mathias, 2017/05/12 16:42:12]

Please export the commands preceeding and following $initialize_content_exec in
the same fashion as the latter, and join([$preceding, $i_c_e, $following], "
&&\n") afterwards, or similar (i.e. join(['set -e', $p, $i_c_e, $f], ';')).

[f.lopez, 2017/05/12 17:43:39]

I actually thought of this but for a different commit, should I do it in this
one then? cause I'd like to do it for all the exec resources in this manifest
since I'm already here

     user => www,
     minute  => '5-59/20',
   }