Support for proxy about rvm1-ansible HOT 9 CLOSED

are you saying environment is not respected in this role? that would be a bug :)

from rvm1-ansible.

@rngadam What are you proposing, to have the rvm role write out the ~/.curlrc based on the value you provide to the variable or just a rvm1_http_proxy variable which you can set and use in your custom tasks instead of the curlrc?

from rvm1-ansible.

it has been a month without feedback - closing the issue - please let us know if you can provide the requested details and we will reopen

from rvm1-ansible.

Sorry, it's because I worked around it myself. I ended up creating a curlrc.j2 with the following content:

{% if host_proxy %}
proxy = {{host_proxy}}
{% endif %}

...and setting up as appropriate in my group_vars:

host_proxy: http://10.0.2.2:3128/

it seems a bit hacky?

from rvm1-ansible.

what's the status of this issue?

from rvm1-ansible.

Writing out a curlrc like this seems a little out of scope for the role unless I'm missing something? What do you think @mpapis?

from rvm1-ansible.

indeed, it should be up to the admin to set up proxies, a separate role to setup proxies could be an option - still out of scope - closing this.

from rvm1-ansible.

I agree that writing a curlrc is out of scope, but I would argue that proxy support in general is not. The relevant tasks should simply allow passing like an environment like we do for everything else: environment: '{{ proxy_env }}'. How about an rvm1_environment? Because there are various ones to set besides http_proxy including CURL_CA_BUNDLE if your org has their own certificate.

The main argument for this would be 1) users of rvm1 shouldn't have to know specific implementation details, like which tools are used to download, and configure them each specifically via a curlrc, and 2) any other tasks we write ourselves work fine with environment, there's no need to provision a curlrc for anything but rvm1 in our case anyway.

What do you think?

from rvm1-ansible.

@mpapis as far as I understood it, and last I tried, setting environment at the role level is not supported. That is, I cannot do roles: { role: rvm_io.rvm1-ruby, environment: '{{ my_env }}' } Is that wrong or is there another way I can be providing an environment to rvm1?

from rvm1-ansible.