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.

Sign up for GitHub

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

Jump to bottom

Disabling manage-cron does not remove crontab record #139

Closed
Kentzo opened this issue Sep 28, 2018 · 1 comment · Fixed by #161
Closed

Disabling manage-cron does not remove crontab record #139

Kentzo opened this issue Sep 28, 2018 · 1 comment · Fixed by #161

Comments

@Kentzo
Copy link

Kentzo commented Sep 28, 2018

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 4.10.12
  • Module version: 2.4.0

How to reproduce (e.g Puppet code you use)

Set letsencrypt::certonly::manage-cron to true, sync, set to false, sync

What are you seeing

crontab record and script are still present

What behaviour did you expect instead

at least the crontab record should be removed
@bastelfreak
Copy link
Member

Hey @Kentzo, thanks for reporting this bug. Are you able to provide a PR for this?

@craigwatson craigwatson mentioned this issue Jan 16, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Certonly: Refactor manage_cron to ensure_cron with appropriate data type
2 participants
@Kentzo @bastelfreak