docs: fix over-indented yaml configuration of access logs #9930
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
ldez
changed the title
ldez
added
area/documentation
kind/bug/fix
ldez
force-pushed
the
access-logs-yaml-indent-fix
branch
from
25d0166
to
c0ade29
Compare
ldez
added
status/2-needs-review
bot/light-review
ldez
force-pushed
the
access-logs-yaml-indent-fix
branch
from
c0ade29
to
0835db9
Compare
ldez
approved these changes
Jun 4, 2023
traefiker
removed
status/3-needs-merge
bot/light-review
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.
What does this PR do?
The nested yaml is indented by 4 spaces instead of the standard 2 spaces
Motivation
More
Additional Notes