Project

General

Profile

Refactor #13328

Move proxy status (AJAX) actions to API

Added by Lukas Zapletal over 4 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Smart Proxy
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Since all of our proxy status is AJAX only, we should not be building another API and we should refactor it into V2 API. There is no point in maintaining two separate codes for same actions.


Related issues

Related to Foreman - Tracker #12507: Smart Proxy UX improvmentsNew2015-11-17

History

#1 Updated by Lukas Zapletal over 4 years ago

#2 Updated by Lukas Zapletal over 4 years ago

Just for the record, it looks like Puppet / PuppetCA is not AJAX. But we should move what we can regardless.

#3 Updated by Dominic Cleal over 4 years ago

We usually maintain both as they tend to have different characteristics. Any UI feature should be added with a corresponding API - different routes, controllers and actions, but a common implementation.

#4 Updated by Lukas Zapletal over 4 years ago

  • Status changed from New to Resolved

Yeah I figured out, not much experienced with AJAX, but now I understand it contains whole blocks vs clean data.

Also available in: Atom PDF