[Puppet-dev] Re: Removing types/providers from core

I completely missed 'tidy', that was a copy-paste gone wrong. I really have no preference towards that one but John makes a good argument that the way it interacts with file would warrant it to stay in core. Mount on the other hand can only work with mount/umount and is chained to /etc/fstab or

Re: [Puppet-dev] how can i get each java version in each custom facts

On Wed, Oct 8, 2014 at 12:59 PM, Supriya Uppalapati < supriya.uppalap...@gmail.com> wrote: > Hi Andrey, > > When i tried your example, It is not returning any values > > require 'facter/util/file_read' > => true > irb(main):005:0> log = > Facter::Util::FileRead.read("/home/suppalapati/java.txt") >

Re: [Puppet-dev] Package duplicate resource issue - PUP-1073

On Wednesday, October 8, 2014 1:43:09 PM UTC-5, Andy Parker wrote: > My proposal allows > > package { 'mysql-gem': name => mysql, provider => gem, ensure => > installed } > package { 'mysql': ensure => installed } > > Such statements would have previously collided because both would have

Re: [Puppet-dev] Package duplicate resource issue - PUP-1073

On Wednesday, October 8, 2014 11:51:32 AM UTC-7, John Bollinger wrote: > > > > On Wednesday, October 8, 2014 6:55:19 AM UTC-5, Felix Frank wrote: >> >> >> >> If I understand Andy correctly, we might have something like >> >> package { 'mysql-gem': package_name => mysql, provider => gem } >> >> .

Re: [Puppet-dev] how can i get each java version in each custom facts

Hi, My question is *require 'facter/util/file_read'* *=> true* *irb(main):005:0> log = Facter::Util::FileRead.read("/home/suppalapati/java.txt")* *=> "\n/usr/java/jdk1.7.0_25/jre/bin/java\n/usr/java/jdk1.7.0_25/bin/java\n/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.45.x86_64/jre/bin/java\n/usr/lib/jv

[Puppet-dev] Re: Puppet PR Triage 2014-10-07

On Wed, Oct 8, 2014 at 11:49 AM, Rob Reynolds wrote: > Join us for the Puppet PR Triage starting in about 10 minutes at > http://links.puppetlabs.com/pr-triage > > -- > Rob Reynolds > Developer, Puppet Labs > > *Join us at PuppetConf 2014 , September > 20-24 in San Fra

Re: [Puppet-dev] how can i get each java version in each custom facts

Hi Andrey, When i tried your example, It is not returning any values require 'facter/util/file_read' => true irb(main):005:0> log = Facter::Util::FileRead.read("/home/suppalapati/java.txt") => "\n/usr/java/jdk1.7.0_25/jre/bin/java\n/usr/java/jdk1.7.0_25/bin/java\n/usr/lib/jvm/java-1.7.0-openjdk-1

Re: [Puppet-dev] how can i get each java version in each custom facts

On Wed, Oct 8, 2014 at 12:32 PM, Supriya Uppalapati < supriya.uppalap...@gmail.com> wrote: > Hi, > > It isn't executing anything. it means it is not showing individual fact > for each java version. yes my facts(java_version_count ) is showing me how > many lines(means java) i have in java.txt. yes

Re: [Puppet-dev] how can i get each java version in each custom facts

Hi, It isn't executing anything. it means it is not showing individual fact for each java version. yes my facts(java_version_count ) is showing me how many lines(means java) i have in java.txt. yes i placed in wright location.I followed the link which you provided me. I feel some thing is wrong

Re: [Puppet-dev] how can i get each java version in each custom facts

On Wed, Oct 8, 2014 at 11:26 AM, Supriya Uppalapati < supriya.uppalap...@gmail.com> wrote: > Hi All, > > I am trying to get all the java versions and paths where it is located. I > got all java_paths in a fact called java_path. Now i need those versions in > each custom facts. > > I wrote a code b

Re: [Puppet-dev] Package duplicate resource issue - PUP-1073

On Wednesday, October 8, 2014 6:55:19 AM UTC-5, Felix Frank wrote: > > On 10/08/2014 01:23 PM, Trevor Vaughan wrote: > > > > service { 'my_service': require => Package['mysql']{ :provider => 'gem' > } } > > How about require => Package<| title == 'mysql' and provider == 'gem' |> > I filed

Re: [Puppet-dev] Package duplicate resource issue - PUP-1073

