Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
The update request should send all data nested under smart_variable.
To change the puppet class the data sent should be:
{
"smart_variable": {
"puppetclass_id": 1
}
}
Does that work for you?
Comment 4Stanislav Tkachenko
2017-01-12 11:09:22 UTC
Well, it works but looks like update and create methods are not unified.
For example, create sends parameters directly:
> Making HTTP POST request to https://sat6.com/api/v2/smart_variables with ... data {"description": "test1", "variable": "abc", "puppetclass_id": 7}.
> Received HTTP 201 response: {"description":"test1", ..., "puppetclass_id":7, ..., "variable":"abc","id":447,"override_values_count":0,"override_values":[]}
Also other parameters except 'puppet_class_id' can be updated sending directly, e.g. 'description':
> Making HTTP PUT request to https://sat6.com/api/v2/smart_variables/447 with ... and data {"description": "test2"}.
> Received HTTP 200 response: {"description":"test2", ..., "puppetclass_id":7, ...,"variable":"abc","id":447,"override_values_count":0,"override_values":[]}
Though it is also possible to send them nested under smart_variable:
> Making HTTP PUT request to https://sat6.com/api/v2/smart_variables/448 with ... and data {"smart_variable": {"description": "test2"}}.
> Received HTTP 200 response: {"description":"test2", ...}
As for me, either both variants should work correctly (i.e. sending directly and nested) or only one should be available (e.g. sending nested).
Everything should work as nested for smart variables, that is also what is documented.
Some things might be working directly but that is not supported and should not be used.