I'm not sure that we have a use case for the server, but as an aside, we do
have
a use case on the agent side, if that is ever a concern:
We use the ability to set environment variables when doing OpenStack upgrades.
OpenStack has the concept of public (publicURL) and private (internalURL)
Thanks for the responses on this thread so far and some of the
corresponding discussion that has been spawned in the related JIRA ticket
- https://tickets.puppetlabs.com/browse/SERVER-297.
On Tuesday, April 14, 2015 at 9:09:40 AM UTC-7, Nan Liu wrote:
>
> On Tuesday, April 14, 2015 at 4:35:29 AM
On Tuesday, April 14, 2015 at 4:35:29 AM UTC-7, Ken Barber wrote:
>
> > While we are leaning toward a config-file driven approach, we would be
> > interested in hearing of any specific use cases you may know of where
> this
> > may be insufficient. We would specifically be interested in any use
> While we are leaning toward a config-file driven approach, we would be
> interested in hearing of any specific use cases you may know of where this
> may be insufficient. We would specifically be interested in any use cases
> which suggest that some affordance in the design should be made to all
