write mem?

I agree with you that customer make the majority of changes to the bigip_base.conf upon 1st setup so I can see that it is logical to segment the changes into 2 methods to protect the customers that don't want to accidentally change anything. I think the best option is not to combine the 2 methods into one but to simply add a 3rd method in for customers that want to write all changes at once while retaining the 2 ones you already have.

 

 

The 3rd option (b save all type of a thing) is good so that when you issue a certain command so that you can be certain that any change you just made gets written to the BIGIP's disk regardless of which file it's in. This is especially helpful because there are always cases where some BIGIP operators know BIGIP better than others, and so it's easy to get an inexperienced person who doesn't know what F5 stores in 1 file vs. the other. This also sort of holds true in that most devs at big corporations writing code for BIGIP may not know all of the ins & outs of which files store which info so giving them a an easy 1 line method that does it all may not hurt.

 

 

Just my 2 cents for what it's worth. Thanks again.