Thanks for posting your sample code. Much clearer now!
In fact, it spookily reminded me of a node I wrote a while back: Data-driven Programming: fun with Perl, JSON, YAML, XML...
As you can see from that node, I faced a similar problem to what you are asking about.
Generally, I'm a fan of defining a table of properties, as you have done, because it helps to separate the code from the data. After asking my question, I ended up leaving the script alone with its table of properties hard-wired in the script. It was very flexible that way and proved to be easy to maintain over many years. Having the build script itself under version control was essential, of course, to allow us to examine changes to our automated builds over time.
Update: see also: Data Structure References
In reply to Re^3: A good way to input data into a script w/o an SQL database
by eyepopslikeamosquito
in thread A good way to input data into a script w/o an SQL database
by ObiPanda
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |