Ryan Coleman
- Email:
- Registered on: 10/24/2011
- Last connection: 05/16/2012
Projects
- AWS (Reporter, 11/15/2011)
- Cloud-Provisioner (Developer, 11/22/2011)
- Continuous Integration for Modules (Developer, Reporter, 10/24/2011)
- Facter (Developer, Support Staff, 10/24/2011)
- Hiera (Developer, Reporter, Support Staff, 10/24/2011)
- MCollective (Developer, Support Staff, 10/24/2011)
- MCollective Plugins (Developer, Support Staff, 10/24/2011)
- Naginator (Manager, 10/24/2011)
- Puppet (Developer, Reporter, Support Staff, 10/24/2011)
- Puppet Acceptance (Reporter, 10/24/2011)
- Puppet Community Package Repository (Developer, Reporter, Support Staff, 10/24/2011)
- Puppet Dashboard (Developer, Reporter, Support Staff, 10/24/2011)
- Puppet Documentation (Reporter, Support Staff, 10/24/2011)
- Puppet Enterprise (Public) (Reporter, Support Staff, 10/24/2011)
- Puppet Forge (Manager, Support Staff, 10/24/2011)
- Puppet Labs Modules (Developer, Reporter, Support Staff, 10/24/2011)
- PuppetDB (Reporter, 05/17/2012)
- Standard Library (Developer, Reporter, 04/03/2012)
Activity
Reported issues: 98
05/23/2012
- 03:51 pm Facter Feature #14667: External Cache for Facts
- Jeff Weiss wrote:
> Ryan Coleman wrote:
> > I'd like to see the yaml cache stored in Puppet's vardir or its locatio... - 03:39 pm Facter Feature #14667: External Cache for Facts
- I'd like to see the yaml cache stored in Puppet's vardir or its location configurable as another option in puppet.con...
- 11:10 am Puppet Documentation Bug #14240: Mention that open source nodes connecting to PE need to be kept out of the default group
- Nick Fagerlund wrote:
> And it occurs to me that this may actually be a usability bug rather than a docs request. "M...
05/22/2012
- 02:29 pm Puppet Forge Feature #14651: How should we handle testing & development content in Forge modules
(changed the ticket to be less about the solution, more about the problem)
Potential Solution:
One should be ...- 01:41 pm Puppet Forge Feature #14651 (Unreviewed): How should we handle testing & development content in Forge modules
- As we figure out how to solve robust testing and development workflows for Puppet modules, modules are increasingly l...
05/18/2012
- 11:40 am Puppet Forge Feature #14373 (Rejected): Programmatically retrieve structured data about a Forge user
- Ken Barber wrote:
> FYI: Programmatically retrieve information about all the releases of a module:
>
> curl '...
05/17/2012
- 11:43 am Puppet Forge Feature #10072 (Closed): Puppet Module Tool should handle module upgrades
- This has been accomplished by the built-in puppet module tool in Puppet FOSS 2.7.14 and PE 2.5 (puppet module upgrade).
- 09:22 am Puppet Forge Feature #13598: Modulefile metadata should include Puppet and Facter versions that this code is k...
- Just tossing a 'perfect world' idea out there. What if, for all modules that provide spec test, we automatically run ...
- 09:16 am Puppet Forge Feature #13598: Modulefile metadata should include Puppet and Facter versions that this code is k...
- I wonder if these items of metadata should be optional or required. I'm not sure if it's fair to expect module author...
- 09:12 am Puppet Forge Feature #14552 (Unreviewed): Module tool should check for Forge modules compatibility with runnin...
- Once module authors have the option to specify compatible Puppet and Facter versions, the module tool should check fo...
Also available in: Atom