Project

General

Profile

Actions

Feature #2969

closed

remove all legacy api code in UI controllers

Added by Joseph Magen almost 11 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
API
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

User must now use /api/ on json calls that are routed to the API controllers, rather than the UI controllers responding with json


Related issues 2 (0 open2 closed)

Related to Foreman - Feature #2985: Remove as_json methods from AR models ClosedJoseph Magen08/29/2013Actions
Related to Foreman - Bug #3089: Updating settings causes settings page to load again within the pageClosedJoseph Magen09/14/2013Actions
Actions #1

Updated by Joseph Magen over 10 years ago

  • Status changed from Assigned to Ready For Testing
Actions #2

Updated by Dominic Cleal over 10 years ago

  • Category set to Rails
  • Target version set to 1.3.0
Actions #3

Updated by Dominic Cleal over 10 years ago

  • Category changed from Rails to API

As announced in the 1.2 release notes:

Pre-1.1 API (non-/api) is deprecated

The older API is now deprecated and users should migrate to the versioned API at /api, available since Foreman 1.1. If you use paths such as /hosts rather than /api/hosts then you are using the pre-1.1 API and should change your program to use the new one.

http://theforeman.org/manuals/1.2/index.html#Upgradenotes

An HTTP 400 response will result with a message instructing the user to use the /api prefix instead.

Actions #4

Updated by Dominic Cleal over 10 years ago

  • Related to Feature #2985: Remove as_json methods from AR models added
Actions #5

Updated by Joseph Magen over 10 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #6

Updated by Dominic Cleal over 10 years ago

  • Related to Bug #3089: Updating settings causes settings page to load again within the page added
Actions

Also available in: Atom PDF