the certregen
component of the MODULES JIRA project:
https://tickets.puppetlabs.com/browse/MODULES/component/20300/
--
Adrien Thebo | Puppet
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop rec
ontent => 'blah' }
>
> file { '/tmp/stack': ensure => 'directory' }
>
> file { '/tmp/stack/test1': content => 'test' }
>
> file { '/usr/test':
> content => 'test',
> require => File['/
sted, I suppose what I'm trying to do is
> actually save a RAL catalog and then reactivate it via the command line at
> a later point. Do you know if this is possible? I don't really need a
> compiler-level resource catalog since this won't be shipped off of the
> local sy
e web visit
> https://groups.google.com/d/msgid/puppet-dev/CANs%2BFoUnc589eJ3nujpF0G38%3D6hAHOMHVShU7xRU9KfzS%2BTjQg%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-dev/CANs%2BFoUnc589eJ3nujpF0G38%3D6hAHOMHVShU7xRU9KfzS%2BTjQg%40mail.gmail.com?utm_medium=email&utm_source=footer
ing this (and
> glad that I am so we caught that bug prior to release).
>
> Why wouldn't this be the default?
>
> Thanks,
>
> Trevor
>
> On Wed, Jul 15, 2015 at 3:41 PM, Adrien Thebo
> wrote:
>
>> And it looks like _I_ was too hasty; this is done wh
And it looks like _I_ was too hasty; this is done when immutable_node_data
is set. (
https://github.com/puppetlabs/puppet/commit/8ccb3923b7ddd22e53d53dd193edc618b218a2a6
)
On Wed, Jul 15, 2015 at 12:40 PM Adrien Thebo wrote:
> It looks like we do:
> https://github.com/puppetlabs/puppe
> email to puppet-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-dev/CACZQQfOK4iJk7KcFT9_9n3pU-4U90Cxnhw2660FdafMCuYAggg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/puppet-dev/CACZQQfOK
ote, we should make sure that the result of this conversation
makes it back onto the JIRA ticket so we have a record of the design when
we go into actually writing something.
--
Adrien Thebo | Puppet Labs
--
You received this message because you are subscribed to the Google Gro
do not interfere with each other, which is splendid.
>
> Since solution is already done (works for me), I am moving this thread to
> "comment/criticise my setup", ok? If you have opinion about this, please
> speak up.
>
>
The change you've proposed seems extremely sp
t; tvau...@onyxpoint.com
>>
>> -- This account not approved for unencrypted proprietary information --
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Developers" group.
> To unsubscribe from this group and st
/groups.google.com/d/msgid/puppet-dev/910ad676-77c4-43d1-8a95-42e398ab249d%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-dev/910ad676-77c4-43d1-8a95-42e398ab249d%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.goog
it I checked and I think it's a
one line change to
https://github.com/puppetlabs/puppet/blob/3.7.0/lib/puppet/transaction.rb#L224
to check for `s.failed_to_restart?` )
--
Adrien Thebo | Puppet Labs
--
You received this message because you are subscribed to the Google Groups
"Puppet De
il.com
> <https://groups.google.com/d/msgid/puppet-dev/CANhgQXumU1fst6AP2kQ6M4U%2BAaU0Qh%3Dff4gq%2B6c0ig_Yw%2B2g3A%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
Adrien Thebo | Puppet Labs
--
You r
release:
https://tickets.puppetlabs.com/issues/?filter=12624
We're tracking bugs people find in this release with the "Affected Version"
field set to "2.2.0": https://tickets.puppetlabs.com/issues/?filter=12623
--
Adrien Thebo | Puppet Labs
--
You received this message beca
status of CLAs for the pull
request
- Code could use some refactoring, cleanup, and tests, but we can work
with the contributor on that
- Needs a JIRA issue
- Still needs work; pending contributor response; check in next week. (2x)
--
Adrien Thebo | Puppet Labs
--
You received this message because
* and a second one dealing with
>> Style/AndOr since the number of violations of Style/AndOr is really
>> large, and it may be better to tackle it separately.
>>
>
> +1
>
>
>>
>> On Thu, Jul 17, 2014 at 9:23 AM, Adrien Thebo
>> wrote:
>&
PR and start a thread on
puppet-dev to come to a decision about how to better control refresh events.
2709 (PUP-2701): Add PMT build metadata.json tests
- Joshua Partlow to verify these on a few platforms before merging
- Found some failures on centos6; will update prs and then ask if Kur
Starting in about 10 minutes at http://links.puppetlabs.com/pr-triage
--
Adrien Thebo | Puppet Labs
--
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
group and stop receiving emails from it,
>> >> >>>> send
>> >> >>>> an email to puppet-dev+...@googlegroups.com.
>> >> >>>> To view this discussion on the web visit
>> >> >>>>
>> >> >>
on
puppet-dev to come to a decision about how to better control refresh events.
2709 (PUP-2701): Add PMT build metadata.json tests
- Joshua Partlow to verify these on a few platforms before merging
- Found some failures on centos6; will update prs and then ask if Kurt
can continue
--
Ad
Starting in about 10 minutes at http://links.puppetlabs.com/pr-triage
--
Adrien Thebo | Puppet Labs
--
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
w%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-dev/CANhgQXvi-FXfVcNDH75wsX2DZZtN0c58P8enUHOP-nt8GpE5%3Dw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
Adrien Thebo | Puppet L
cerns about #uniqueness_key being public API, and composite
namevars are not well supported. We need to decide if we want to really
support those.
Discussion: can we add `unless` and `onlyif` as metaparameters for all
resources? Discussion outcome: ...maybe?
--
Adrien Thebo | Puppet Lab
Also, Peter Huene was there. This fact should not be understated.
On Wed, Apr 23, 2014 at 1:48 PM, Adrien Thebo wrote:
> Pull request triage - 2014-04-23
>
> Joined: Adrien, Andy, Josh, Rob, Ethan, Felix, Ken, Brian, Charlie
>
> Held over:
>
> Puppet:
>
> 2309: Sep
t of environment work
2525: (PUP-1942) Initial pass at a global scope
- Andy to close
2549: (PUP-2298) add support for Type#in_valid_catalog? methods to
transaction
- What sort of hooks do we want to define over the application lifetime?
- Implement validate method on Type ancestor class,
642/643: Fun with AIX networking
- 559: (FACT-233) Add dhcp_server fact
- 560: (FACT-234) Add uuid_
- 644: (#7559) Use /sys/hypervisor/version/extra to distinguish AWS VM in
VPC
Felix:
- 2487: (PUP-2098) 'only_uid' property on resources 'user'
Zach:
- 2495: Implemen
solve all
problems at once and got stuck aiming for perfection. This time I want to
see how the new functionality works, how people want to solve issues with
fact compatibility issues, and so forth.
--
Adrien Thebo | Puppet Labs
--
You received this message because you are subscribed to the
ders found
- 2420: Disambiguation of handling source_or_content for fileservers vs
local re...
- 2485: (PUP-2096) Support alternate http client classes in http_pool
- 2082: Add install options apt
--
Adrien Thebo | Puppet Labs
--
You received this message because you are subscribed to the Goo
the 2.0.0rc1 tag in the Facter repo was already occupied by that
cancelled release, and since issuing a RC5 out of nowhere might have been
confusing, we decided to go directly to 2.0.1 instead.
Facter 2.0.1-rc4 Contributors
Adrien Thebo
Facter 2.0.1-rc4 Changelog
Adrien Thebo (3):
sudo call in one of the execs, may need to confine to root, Adrien will
touch base with Alex on this
608: Needs commit message updated to include ticket number - Adrien
609: Josh C is updating
610: Adrien to pull into stable
617: replaced by 642 and Adrien will follow up with Moses
--
Adrie
behave this way. It breaks
> nothing and fixes everything, as far as I can see.
>
> On Saturday, March 8, 2014 2:48:21 PM UTC-6, Pedro Côrte-Real wrote:
>
>> On Fri, Mar 7, 2014 at 10:15 PM, Adrien Thebo
>> wrote:
>> > Long story short, allowing multiple resour
be 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
> https://groups.google.com/d/msgid/puppet-dev/CANs%2BFoXMgnXvTOwe62Yz2o80E%3D5SqytRMrRXSXLZORiV50tnDg%40mail.gmail.com<https://groups
On Tue, Feb 18, 2014 at 2:52 PM, Stefan Schulte <
stefan.schu...@taunusstein.net> wrote:
> Hi Adrien,
>
>
> On 18.02.2014 18:50, Adrien Thebo wrote:> I should have responded sooner
> to this thread, but now that the horse
> > has clearly left the barn I might as wel
t; -Stefan
>
> --
> 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.
> To view this di
oogle 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 https://groups.google.com/d/
> msgid/puppet-dev/ldd9h9%24cga%241%4
oups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-dev/52EFFE1B.6080906%40cpan.org.
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
Adrien Thebo | Puppet Labs
--
You received this message because you are subsc
to
facter-2. When we've backported all the commits that we want to release in
Facter 2, we'll revert any remaining changes in master that aren't in
facter-2, and then merge facter-2 up into master.
On Thu, Dec 19, 2013 at 12:33 PM, Adrien Thebo wrote:
> Is this with respect to th
t to this email that has generally gotten
positive reviews.
On Thu, Dec 19, 2013 at 2:56 AM, Erik Dalén wrote:
> Do you have any draft of what the structure will look like?
>
> Will it be much different from the overall structure of ohai?
>
>
> On 3 December 2013 23:27, Adr
w this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-dev/52B2D4FB.4030800%40cea.fr.
>
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
Adrien Thebo | Puppet Labs
--
You received this message because you are subscribed to the Google
ils 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/CAJtE5vS6R%3D6BnW5%3D-3YB%3D%3D2pPr2ho21_4kuLoOUoWR66zwNT1g%40mail.gmail.com
> .
> For more options, visit https://groups.google
-
base: future master
-
features: more facts from (current) master, select facts rewritten as
structured facts
--
Adrien Thebo | Puppet Labs
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubs
ented at
http://docs.puppetlabs.com/puppet/2.7/reference/lang_namespaces.html and is
the supported approach to resource namespacing. It's very unlikely that
this will change at all, let alone in the near future, and has been the
accepted best practice for at least 2 - 3 years.
--
Adrien Thebo |
ell]<https://trello.com/c/G1kDRp1H/1502-pr-puppet-1947-22699-set-value-collection-for-boolean-params-dustin-j-mitchell>
merged into master in 80e1bab; this should be released in 3.3.0. Thanks
again for the contribution!
<https://gist.github.com/gepetto-bot/5166341#pr-puppet1963-maint-prefer-jso
t;https://gist.github.com/gepetto-bot/5166341#pr-puppet1914-21069-refresh-the-cache-of-launchd-plists-on-a-miss-dustin-j-mitchell>(PR
puppet/1914) (#21069) refresh the cache of launchd plists on a miss [Dustin
J.
Mitchell]<https://trello.com/c/gzyC5FeK/1455-pr-puppet-1914-21069-refresh-the
may need to place a bit of
> "suitability" logic at the top of their script. I think facter has to make
> this determination for Windows Vs. Linux by not executing facts on Linux
> with common windows extensions.
>
> --
> You received this message because you are subsc
e original commit
itself was not merged, it will look like the pull request was rejected,
even though they really were merged.
--
Adrien Thebo | Puppet Labs
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from
oll]<https://trello.com/c/QIzlt2nN/1443-pr-puppet-1903-maint-pson-reporting-requires-master-3-3-0-not-3-2-2-floatingatoll>
superceded by GH-1904, closed without merge.
<https://gist.github.com/gepetto-bot/5166341#pr-puppet1818-issue22043-double-escaping-facts-kylo>(PR
puppet/1818) I
you're using that networkless PC. You can collect the facts from your nodes
and copy them to a networkless puppet master. From there you compile node
catalogs, and then sign _those_. Then you can copy those catalogs and
signatures back to your rsync server, and you have all the perks of using a
closed without
merge.
<https://gist.github.com/gepetto-bot/5166341#other>Other<https://gist.github.com/gepetto-bot/5166341#pr-puppet1847-21201-remove-thread-safety-code-andrew-parker>(PR
puppet/1847) (#21201) Remove thread-safety code [Andrew
Parker]<https://trello.com/c/Zw7lKlxk/1360-pr-p
request, what about `transaction_teardown` or something
like that?
And with respect to the yardoc, we could define a new yard tag like
`@callback [caller] description` or something to that.
--
Adrien Thebo | Puppet Labs
--
You received this message because you are subscribed to the Google Gro
t;> thought.
>>
>>
>>
> I am all for this kind of explicit style, but it is an even larger
> departure from what we have.
>
I've played around with patterns like this in my own projects, and there
are pros and cons. You can get more flexibility and power when dec
) 15586 - rdoc::usage failing on ruby
1.9.3<https://trello.com/c/0r7aki0c/1091-pr-facter-299-15586-rdoc-usage-failing-on-ruby-1-9-3>
superceded by GH-522; closed without merge. Another painfully old pull
request has been laid to rest and given a proper burial.
--
Adrien Thebo | Puppet Labs
dependency.
My vote is to go with Mike's earlier comment that we unvendor, submit fixes
to upstream, make it a proper dependency on OSX and either package
CFPropertyList by itself or bundle it in during package generation. Are
there any other solutions?
--
Adrien Thebo | Puppet Labs
--
You r
On Thu, Aug 29, 2013 at 1:58 AM, Christian Kruse wrote:
> Hi,
>
> Am Mittwoch, 28. August 2013 19:53:42 UTC+2 schrieb Adrien Thebo:
>
>> Moreover, by our current standards CFPropertyList is not a candidate for
>> vendoring. The general guideline for vendoring is that cand
On Wed, Aug 28, 2013 at 1:09 PM, Brian Warsing wrote:
> I see, thanks Adrien -- the picture is coming into focus for me. So, the
> initial concern regarding the method collision aside, the major obstacle is
> vending code that requires periodic patching, which in turn demands a bunch
> of awkward
On Wed, Aug 28, 2013 at 12:36 PM, Adrien Thebo wrote:
> On Wed, Aug 28, 2013 at 12:33 PM, Brian Warsing wrote:
>
>> Can you clarify: PuppetLabs patches the CFPropertyList gem before vending
>> it?
>>
>
> We have a pull request targeted at Facter that han
ases like this if we're going to accept that change _and_ get it upstream,
we would probably have to handle the submission against upstream ourselves.
--
Adrien Thebo | Puppet Labs
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers&quo
acter's entire operation on OS X based on a
> gem that a user has to install. Since we own the packaging, it's entirely
> conceivable that we could bundle the gem along with Puppet, but now we have
> a packaging issue.
>
>
> On Wed, Aug 28, 2013 at 11:06 AM, Adri
nhke wrote:
>
>
> On Wednesday, August 28, 2013 10:53:42 AM UTC-7, Adrien Thebo wrote:
>>
>> Hi folks,
>>
>> I've been working on some issues on how Facter handles plist libraries,
>> and right now we're in a bit of a bind. The short story is that i
what
would be best. Keep CFPropertyList vendored inside of Facter and carry
patches to ensure compatibility? Remove the library and try to load it
opportunistically? Remove it entirely?
--
Adrien Thebo | Puppet Labs
--
You received this message because you are subscribed to the Google Groups
&
>
>
> --
> Andrew Parker
> a...@puppetlabs.com
> Freenode: zaphod42
> Twitter: @aparker42
> Software Developer
>
> *Join us at PuppetConf 2014, September 23-24 in San Francisco*
>
> --
> You received this message because you are subscribed to the Google Groups
dlib-validate-slength>
the stdlib validate_slength method was a bit of a mess and bugs were
creeping in because of that. 66865f2 adds a significant refactor of the
code that should make the method more usable moving forward.
--
Adrien Thebo | Puppet Labs
--
You received this message because yo
ub.com/gepetto-bot/5166341#pr-facter509-22060-fix-undefined-path-in-macaddressrb-mark-zeren>(PR
facter/509) (#22060) Fix undefined path in macaddress.rb [Mark
Zeren]<https://trello.com/c/qv4hR3YC/1304-pr-facter-509-22060-fix-undefined-path-in-macaddress-rb-mark-zeren>
duplicate of GH
-get-the-most-used-interface-johnnyrun>
the conversation on this pull request indicates that this isn't the best
approach, and the pull request got stale. Closing without merge.
--
Adrien Thebo | Puppet Labs
--
You received this message because you are subscribed to the Google Groups
support for finalize method to providers [Thomas
Linkin]<https://trello.com/c/Xvy5QOLx/1262-pr-puppet-1800-3946-add-support-for-finalize-method-to-providers-thomas-linkin>
the pull request didn't fully address the issue raised by redmine-3946;
closed without merge by contributor.
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://groups.google.com/groups/opt_out.
>
>
>
--
Adrie
e've done on Facter and Puppet, so there
shouldn't be any surprises here.
If you have any questions or concerns, please let us know on the mailing
list
or #puppet-dev on irc.freenode.net.
--
Adrien Thebo | Puppet Labs
--
You received this message because you are subscribed to the Goog
on, but we also don't
> want to do unnecessary cargo-culting.
>
> John Fritz and Jim Toth
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Developers" group.
> To unsubscribe from this group and stop receiving em
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?hl=en.
> For more options, visit https://groups.googl
t http://groups.google.com/group/puppet-dev?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
Adrien Thebo | Puppet Labs
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from
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?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
file.
So, what's the best way to handle the case where a file can't be
prefetched? Should we not touch any resources that the ParsedFile provider
manages on a failure like this, or should we risk losing some records to
manage the rest of the resources?
--
Adrien Thebo | Puppet Labs
-
Thanks,
> Justin
>
> --
> 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.
> To post
quot;Puppet Developers" group.
> To 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/pu
On Tue, Feb 19, 2013 at 11:10 PM, Andrew Parker wrote:
>
>
> On Feb 20, 2013, at 6:57 AM, Adrien Thebo wrote:
>
> One clarification - this file is a configuration file but it's going to be
> static, and specifically non-editable by the user. /usr being mounted as
> re
it in
> the gemdir, and do it correctly (from an FHS perspective) by default?
> Alternatively, Puppet could just look in /etc first and fallback to the
> libdir if /etc isn't there.
>
>
>
>
> On Tue, Feb 19, 2013 at 4:35 PM, Adrien Thebo wrote:
>
>> Hi all,
&g
't a viable solution in the long run; does anyone see a
better way of addressing this?
--
Adrien Thebo | Puppet Labs
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails fr
ing caching for 1.7?
> >
> > "Starting with Facter 1.7.0, you can now specify that the contents of a
> fact’s “setcode” block should be cached for faster retrieval."
> >
> > Quote from http://docs.puppetlabs.com/guides/custom_facts.html
>
> I think the caching ran i
I'm way late to the party, but +1 on this.
On Apr 23, 12:22 pm, Jo Rhett wrote:
> Why not encourage both? Separate the lists but suggest that replying to a
> commit message on the dev list is encouraged. Or if you can, set reply-to on
> the commit messages to go back to dev ;-)
>
> On Apr 23, 2
o 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/puppet-dev?hl=en.
>
--
Adrien Thebo | Puppet Labs
pgp: 0x6F1C4519 pgp.mit.edu
One of the things I've noticed is that puppet doesn't handle indirect
usage or reference of resources. For instance, there's the often cited
case of wanting to upgrade vulnerable packages, but only if they're
present on the system. It would be nice to be able to pull in more
system information like
I've been revisiting this, and it looks like there was a bug in the linux
kernel that got fixed in 2.6.13 that could cause ruby to hang, as was
detailed in http://projects.puppetlabs.com/issues/4466 . Since we support
CentOS 4 and later, and CentOS 4.0 was released with 2.6.9, we're not out of
the
the moment are finding that some
> files are 4 space indents, some are 2 space - and sometimes people are
> mixing 2 space indents within 4 space indent files.
>
> I know we've done this before for Puppet - so I wouldn't mind getting
> some opinion and ideas on this kind of a
new file it will ensure that the file has not been
loaded before.
Signed-off-by: Adrien Thebo
---
Local-branch: ticket/master/8491-remove_multiple_fact_loading
lib/facter/util/loader.rb|8
spec/fixtures/unit/util/loader/nosuchfact.rb |1 +
spec/unit/util
new file it will ensure that the file has not been
loaded before.
Signed-off-by: Adrien Thebo
---
Local-branch: ticket/master/8491-remove_multiple_fact_loading
lib/facter/util/loader.rb|7 +++
spec/fixtures/unit/util/loader/nosuchfact.rb |1 +
spec/unit/util
Added before and after hooks to store and restore environment data so
that changes to the hash do not persist between runs.
Signed-off-by: Adrien Thebo
---
Local-branch: ticket/master/8615
spec/spec_helper.rb | 11 ++-
1 files changed, 10 insertions(+), 1 deletions(-)
diff --git a
spec/unit/data and spec/fixtures were both directories containing
fixture data, but were arbitrarily separated. Consolidated the files.
Signed-off-by: Adrien Thebo
---
Local-branch: ticket/master/maint-consolidate-fixtures
.../data => fixtures}/6.0-STABLE_FreeBSD_ifconfig |0
.../d
From: Orion Poplawski
Added facts to differentiate Scientific Linux from Redhat.
Signed-off-by: Adrien Thebo
---
Local-branch: ticket/master/7682
lib/facter/hardwareisa.rb|2 +-
lib/facter/lsbmajdistrelease.rb |2 +-
lib/facter/macaddress.rb
operatingsystem.
In the manufacturer utility module, removed unneeded utility methods,
simplified DMI querying to make it more general purpose, and cleaned up
the dmi table accessor. Refactored the accompanying unit tests and moved
raw test data into fixture files.
Signed-off-by: Adrien Thebo
- prtdiag fails in many different environments; abstracting this away into a
utility module.
- Updated unit tests to reflect the change
- Solaris manufacturer fact now calls the utility module instead of
directly.
Signed-off-by: Adrien Thebo
---
Local-branch: ticket/master/7038
lib
Added osfamily fact to determine if a given operating system is a
derivative of a common operating system.
Signed-off-by: Adrien Thebo
---
Local-branch: ticket/master/6792
lib/facter/osfamily.rb | 27 +++
spec/unit/osfamily_spec.rb | 32
wrote:
> +1,
> To support SLES/SLED/OpenSuSE ...
>
> +elsif FileTest.exists?("/etc/SuSE-version")
> + "suse"
>
> Cheers
> Mike
>
> On 9/06/11 6:43 AM, Adrien Thebo wrote:
>> Added osfamily fact to determine if a given operating system i
Added osfamily fact to determine if a given operating system is a
derivative of a common operating system.
Signed-off-by: Adrien Thebo
---
Local-branch: ticket/master/6792
lib/facter/osfamily.rb | 24
spec/unit/osfamily_spec.rb | 26 ++
2
Added osfamily fact to determine if a given operating system is a
derivative of a common operating system.
Signed-off-by: Adrien Thebo
---
Local-branch: ticket/master/6792
lib/facter/osfamily.rb | 24
1 files changed, 24 insertions(+), 0 deletions(-)
create mode
ct.
>
> Signed-off-by: Adrien Thebo
> ---
> Local-branch: ticket/master/7753
> lib/facter/util/collection.rb | 16 ++--
> lib/facter/util/fact.rb | 19 ---
> 2 files changed, 22 insertions(+), 13 deletions(-)
>
> diff --git a/lib/facter/u
Added exception handling to the fact class. When adding a resolution to
a fact, if an exception was thrown outside of the setcode block, facter
would crash. Added handling so that if an exception is thrown, facter
logs the error and discards the fact.
Signed-off-by: Adrien Thebo
---
Local-branch
For some reason, the :timeout option in ipaddress.rb option started
causing facter to crash, since there is no timeout= method in the
collection, fact, or resolution classes. Removed the option, and
replaced it with a call to the limit method inside the resolution block.
Signed-off-by: Adrien
Added exception handling to the fact class. When adding a resolution to
a fact, if an exception was thrown outside of the setcode block, facter
would crash. Added handling so that if an exception is thrown, facter
logs the error and discards the fact.
Signed-off-by: Adrien Thebo
---
Local-branch
This adds error handling when actually adding a new resolve to a fact. It also
fixes a regression in the ipaddress fact and uses the correct method of setting
a timeout in fact resolution.
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To
From: adrienthebo
Signed-off-by: Adrien Thebo
---
Local-branch: ticket/master/7726
lib/facter/memory.rb |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/lib/facter/memory.rb b/lib/facter/memory.rb
index 992f2ad..ef861ad 100644
--- a/lib/facter/memory.rb
+++ b/lib
1 - 100 of 114 matches
Mail list logo
