-
-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove config when module is ensured to absent #478
Conversation
Fixes #477 |
manifests/extension/config.pp
Outdated
exec { $cmd: | ||
onlyif => "${ext_tool_query} -s ${_sapi} -m ${so_name} | /bin/grep 'No module matches ${so_name}'", | ||
require => ::Php::Config[$title], | ||
} | ||
} | ||
|
||
if $php::fpm { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is specific to Debian
as well?
Hi @amateo, thanks for this PR as well! Can you take a look at travis? The jobs are failing on CentOS, probably because of the if block in line 118 (see my inline comment for that). Could you add an acceptance test for this so we know it's working properly now? |
When the module is ensured to absent, it removes its config and not try to create the config file and enable it.
Hi @bastelfreak. I think all problems are now solved. |
Thanks! |
This patch ends up being a bit of a wild goose chase for all the available values of $ensure, since it can also be 'snapshot' or a pinned version. Even with #485 these will be marked as 'absent'. Doesn't it make more sense for line 93 to simply be |
I have just made #493 with this last change. |
When the module is ensured to absent, it removes its config and not try
to create the config file and enable it.