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
Created by tontonitch on 2016-10-25 12:05:51 +00:00
Assignee: (none)
Status: Rejected (closed on 2016-11-10 10:01:16 +00:00)
Target Version: (none)
Last Update: 2016-11-10 10:01:16 +00:00 (in Redmine)
Hi,
Neither puppet 4 nor the future parser are supported in Red Hat Satellite.
Consequently, it would be great if the new puppet module for Icinga2 would still be compatible with Puppet 3 (>= 3.8.6 which is the current version used by Satellite).
Updated by tontonitch on 2016-11-08 11:49:00 +00:00
Hi Sheqa,
Currently I don't have any issue with the module when used with RH Satellite 6.2 (using puppet 3.8.6).
But I had some issues with other modules rewritten using "future parser".
Consequently, I wanted to inform you of that situation in case you planned to use the "future parser".
Best regards,
Yannick
Currently I don't have any issue with the module when used with RH Satellite 6.2 (using puppet 3.8.6).
Awesome!
But I had some issues with other modules rewritten using "future parser".
Consequently, I wanted to inform you of that situation in case you planned to use the "future parser".
Our intention is to be comaptible to Puppet => 3.8.6
If you encounter any misbehaviour, please open an issue :-)
This issue has been migrated from Redmine: https://dev.icinga.com/issues/12982
Created by tontonitch on 2016-10-25 12:05:51 +00:00
Assignee: (none)
Status: Rejected (closed on 2016-11-10 10:01:16 +00:00)
Target Version: (none)
Last Update: 2016-11-10 10:01:16 +00:00 (in Redmine)
Hi,
Neither puppet 4 nor the future parser are supported in Red Hat Satellite.
Consequently, it would be great if the new puppet module for Icinga2 would still be compatible with Puppet 3 (>= 3.8.6 which is the current version used by Satellite).
https://docs.puppet.com/puppet/3.8/reference/experiments\_future.html
Best regards,
Yannick
The text was updated successfully, but these errors were encountered: