Details
-
Task
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
scheduled_task 0.1
-
-
Windows
-
Windows Kanban
-
Needs Assessment
Description
The scheduled_task module has thus far only shipped with a new provider, but not changed existing behavior / defaults for v1 tasks, whose type definition remains in core Puppet.
Based on some discovery, it has been determined that Puppet will always try to load module code first (types and providers) and if a module satisfies a type / provider name, the code will be loaded / cached from the module only. This means that Puppet already has a system in place that allows for overriding core types and providers with module code in a way that the original code is never even parsed.
This ends up being a critically important property for this module. This allows the existing type definition to be brought in from the Puppet core code, as well as the existing provider. Since the new provider has all the same functionality as the original provider, the old provider may then have defaultfor :operatingsystem => :windows removed, effectively neutralizing the old provider. That makes it straightforward to mark the new provider as the default and ignore the old provider when the module is present, which is the goal of this module.
Attachments
Issue Links
- blocks
-
MODULES-6526 scheduled_task: modify v1 task to add compatibility property, add helper class that v2 provider consumes for working with v2 tasks
-
- Resolved
-
- relates to
-
MODULES-6505 scheduled_task : SPIKE technical direction of v2 scheduled_task type and provider
-
- Resolved
-
-
MODULES-6395 scheduled_task : SPIKE Scaffold out v2 scheduled_task type that defaults to using v2 provider
-
- Resolved
-