Skip to content
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

Improve generated documentation #6037

Merged
merged 2 commits into from
Jan 11, 2018

Conversation

tsg
Copy link
Contributor

@tsg tsg commented Jan 10, 2018

The Filebeat module all docs follow the same template. This updates
the generated docs to contain this template and mark the section that
need work as TODOs.

The Filebeat module all docs follow the same template. This updates
the generated docs to contain this template and mark the section that
need work as TODOs.
@tsg
Copy link
Contributor Author

tsg commented Jan 10, 2018

@dedemorton You review on this one would be appreciated.

Copy link
Contributor

@dedemorton dedemorton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great! Just a couple of comments. Otherwise, LGTM.

include::../include/configuring-intro.asciidoc[]

TODO: provide an example configuration

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's an example in config-option-intro.asciidoc that uses the fileset_ex attribute to resolve a fileset name:

TIP: When you specify a setting at the command line, remember to prefix the
setting with the module name, for example, +{modulename}.{fileset_ex}.var.paths+
instead of +{fileset_ex}.var.paths+.

So...I would add a TODO item before line 54. Something like:

TODO: Set the fileset_ex attribute to the name of any fileset in your module. For example:
:fileset_ex: access


include::../include/config-option-intro.asciidoc[]

TODO: document: fileset variables
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we expand the instructions here and provide an example? Or will that confuse users? If you think this would be confusing to module developers, we can provide feedback when the module is submitted for review.

TODO: document: fileset variables. If you're describing a variable that's common to other modules, you
can reuse shared descriptions by including the relevant file. For example:
[float]
==== `access` log fileset settings

include::../include/var-paths.asciidoc[]

@tsg
Copy link
Contributor Author

tsg commented Jan 11, 2018

@dedemorton While addressing your comments I realised that I can also make use of the {fileset} variable to makes things simpler. Can you have another look?

Copy link
Contributor

@dedemorton dedemorton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ruflin ruflin merged commit a10edb3 into elastic:master Jan 11, 2018
@ruflin ruflin added Filebeat Filebeat :Generator Related to code generators for building custom Beats or modules. labels Jan 11, 2018
@ruflin
Copy link
Collaborator

ruflin commented Jan 11, 2018

@kvch This might affect your PR in #5544

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Filebeat Filebeat :Generator Related to code generators for building custom Beats or modules. review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants