This change adds config options so that operators can choose the default
transports for server software_config_transport and deployment
signal_transport. With properly set config values, templates should
have no need for setting these options at all, making templates more
portable across clouds.
The defaults currently are the cfn transports but consideration could be
made in the future to switch to swift.
Downstream deployment tools (puppet etc) would have enough information
to set the best heat.conf values, with something like the following
logic:
- if there is an object-store endpoint, set for *TEMP_URL*
- if there is no cloudformation endpoint, set for *HEAT*
- else set for *CFN*
Change-Id: I5f3d41db35e380486051cee432a7190b3c51fa00
Related-Blueprint: software-config-swift-signal
9fa9a101ca