[Puppet-dev] Puppet Platform 8

Hi all, Here are our current plans for the Puppet Platform 8 release due out in February 2023. The work for this effort is contained in https://tickets.puppetlabs.com/browse/PA-4664. *Ruby 3.2* Ruby 3.2 should be released December 25, 2022 and we plan to vendor that version in puppet-agent pa

[Puppet-dev] Puppet 7.x branches

Hi all, Over the next several days, we will be creating `7.x` branches for the `puppet` and `puppet-agent` repos. Please target `7.x` for backward compatible features and bug fixes and `main` for everything else. Pull requests merged to `7.x` will automatically be merged to `main`, so you don'

[Puppet-dev] Disabling Legacy Facts in Puppet 8

Hi all, With Puppet 8 coming, I'd like to map out what's required to disable legacy facts by default. First some context, legacy facts are flat key=value pairs and originally that's how Facter reported facts. In Facter 3.5

Re: [Puppet-dev] Re: [Puppet Users] Upcoming changes to the rolling 'puppet' repos!

to Ruby 2.7 > > best > > ~pete > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-dev+unsubscr...@googleg

[Puppet-dev] Puppet Platform 7

ws/puppet7-nightly/ http://nightlies.puppet.com/downloads/mac/puppet7-nightly/ Finally, we'd love to hear your feedback on the puppet-dev mailing list or #puppet-dev in slack <https://puppetcommunity.slack.com/archives/C0W1X7ZAL> Thanks! Josh -- Josh Cooper | Software Engineer j...@puppet.com -- You r

[Puppet-dev] Default puppet branch

Hi all, I wanted to provide a heads up that we're changing the default branch for the puppet repo to main, effective today. Later this month, we're going to rename the master branch to 6.x leaving us with 3 active branches: main 6.x 5.5.x Each branch will continue to be auto-merged to later br

[Puppet-dev] Execution API Priorities

