Puppet.features.root? will now correctly report whether Puppet is
running with elevated administrative privileges on Windows, instead of
always returning true (#8662).  Management of permissions and
ownership of Puppet's internal files was also disabled as part of this
change until the general problem of managing file ownership, and
permissions has been addressed.  This has been merged into the 2.7.x
branch, and should be available in the next 2.7.x release after 2.7.3.

The exec type now works on Windows (#8410).  This also includes some
refactoring around how Puppet determines whether a path is absolute or
not, which is a step towards a larger refactor in this area.  This has
been merged into the 2.7.x branch, and should be available in the next
2.7.x release after 2.7.3.

Jeff Blane provided a fix for a debug message (01df2375), which has
been merged into the master branch, and will be available in Telly.

Completed items:

 * #8662 - Puppet.features.root? always returns true on Windows

 * #8410 - Exec provider for Windows

 * Remove spurious "exec" from a debug string

Current backlog:

 * #8439 - Basic facter on Windows

 * #8414 - Task scheduler type/provider for Windows

 * #8411 - File type working on Windows

 * #9186 - Windows file security support

 * #9189 - File provider on Windows

 * #8412 - MSI package provider for Windows

 * #8413 - Ability to run Puppet as an agent on Windows

 * #7316 - puppet applications delivered via pluginsync don't work.

 * #5517 - Overriding parameters on included & inherited classes

 * #3741 - Custom facts loaded multiple times

 * #4916 - Plugins should not be able to override core functionality.

-- 
Jacob Helwig
,----
| Join us for PuppetConf, September 22nd and 23rd in Portland, OR
| http://bit.ly/puppetconfsig
`----

Attachment: signature.asc
Description: Digital signature

Reply via email to