Comments (11)
What do you mean by support? If the cron job is managed by puppet, the application user won't get able to modify it because puppet will change it back.
from puppet-cron.
You're correct. /var/spool/cron/ support would still be nice.
from puppet-cron.
To be clear, are you are saying you want this module to also duplicate the functionality of the core module and give you the option of which method to use for a job?
from puppet-cron.
I need the ability to manage /etc/cron.allow, /etc/cron.deny -- which the core module doesn't provide -- and the ability to put the cron jobs in /var/spool/cron/.
My application expects the users' cron job to be in /var/spool/cron/ and if it's not there, the application will create its own cron job. Yes, that stinks and it's poor coding on the part of the application but if I can get Puppet to put the cron job in /var/spool/cron/ then the application complains less.
The application takes hours if not days to configure and set up properly and hasn't been changed since 2017. My users are running BASH scripts to a bunch of setup and if I can Puppetize a good portion of the setup, I can save them nearly 8 hours of configuration and manual setup. Even just the ability to 'crontab -l' or 'cat /var/spool/cron// would be very useful. The users lose the ability to see the application jobs when the jobs are owned by root.
This is a commercial application that I cannot change. It's unbelievable how much effort goes into installing and configuring it.
Perhaps adding a variable called $cronjob_path and defaulting it to /etc/cron.d would be easy enough and not change behavior.
from puppet-cron.
The user story makes it clear, thanks. I am trying to pull some attention to this on Slack/libera so we can decide what to do.
from puppet-cron.
I'm working on a very rough draft of my ideas in a pull request. The only gotcha I see so far is:
if $default_cron_job_path != /etc/cron.d {
$path = "${cronjob_path}/${user}"
| else {
$path = "/etc/cron.d/${title}"
}
from puppet-cron.
I don't know that /var/spool/cron supports directories - usually there is just a file there.
from puppet-cron.
I don't know that /var/spool/cron supports directories - usually there is just a file there.
Whoop...my mistake. /var/spool/cron/ is the intended $path.
This is already getting more involved than I expected. The individual jobs will all have to be merged together under a single user's /var/spool/cron/ file. Perhaps this is a lot of work for little reward.
from puppet-cron.
I am looking at just changing the name of this module to crond
which should make it possible to use both
from puppet-cron.
puppetlabs-cron_core cannot co-exist with puppet-cron so using puppetlabs-cron_core one loses the ability to manage /etc/cron.allow.
I thought cron_core is always present in puppet-agent. I don't see the conflict. You can even deploy it your environment as cron_core
without issue.
from puppet-cron.
My apologies. I did manage to figure out using cron_core and puppet-cron.
from puppet-cron.
Related Issues (20)
- Please make a new release HOT 1
- Small patch to support FreeBSD cron job file group attribute HOT 3
- Commas in template are ignoring. How to use the enumeration?
- Resource type not found: Cron::Special HOT 2
- Add support for tilde (Randomization)
- Support for Managing Anacron HOT 1
- Job Template EPP Conversion Empty Newline
- Comma character in hour/minute parameters HOT 3
- Special to support @startup HOT 2
- cron: users_allow -> overwrite in module manifest (without hiera)
- Special parameter is now set incorrectly with two @ HOT 3
- Allow multiple applications (profiles) to add users to cron.[allow|deny]
- Implement CIS Benchmark requirements HOT 4
- pattern error Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Syntax error at '/' at /etc/puppetlabs/code/environments/ci/modules/cron/types/minute.pp:4:11 on node HOT 2
- Compare with cron_core ? HOT 2
- Can't get weekday options to work as an array of days HOT 2
- Fails on FreeBSD because gid 0 is wheel, not root HOT 1
- Test and enable for Puppet 7
- cron type patterns don't fully support cron syntax HOT 4
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-cron.