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

Fix documentation for s3 output #181

Closed
wants to merge 1 commit into from

Conversation

ctbarrett
Copy link
Contributor

The example configuration lists access_key_id and secret_access_key as required parameters, but later references in the documentation contradict that here and here.

This changes the (required) comments to (optional).

The example configuration lists `access_key_id` and `secret_access_key` as required parameters, but later references in the documentation contradict that [here](https://www.elastic.co/guide/en/logstash/current/plugins-outputs-s3.html#plugins-outputs-s3-options) and [here](https://www.elastic.co/guide/en/logstash/current/plugins-outputs-s3.html#plugins-outputs-s3-access_key_id).

This changes the `(required)` comments to `(optional)`.
@ctbarrett
Copy link
Contributor Author

CLA signed/verified

@jsvd jsvd requested a review from robbavey May 23, 2018 14:36
@robbavey robbavey self-assigned this May 29, 2018
Copy link
Contributor

@robbavey robbavey left a comment

Choose a reason for hiding this comment

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

lgtm

@robbavey
Copy link
Contributor

@ctbarrett Thank you for your contribution! This PR will be merged and published shortly

@robbavey robbavey closed this May 29, 2018
@robbavey robbavey reopened this May 29, 2018
@elasticsearch-bot
Copy link

Rob Bavey merged this into the following branches!

Branch Commits
master ad0c6b1

@ctbarrett ctbarrett deleted the patch-1 branch May 29, 2018 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants