Bug #35540: smart_proxy_dynflow does not construct callaback url properly if the launcher-based api is used - foreman-tasks - Foreman

Actions

Bug #35540

closed

smart_proxy_dynflow does not construct callaback url properly if the launcher-based api is used

Added by Adam Ruzicka over 1 year ago. Updated over 1 year ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Proxy plugin

Target version:

-

Difficulty:

Triaged:

No

Bugzilla link:

Pull request:

https://github.com/theforeman/smart_proxy_dynflow/pull/114

Fixed in Releases:

smart_proxy_dynflow-0.8.2

Found in Releases:

Red Hat JIRA:

Actions

#1

Updated by The Foreman Bot over 1 year ago

Status changed from New to Ready For Testing
Pull request https://github.com/theforeman/smart_proxy_dynflow/pull/114 added

Actions

#2

Updated by The Foreman Bot over 1 year ago

Fixed in Releases smart_proxy_dynflow-0.8.2 added

Actions

#3

Updated by Adam Ruzicka over 1 year ago

Status changed from Ready For Testing to Closed

Applied in changeset foreman_proxy_dynflow|4c8e9f913743cc22291b1c8bfc96efc1c28883c4.

Actions

Also available in: Atom PDF