-
Notifications
You must be signed in to change notification settings - Fork 1.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
Add config spec #6908
Add config spec #6908
Conversation
Codecov Report
|
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.
Nice. Not the easiest config spec to translate :)
Left few comments.
# extra_performance_metrics: true | ||
|
||
## Log Section (Available for Agent >=6.0) | ||
options: |
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.
(nit) Shall we keep that commented by default ? I guess doesn't change much to have an empty dict either.
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.
Yes I agree, but ddev
doesn't seem to support it for now. I agree an empty options
dict by default shouldn't be a problem since we do
options = instance.get('options', {}) or {} # options could be None if empty in the YAML
I can look at how to add commented-out-by-default sections to ddev
, but looks like it's not a blocker to get this PR merged.
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.
Yes, not a blocker for this PR.
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.
@hithwen @AlexandreYang Thanks, I think I addressed all your comments.
4b9d2ae
to
c921e7b
Compare
# # Columns without a name are ignored. Add additional columns to skip: | ||
# # - {} |
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.
Not sure I understood this comment: is it that eg if the query returns 3 columns, we can do - {}
on the first one and define the 2 others to only submit metrics for the last 2 columns? Not sure this is correct, since if the user wants to "skip columns" then they can just omit them in the SELECT
clause 🤔 So I removed it for now.
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.
@ofek added this feature recently so he must remember what he meant
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
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.
Service in the logs section is not recommended anymore
Can you bump checks base on the setup to 11.0.0? (to include service features) |
What does this PR do?
Add config spec for MySQL
Motivation
Config specs everywhere! Also I might need to add a
charset
option for a support case, so having the config spec done beforehand would be nice.Additional Notes
Not super happy with optional sections such as
ssl
,custom_queries
orqueries
showing up as un-commented in the generatedconf.yaml.example
- but we can look at tweaking ddev later.Review checklist (to be filled by reviewers)
changelog/
andintegration/
labels attached