Project

General

Profile

Actions

Bug #12004

closed

API: cannot query environments by name

Added by Elodie B almost 9 years ago. Updated about 6 years ago.

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

Description

I upgraded from 1.8 series to 1.9.2 yesterday. With 1.8 I was able to get environments informations with the API by doing a GET with environment name, for example with curl:
curl -k -u user:secret -H "Accept: version=2,application/json" -H "Content-Type: application/json" https://foreman.mydomain/api/environments/production

Since the upgrade, I am only able to query environment with id:
curl -k -u user:secret -H "Content-Type: application/json" https://foreman.mydomain/api/environments/production
return "message": "Resource environment not found by id 'production'"

I sent an email to users mailing-list and Dominic told me to open an issue and it might be linked to #11037

Thank you


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #11037: Puppet class importer crashes with ruby stack trace trying to import an environment named: newClosedShlomi Zadok07/07/2015Actions
Actions #1

Updated by Dominic Cleal almost 9 years ago

  • Related to Bug #11037: Puppet class importer crashes with ruby stack trace trying to import an environment named: new added
Actions #2

Updated by Dominic Cleal almost 9 years ago

  • Category set to API
  • Translation missing: en.field_release set to 91
Actions #3

Updated by The Foreman Bot almost 9 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2800 added
  • Pull request deleted ()
Actions #4

Updated by Shlomi Zadok almost 9 years ago

  • Assignee set to Shlomi Zadok
Actions #5

Updated by Shlomi Zadok almost 9 years ago

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

Also available in: Atom PDF