8/17/2012 10:28:17 AM
Anyone have good deployment practices they'd like to share?
Alternatively, anyone have horror stories of bad deployment ideas that burned them that I should avoid?
One concept I'd like to bat around is deploying SS initially with limited functionality (no auto-password changing, discovery, expiry, etc.).
I'd like it initially to be basically a password wallet.
I'd like to then, at a later date, slowly unroll features to my users such as discovering dependencies and doing auto password management.
Will I be painting myself into a corner or wishing I would've done things differently once I get to the point of rolling out these features?
I just don't want to start down one road, have a ton of secrets put into the server and then go to enable some functionality only to find I have to "touch" each previously stored secret to enable something or other, etc.
Does that make sense?
Feel free to share any deployment plans that you might have!