| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| cloud | ||
| commands | ||
| database | ||
| files | ||
| internal | ||
| inventory | ||
| messaging | ||
| monitoring | ||
| net_infrastructure | ||
| network | ||
| notification | ||
| packaging | ||
| source_control | ||
| system | ||
| utilities | ||
| web_infrastructure | ||
| windows |
As far as I can tell, `name` is a required parameter. The guard test at (now) line 458 says you need name if `state == present` and at 464 if `state != present`, although that's not quite as clear. Each of the code paths at 485 - 495 pass the name param through to `add_job`, `update_job` and `remove_job`, and the actual _update_job method earlier seems to require it too. However I don't really know python so I may be wrong, but I can't see the circumstances when `name` is not required.
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| cloud | Loading commit data... | |
| commands | Loading commit data... | |
| database | Loading commit data... | |
| files | Loading commit data... | |
| internal | Loading commit data... | |
| inventory | Loading commit data... | |
| messaging | Loading commit data... | |
| monitoring | Loading commit data... | |
| net_infrastructure | Loading commit data... | |
| network | Loading commit data... | |
| notification | Loading commit data... | |
| packaging | Loading commit data... | |
| source_control | Loading commit data... | |
| system | Loading commit data... | |
| utilities | Loading commit data... | |
| web_infrastructure | Loading commit data... | |
| windows | Loading commit data... |