It should be possible to line break CEL validation expressions

[alvaroaleman]

We have CEL expressions that are more than 700 characters long and completely unreadable due to the fact that they have to be defined as one single long line. We should find a way to allow defining them over multiple lines.

[sbueringer]

Sounds good. I guess programming in markers has its limits :) (at least today)

[JoelSpeed]

Is it possible to share one of the long expressions?

We have had issues in the past where folks have tried to write supremely long expressions, but always managed to break the expressions down into smaller chunks and create a set of rules, rather than one rule to rule them all. I'd be tempted to say that you can probably achieve something similar but, without seeing an expression it's hard to say

[tomasaschan]

Can't you just use the built-in YAML support for various ways to write multiline strings? yaml-multiline.info is my go-to reference for this, and that tells me you can do this:

validationExpression: >-
  here you can put whatever
  with newlines and whitespace as you like
  and newlines will be replaced by spaces
  when compliant parsers interpret this document
  thanks to the >- at the head

[sbueringer]

The problem is not how to do it manually in CRD YAMLs. The problem is about how to do this in a marker on a Go field.

[tomasaschan]

Ah, sorry, I misread the question then!

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[sbueringer]

/remove-lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale