Project

General

Profile

Actions

Bug #4800

closed

Latest API prefix is not correct

Bug #4800: Latest API prefix is not correct

Added by Vincent MEMBRÉ almost 12 years ago. Updated almost 12 years ago.

Status:
Released
Priority:
2
Category:
API
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

URLs on latest API in 2.9 are waiting for prefix "lastest" instead of "latest"...

This is not happening in 2.10 because of the refactoring on how we create API ...


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #4796: Node API version 4 can only get Node detailsReleasedFrançois ARMANDActions

Updated by Vincent MEMBRÉ almost 12 years ago Actions #1

  • Subject changed from typo in latest API URL only in 2.9 to in 2.9, you cannot access latest API using "latest" prefix (use lastest instead ...)

Updated by Vincent MEMBRÉ almost 12 years ago Actions #2

  • Status changed from New to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/505

Updated by François ARMAND almost 12 years ago Actions #3

Great the doc didn't had the typo, else we would have been in a big mess to support it.

Updated by Vincent MEMBRÉ almost 12 years ago Actions #4

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Updated by Vincent MEMBRÉ almost 12 years ago Actions #6

  • Subject changed from in 2.9, you cannot access latest API using "latest" prefix (use lastest instead ...) to Latest API prefix is not correct

Updated by Vincent MEMBRÉ almost 12 years ago Actions #7

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.9.5 (announcement , changelog) and 2.10.1 (announcement , changelog), which were released today.

Actions

Also available in: PDF Atom