Updates Custom-Cron Documentation to prevent chef incompatibilities while adding cronjobs #457
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The documentation looks good. Why is there an edited thinking sphinx recipe in this PR? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of your patch
Adds Chef compliant naming section for naming cronjobs -
custom-cronRecommended Release Notes
Adds documentation for client to advice on naming only in the numeric way for the cronjobs timing parameters
Estimated risk
High - Invalid cron naming might lead to duplicate cron entries
Components involved
custom-croncookbooksDependencies
None
Description of testing done
Validated based on the ZD ticket #172818
QA Instructions
Nothing to QA technically, as this would be just simple modifications on documentation