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

Add more possible values for update frequency #1157

Closed
webcompas opened this issue Dec 20, 2023 · 0 comments
Closed

Add more possible values for update frequency #1157

webcompas opened this issue Dec 20, 2023 · 0 comments
Labels
community

Comments

@webcompas
Copy link

Use Case

Currently $apt::update only accepts "always", "daily", "weekly" or "reluctantly" as a valid "frequency" value. Depending on Puppet's "runinterval" setting it would be better to have more and flexible options.

Proposed solution

I'd suggest to add at least two additional valid values:

  • "hourly": 3600 seconds since last update
  • Integer: Number of seconds since last update
webcompas added a commit to webcompas/puppetlabs-apt that referenced this issue Dec 21, 2023
@webcompas
Support "hourly" and Integer as value for update frequency (fixes pup…
5265b13 
…petlabs#1157)
@webcompas webcompas mentioned this issue Dec 21, 2023
Merged
2 tasks
bastelfreak pushed a commit to webcompas/puppetlabs-apt that referenced this issue Feb 15, 2024
@webcompas @bastelfreak
Support "hourly" and Integer as value for update frequency (fixes pup…
8e03966 
…petlabs#1157)
bastelfreak added a commit that referenced this issue Feb 15, 2024
@bastelfreak
Merge pull request #1159 from webcompas/main
3e364df 
Support "hourly" and Integer as value for update frequency (fixes #1157)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
community
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@webcompas @ia-content