Skip to content
This repository has been archived by the owner on Jul 23, 2020. It is now read-only.

Migrate Deployments API to use proxy instead of accessing OpenShift directly. #2096

Closed
stooke opened this issue Jan 29, 2018 · 3 comments · Fixed by fabric8-ui/fabric8-ui#3469
Closed

Migrate Deployments API to use proxy instead of accessing OpenShift directly. #2096

stooke opened this issue Jan 29, 2018 · 3 comments · Fixed by fabric8-ui/fabric8-ui#3469
Assignees
@stooke
Labels
area/deployments team/platform type/task
Milestone
Platform Backlog

Comments

@stooke
Copy link
Collaborator

stooke commented Jan 29, 2018 •
edited
Loading

To support multicluster, etc, the Deployments API (in WIT) must be migrated to the OSIO proxy wherever it tries to access OpenShift clusters.

Part of user story #2632
@joshuawilson joshuawilson added this to the Platform Backlog milestone Jan 29, 2018
@alexeykazakov alexeykazakov mentioned this issue Jan 29, 2018
Open
@stooke
Copy link
Collaborator Author

stooke commented Feb 22, 2018 •
edited
Loading

When #2342 (Add Metrics, Console, Logs API support to OSO Proxy service) is complete, a second PR will be created to enable WIT to use Proxy for those remaining URLs.

@stooke stooke mentioned this issue Feb 23, 2018
Closed
@joshuawilson joshuawilson modified the milestones: Sprint 145, Sprint 146 Mar 6, 2018
@stooke stooke mentioned this issue Mar 15, 2018
Closed
2 tasks
@joshuawilson joshuawilson modified the milestones: Sprint 146, Sprint 147 Mar 27, 2018
@stooke stooke mentioned this issue Sep 13, 2018
Open
@stooke
Copy link
Collaborator Author

stooke commented Sep 14, 2018

A second WIT PR has been added for proxy support

#2284 migrate WIT to use proxy for all deployments API requests
fabric8-services/fabric8-wit#2284

@joshuawilson
Copy link
Member

@alexeykazakov what do you want to do about this?

@joshuawilson joshuawilson mentioned this issue Jan 2, 2019
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@stooke stooke

Labels
area/deployments team/platform type/task
Projects
None yet
Milestone
Platform Backlog
2 participants
@joshuawilson @stooke