Using a full path for path is not always desirable. about puppet-alternatives HOT 6 CLOSED

Workaround:

   exec{'jdk8':
      command => '/usr/bin/alternatives  --set java java-1.8.0-openjdk.x86_64',
      unless  => '/usr/bin/readlink /etc/alternatives/java | /usr/bin/grep -q /java-1.8.0-openjdk-1.8.0'
    }

from puppet-alternatives.

Are there any news?

from puppet-alternatives.

Just hit this as well. Upvote, FWIW.

from puppet-alternatives.

Just added a PR to simply remove the validation line. Don't know that there's a great solution to also looking at "families", but I haven't dug into the alternatives system much. A quick look appears that the "family" thing is not a term mentioned in the man pages. But as the OP and I have discovered, it does seem to work for the JDK, at least.

I'm able to use update-alternatives --set java java-latest-openjdk.x86_64 successfully, and with the code change, I can use this in the manifest:

  alternatives { 'java':
    mode => 'manual',
    path => 'java-latest-openjdk.x86_64',
  }

from puppet-alternatives.

...and, as with all things, it turned out not to be that simple, of course. :D
Since my setup doesn't need to have multiple jdk's installed, I'm going to punt, but it would be great if this could work. I'll look at it more as I get time, but for now, my PR just results in puppet setting the alternative every run, which is obviously not desired.

from puppet-alternatives.

Would be great if this could be fixed.

Here is a workaround for Java 11 under RHEL 7:

alternative_entry {'/usr/lib/jvm/jre-11-openjdk/bin/java':
    ensure   => present,
    altlink  => '/usr/bin/java',
    altname  => 'java',
    priority => 999999,
    require  => Package['java-11-openjdk-headless'],
}

alternatives { 'java':
  path    => '/usr/lib/jvm/jre-11-openjdk/bin/java',
  require => Alternative_entry['/usr/lib/jvm/jre-11-openjdk/bin/java'],
}

This adds an entry with a static path using the already available link under /usr/lib/jvm

from puppet-alternatives.