https://www.puppet.com/community logo
Join Slack
Powered by
# puppet
  • s
    This message was deleted.
    v
    s
    d
    • 4
    • 4
  • s
    This message was deleted.
    j
    b
    • 3
    • 34
  • d
    kermit typing CAT team -- modules is about to start up in #CFD8Z9A4T
  • s
    This message was deleted.
    b
    y
    +2
    • 5
    • 8
  • s
    This message was deleted.
    b
    r
    c
    • 4
    • 17
  • d
    fry dancing 🧑‍🏫Puppet Core Team is about to start up in #CFD8Z9A4T
  • s
    This message was deleted.
    b
    j
    +2
    • 5
    • 19
  • s
    This message was deleted.
    n
    c
    • 3
    • 5
  • s
    This message was deleted.
    y
    e
    +2
    • 5
    • 8
  • d
    Hi, I'm trying to write a provider to manage open and closed ports with firewalld. I know that a module already exists for that, but it is mostly for learning purpose. However, I encounter 2 issues. 
    pdk
    creates the type and provider with 
    SimpleProvider
    , which is fine. The 
    delete
    method gets a context and a name as parameters, but no 
    should
    , and there is no way to find which port and protocol should be removed. Is there another solution than forcing this information to be stored in the name of the resource? Second issue I have with SimpleProvider is the syntax to use to confine the provider. How to use the equivalent of 
    :command
    and 
    :confine
    that we have in a low-level implementation?
  • s
    This message was deleted.
    chocolatey 2
    r
    r
    • 3
    • 2
  • b
    Hello again! I'm using puppet-mysql module to manage an enterprise version of MariaDB. I need to modify the systemd unit file for the service (/usr/lib/systemd/system/mysqld.service) I don't see anything in the mysql module that leads me to believe that the module can manage the unit file. Would a systemd module be appropriate or should I just make a one-off template for the unit file?
  • v
    in the profile class, where you call mysql::server you can add 
    systemd::unit_file
    or, maybe just 
    systemd::dropin_file
    just need to insert it between classes of mysql
  • v
    Copy code
    Class['mysql::server::install'] -> Systemd::Dropin_file['custom'] ~> Class['mysql::server::service']
  • b
    use 
    systemd::dropin_file
    🙂
  • b
    Thanks, guys. That seems like something that would be useful in the mysql/mariadb module.
  • s
    There's a big philosophy of where to draw the line between what one module does and what another does. I could see the argument either way as to whether a module like mysql should be able to manage its own unit file versus leveraging the systemd module. It's certainly worth opening a Git Issue to see if thoughts had changed over time.
  • s
    This message was deleted.
    m
    y
    • 3
    • 11
  • s
    Hello, as diskussed in this thread https://puppetcommunity.slack.com/archives/C0W298S9G/p1688997966881979 I went with the option to create a new provider for postgresql_conf. The current code is on Github: https://github.com/puppetlabs/puppetlabs-postgresql/blob/8205c5f67e8ae5a6c62b8f355ff8eabf85d01191/lib/puppet/provider/postgresql_conf/ruby.rb Using the provider shows the following error:
    Copy code
    Error: Could not autoload puppet/provider/postgresql_conf/ruby: undefined local variable or method `resource' for Puppet::Type::Postgresql_conf::ProviderRuby:Class
Did you mean?  resource_type
Error: Could not autoload puppet/type/postgresql_conf: Could not autoload puppet/provider/postgresql_conf/ruby: undefined local variable or method `resource' for Puppet::Type::Postgresql_conf::ProviderRuby:Class
Did you mean?  resource_type
Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Type-Name, Could not autoload puppet/type/postgresql_conf: Could not autoload puppet/provider/postgresql_conf/ruby: undefined local variable or method `resource' for Puppet::Type::Postgresql_conf::ProviderRuby:Class
Did you mean?  resource_type (file: /vagrant/puppet/modules/postgresql/manifests/server/config_entry.pp, line: 76, column: 5) (file: /vagrant/puppet/modules/postgresql/manifests/server/instance/config.pp, line: 206)
    As far as I understand and saw in other providers, the 
    resource
    hash should be available. Are there any conditions? I know e.g. 
    @property_hash
    is dependent on prefetching.
  • s
    This message was deleted.
    n
    c
    e
    • 4
    • 8
  • s
    This message was deleted.
    c
    • 2
    • 1
  • v
    safer bet would be to define a stage with just that exec that runs at the end
  • c
    Greetings puppetteers! I have a basic question that I can't seem to successfully find the answer for: When I'm removing a user, I get a failure from the group resource - cannot remove the user's primary group before the user is removed. However, puppet autorequires the user's primary group if present managed (as it is in my case). Is there a built-in way to handle this case of removing a user, or do I need to add a resource ordering directive for the cases of removing instead of adding users? The order when adding a user is User['foo'] requires Group['foo'], but when removing a user it becomes User['foo'] before Group['foo']. My google-fu is failing me terribly this morning. This is obviously a thoroughly solved problem.
  • s
    This message was deleted.
    💯 1
    c
    v
    +5
    • 8
    • 33
  • s
    This message was deleted.
    n
    m
    c
    • 4
    • 13
  • s
    This message was deleted.
    n
    m
    • 3
    • 4
  • s
    This message was deleted.
    s
    • 2
    • 1
  • s
    This message was deleted.
    👍🏻 1
    surprised 1
    y
    b
    d
    • 4
    • 8
  • s
    This message was deleted.
    y
    r
    +5
    • 8
    • 15
  • s
    This message was deleted.
    b
    b
    • 3
    • 3
1...400401402...428Latest