You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 16, 2020. It is now read-only.
tower-cli host modify -n host1 --variables "ansible_python_interpreter=/usr/bin/python26" -v
*** DETAILS: Checking for an existing record. *********************************
GET http://localhost:8013/api/v2/hosts/
Params: {'name': u'host1'}
*** DETAILS: Writing the record. **********************************************
PATCH http://localhost:8013/api/v2/hosts/16/
Data: {'name': u'host1', 'variables': u'ansible_python_interpreter=/usr/bin/python26'}
Error: The Tower server claims it was sent a bad request.
PATCH http://localhost:8013/api/v2/hosts/16/
Params: None
Data: {"name": "host1", "variables": "ansible_python_interpreter=/usr/bin/python26"}
Response: {"variables":["Cannot parse as JSON (error: No JSON object could be decoded) or YAML (error: Input type `str` is not a dictionary)."]}
It actually looks like this is kind of intentional, because the host model uses the Variables type instead of the StructuredInput type, meaning that it passes the variables as they are to the server, and does not accommodate the key=value syntax.
The text was updated successfully, but these errors were encountered:
Bug discovered from mailing list:
It actually looks like this is kind of intentional, because the host model uses the
Variables
type instead of theStructuredInput
type, meaning that it passes the variables as they are to the server, and does not accommodate the key=value syntax.The text was updated successfully, but these errors were encountered: