Jira (FACT-1351) Facter on Alpine Linux requires root permissions
Title: Message Title Gareth Rushgrove commented on FACT-1351 Re: Facter on Alpine Linux requires root permissions Ethan Brown Branan Riley thanks, I'll either make some time for this or close as won't fix so it gets out of the way either way. Cheers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1351) Facter on Alpine Linux requires root permissions
Title: Message Title Gareth Rushgrove commented on FACT-1351 Re: Facter on Alpine Linux requires root permissions Branan Riley thanks. When would you need something by for that release? I've been on holiday for the last week so just catching up. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7541) Explore removing export / collect / virtual / realize syntax
Title: Message Title Gareth Rushgrove commented on PUP-7541 Re: Explore removing export / collect / virtual / realize syntax A couple of points: The first a quick example of usage. The dummy_service module, which is commonly used when building Docker images using Puppet, uses the resource collectors to clobber all services in the catalog. https://github.com/puppetlabs/puppetlabs-dummy_service/blob/master/manifests/init.pp I'd love to see usage data here, given that most Puppet users won't see this issue. For instance it would be interesting to present information about the usage of these language features from a) Puppet modules on the Forge and b) Puppet code available in the Google BigQuery index. Both of those datasets are publicly available and might help identify how widely used these features are and for what usecases. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1351) Facter on Alpine Linux requires root permissions
Title: Message Title Gareth Rushgrove commented on FACT-1351 Re: Facter on Alpine Linux requires root permissions Unfortunately this is the only way of running Facter at present on Alpine as we don't have native puppet agents available. The puppet-agent-alpine (https://hub.docker.com/r/puppet/puppet-agent-alpine/) docker image has proved the most popular of the agent images released, with 46071 downloads as of today. That incorporates the workaround but if we want to have supported Docker images using Alpine (based on the above that would likely be appreciated by the community) we'll probably need to consider this issue. That might want tracking elsewhere so feel free to close and simply link that up I guess. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4182) add a flag to get JSON output from puppet resource
Title: Message Title Gareth Rushgrove commented on PUP-4182 Re: add a flag to get JSON output from puppet resource Note that this already works for YAML, ie. puppet resource package --to_yaml There are lots of oneliners for converting yaml to json as well: http://www.commandlinefu.com/commands/view/12218/convert-yaml-to-json Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6963) Puppet doesn't detect systemd as default service provider on CoreOS
Title: Message Title Gareth Rushgrove commented on PUP-6963 Re: Puppet doesn't detect systemd as default service provider on CoreOS Ah, yes. That is definitely the root cause, thanks for linking up. Facter 3.6.0 should be part of puppet-agent 1.9.0 which should be available in a week or so I believe. Once that's updated I'll be updating the puppet namespace Docker images. In the meantime you could override the fact in question via an ENV. Environment variables prefixed with FACTER_ win out over facter's detection. eg. $ docker run -e FACTER_osfamily=coreos puppet/facter osfamily coreos Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-6963) Puppet doesn't detect systemd as default service provider on CoreOS
Title: Message Title Gareth Rushgrove commented on PUP-6963 Re: Puppet doesn't detect systemd as default service provider on CoreOS @davideagle mmm, yes, that sounds like a separate issue against Facter. From what you've posted it sounds like facter isn't correctly detecting osfamily as coreos? If you could open a new issue under against Facter, with as much detail for recreating the isssue as possible that would be helpful. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1441) Add "cloud" fact that identifies Azure
Title: Message Title Gareth Rushgrove commented on FACT-1441 Re: Add "cloud" fact that identifies Azure Kenn Hussey I wasn't directly involved in this work but I do have some context from reviewing the PR. So I've gone ahead and added release notes. Might be worth getting Kenaz Kwa or Susannah Axelrod to double check Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1441) Add "cloud" fact that identifies Azure
Title: Message Title
Gareth Rushgrove updated an issue
Facter / FACT-1441
Add "cloud" fact that identifies Azure
Change By:
Gareth Rushgrove
Release Notes Summary:
The addition of a new top-level fact, cloud, intended for discovering whether a node is running on a given public cloud provider. In this first release this currently detects wether the node is running in Azure, and provides that information in the cloud.provider fact.No other cloud providers are currently detected.{code}"cloud": {"provider": "azure"}{code}
Release Notes:
New Feature
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3156) (maint) Start using clj-parent
Title: Message Title Gareth Rushgrove updated an issue PuppetDB / PDB-3156 (maint) Start using clj-parent Change By: Gareth Rushgrove Team: Cloud & Future Tech Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6963) Puppet doesn't detect systemd as default service provider on CoreOS
Title: Message Title Gareth Rushgrove commented on PUP-6963 Re: Puppet doesn't detect systemd as default service provider on CoreOS I've opened a PR with the relevant changes to address this at https://github.com/puppetlabs/puppet/pull/5402 I've tested it successfully with the following image https://hub.docker.com/r/garethr/puppet-agent-coreos/ which was built from the following Dockerfile: from puppet/puppet-agent RUN sed -i "/defaultfor :osfamily => :suse/a \ \ defaultfor :osfamily => :coreos" /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service/systemd.rb Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it,
Jira (PUP-6963) Puppet doesn't detect systemd as default service provider on CoreOS
Title: Message Title Gareth Rushgrove created an issue Puppet / PUP-6963 Puppet doesn't detect systemd as default service provider on CoreOS Issue Type: Bug Assignee: Unassigned Created: 2016/12/01 10:44 AM Priority: Normal Reporter: Gareth Rushgrove CoreOS is correctly identified by facter (https://github.com/puppetlabs/facter/blob/11288d2a33caec577fe696bd02e4bed12e5ac12d/lib/inc/internal/facts/linux/os_coreos.hpp) but when trying to manage services Puppet detects both init.d and systemd and defaults to init.d. In reality CoreOS uses systemd for all service management. Expected behaviour: The service provider should use systemd as the default provider for CoreOS Add Comment This
Jira (FACT-1441) Add "virtualization" fact that identifies AWS, Azure, etc
Title: Message Title
Gareth Rushgrove commented on FACT-1441
Re: Add "virtualization" fact that identifies AWS, Azure, etc
So, naming is hard.
This issues goes from a specific need "We should add a fact that determines whether or not a VM is running in Azure" to a general solution:
"virtualization": {
"hypervisor": "kvm",
"cloud": {
"provider": "azure",
"metadata": ...
}
But I think their is an assumption in the proposed structure which isn't explicit, and which I think is wrong. It assumes that a cloud provider is providing virtual machines running on top of a hypervisor. That's not 100% true of, for instance, Packet or Softlayer or Oracle Cloud. For instance the following would not make sense, because Packet isn't using virtualization.
"virtualization": {
"cloud": {
Jira (PDB-2669) Provide Official Docker PuppetDB
Title: Message Title Gareth Rushgrove commented on PDB-2669 Re: Provide Official Docker PuppetDB We now have Docker images available on Hub for various bits of Puppet software. You can find the images, including a PuppetDB image, at: https://hub.docker.com/u/puppet/ The tools used to build, including Dockerfiles, are in: https://github.com/puppetlabs/puppet-in-docker Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2752) puppet-client-tools package for Xenial is missing
Title: Message Title Gareth Rushgrove created an issue PuppetDB / PDB-2752 puppet-client-tools package for Xenial is missing Issue Type: Bug Assignee: Unassigned Created: 2016/05/27 7:22 AM Priority: Normal Reporter: Gareth Rushgrove As per conversation with Ryan Senior While following the documentation https://docs.puppet.com/puppetdb/latest/pdb_client_tools.html to install the puppet-client-tools, in order to use the new puppet query feature I hit a snag: Unable to locate package puppet-client-tools I'm running on Ubuntu Xenial, which we've just started shipping agent support for. Xenial is supported in the next PE release I believe. It looks like puppet-client-tools packages haven't made it to the xenial package repos yet.
Jira (PUP-6323) Support tdnf package provider for VMware PhotonOS
Title: Message Title Gareth Rushgrove created an issue Puppet / PUP-6323 Support tdnf package provider for VMware PhotonOS Issue Type: Bug Assignee: Unassigned Created: 2016/05/19 12:55 AM Priority: Normal Reporter: Gareth Rushgrove PhotonOS is a RPM derivative OS from VMware. However it does not use yum, nor the newer DNF. It uses a DNF compatible application called TDNF (https://github.com/vmware/tdnf). Some details from http://www.vcritical.com/2015/06/quickly-update-to-docker-1-6-on-photon-by-using-tdnf/ TDNF is a VMware innovation that offers DNF-compatible package management without a massive Python footprint. Add Comment
Jira (FACT-1422) Facter should detect PhotonOS
Title: Message Title
Gareth Rushgrove created an issue
Facter / FACT-1422
Facter should detect PhotonOS
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2016/05/18 4:19 AM
Priority:
Normal
Reporter:
Gareth Rushgrove
facter running on PhotonOS correctly detects it as Linux but does not provide details about the PhotonOS version. For instance:
{
architecture => "x86_64",
family => "Linux",
hardware => "x86_64",
Jira (PUP-6262) Provide Official Docker Puppetmaster
Title: Message Title Gareth Rushgrove commented on PUP-6262 Re: Provide Official Docker Puppetmaster Hi John Moser. I'm Gareth, one of the engineers at Puppet. As it happens I've been working on official docker images for various bits of Puppet software recently. I'll look to get the repository I'm working on opened up in the next week or so and update here when I do. Certainly open to collaborating on that. My implementation is pretty similar to what you have, along with a bunch of build toolchain stuff and testing. In the meantime, I'd love to understand your usecases. What made you consider running Puppet in Docker in the first place? What advantages do you see in doing so? Thanks again. Hopefully you'll like what I have so far, it's still definitely work in progress. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2669) Provide Official Docker PuppetDB
Title: Message Title Gareth Rushgrove commented on PDB-2669 Re: Provide Official Docker PuppetDB Hi John Moser. I'm Gareth, one of the engineers at Puppet. As it happens I've been working on official docker images for various bits of Puppet software recently. I'll look to get the repository I'm working on opened up in the next week or so and update here when I do. Certainly open to collaborating on that. My implementation is pretty similar to what you have, along with a bunch of build toolchain stuff and testing. In the meantime, I'd love to understand your usecases. What made you consider running Puppet in Docker in the first place? What advantages do you see in doing so? Thanks again. Hopefully you'll like what I have so far, it's still definitely work in progress. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1351) Facter on Alpine Linux requires root permissions
Title: Message Title
Gareth Rushgrove updated an issue
Facter / FACT-1351
Facter on Alpine Linux requires root permissions
Change By:
Gareth Rushgrove
Running facter on Alpine linux as a non-root user currently fails with the following error:{code}$ facterPermission denied @ dir_initialize - /sys/block/{code}The version of facter is 2.4.6, installed via the gem as a native package for Alpine is not available.{code}$ facter --version2.4.6{code}Note that asking for specific facts does not trigger the error, for instance:{code ] } $ facter osfamilyLinux{code}I've tracked this down to the blockdevice facts, and can trigger the error by asking for those facts directly.{code}$ sudo facter | grep blockblockdevice_sda_model => VBOX HARDDISKblockdevice_sda_size => 10737418240blockdevice_sda_vendor => ATAblockdevices => sda$ facter blockdevice_sda_modelCould not retrieve blockdevice_sda_model: Permission denied @ dir_initialize - /sys/block/$ facter blockdevice_sda_sizeCould not retrieve blockdevice_sda_size: Permission denied @ dir_initialize - /sys/block/$ facter blockdevice_sda_vendorCould not retrieve blockdevice_sda_vendor: Permission denied @ dir_initialize - /sys/block/$ facter blockdevicesCould not retrieve blockdevices: Permission denied @ dir_initialize - /sys/block/{code}So it appears to be the block device facts which require the permissions.The workaround I'm using at present is to delete those facts from the filesystem :){code}$ sudo rm /usr/lib/ruby/gems/2.2.0/gems/facter-2.4.6/lib/facter/blockdevices.rb{code}I think it would be good if, instead of preventing all output due to failures in individual facts, facter could fail only to output the blockdevice facts, maybe logging a warning, and output everything else.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (FACT-1351) Facter on Alpine Linux requires root permissions
Title: Message Title Gareth Rushgrove created an issue Facter / FACT-1351 Facter on Alpine Linux requires root permissions Issue Type: Bug Assignee: Unassigned Created: 2016/02/26 12:54 AM Priority: Normal Reporter: Gareth Rushgrove Running facter on Alpine linux as a non-root user currently fails with the following error: $ facter Permission denied @ dir_initialize - /sys/block/ The version of facter is 2.4.6, installed via the gem as a native package for Alpine is not available. $ facter --version
Jira (PDOC-70) Always generate JSON output for Rake task
Title: Message Title Gareth Rushgrove created an issue Puppet Strings / PDOC-70 Always generate JSON output for Rake task Issue Type: Improvement Assignee: Unassigned Created: 2016/02/21 9:12 AM Priority: Normal Reporter: Gareth Rushgrove At the moment it's not possible to generate the JSON output using the rake tasks, without knowing the internals and writing your own rake task. Given how useful that output can be, I think it's a reasonable default to always generate it. I've opened https://github.com/puppetlabs/puppetlabs-strings/pull/72/files with that change. My rationale for that is by always generating it more people will find out about it, and potentially use it to do awesome. A user that really doesn't want that can always add it to .gitignore or similar, or write there own rake task. This could be made configurable later, or split into separate tasks. I'm less bothered about the implementation and more interested in the default. Outputting by default could lead to more visibility/usage of the format, which can only be a good thing. Add Comment
Jira (PUP-5743) Puppet 3.8.5 breaks compatibility with rspec-puppet
Title: Message Title
Gareth Rushgrove commented on PUP-5743
Re: Puppet 3.8.5 breaks compatibility with rspec-puppet
Posting the upstream bug so everything is in one place:
I hit an issue this morning with the Docker module in Travis where a single test (which had previously passed) failed, but only under the newly released Puppet 3.8.5 (released January 21st). This was also reported independently by another contributor garethr/garethr-docker#396.
Running the test on it's own see's it pass. Testing with previously passing code fails. Testing with rspec-puppet master and with 2.3 also fails. As suggested by @DavidS I tried 2.2 and this allowed the test to pass.
After much spelunking I was able to get a small test case which reliably recreates the failure.
require 'spec_helper'
describe 'docker::run', :type => :define do
let(:title) { 'sample' }
context 'passing the required params' do
let(:facts) { {:osfamily => 'Archlinux'} }
let(:params) { {'command' => 'command', 'image' => 'base'} }
initscript = '/etc/systemd/system/docker-sample.service'
Jira (PUP-5743) Puppet 3.8.5 breaks compatibility with rspec-puppet
Title: Message Title Gareth Rushgrove commented on PUP-5743 Re: Puppet 3.8.5 breaks compatibility with rspec-puppet Just to connect all the things. I hit this this morning working on the docker module. Another test case at https://github.com/rodjek/rspec-puppet/issues/353 which demonstrates triggering the issue by making more than 16 identical tests. First 16 pass. All the rest fail My fix was to pin to rspec-puppet 2.2.0 which didn't exhibit this behaviour. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5743) Puppet 3.8.5 breaks compatibility with rspec-puppet
Title: Message Title Gareth Rushgrove commented on PUP-5743 Re: Puppet 3.8.5 breaks compatibility with rspec-puppet I've put up a PR that appears to resolve the problem: https://github.com/rodjek/rspec-puppet/pull/354/files I've not had chance to write a test or to widely test this but it resolves the issue for the Docker module test suite and has some level of understanding of the problem. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5743) Puppet 3.8.5 breaks compatibility with rspec-puppet
Title: Message Title Gareth Rushgrove commented on PUP-5743 Re: Puppet 3.8.5 breaks compatibility with rspec-puppet Other observations: I think the note about shared_examples is a red-herring. I'm not using them anywhere in the docker test suite and still see the issues I've run the test using rspec 3.4.0 (latest release) and rspec 3.1.0 (last release to support Ruby 1.8.7). The behaviour (ie. failure only on rspec-pupet 2.3.0 and Puppet 3.8.5) occurs on both The same test suites pass on rspec-puppet 2.3.0 on the 4+ series and on 3.8.4 and below, it's just the combination of rspec-puppet 2.3.0 AND Puppet 3.8.5 that triggers the issue The number 16 seems key to finding the cause, see the max cache size: https://github.com/rodjek/rspec-puppet/blob/8a90608341077197323c6e35c042f7d1699a3cae/lib/rspec-puppet/cache.rb#L4. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5743) Puppet 3.8.5 breaks compatibility with rspec-puppet
Title: Message Title Gareth Rushgrove commented on PUP-5743 Re: Puppet 3.8.5 breaks compatibility with rspec-puppet Quick suggestion by Henrik Lindberg, changing the magic number in https://github.com/rodjek/rspec-puppet/blob/8a90608341077197323c6e35c042f7d1699a3cae/lib/rspec-puppet/cache.rb#L4 to 5 instead of 16 results in n-5 test failures rather than n-16. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1661) Extend Skeleton functionality, including downloading from path
Title: Message Title Gareth Rushgrove commented on PUP-1661 Re: Extend Skeleton functionality, including downloading from path Peter Souter do you have a link to the module you created? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1163) Facts for VMware hosts ala EC2 facts
Title: Message Title Gareth Rushgrove created an issue Facter / FACT-1163 Facts for VMware hosts ala EC2 facts Issue Type: Improvement Assignee: Unassigned Created: 2015/08/13 12:51 AM Priority: Normal Reporter: Gareth Rushgrove Interesting conversation on twitter https://twitter.com/cdenneen/status/631647908845236224 I was hoping with the ec2 metadata now as built in facts same would come for @VMware These would be similar to the EC2 facts I would imagine, ie. accessing the vSphere API from the instance and returning details about that same host. Add Comment
Jira (PUP-3656) Prefetch eats most exceptions (those derived from StandardError), there is no way to fail out.
Title: Message Title Gareth Rushgrove commented on PUP-3656 Re: Prefetch eats most exceptions (those derived from StandardError), there is no way to fail out. Just talking with Ethan Brown who pointed out a workaround for this exists today (hence the change of title). If you create your own exception inheriting from Exception and throw that you can block the whole run. class MyError Exception and then in prefetch somewhere raise MyError This results in a run that stops: $ puppet apply tests/sg.pp Notice: Compiled catalog for pro.local in environment production in 0.07 seconds Error: Could not run: MyError Simply raising StandardError, say with:
Jira (PUP-4182) add a flag to get JSON output from puppet resource
Title: Message Title Gareth Rushgrove commented on PUP-4182 Re: add a flag to get JSON output from puppet resource Just a note that I'd love to see this too. I think for managing environment/remote resources puppet resource is actually quite a killer feature. The AWS module is hugely improved by having a Puppet native command line interface. I would imagine other cloud-provider resources, and some of the other ideas like Kubernetes, Docker Swarm, Mesos Aurora/Marathon/Chronos, will see the same thing too. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-686) --detailed-exit-codes not honored when --noop is used
Title: Message Title Gareth Rushgrove commented on PUP-686 Re: --detailed-exit-codes not honored when --noop is used With regards whether this is the right thing to do, I wanted to do this just a few days ago. My usecase was using noop for auditing, watching for changes and throwing an error if any where found. I found the existing experience surprising. I ended up doing something horrible with --lastrunfile, --postrun_command and this shell script: https://github.com/puppetlabs/puppetlabs-aws/blob/master/examples/audit-security-groups/count_out_of_sync_resources.sh Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3188) Puppet module tool no longer processes files starting with a period as erb
Title: Message Title Gareth Rushgrove updated an issue Puppet / PUP-3188 Puppet module tool no longer processes files starting with a period as erb Change By: Gareth Rushgrove Affects Version/s: PUP3.7.0 Affects Version/s: PUP3.6.0 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3188) Puppet module tool no longer processes files starting with a period as erb
Title: Message Title Gareth Rushgrove commented on PUP-3188 Re: Puppet module tool no longer processes files starting with a period as erb Sorry, I thought I'd updated this ticket. My bad. This is fixed in 3.7.x, although you can recreate it with 3.6.x. It would be nice to have a test that checks this functionality though, but you can close this issue as fixed I think. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3656) Prefetch eats all exceptions, there is no way to fail out.
Title: Message Title Gareth Rushgrove commented on PUP-3656 Re: Prefetch eats all exceptions, there is no way to fail out. +1 from me too. This will likely affect providers that use network based APIs more than other on host providers. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3188) Puppet module tool no longer processes files starting with a period as erb
Title: Message Title Gareth Rushgrove assigned an issue to Gareth Rushgrove Puppet / PUP-3188 Puppet module tool no longer processes files starting with a period as erb Change By: Gareth Rushgrove Assignee: AndersonMills GarethRushgrove Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
