https://www.puppet.com/community logo
Join Slack
Powered by
# voxpupuli
  • e
    @vchepkov Would you mind ellaborating in this too? "your code implies one can enable same stream multiple times"
  • v
    Copy code
    dnf_module { 'module_nginx_stream_1.20':
  module         => 'nginx',
  enabled_stream => true,
}
dnf_module { 'module_nginx_stream_1.22':
  module         => 'nginx',
  enabled_stream => true,
}
    That's a valid puppet code, not a valid desired state, unlike
    Copy code
    package { 'nginx':
  ensure   => '1.20',
  provider => dnfmodule,
}
package { 'nginx':
  ensure   => '1.22',
  provider => dnfmodule,
}
  • v
    that will fail before code applied
  • e
    @vchepkov Gotcha
  • v
    If you want only stream managed and package be managed by specialized module, also possible
    Copy code
    package { 'nginx':
        ensure      => '1.20',
        enable_only => true,
        provider    => dnfmodule,
        before      => Class['nginx'],
      }
  • p
    I vaguly recall a bug with the 
    dnfmodule
    provider and the nvidia module stream
  • e
    @vchepkov In fact, you meant the same module, regardless of the streams. Maybe a poor use of title and parameters.
  • v
    luckily, at some point puppet fixed the problem of having one name per resource type
  • v
    if you don't like that, you can write something like this
  • v
    Copy code
    package { 'nginx-module':
        ensure      => '1.20',
        name        => 'nginx',
        enable_only => true,
        provider    => dnfmodule,
        before      => Class['nginx'],
      }
  • e
    @vchepkov Yes. That was my intended behaviour. Recalling better, my intention is to allow managing different profiles at different places. That requires the module name to be the same, so needs a title to differentiate. Well, the same as you showed.
  • e
    @vchepkov I couldn't do 2 things so far: 1. Install multiple profiles 2. Change profile state keeping stream state
  • v
    imho, you can't install multiple profiles. second, I find them completely useless and prefer to be explicit in my dependencies, not rely on something that may change
  • v
    profile is nothing more then a pre-set collection of packages
  • v
    I doubt postgresql module would ever say - install server stuff
  • v
    it bound to be more specific
  • e
    @vchepkov Well, in fact you can install multiple profiles. I don't know much about use cases, but I've seen some that require, for example, server and client packages, or development and whatever other one, at the same time. How good is that may be debatable, but it's something I commonly see. About being useful, I guess this depends more on who's using the stuff. I understand DNF modules, so their profiles, are there for a reason.
    🤷‍♂️ 1
    🙈 1
  • v
    I would submit a bug to puppet about not supporting multiple profiles
  • s
    This message was deleted.
    v
    e
    • 3
    • 3
  • v
    TIL: rubocop has --lint and --fix-layout options
  • v
    neat
  • v
    ewoud: can you take a look at https://github.com/ekohl/metadata_json_deps/pull/16 again?
  • v
    bastelfreak: what's the benefit of it right now? it just means you need to do a new major version but does it add any value?
  • v
    bastelfreak: unless there's something you want to use that Ruby 2.4 / 2.5 / 2.6 doesn't support
  • v
    the newer puppet_metadata/puppet_forge require ruby 2.7. I just wanted to avoid that people use metadata_json_deps on an old ruby and it fails to honour the minimal required ruby version
  • v
    if that's not an issue to you I can keep the older rubies
  • v
    I'd think that bundler can figure out that it should use an older version, or people can pin it bundler can't
  • v
    but for now I don't think it's an issue
  • v
    perfect, will update it
  • v
    ewoud: can we merge https://github.com/voxpupuli/voxpupuli-acceptance/pull/57 for now or would you like to see some adjustments?
1...535536537...647Latest