You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the php module was introduced to manage the php installation and the composer installation on the servers, each puppet run now tries to update composer. This results in a message like: Notice: /Stage[main]/Php::Composer::Auto_update/Exec[update composer]/returns: executed successfully
for each puppet run, the run will then be marked as "changed", even if no update of composer was done. The module should, by default, only attempt to update composer after 30 days, iirc.
The text was updated successfully, but these errors were encountered:
Since the php module was introduced to manage the php installation and the composer installation on the servers, each puppet run now tries to update composer. This results in a message like:
Notice: /Stage[main]/Php::Composer::Auto_update/Exec[update composer]/returns: executed successfully
for each puppet run, the run will then be marked as "changed", even if no update of composer was done. The module should, by default, only attempt to update composer after 30 days, iirc.
The text was updated successfully, but these errors were encountered: