Skip to content
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

WIP: Finish and release v2.0.0 #92

Open
wants to merge 17 commits into
base: master
Choose a base branch
from
Open

WIP: Finish and release v2.0.0 #92

wants to merge 17 commits into from

Conversation

hartmantis
Copy link
Owner

@hartmantis hartmantis commented Jul 25, 2017

What work remains to cut a v2 release?

  • What permissions should be used for the config files? At least in Ubuntu, the default clamd.conf and freshclam.conf have different ownership and different permissions.
  • Finish refactoring the initial update strategy. When should freshclam by run via an execute? When should Chef wait for it before proceeding?
  • Finish refactoring the old cron recipe into a scheduled scan custom resource.
  • Finish the clamav_addon resource, or make it just for clamav-milter and clamsmtpd if that's easier, (this could also wait for v2.1).
  • Finish re-adding Debian support and testing.
  • Finish adding back RHEL support. Note that RHEL7 has separate packages for systemd vs sysvinit support.
  • Add any other supported platform support and testing (Fedora?).
  • Update the README.
  • Fix the inevitable remaining build failures.

Otherwise we start polluting the resource namespaces with too many methods and
some collide with property names.
To start, for a "Debian" config, we've pulled the default config files off a
base Ubuntu 16.04 instance.
Also reorder operations so freshclam is ready before clamd is.
This should make it easier to add custom notifications between the different
child resources, i.e. in a recipe that just does an `include_recipe 'clamav'`.
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 6c1e4ec on jdh-v2.0 into ** on master**.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants