Comments (9)
I thought about using dovecot::extconfigs
for both, probably with the path relative to ${dovecot::config_path}
as key
from puppet-dovecot.
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.
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.
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.
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.
and by the way: thank you for your work and your awesome lib. /cheer
from puppet-dovecot.
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.
fixed with #10
from puppet-dovecot.
Release on forge in v1.1.0
from puppet-dovecot.
Related Issues (14)
- Add changelog
- `include_in_main_config` in `create_config_file_resources.pp` is ignored and does nothing HOT 1
- Version dependencv HOT 4
- $extconfigfile missing in init.pp ? HOT 7
- notation for empty section HOT 3
- Hashes in extconfig HOT 7
- Purging config files under conf.d HOT 1
- Stdlib dependency outdated HOT 3
- dovecot::extconfigs just printing additional_content HOT 2
- Multiple passdb configs in 10-auth HOT 3
- Release on forge HOT 2
- Update link to Forge HOT 1
- dovecot::sieve does not work with `source` anymore
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from puppet-dovecot.