-
-
Notifications
You must be signed in to change notification settings - Fork 59
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.
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
Use puppet-strings for reference docs #58
Conversation
The parameters currently missing documentation are...
I decided to leave them out of this PR and will create a separate PR for them. I can also create follow-up PRs to
Let me know what you think. Again, I didn't want to put too much in this single PR (making it hard to review). |
@@ -111,6 +111,9 @@ class { '::chrony': | |||
port => 123, | |||
} | |||
``` | |||
#### Note |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This note had got separated from its example.
# main chrony class | ||
# @summary Installs and configures chrony | ||
# | ||
# @example Install chrony with default options |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've copied the examples from the README, but not deleted them (yet). I think it's nice that there are at least a few of the most important examples there and not just in the reference docs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks
manifests/init.pp
Outdated
# stepping the time may be wanted. In this case, set `makestep_updates` to `-1` | ||
# to allow stepping the time for any update. | ||
# @param makestep_updates | ||
# Together with `makestep_seconds`, this configures the `makestep` parameter of `chronyd`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasn't sure what to do here. Happy to change this to new wording (to remove the duplication), or perhaps this could be done in a future PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please reword this, it's horrible to get your head around these sentences.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reworded and linked to official docs (which aren't great either TBH). I've also added an @example
and data types to the parameters.
@alexjfisher nice work, |
Not all parameters are currently documented. This commit migrates the ones that were documented in the README to REFERENCE.md using puppet strings.
1f13111
to
bc6af32
Compare
@alexjfisher is it ready for merging? |
yes. I was going to leave further improvements to future PRs. I didn't want to mix too many things in one diff making it hard to review. |
Not all parameters are currently documented. This commit migrates the
ones that were documented in the README to REFERENCE.md using puppet
strings.