Avoid using lookup() in the module
Avoid using lookup() in the module

Relying on lookup() has undesired side effects when following the roles
& profile pattern recommendations thoroughly.

A user may have configured bacula this way, expecting to use the pool
"Target":

```puppet
class profile::bacula_client {
  class { 'bacula::client':
    default_pool => 'Target',
    ...
  }
  ...
}

class profile::my_application {
  bacula::job { 'my_application':
    ... (with no explicit pool)
  }
}
```

However, because bacula::job use lookup(), the job resource fetches the
Hiera default value "Default" instead of the value "Target" configured
by the user of the module.

xaque208/puppet-bacula