[Feature] -t mandatory field for .kluctl.yaml

[jcpunk]

Command

• check-image-updates
• delete
• deploy
• diff
• helm-pull
• helm-update
• list-images
• list-targets
• poke-images
• prune
• render
• seal
• validate
• version

Who are you?

Pat Riehecky, Computing Specialist at Fermilab

What do you want to do?

I'd like to provide a useful error when someone runs kluctl deploy on a repository but my discriminator expects that a target will be set.

Why do you need that?

With .kluctl.yaml containing:

discriminator: "example-{{ target.name }}"

Just running kluctl deploy results in invalid kubernetes objects. This is essentially a config issue on my end (example- is not a valid object and I'm running it wrongly).

But having a way to kick out an error to the user saying "select from the list of valid targets" when I know it is required would be handy.

[benedikt-bartscher]

Hi @jcpunk, i just wanted to mention that i am using a similar discriminator and i got the same error. So it is probably a good idea to add some kind of warning.

Maybe we could add an option for a default target to .kluctl.yml and if it's not defined make -t required?

[jcpunk]

I like the idea of having a "default target" but I wonder if that reduces the explicit nature of the current commands.

Right now there is "no hidden magic", folks must be explicit about which target they want.

[codablock]

I'm also for not having a default target. IMHO it's better to have this as explicit as possible. But I'm also open to be convinced otherwise if good use-cases are brought up.