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

Docs: Fix wrong and missing common configuration section descriptions #5119

Closed
DylanGuedes opened this issue Jan 12, 2022 · 2 comments
Closed
Labels
stale A stale issue or PR that will automatically be closed.

Comments

@DylanGuedes
Copy link
Contributor

DylanGuedes commented Jan 12, 2022

Describe the bug
Bug 1: path_prefix configuration from the common section is wrongly describing it as When defined, the given prefix will be present in front of the endpoint paths., when it is used to compose file paths to read/write from.
Bug 2: Both, chunks_directory and rules_directory (also from the common section) aren't documented

To Reproduce
N/A

Expected behavior
N/A

Environment:
N/A

Screenshots, Promtail config, or terminal output
N/A

@stale
Copy link

stale bot commented Mar 2, 2022

Hi! This issue has been automatically marked as stale because it has not had any
activity in the past 30 days.

We use a stalebot among other tools to help manage the state of issues in this project.
A stalebot can be very useful in closing issues in a number of cases; the most common
is closing issues or PRs where the original reporter has not responded.

Stalebots are also emotionless and cruel and can close issues which are still very relevant.

If this issue is important to you, please add a comment to keep it open. More importantly, please add a thumbs-up to the original issue entry.

We regularly sort for closed issues which have a stale label sorted by thumbs up.

We may also:

  • Mark issues as revivable if we think it's a valid issue but isn't something we are likely
    to prioritize in the future (the issue will still remain closed).
  • Add a keepalive label to silence the stalebot if the issue is very common/popular/important.

We are doing our best to respond, organize, and prioritize all issues but it can be a challenging task,
our sincere apologies if you find yourself at the mercy of the stalebot.

@stale stale bot added the stale A stale issue or PR that will automatically be closed. label Mar 2, 2022
@stale stale bot closed this as completed Apr 18, 2022
@darxriggs
Copy link
Contributor

This should not be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale A stale issue or PR that will automatically be closed.
Projects
None yet
Development

No branches or pull requests

2 participants