Don't include annotations: key when there are no annotations
#163
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.
A customer reported lint warnings in the output yaml from kube yaml plugin for IntellilJ because
annotation:keys were set with no value.This PR updates the chart to not emit the annotations key if no values are going to be set.
I am not sure how to enforce this in unit tests.
helm unittestseems to only be capable of checking values, not the existence of keys, so tests can't tell the difference between theannotations:key not being present or simply empty.Alternatively, we could just require that every entity has a description annotation.
Checklist
Test plan
Ran
helm template ./charts/sourcegraphand ensured allannotations:keys had values.