-
Notifications
You must be signed in to change notification settings - Fork 506
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
Improve values schema #139
Improve values schema #139
Conversation
The amount of changes kinda got away from me. Let me know what you think and if I should go an add actual validations to this PR as well or if I should make it smaller instead. |
What actual validation do you mean? Isn't it enforced already? |
The requirement for having at least one of standaloneCollector or agentCollector enabled is already present. I was going to review and see if there were any other scenarios. There may not be. |
Looking through the only other validation I could come up with was something fancy around standaloneCollector.enabled and podDisruptionBudget/autoscaling, but I think all that matters is that enabled is required by the properties. The actual value of enabled doesn't matter. So I think this PR gets the schema into a good state to validate the current values.yaml. |
I don't think the fancy validations are that important to have. My idea is that we need to define all the properties with |
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.
LGTM
Works towards #135
This PR defines all the properties for opentelemetry-collector's values.schema.yaml. Actual validations to follow.