Issue #2: update taskotron-proxy playbook to work with execdb - execdb

taskotron / execdb

#2 update taskotron-proxy playbook to work with execdb

Closed: Fixed Opened Mar 30, 2015 by tflink.

Since the machine hosting execdb in dev isn't public, it's frontend needs to be proxied through taskotron-dev01. In the infra ansible repo, this is handled by the taskotron/taskotron-proxy role.

Update the taskotron/taskotron-proxy role so that it works with the execdb frontend

somebody commented Mar 30, 2015

This ticket is a duplicate of https://pagure.io/taskotron/issue/96

somebody commented Mar 30, 2015

This ticket is a duplicate of https://pagure.io/taskotron/execdb/issue/2

mkrizek commented Jul 29, 2015

@tflink, hasn't this been done?

jskladan commented Nov 3, 2015

Seems to be fixed, as far as I can tell.

Metadata Update from @tflink:
- Issue tagged with: infrastructure

Aug 4, 2017

Metadata

Assignee

None

Tags

Blocking

None

Depending on

None

Priority

Low

taskotron / execdb

#2 update taskotron-proxy playbook to work with execdb Closed: Fixed Opened Mar 30, 2015 by tflink.

Metadata

infrastructure

#2 update taskotron-proxy playbook to work with execdb

Closed: Fixed Opened Mar 30, 2015 by tflink.