-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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(operator): Improve API documentation for schema version #13122
Conversation
// EffectiveDate contains a date in YYYY-MM-DD format which is interpreted in the UTC time zone. | ||
// | ||
// The configuration always needs at least one schema that is currently valid. This means that when creating a new | ||
// LokiStack it is recommended to add a schema with the latest available version and an effective date of "yesterday". |
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.
@xperimental perhaps instead of
LokiStack it is recommended to add a schema with the latest available version and an effective date of "yesterday".
by
LokiStack it is recommended to add a schema with the latest available version and it should have an effective date of "yesterday".
?
For being clear that the "recommended" is only for the schema version, but for the effective date, it should/must from yesterday for new installations
What this PR does / why we need it:
This PR aims to improve the explanation of the schema version fields.
Which issue(s) this PR fixes:
Fixes LOG-5549
Checklist
CONTRIBUTING.md
guide (required)