Feature Requests

With the announcement of: https://circleci.com/docs/ip-ranges-list.json I'd like to request that you include all your IP Ranges in this json blob, this way we do not have to hardcode all these whitelisted IPs via a variable for your AWS Builder nodes as you see in the attached picture, which we sourced from: https://circleci.com/docs/ip-ranges/ 3.228.39.90 18.213.67.41 34.194.94.201 34.194.144.202 34.197.6.234 35.169.17.173 35.174.253.146 52.3.128.216 52.4.195.249 52.5.58.121 52.21.153.129 52.72.72.233 54.92.235.88 54.161.182.76 54.164.161.41 54.166.105.113 54.167.72.230 54.172.26.132 54.205.138.102 54.208.72.234 54.209.115.53

The IP ranges ( https://circleci.com/docs/2.0/ip-ranges/ ) feature currently only supports the Docker executor. This request represents adding support for similar functionality on jobs that use the Machine executor.

In some cases, you may have a firewall that blocks non-standard ports. In this case, it is difficult to utilize the SSH rerun feature as the IP is always changing. It would be great to have access to an IP range specifically set aside for the SSH rerun feature to allow for a more fine grain control in a given firewall.

Exclusive access to an IP address for outgoing traffic during job execution on CircleCI Cloud. Similar to existing IP ranges ( https://circleci.com/docs/2.0/ip-ranges/ ) functionality, but instead of sharing traffic on IP addresses with other CircleCI customers, traffic is exclusive to one organization paying for the IP address(es).

The IP ranges ( https://circleci.com/docs/2.0/ip-ranges/ ) feature currently only supports the Docker executor. This request represents adding support for similar functionality on jobs that use the Windows executor.