On Thursday, January 31, 2019 at 8:40:40 AM UTC-6, Jochen Haeberle wrote:
> Nevertheless the question remains why the code is working in my dev
> environment. Both environments are the same as much as you can get.
>
>
I hope you'll forgive me if I'm inclined to doubt that the same code is
Hi John,
thanks for your support! I see your point, especially with the different use of
notify.
It’s disapointing to hear one should still keep away from ensure_packages, as
it greatly helps me to install packages only when needed. This goes mostly for
apache modules and php extensions in my
On Thursday, January 31, 2019 at 8:00:05 AM UTC-6, jcbollinger wrote:
As long as I'm standing on this soapbox, though, I'd like to remark that
> ensure_packages() is a jerry-rig, not an actual solution to any Puppet
> problem. It and its brethren, ensure_package(), ensure_resources(), and
>
On Monday, January 28, 2019 at 5:02:42 PM UTC-6, Jochen Haeberle wrote:
>
> Hi,
>
> I am using serverless puppet apply on some nodes. I prepared a set of
> manifests using forge plugins. I developed everything using Vagrant quite
> fine.
>
> Now I put my code via git on a debian 9.7 VM with
Hi,
you are probably right. Here we go:
as I am using puppet apply, I have in my site.pp:
include role::fips_tool
in fips_tool there is, among other code:
...
class { profile::software::apache:
php_version => '7.3',
default_redirect_to => 'http://my.host.name',
maindir
Sharing the code that you're working with will make it possible for people
to help solve your problem.
On Wed, Jan 30, 2019 at 10:22 AM Jochen Haeberle
wrote:
> Hi @all,
>
> does anyone have an idea what could be happening? I think this might be
> some sort of configuration error on the node,
Hi @all,
does anyone have an idea what could be happening? I think this might be
some sort of configuration error on the node, on the other hand, puppet
obviously seems able to compile a catalog.
What could be the reason for such a difference in behaviour on Debian 9.7
either on Vagrant or
