irule development - fixed variables within iRule context
looking for some input how others are handling such a situation. with irule development you are often working with at least two irules in a certain environment (single bigip). of course multiple environments (dev, test, prod) is better but not always possible. so i have: irule (attached to most virtual servers) irule-new (attached to a single "test" virtual server) what i like is to have irule code which can be copied without any changes from irule-new to irule as the method "to put it into production". this of course causes issues when you have differences between the old and new environment surrounding the bigip. for example a new header, are different URI, .... another thing are "fixed" variables you use per irule, a debug level, a path, a pool. so variables you want to set once and then use through the whole irule. you can use static variables but these have a bigip wide effect, so that cant be used to have difference on iRule level. different static variables for the current and new irule are possible, but that means changing the irule code when moving to another irule. datagroups are an option, but those are also bigip wide. in some cases i use datagroups with a variable per host, but that doesnt scale very well. so how do you keep your variables within a single iRule context?