diff options
| author | Tim Smith <tsmith@chef.io> | 2020-06-16 21:34:41 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-06-16 21:34:41 -0700 |
| commit | 0fd8e78fd3d2794cb46a776f890c70f571a6343d (patch) | |
| tree | 496be80693543c4f44ed92de5d622c88c312f80f | |
| parent | c5222dac2bb17efceddceaab7d35ec0458ebbdea (diff) | |
| download | chef-162.tar.gz | |
Update RELEASE_NOTES.md
162
Signed-off-by: Tim Smith <tsmith@chef.io>
Co-authored-by: pete higgins <pete@peterhiggins.org>
| -rw-r--r-- | RELEASE_NOTES.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md index 56f62504b5..8b83cac72a 100644 --- a/RELEASE_NOTES.md +++ b/RELEASE_NOTES.md @@ -66,7 +66,7 @@ The `chef_client_scheduled_task` resource has been updated to default the `frequ ### cron / cron_d -The `cron` and `cron_d` resources have been updated using the new Custom Resource Partials functionality introduced in Chef Infra Client 16. This has allowed us to standardize the properties used to declare cron job timing between the two resources. Timing properties all accept the same types / ranges and include the same validation, which makes moving from `cron` to `cron_d` seemless. +The `cron` and `cron_d` resources have been updated using the new Custom Resource Partials functionality introduced in Chef Infra Client 16. This has allowed us to standardize the properties used to declare cron job timing between the two resources. Timing properties all accept the same types / ranges and include the same validation, which makes moving from `cron` to `cron_d` seamless. ### cron_access |