Code Monkey home page Code Monkey logo

Comments (9)

oxc avatar oxc commented on September 14, 2024 1

I thought about using dovecot::extconfigs for both, probably with the path relative to ${dovecot::config_path} as key

from puppet-dovecot.

c33s avatar c33s commented on September 14, 2024

#7 (comment)

I would instead provide a simple file wrapper that notifies the dovecot service, and on top of that a type that takes a key-value hash and renders it with a template.

do i understand you right, that you are planning to add this feature? will you add some kind of hiera wrapper to handle this config files as easy as the current config?

from puppet-dovecot.

oxc avatar oxc commented on September 14, 2024

I had no immediate plans initially, but I will try to whip something up today. Of course it will be accessible using hiera, but most likely on a different key, not the main dovecot::configs key

from puppet-dovecot.

c33s avatar c33s commented on September 14, 2024

most likely on a different key, not the main dovecot::configs key which of course makes much more sense. i just made a quickfix to get this mailserver up and running again.

would you handle the ext files in /etc/dovecot/conf.d different from them located in /etc/dovecot (same key/different keys)?

from puppet-dovecot.

c33s avatar c33s commented on September 14, 2024

sounds good. both ways (shared and seperate keys) look fine for me as you are providing a very good drop in example in your readme.

does it make sense to allow an absolute path? i am thinking about the ability to put config files on locations an operator want without opening a ticket or a pull request (just thoughts)

from puppet-dovecot.

c33s avatar c33s commented on September 14, 2024

and by the way: thank you for your work and your awesome lib. /cheer

from puppet-dovecot.

oxc avatar oxc commented on September 14, 2024

would you handle the ext files in /etc/dovecot/conf.d different from them located in /etc/dovecot (same key/different keys)?

After looking into it more closely, I'd say that supporting .conf.ext files in conf.d does not really make sense at all. The example-config uses them to easily provide multiple options the user can choose one from, but this is not required in a puppet setup, where you explicitly list all your configuration.

from puppet-dovecot.

c33s avatar c33s commented on September 14, 2024

fixed with #10

from puppet-dovecot.

oxc avatar oxc commented on September 14, 2024

Release on forge in v1.1.0

from puppet-dovecot.

Related Issues (14)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.