Errors & Fails to set file if location name includes a slash

[pmgarman]

nginx::resource::location { '/dir':
    ensure   => present,
    proxy  => 'http://127.0.0.1:2368',
    location => '/dir',
    vhost  => 'domain.com'
}

Error: Could not set 'file' on ensure: No such file or directory - /tmp/nginx.d/domain.com-500-/dir.puppettmp_2073 at 139:/etc/puppet/modules/nginx/manifests/resource/location.pp
Error: Could not set 'file' on ensure: No such file or directory - /tmp/nginx.d/domain.com-500-/dir.puppettmp_2073 at 139:/etc/puppet/modules/nginx/manifests/resource/location.pp

resolved by removing the slash from the name like below.

nginx::resource::location { 'dir':
    ensure   => present,
    proxy  => 'http://127.0.0.1:2368',
    location => '/dir',
    vhost  => 'domain.com'
}

[ghost]

I just ran into this myself today, and it is needlessly complicating my manifests.

I deny access to a number of directories and in order to keep things short, I'll declare a resource. Something like this:

define foo {
  nginx::resource::location { "${fqdn}-${name}":
      ensure              => present,
      www_root            => "/var/www/${fqdn}",
      location            => "$name",
      vhost               => "$fqdn",
      location_deny       => ["all"],
    }
}

Ideally, I could then do this:

foo{  ["/app/", "/includes/", "/lib/", "/var/export/" ]:  }

Instead, I have to do this:

foo{ "app":
  location=> "/app/"
 }

foo{ "includes":
  location => "/includes/"
} 
 etc...

[jfryman]

Take a look at the PR I just pushed - does this fix it for you?

[ghost]

Yep, works like a charm.

[jfryman]

🤘