Jesse contributed a PR so that puppet can specify the priority for processes it starts.[1] This is important when the puppet daemon is running at a lower priority but needs to start process and services running at normal priority.[2] Adding a `priority` argument to `Puppet::Util::Execute.execut

Re: [Puppet-dev] [Puppet-Users] Puppet Platform 6 Update

On Wed, Jul 18, 2018 at 8:57 PM R.I.Pienaar wrote: > > > > On Thu, 19 Jul 2018, at 01:27, Eric Sorenson wrote: > > > > > > > On Jul 16, 2018, at 10:52 PM, R.I.Pienaar wrote: > > > > > > > > > > > > On Tue, 17 Jul 2018, at 02:40, Eric Sorenson wrote: > > >> Another effort that's underway but not y

[Puppet-dev] [Puppet-Users] Puppet Platform 6 Update

of that brittle exec, or manage that one API that eluded you until now.See https://github.com/puppetlabs/puppet-resource_api <https://github.com/puppetlabs/puppet-resource_api> and https://github.com/puppetlabs/puppet-specifications <https://github.com/puppetlabs/puppet-specifications> f

Re: [Puppet-dev] Re: Moving non-core types and providers out of puppet

anyways to load different versions of types in different environments. Josh [1] https://projects.puppetlabs.com/issues/18154 -- Josh Cooper | Software Engineer j...@puppet.com | @coopjn -- You received this message because you are subscribed to the Google Groups "Puppet Developers&quo

Re: [Puppet-dev] Re: Moving non-core types and providers out of puppet

tting this in 'puppet-agent' itself is a good idea > *at all*, particularly considering that we still can't build puppet-agent > from source to override any shenanigans that may arise from these good > intentions. > > Thanks, > > Trevor > > On Thu, Apr 26, 201

[Puppet-dev] Re: Moving non-core types and providers out of puppet

ay be locally installed (vendored or otherwise). Finally, if you really don't want to use vendored modules, then you can override basemodulepath, omitting the "vendored_modules" directory, and everything will work as it did before. Josh [1] https://github.com/puppetlabs/puppet-sp

Re: [Puppet-dev] Significance of 'puppet generate types' and title patterns that use procs

s discussion on the web visit https://groups.google.com/d/ > msgid/puppet-dev/CANs%2BFoXaVabKFbyg-f4nGou%3Dd% > 2BO4R52eECXNxbRnjSijtNh5mg%40mail.gmail.com > <https://groups.google.com/d/msgid/puppet-dev/CANs%2BFoXaVabKFbyg-f4nGou%3Dd%2BO4R52eECXNxbRnjSijtNh5mg%40mail.gmail.com?utm_medium=email&utm

[Puppet-dev] Moving non-core types and providers out of puppet

We've been talking about moving non-core types and providers out of the puppet repo for many years[1], and we are going to make every effort to make that happen for Puppet 6, finally! I've written up a proposal in the form of a PR to the puppet-specifications repo[2]. Please take a look and com

Re: [Puppet-dev] Re: Announce: Puppet Platform 5.3.4 is now available

iving emails from it, send an > email to puppet-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/puppet-dev/6e2a1958-9fa3-42b2-b568-f505ccc4dedd%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-dev/6e2a1958-

[Puppet-dev] [puppet-dev] Force pushed to puppet#stable branch

problems when you next pull or open a PR against stable. The fixes for PUP-7543 and PUP-7612 have been reapplied to puppet#stable. None of the other puppet branches were affected, but please let us know if you see any problems. Josh -- Josh Cooper | Software Engineer j...@puppet.com | @coopjn

Re: [Puppet-dev] Puppet 5 release planning

lter=12940 > [3] https://groups.google.com/d/topic/puppet-dev/3-HSUz5OnHg/discussion > > Eric Sorenson - eric.soren...@puppet.com > director of product, ecosystem and platform > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Dev

[Puppet-dev] Custom Types

We're thinking about solutions to the environment isolation problem described in https://tickets.puppetlabs.com/browse/SERVER-94. The short version is that during compilation, the master will load resource types from the environment for that agent (these are resource types defined in ruby and o

[Puppet-dev] Puppet PR Triage for Jan 26, 2016

Starting the PR triage for puppet/facter/hiera now at http://links.puppetlabs.com/pr-triage. Josh -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-d

[Puppet-dev] [Puppet Users] Announce: Puppet-Agent 1.3.0

idual components here: http://docs.puppetlabs.com/puppet/4.3/reference/about_agent.html To install or upgrade puppet-agent, follow the getting started directions: http://docs.puppetlabs.com/puppet/4.3/reference/index.html -- Josh Cooper Developer, Puppet Labs -- You received this message because yo

[Puppet-dev] Re: Puppet Community PR Triage starting now

On Tuesday, October 20, 2015 at 10:01:54 AM UTC-7, Josh Cooper wrote: > > Sorry for the short notice, but we're starting the triage now: > http://links.puppetlabs.com/pr-triage > Notes are posted in https://github.com/puppet-community/community-triage/blob/master/core/no

[Puppet-dev] Puppet Community PR Triage starting now

Sorry for the short notice, but we're starting the triage now: http://links.puppetlabs.com/pr-triage Josh -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[Puppet-dev] PR Triage starting in an hour

The PR triage is starting today in about an hour at 10AM Pacific time. We don't have much in the pull request queue to talk about, so if you have questions, something you're working on, today would be a good time to join. As always, the link to the google hangout is http://links.puppetlabs.com/p

Re: [Puppet-dev] Puppetconf 2015: pre-summit tea party

ed this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-dev+unsubscr...@googlegroups.com > > . > To view this discussion on the web visit > h

Re: [Puppet-dev] Re: Community PR Triage for 2015-07-07

gt; Thanks, > > Trevor > > On Tue, Jul 7, 2015 at 3:06 PM, Josh Cooper wrote: > >> PR triage notes are posted to >> https://github.com/puppet-community/community-triage/blob/master/core/notes/2015-07-07.md >> >> Also thanks to Felix for bringing up th

[Puppet-dev] Re: Community PR Triage for 2015-07-07

comment on the ticket if it's not. Josh On Tue, Jul 7, 2015 at 9:36 AM, Josh Cooper wrote: > The PR triage for puppet/facter/hiera/puppet-server will be starting at 10:00 > AM PDT today at http://links.puppetlabs.com/pr-triage > > Josh > > -- > Josh Cooper > Developer

[Puppet-dev] Community PR Triage for 2015-07-07

The PR triage for puppet/facter/hiera/puppet-server will be starting at 10:00 AM PDT today at http://links.puppetlabs.com/pr-triage Josh -- Josh Cooper Developer, Puppet Labs *PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland, Oregon! Join us October 5-9.* *Register

[Puppet-dev] Re: Community PR Triage for 2015-06-30

On Tuesday, June 30, 2015 at 8:19:23 AM UTC-7, Josh Cooper wrote: > > The PR triage for puppet/facter/hiera/puppet-server will be starting at 10:00 > AM PDT today at http://links.puppetlabs.com/pr-triage > > Notes from today's PR triage are posted: https://github.com/puppet

[Puppet-dev] Community PR Triage for 2015-06-30

The PR triage for puppet/facter/hiera/puppet-server will be starting at 10:00 AM PDT today at http://links.puppetlabs.com/pr-triage Josh -- Josh Cooper Developer, Puppet Labs *PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland, Oregon! Join us October 5-9.* *Register

[Puppet-dev] PR Triage cancelled June 23rd

Unfortunately we are still working on puppet 4.2 and facter 3.0 releases, and will need to cancel tomorrow's PR triage session for puppet/puppet-server/facter/hiera. We'll resume June 30th. Thank you for your patience. Josh -- Josh Cooper Developer, Puppet Labs *PuppetConf 2015 &l

Re: [Puppet-dev] Community PR Triage for 2015-06-02

t-community/community-triage/blob/master/core/notes/2015-06-02.md -- Josh Cooper Developer, Puppet Labs *PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Adopter discount <https://www.ev

[Puppet-dev] Puppet PR Triage

There's no PR triage today as we're having a company meeting. We'll resume next week at the regularly scheduled time. Josh -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, s

Re: [Puppet-dev] rspec-puppet issues under Ruby 2

usedCommentId=114681&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-114681 [9] https://github.com/puppetlabs/puppet/blob/3.7.3/lib/puppet/util/command_line.rb#L135-L141 [10] https://tickets.puppetlabs.com/browse/PUP-3268 -- Josh Cooper Developer, Puppet Labs *Join

Re: [Puppet-dev] Modifying property names

want the setters to store the new values: def property_one=(value) @one = value end def property_two=(value) @two = value end and implement a `flush` method to update the resource with all of the new values. def flush # save resource using @one & @two end Josh -- Josh Cooper Developer, P

Re: [Puppet-dev] Puppet PR Triage starting in 30 minutes

us know if you find the new format better, or not, or things that could be done better. Josh On Wed, Nov 19, 2014 at 9:29 AM, Josh Cooper wrote: > The Puppet/Facter/Hiera PR triage will be starting in 30 minutes at > http://links.puppetlabs.com/pr-triage > > Josh > > --

[Puppet-dev] Puppet PR Triage starting in 30 minutes

The Puppet/Facter/Hiera PR triage will be starting in 30 minutes at http://links.puppetlabs.com/pr-triage Josh -- Josh Cooper Developer, Puppet Labs *Join us at **PuppetConf 2015, October 5-9 in Portland, OR - * http://2015.puppetconf.com. *Register early to save 40%!* -- You received

Re: [Puppet-dev] Re: zpool mirror and raidz virtual devices

ve just been assigned to work on Puppet in >> Solaris. I am just getting oriented, but this looks like something we >> should be working on. Is this functionality being covered elsewhere? If >> not, I can open an internal ticket to get this covered. >> >> So far, we are

Re: [Puppet-dev] Re: zpool mirror and raidz virtual devices

on after. > > > Cheers, > Geoffrey > > > On Monday, November 10, 2014 11:06:51 PM UTC-8, Josh Cooper wrote: >> >> There looks to be a bug in the current zpool provider, where if you have >> a manifest like: >> >> mirror => [&q

[Puppet-dev] Puppet PR Triage starting soon

Starting the Puppet/Facter/Hiera PR triage in 30 minutes at http://links.puppetlabs.com/pr-triage Josh -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to pup

Re: [Puppet-dev] zpool mirror and raidz virtual devices

On Tue, Nov 11, 2014 at 5:09 AM, Joshua Hoblitt wrote: > On 11/11/2014 12:06 AM, Josh Cooper wrote: > > Adam put together a PR at https://github.com/Incognito1992/puppet/compare/ > ticket/master/PUP-3388-zpool-mirrors, but while researching it, I think > this is really a regress

[Puppet-dev] zpool mirror and raidz virtual devices

There looks to be a bug in the current zpool provider, where if you have a manifest like: mirror => ["disk1 disk2", "disk3 disk4"], Puppet will execute: zpool create data mirror "disk1 disk2" "disk3 disk4" Instead of: zpool create data mirror disk1 disk2 mirror disk3 disk4 Adam p

Re: [Puppet-dev] Re: Puppet PR Triage 2014-11-05

On Wed, Nov 5, 2014 at 12:06 PM, Henrik Lindberg < henrik.lindb...@cloudsmith.com> wrote: > On 2014-05-11 18:00, Josh Cooper wrote: > >> Starting the PR triage for puppet/facter/hiera in an hour (10am PST) at >> http://links.puppetlabs.com/__pr-triage >> <http

[Puppet-dev] Puppet PR Triage 2014-11-05

Starting the PR triage for puppet/facter/hiera in an hour (10am PST) at http://links.puppetlabs.com/pr-triage Josh -- Josh Cooper Developer, Puppet Labs *Join us at **PuppetConf 2015, October 5-9 in Portland, OR - * http://2015.puppetconf.com. *Register early to save 40%!* -- You received

[Puppet-dev] Setting log levels in puppet.conf

Stefan Goethals added the ability to specify puppet's log_level in puppet.conf[1] and it will be available in Puppet 4.0. This was originally redmine ticket #4761, so thank you Stefan for resolving that! I did run into one surprise and wanted to get feedback. If you specify log_level=debug in p

[Puppet-dev] Puppet PR triage for 20140-05-21

Join us in a Google hangout at http://links.puppetlabs.com/pr-triage -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com

[Puppet-dev] Notes from Puppet PR Triage for 2014-05-14

Pull request triage - 2014-05-14 Joined: Adrien, Andy, BrianL, Charlie, Erik Dalén (community), Ethan, Felix (community), Henrik, JoshC, JoshuaP, PeterH, Zach Candidates for merging: - 2492: (PUP-1381) issue warnings to current users of cron purging - 2473: (PUP-1775) Acquire and block for Y

[Puppet-dev] Platform PR Triage starting at 10:00 PDT

The PR triage for this week will be starting shortly at 10am Pacific Daylight Time. You can join in the hangout at http://links.puppetlabs.com/pr-triage Josh -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group

Re: [Puppet-dev] Re: [Puppet Users] Re: Puppet and Windows ACLs (Access Control Lists)

d go onto the ACL. > So something like: ace { 'admins': identity => 'Administrators', rights => [full], } ace { 'users': identity => 'Users', rights => [read_execute, list] } acl { 'c:\somedir': ensure => present

Re: [Puppet-dev] Re: [Puppet Users] Re: Puppet and Windows ACLs (Access Control Lists)

>> Additionally, although POSIX ACEs are unordered, it is my understanding > that the order of ACEs within a Windows ACL is significant. If that is > indeed correct then I don't see how the proposed model accounts for it. > >> >> Yes, you are correct. We're talk

Re: [Puppet-dev] Re: RFI: Windows Reboot Provider - Reboot At End

unsubscribe from this group and stop receiving emails from it, send an > email to puppet-dev+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-dev@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-dev. > For more options, visit https://grou

Re: [Puppet-dev] Puppet::Util.replace_file vs Puppet::Util::FileLocking

evor Vaughan > Vice President, Onyx Point, Inc > (410) 541-6699 > tvaug...@onyxpoint.com > > -- This account not approved for unencrypted proprietary information -- > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers&qu

Re: [Puppet-dev] Re: Performance regression between 3.2.1-rc1 and 3.1.1?

parker42 > Software Developer > > *Join us at PuppetConf 2013, August 22-23 in San Francisco - * > http://bit.ly/pupconf13* > **Register now and take advantage of the Early Bird discount - save 25%!* > > -- > You received this message because you are subscribed to the Google G

Re: [Puppet-dev] Re: Performance regression between 3.2.1-rc1 and 3.1.1?

for running the Puppet unit > tests.) > > Wil > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-dev+unsub

[Puppet-dev] Facter 1.7.x branch deletion

Hello, With the release of Facter 1.7.1[1], we'd like to delete the `1.7.x` branch in an effort to streamline the contribution process to Facter by using statically named branches, `stable` and `master`. Moving forward, any bug fix that would have gone into `1.7.x`, should instead be targeted a

[Puppet-dev] Managing System Reboots

rm-14.reboot/index.md [2] https://github.com/puppetlabs/armatures/pull/30 [3] https://github.com/joshcooper/armatures/blob/master/arm-0.arm/arm.md -- Josh Cooper Developer, Puppet Labs Join us at PuppetConf 2013, August 22-23 in San Francisco - http://bit.ly/pupconf13 The first 150 tickets sold wi

Re: [Puppet-dev] Any advice on "Puppet::Util::Log requires a message" failure

On Thursday, December 13, 2012 8:54:52 AM UTC-8, Roman Shaposhnik wrote: > > On Tue, Dec 11, 2012 at 11:08 AM, Andy Parker > > > wrote: > > That stacktrace is it trying to execute the start command for some > service > > and failing. It should be providing a message like "Could not #{type}

Re: [Puppet-dev] Puppet bugs #17295 and #18393

Hi Alex, On Tue, Jan 15, 2013 at 5:31 PM, Alex Harvey wrote: > Hi Josh, > > > On Tuesday, January 15, 2013 8:50:53 AM UTC+11, Josh Cooper wrote: >> >> >> I'm concerned about overloading the same flag to specify different >> types of algorithms. To gener

Re: [Puppet-dev] Puppet bugs #17295 and #18393

currently, is that it always uses SHA256 on the master when signing certificates. Instead, it should, depending on the CA policy, sign the CSR using the same signature algorithm that was used to generate the CSR, or the one that the master is configured to use. As it is now, if you have one agent tha

Re: [Puppet-dev] Solaris processorcount fact - what to do

ps.google.com/d/msg/puppet-dev/-/GZEBOO_xeoMJ. > To post to this group, send email to puppet-dev@googlegroups.com. > To unsubscribe from this group, send email to > puppet-dev+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/pupp

[Puppet-dev] hiera-puppet

/README.md -- Josh Cooper Developer, Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to puppet-dev@googlegroups.com. To unsubscribe from this group, send email to puppet-de

Re: [Puppet-dev] Windows file permission management very slow

I should have the SID resolution issue fixed soon. It would be great if you could try it out when I have a fix. Josh -- Josh Cooper Developer, Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to t

Re: [Puppet-dev] Re: SOS!! Need help..

ogle Groups > "Puppet Developers" group. > To post to this group, send email to puppet-dev@googlegroups.com. > To unsubscribe from this group, send email to > puppet-dev+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/g

Re: [Puppet-dev] Re: forge interactions, ssl and ca_path/ca_file

ppropriate trust store. There seems to be a ruby method for it[2] As far as Windows, there's an openssl patch to have it use capi (crypto api) to load the trusted certs[3]. Josh [1] http://fossies.org/dox/brx.src-1.6.0/x509__d2_8c_source.html#l00065 [2] https://github.com/ruby/ruby/blob/trunk

Re: [Puppet-dev] Announce: Facter 1.6.10

On Wed, Jun 13, 2012 at 5:45 PM, Moses Mendoza wrote: > Facter 1.6.10 is a maintenance release candidate in the 1.6.x branch with > bug fixes. > > It includes contributions from Hailee Kenney, Josh Cooper, Jeff Weiss, > Stefan Shulte, and Moses Mendoza. > > This release is a

Re: [Puppet-dev] Community input requested on potential `unless_uid` addition to user resources

er > Puppet Labs, Inc. > jeff.we...@puppetlabs.com > > I can see value for this on Windows as well, though it would likely require a regex: ignore => 'S-1-5-21-*-500' # Administrator Josh -- Josh Cooper Developer, Puppet Labs -- You received this message because you are

Re: [Puppet-dev] Text Console Colors

2console, file a ticket about the > >>> >>> background > >>> >>> issue, and either submit a pull request to Luis or fork our own > >>> >>> version and > >>> >>> patch it there. If this sounds reasonable, I'l

Re: [Puppet-dev] Text Console Colors

we are > ideally trying to avoid. I think we should go with win32console, file a ticket about the background issue, and either submit a pull request to Luis or fork our own version and patch it there. If this sounds reasonable, I'll file the ticket. And Ken, it sounds like you already know w

Re: [Puppet-dev] Text Console Colors

> > >>> ken. > >> > >> > >> I think we're on the same page. The way Puppet::Util::Colors is > implemented > >> is in pursuit of the same goal. While we don't (yet) have semantic > class > >> names, we definitely *don'

Re: [Puppet-dev] Release Candidates (1 week away)

Reviewing now. Sorry, I didn't see the github notification. Josh On Wed, Jan 11, 2012 at 1:32 PM, Ken Barber wrote: > FYI ... this is a blocker for Facter 1.6.5rc: > > https://github.com/puppetlabs/facter/pull/140 > > It needs senior review. Josh Cooper was looking at

[Puppet-dev] Open Source Team Iteration (ending 12/30/2011)

e provider to support the source parameter, as well as improving the pacman spec tests. Josh -- Josh Cooper Developer, Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to puppet-dev@go

[Puppet-dev] Open Source Team Iteration and Planning Summary

Puppet should allow rubygems to deliver new functionality #3910 - Server is not authoritative over client environment when specified in an ENC #3534 - Dashboard should support ability to set variables as arrays in the ENC #2247 - enablerepo and disablerepo for yum type Josh -- Josh Cooper D

[Puppet-dev] Re: ERROR: Connection reset by peer

Hi Dmitry, On Nov 15, 9:49 pm, James Turnbull wrote: > Dmitry wrote: > > Or, if this situation is too uncommon, is there any way to ask puppet > > agent to always act as if master is running on remote host, even if it > > runs on the same host and to always communicate via network? > > > Thanks.

Re: [Puppet-dev] Re: Add the example 'log' listener

orking on modifying the PIF to take into account your > comments, and my answers are interspersed into yours below. > > I'm also sending an official pull request at the same time. > Thanks for your time, > > On 17/06/11 01:10, Josh Cooper wrote: > > Hi Brice, &g

Re: [Puppet-dev] Facter Branch Updates

> > We have > > 1.6.x --> feature set for 1.6 (no API breakage please, mostly bug fixes) > 1.7.x --> new features go here > master --> newer, possibly experimental things here (this might be > 2.0 eventually, or who knows) > > 1.6rc exists, (as it has in the past) and is where facter is currentl

Re: [Puppet-dev] #2157 - help on windows paths

On Tue, Aug 23, 2011 at 4:27 PM, Ken Barber wrote: > >> If PROGRAMDATA is defined, I would use that value. > >> Otherwise, if ALLUSERSPROFILE is defined (and it should be), I would use > >> %ALLUSERSPROFILE%\Application Data > > > > I actually like this methodology over relying on win32-dir mysel

Re: [Puppet-dev] #2157 - help on windows paths

On Tue, Aug 23, 2011 at 12:46 PM, Ken Barber wrote: > Thanks Josh. > > > The ProgramData environment variable is not supported on 2003. The > > equivalent directory on 2003 (and other legacy systems) > > is %ALLUSERSPROFILE%\Application Data.[1] > > Gah! (/me goes off to download Windows 2003 ...

Re: [Puppet-dev] #2157 - help on windows paths

On Tue, Aug 23, 2011 at 11:31 AM, Ken Barber wrote: > > Generally speaking: Facter should probably still work (though in a > > degraded mode) without the win32-dir gem installed. > > Hmm. ENV["ProgramData"] is actually the same as Dir::COMMON_APPDATA on > 2008R2. I can avoid the gem completely th

[Puppet-dev] Open Source Team iteration & planning summary 2011-08-05

We completed a number of tasks that allow us to run the facter and spec tests on Windows as part of our continuous integration system[1]. All of the tests now pass on Windows Server 2008 R2, with exception of tests that are marked as fails_on_windows. These tests are known to fail because we have n

[Puppet-dev] [PATCH/puppet 1/1] (#8644) Host provider on Windows

rking, I removed the tag from those tests, and verified that the tests now pass. There are two tests in resources_spec that fail because the user and exec providers are not supported on Windows yet, so those tests are marked as fails_on_windows. Reviewed-by: Pieter van de Bruggen Signed-off-by:

[Puppet-dev] [PATCH/puppet 1/2] (#8660) Default config dir to %PROGRAMDATA% on Windows

%\ProgramData. This commit also updates puppet's default run_mode var and conf directories when running as "root" to match the install script, and fixes the spec test, which was looking in the Dir::WINDOWS directory. Reviewed-by: Cameron Thomas Signed-off-by: Josh Cooper --- Local

[Puppet-dev] [PATCH/puppet 2/2] (#8660) Fix destdir option on Windows

two paths, stripping off the drive specifier, if present. Also fixed a minor bug, which caused a deprecation warning to always be printed when the --destdir option is omitted, which is the default case. Reviewed-by: Cameron Thomas Signed-off-by: Josh Cooper --- Local-branch: ticket/master/8660

[Puppet-dev] [PATCH/facter 1/1] (#8660) Fix destdir option on Windows

two paths, stripping off the drive specifier, if present. Also added the deprecation warning if the DESTDIR environment variable is specified (to match the puppet install.rb script). Reviewed-by: Cameron Thomas Signed-off-by: Josh Cooper --- Local-branch: feature/master/facter-windows install.rb

[Puppet-dev] [PATCH/puppet 1/1] (#8663) Disable spec tests for unsupported functionality on Windows

different semantics than Unix, where the command is splatted, Kernel.exec(*command). Since this truly is a Windows bug, I removed the fails_on_windows tag and updated ticket #8410. Reviewed-by: Jacob Helwig Signed-off-by: Josh Cooper --- Local-branch: ticket/master/8663-windows-spec-tests spec/i

Re: [Puppet-dev] Re: Debugging Puppet on Windows

On Thu, Jul 28, 2011 at 12:34 PM, Nan Liu wrote: > On Thu, Jul 28, 2011 at 2:24 PM, Josh Cooper wrote: > > On Mar 18, 12:20 pm, Markus Roberts wrote: > >> On Fri, Mar 18, 2011 at 12:07 PM, Jay Flowers > wrote: > >> > I finally got some more time to work on thi

[Puppet-dev] Re: Debugging Puppet on Windows

On Mar 18, 12:20 pm, Markus Roberts wrote: > On Fri, Mar 18, 2011 at 12:07 PM, Jay Flowers wrote: > > I finally got some more time to work on this.  I ended up getting RubyMine > > setup and configured for me to develop and debug with. > > > I logged a bug on this: > >https://projects.puppetlabs.

[Puppet-dev] [PATCH/puppet 4/4] (#8663) Drive letters are not valid absolute paths on Windows

One of the file spec tests was attempting to use X: as a fully qualified file path, and the file type was correctly rejecting it, since it is a relative path. This commit changes the spec test to expect the file type to raise an exception. Reviewed-by: Jacob Helwig Signed-off-by: Josh Cooper

[Puppet-dev] [PATCH/puppet 3/4] (#8663) Update the run_mode spec test on Windows to match the code

. See #8660. Reviewed-by: Jacob Helwig Signed-off-by: Josh Cooper --- Local-branch: ticket/master/8663-windows-spec-tests spec/unit/util/run_mode_spec.rb | 10 +++--- 1 files changed, 7 insertions(+), 3 deletions(-) diff --git a/spec/unit/util/run_mode_spec.rb b/spec/unit/util

[Puppet-dev] [PATCH/puppet 1/4] (#8663) Reenable spec tests on Windows that now pass

The cacher was causing spec tests to fail due to Time.now not having millisecond resolution on Windows. Now that usage of the cacher has been removed from many places, these tests now pass. Reviewed-by: Jacob Helwig Signed-off-by: Josh Cooper --- Local-branch: ticket/master/8663-windows-spec

[Puppet-dev] [PATCH/puppet 2/4] (#8663) The ssh_authorized_key type is not supported on Windows

We are not supporting the ssh_authorized_key type on Windows at this time, since Windows does not ship with an ssh server (though there are third-party versions available). As a result these spec tests have been disabled. Reviewed-by: Jacob Helwig Signed-off-by: Josh Cooper --- Local-branch

[Puppet-dev] [PATCH/puppet 3/3] Fix issue with forward and backslashes in Windows paths

eproduce a specific bug, which caused rdoc to try to create a directory of the form: C:/.../files/C:/ Of course, this fails because ':' is not a valid filename character on Windows. Paired-with: Nick Lewis Reviewed-by: Jacob Helwig Signed-off-by: Josh Cooper --- Local-branch: featu

[Puppet-dev] [PATCH/puppet 1/3] Update certificate spec tests for Windows

PuppetSpec::Files.tmpdir instead, which automatically cleans up temporary directories after the tests have run. Reviewed-by: Jacob Helwig Signed-off-by: Josh Cooper --- Local-branch: feature/master/8268-puppet-agent-windows spec/integration/ssl/certificate_authority_spec.rb | 14 ++

[Puppet-dev] [PATCH/puppet 2/3] Disable spec tests for unsupported functionality on Windows

e been replaced with PuppetSpec::Files.tmpdir. Reviewed-by: Jacob Helwig Signed-off-by: Josh Cooper --- Local-branch: feature/master/8268-puppet-agent-windows spec/integration/network/server/webrick_spec.rb | 14 ++ spec/integration/type/tidy_spec.rb |2 +- spec/inte

Re: [Puppet-dev] Re: [PATCH/puppet 1/6] (#8489) Consistently use File::PATH_SEPARATOR

On Wed, Jul 20, 2011 at 11:42 AM, Nick Fagerlund < nick.fagerl...@puppetlabs.com> wrote: > On Jul 20, 8:17 am, Jacob Helwig wrote: > > I can see adding a note something like "separated by the > > '#{File::PATH_SEPARATOR}' character (varies by platform).", but I'd > > really rather not have us lis

Re: [Puppet-dev] [PATCH/puppet 3/6] Fix tests with "relative" paths on Windows

> > > it "should not fail if the path is fully qualified, with a trailing > separator" do > > -path = "/some/path/with/trailing/separator" > > -path_with_separator = "#{path}#{File::SEPARATOR}" > > -File.stubs(:lstat).with(path).returns stub('stat') > > +path_with_separator = "#{

Re: [Puppet-dev] [PATCH/puppet 5/6] Maint: Don't test for extended signals on Windows

the ability to > reload the configuration file of a running Puppet Agent in daemon > mode, then great. Otherwise something to indicate that this is still > pending would be awesome. > > Daniel > > On Tue, Jul 19, 2011 at 15:38, Josh Cooper wrote: > > HUP, USR1, and USR2 are

Re: [Puppet-dev] [PATCH/puppet 5/6] Maint: Don't test for extended signals on Windows

HUP, USR1, and USR2 are not supported on Windows, so I don't see any point in writing a pending test for something that will never happen. Josh On Tue, Jul 19, 2011 at 3:36 PM, Daniel Pittman wrote: > On Tue, Jul 19, 2011 at 14:59, Josh Cooper wrote: > > The signals HUP, USR1, an

Re: [Puppet-dev] [PATCH/puppet 2/6] (#8268) Require windows drive letters in absolute file paths

into utility methods like we taked about. Josh On Tue, Jul 19, 2011 at 3:19 PM, Daniel Pittman wrote: > On Tue, Jul 19, 2011 at 14:59, Josh Cooper wrote: > > When testing whether a file path is absolute, the regexp was only > > handling POSIX style file paths. This commit requires Wi

[Puppet-dev] [PATCH/puppet 1/1] Fix spec test failure on 1.9.2

The previous set of windows patches accidentally changed %w{/one} to make_absolute("/one"). This commit changes it back to [make_absolute("/one")]. Reviewed-by: Jacob Helwig Signed-off-by: Josh Cooper --- Local-branch: feature/master/8268-puppet-agent-windo

[Puppet-dev] [PATCH/puppet 6/6] Maint: Fix miscellaneous tests

ed-by: Jacob Helwig Signed-off-by: Josh Cooper --- Local-branch: feature/master/8268-puppet-agent-windows spec/integration/util/settings_spec.rb |4 ++-- spec/unit/application/inspect_spec.rb |1 + spec/unit/parser/functions/sprintf_spec.rb |3 ++- spec/unit/pro

[Puppet-dev] [PATCH/puppet 4/6] Maint: Tagged spec tests that are known to fail on Windows

run: rspec --tag ~fails_on_windows spec Reviewed-by: Jacob Helwig Signed-off-by: Josh Cooper --- Local-branch: feature/master/8268-puppet-agent-windows spec/integration/application/doc_spec.rb |2 +- .../file_serving/terminus_helper_spec.rb |2 +- .../indirec

  1   2   >