Our foreman 1.2.0 has been upgraded twice. (1.0 => 1.1 => 1.2)
After some further testing I see that a fresh foreman 1.2 install does have the id and other fields if I ad a new parameter.

"host": {
    "owner_type": "User",
    "medium_id": 1,
    "owner_id": 1,
    "compute_resource_id": null,
    "puppet_proxy_id": null,
    "image_id": null,
    "architecture_id": 1,
    "host_parameters": [
    {
        "host_parameter": {
          "reference_id": 1,
          "priority": 4,
          "created_at": "2013-08-29T18:04:55Z",
          "value": "test",
          "updated_at": "2013-08-29T18:04:55Z",
          "name": "test",
          "id": 1
        }
      }
    ],

@Dominic, ok thanks ill try that with the v2 api.

Above result is from the v1 api.

Oeps, Sorry

It seems the difference is caused by using /api or not in the url when using/calling the api

curl -H "Content-Type:application/json" -s -H "Accept:application/json" -k -u admin:changeme https://foreman/api/hosts/cjiblx3211 | prettify_json.rb

"host_parameter": {
          "value": "o999",
          "name": "c_omgeving" 
        }

curl -H "Content-Type:application/json" -s -H "Accept:application/json" -k -u admin:changeme https://foreman/hosts/cjiblx3211 | prettify_json.rb

"host_parameter": {
          "value": "o999",
          "name": "c_omgeving",
          "id": 399,
          "updated_at": "2013-02-22T10:01:15Z",
          "reference_id": 132,
          "created_at": "2013-02-22T10:01:15Z",
          "priority": 4
        }

Probably not a bug then. I assume it can be closed?

Did some more testing:

The issue is not only the /api. Included Parameters via inheritance (or because of foreman 1.0 => 1.1 => 1.2 upgrade?) don't have the id and the other missing values.

As soon as I override an inherited parameter it will become an global host parameter and will then have the missing fields.

After some more testing I think this one really can be closed.

Sorry mixed the numbers arround (with /api should be 60 en without api should be 105.)

The reason for the difference in results count is that /api/ uses pagination and without /api/ does not. If you page ?per_page=100000 in the URL, then it will show all the results in one call.

Joseph,

Ok thanks,

I'll merge both pulls to my test environment and will test them then.

Afterwards I will update this ticket with the results.

Joseph

Tested pull 863 on Foreman 1.2.1. There where still some parameters/values missing but probably for an reason.

To be sure the list of missing or extra parameters/values is shown bellow:

1. no api (in no api but not in with api):

"host_id":1 # (under "interfaces")
"location_id":null
"organization_id":null

"last_compile":"2013-09-03T15:01:39Z"
"last_freshcheck":null
"serial":null
"source_file_id":null
"puppet_status":100663296

"root_pass":"xybxa6JUkz63w" # (Security reasons?)

1. with api: (in with api but not in no api): # (The following is New/Extra so shouldn't be an issue)

1. New/Extra
   "interface": # (interface detail now listed under interface: instead interfaces:)
   "sp_ip":"192.168.88.50"
   "sp_mac":"00:00:00:00:00:01"
   "sp_name":"bmc1"
   "sp_subnet_id":1
   "type":"Nic::BMC" or "type":"Nic::Managed"

1. Listed twice (For obvious reasons, explained by you to domcleal (comment: didn't remove :attrs for the same reason above not to break any current API v1 consumers that we use :attrs.))
   "username":"a"
   "password":"b"
   "provider":"IPMI"

I hope the differences are not caused by the per_page option, but the following commands with different per_page values had the same result. So I might be doing something wrong.

curl -H "Content-Type:application/json" -s -H "Accept:application/json" -k -u admin:changeme https://foreman/api/hosts/foreman.localdomain?per_page=50 | prettify_json.rb | wc -l
97

curl -H "Content-Type:application/json" -s -H "Accept:application/json" -k -u admin:changeme https://foreman/api/hosts/foreman.localdomain?per_page=10000 | prettify_json.rb | wc -l
97

For facts api/hosts/:id/facts the per_page option does work, but appears to do nothing with api/hosts/:id

Ronny,

I updated the pull request per your comments. Thanks. I included all your comments except adding "host_id":1 # (under "interfaces") since it's redundant as the api call is on hosts/1

As you found out, the :per_page attribute only works on a collection of objects (ex. /facts, /hosts, etc). It does not work on a single object (ex. hosts/:id)

Is this going into the 1.3?

Lukas Zapletal wrote:

Is this going into the 1.3?

It's already in.