An interesting discussion point that came up on IRC with Ante, is that we might want to support:
juju-private-address
As the official name of the values that we will put in "unit-get private-address". That should end up with a similar property because of how default-inheritance works. (If you set a default binding, that implicitly sets all named bindings.)
That would let you do:
juju deploy app --bind foo,juju-private-address=bar
So all other bindings default to foo, but the specific not-otherwise-namespaced-to-a-binding would get you bar.
The particular use case is because nagios talks to nova-compute only via the 'juju-info' relation. Which doesn't otherwise have a binding associated with it. (we could potentially use juju-info as the binding name as well.)
An interesting discussion point that came up on IRC with Ante, is that we might want to support: address
juju-private-
As the official name of the values that we will put in "unit-get private-address". That should end up with a similar property because of how default-inheritance works. (If you set a default binding, that implicitly sets all named bindings.)
That would let you do: private- address= bar
juju deploy app --bind foo,juju-
So all other bindings default to foo, but the specific not-otherwise- namespaced- to-a-binding would get you bar.
The particular use case is because nagios talks to nova-compute only via the 'juju-info' relation. Which doesn't otherwise have a binding associated with it. (we could potentially use juju-info as the binding name as well.)