chucknorris/roundhouse — Issue #46: Custom configuration option
Author: wimjans
Created: 2012-01-16 11:38:03+00:00
State: open

Would it be possible to allow custom configuration options, which than can be used by the token replacer.

We have a requirement where Oracle tables and indexes should be created in custom tablespace, but at the moment I have to hardcode them inside the script.
As we want to do installation to multiple customers, all with different naming conventions, we want to parameterize these inside the scripts:

eg: create table test(n number) tablespace {{tabts}}
;

Where tabts is a custom configuration option. The same goes for index tablespaces.

I can cheat a little bit, for example, I use the indexFolderName and specify the index tablespace name to be used.
This means I need to create multiple install scripts, where files will be put in an unknown directory (depends on the name of the tablespace.

Also, sometimes I want to use more than 1 index tablespace name (for partitioned indexes for example).

Currently I do not see a way to work around this, apart from hardcoding the tablespace names