Project

General

Profile

Feature #12216

allow compute resource connections to use a proxy

Added by Ohad Levy over 7 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Justin Sherrill
Category:
Compute resources
Target version:
1.17.0
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman/pull/4616
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

as a user, I would like to use a proxy to connect to external api services (such as aws).

this might be a tracker bug if each compute resource implementation would be different.

Related issues

Related to Foreman - Feature #20201: Global HTTP proxy for outgoing requestsClosed
Related to Foreman - Bug #21328: Incorrect link from welcome page - http proxiesClosed2017-10-15
Related to Foreman - Bug #21330: http proxy test connection should clear toasts when clicking on it multiple timesClosed2017-10-16
Related to Foreman - Bug #21331: http proxy name is not defined as requierd Closed2017-10-16
Related to Foreman - Bug #21332: http proxy form does not open in two-paneClosed2017-10-16
Related to Foreman - Bug #21333: http_proxy js does not exists, yet its added to the compilation listClosed2017-10-16
Related to Foreman - Bug #21334: EC2 http proxy must use HTTPSNew2017-10-16
Related to Foreman - Bug #22067: after creating the first proxy, you are being redirected to the new proxy page againNew2017-12-24
Related to Foreman - Bug #22066: http test connection works even if the proxy is not setNew2017-12-24

Associated revisions

Revision e6b0f4fa (diff)
Added by Justin Sherrill over 5 years ago

Fixes #12216 - support http proxies for compute resources

History

#1 Updated by The Foreman Bot almost 6 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Justin Sherrill
  • Pull request https://github.com/theforeman/foreman/pull/4616 added

#2 Updated by Timo Goebel over 5 years ago

  • Legacy Backlogs Release (now unused) set to 296

#3 Updated by Marek Hulán over 5 years ago

  • Related to Feature #20201: Global HTTP proxy for outgoing requests added

#4 Updated by Justin Sherrill over 5 years ago

  • % Done changed from 0 to 100
  • Status changed from Ready For Testing to Closed

#5 Updated by Ohad Levy over 5 years ago

  • Related to Bug #21328: Incorrect link from welcome page - http proxies added

#6 Updated by Ohad Levy over 5 years ago

  • Related to Bug #21330: http proxy test connection should clear toasts when clicking on it multiple times added

#7 Updated by Ohad Levy over 5 years ago

  • Related to Bug #21331: http proxy name is not defined as requierd added

#8 Updated by Ohad Levy over 5 years ago

  • Related to Bug #21332: http proxy form does not open in two-pane added

#9 Updated by Ohad Levy over 5 years ago

am i reading this right - only EC2 is currently supported? but via the API you can still update the proxy for other compute resources?

Also.. we should not allow to use HTTP proxies for traffic like EC2 (it should be forced to https proxies).

#10 Updated by Ohad Levy over 5 years ago

  • Related to Bug #21333: http_proxy js does not exists, yet its added to the compilation list added

#11 Updated by Ohad Levy over 5 years ago

  • Related to Bug #21334: EC2 http proxy must use HTTPS added

#12 Updated by Ohad Levy over 5 years ago

  • Related to Bug #21340: multiple settings lookup for http proxy for every UI action added

#13 Updated by Timo Goebel over 5 years ago

  • Related to deleted (Bug #21340: multiple settings lookup for http proxy for every UI action)

#14 Updated by Ohad Levy over 5 years ago

  • Related to Bug #22067: after creating the first proxy, you are being redirected to the new proxy page again added

#15 Updated by Ohad Levy over 5 years ago

  • Related to Bug #22066: http test connection works even if the proxy is not set added

Also available in: Atom PDF