Working with different environments, load files specific to environment about configuration-as-code-plugin HOT 3 CLOSED

Yes indeed it supports multiple via a comma separated list.

Documented in the README as well as in code:

from configuration-as-code-plugin.

I don't think this makes a lot of sense.

Simply have two different configs if you want to treat your environments differently. Asking for complexity for complexity's sake makes no sense.

Have you tried to see how far you can get with variable substitution support that already exist?

from configuration-as-code-plugin.

@jetersen
I can do with variable substitution 90% of the things.

Yes, I can load different configs.
The thing is that I have configs splited to a lot files, and I was loading them by just defining just single folder with CASC_JENKINS_CONFIG

And now, since I can't load all files (some of them are env specific) I need to specify huge comma separated list of files in this variable. I think it would be much more readable as I described above.
But now I'm thinking, I did not tried to specify list of just two folders (common and ${env}), maybe that could do the thing.

edit:
that worked, thank you for directions, I'm closing this now :)

from configuration-as-code-plugin.