On Wed, Oct 8, 2014 at 6:33 AM, Felix Frank wrote: > On 10/08/2014 03:23 PM, Trevor Vaughan wrote: > > > > If you go with the descriptive namevar, you'll need to make the > > separator something that won't show up in a package name. So probably > > one of '+/,|' etc... > > That's not what I'm say

Re: [Puppet-dev] Removing types/providers from core

On Wednesday, October 8, 2014 5:46:31 AM UTC-5, Trevor Vaughan wrote: > > I agree with your assessment of what should stay and what should not with > the exception of tidy and mount. Those two are not platform specific from > what I can tell. > > I agree that Tidy is not platform-specific. Mo

[Puppet-dev] how can i get each java version in each custom facts

Hi All, I am trying to get all the java versions and paths where it is located. I got all java_paths in a fact called java_path. Now i need those versions in each custom facts. I wrote a code but this not executing . Please help me *require 'rexml/document'* *require 'facter'* *Facter.add("j

[Puppet-dev] Puppet PR Triage 2014-10-07

Join us for the Puppet PR Triage starting in about 10 minutes at http://links.puppetlabs.com/pr-triage -- Rob Reynolds Developer, Puppet Labs *Join us at PuppetConf 2014 , September 20-24 in San Francisco* -- You received this message because you are subscribed to t

Re: [Puppet-dev] Package duplicate resource issue - PUP-1073

On Tuesday, October 7, 2014 9:10:11 PM UTC-5, Daniele Sluijters wrote: > > Separate types undoes basically what "package" now tries to make as > transparent as possible. I guess a case could be made to have "package" > only deal with the OS native package provider and have separate types and > p

Re: [Puppet-dev] Package duplicate resource issue - PUP-1073

This is the best idea I've heard. Certain puppet types intend to provide an abstraction. This abstraction only works for native package providers in this case because anything else requires the user to make an informed decision. I think having all other package providers be separate types is ju

Re: [Puppet-dev] Package duplicate resource issue - PUP-1073

It may be but, if we're already going to munge about with the namevar to make it unique, why not just use it without having to type more? Trevor On Wed, Oct 8, 2014 at 9:33 AM, Felix Frank wrote: > On 10/08/2014 03:23 PM, Trevor Vaughan wrote: > > > > If you go with the descriptive namevar, you

Re: [Puppet-dev] Package duplicate resource issue - PUP-1073

On 10/08/2014 03:23 PM, Trevor Vaughan wrote: > > If you go with the descriptive namevar, you'll need to make the > separator something that won't show up in a package name. So probably > one of '+/,|' etc... That's not what I'm saying. I'm saying let the namevar no longer be the package name at

Re: [Puppet-dev] Package duplicate resource issue - PUP-1073

So, I would *love* to see proper inheritance for Types. Currently, I can inherit Providers and do classic OO stuff but I can't do that with Types and it drives me a bit nuts. If you go with the descriptive namevar, you'll need to make the separator something that won't show up in a package name.

Re: [Puppet-dev] Package duplicate resource issue - PUP-1073

On 10/08/2014 01:23 PM, Trevor Vaughan wrote: > > service { 'my_service': require => Package['mysql']{ :provider => 'gem' } } How about require => Package<| title == 'mysql' and provider == 'gem' |> Not that it matters - having two Package[mysql] resources will *never* be a thing. If I understa

Re: [Puppet-dev] Package duplicate resource issue - PUP-1073

Sorry for the double post but I just thought of this. 1) The ldap provider probably needs to be removed from 'user'. Yes, they are users but they're not native, they could be one of many things. 2) If we do want to keep gem as a package provider, you'll need something like the following: service

Re: [Puppet-dev] Package duplicate resource issue - PUP-1073

That's the fundamental issue though. Package isn't a package. Package is one of many distinct things. This is like the following: user { 'foo': provider => 'passwd' } user { 'foo': provider => 'apache' } They're simply two different things so they would be user (i.e. native user) and apache_us

Re: [Puppet-dev] Removing types/providers from core

I agree with your assessment of what should stay and what should not with the exception of tidy and mount. Those two are not platform specific from what I can tell. However, I would like to request that, if they stay, that improvements/enhancements to native types are either included or excluded w

Re: [Puppet-dev] Removing types/providers from core

Hi there, agree with most of this, see comments below. On 10/08/2014 04:36 AM, Daniele Sluijters wrote: > > I would also keep resources, notify, stage and schedule around and the > filebucket because of how they influence Puppet's behaviour and the > behaviour of other resources. I'm not sure a