[loki helm chart] Validation requires schemaConfig to be specified even if loki config is managed outside the chart

[asherf]

Describe the bug
When using the option to set loki.configObjectName (and loki.generatedConfigObjectName) in order to manage the loki config from outside the loki chart (by creating a configmap and passing its name to the chart)
the validation here still requires the schemaConfig to be set, even though in this use case, it won't be actually used.

Expected behavior
If a loki.generatedConfigObjectName is empty (i.e. the loki chart does't create a loki configmap object) this validation should be short circuited.

Environment:

• Infrastructure: Kubernetes
• Deployment tool: simply scalable

Screenshots, Promtail config, or terminal output
╷
│ Error: execution error at (loki/templates/validate.yaml:40:4): You must provide a schema_config for Loki, one is not provided as this will be individual for every Loki cluster. See https://grafana.com/docs/loki/latest/operations/storage/schema/ for schema information. For quick testing (with no persistence) add --set loki.useTestSchema=true
│
│

[malekerramli]

im having the same exact issue using terraform