It appears to me that the consistent answer is to have (1) environment
variables which are (2) consumed in the Vagrantfile and passed via
configuration parameters to vagrant (or a relevant plugin). e.g.
if ENV.has_key?('SUB_USERNAME') && ENV.has_key?('SUB_PASSWORD')
config.registration.username = ENV['SUB_USERNAME']
config.registration.password = ENV['SUB_PASSWORD']
end
So my vote is that we continue to same pattern.
On Tue, Aug 9, 2016 at 9:05 AM, Lalatendu Mohanty <[email protected]>
wrote:
> + container-tools
>
>
> On 08/09/2016 05:53 PM, Lalatendu Mohanty wrote:
>
>> Hi,
>>
>> We are trying to understand the user experience around using a proxy
>> server with ADB/CDK. Here are the choices we have.
>>
>> 1. Export all proxy variables i.e. proxy server, proxy user/password to
>> environment and then the subsequent "vagrant up" will pick the information
>> and does the required configuration.
>>
>> 2. Add some proxy information in the Vagrantfile. Whenever user wants to
>> ad the proxy information, he has to edit the Vagrantfile.
>>
>> IMO #1 looks fine to me. But not sure about it.
>>
>> Let us know what you think.
>>
>> Thanks,
>>
>> Lala
>>
>
>
> _______________________________________________
> Devtools mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/devtools
>
_______________________________________________
Container-tools mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/container-tools
