Allow default property definitions in the spec to reference other property values.

[eddiemoya]

Feature Description

Problem Statement:
When creating a spec I would like to use other properties to define default values for other properties. This is currently not possible.

Proposed Solution:

substringA: string | default="hello"
substringB: string | default="world"
combined: string | default="${schema.spec.substringA} ${schema.spec.substringB}"

• Please vote on this issue by adding a 👍 reaction to the original issue
• If you are interested in working on this feature, please leave a comment

[ellistarn]

We've explored the idea of variables like:

spec:
  schema:
    ...
    spec:
      substringA: string | default="hello"
      substringB: string | default="world"
      combined: string | default = ""
  resources:
    - id: foo
      variable: "${schema.spec.substringA} ${schema.spec.substringB}"
    - id: bar
      template:
        apiVersion: apps/v1
        kind: Deployment
        metadata:
          name: ${ schema.combined == "" ? foo : schema.combined}
           ...

[eddiemoya]

name: ${ schema.combined == "" ? foo : schema.combined}

Seems like this would allow us to combine strings while still allowing the instance to override the combined value. This would be great!

Would the logic here also be used in the variable itself?
variable: ${schema.combined == "" ? "${schema.spec.substringA} ${schema.spec.substringB}" : schema.combined}

I'm not sure that syntax makes any sense, but I think it gets my question across.

[ellistarn]

Oh yeah -- the default can be simplified into the variable itself. Logic is slightly wrong, but concept is right.