Project

General

Profile

Actions
Copy link

Bug #3965

closed

chefproxy smart-proxy's feature should map same API as Foreman

Added by Romain Vrignaud almost 11 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Romain Vrignaud
Category:
Smart Proxy
Target version:
1.4.0
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

We should move /reports and /facts to /api/reports and /api/hosts/facts API on smart-proxy in order to be transparent on the client side

Actions
Copy link
 #1

Updated by Marek Hulán almost 11 years ago

Would it make sense to keep both variants instead of moving?

Actions
Copy link
 #2

Updated by Dominic Cleal almost 11 years ago

  • Status changed from New to Ready For Testing
  • Target version set to 1.9.2
  • Translation missing: en.field_release set to 2
Actions
Copy link
 #3

Updated by Romain Vrignaud almost 11 years ago

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

Also available in: Atom PDF