POST endpoint json request body uses field name id. PUT endpoint uses appId in the path and allows for field name id in the request body. For the PUT the id in the request body is ignored.
This appears to cause a problem with tapipy. Possibly because tapipy is creating a single dictionary from path parameters and fields in the request body.
Nathan Freeman and Tyler Clemens discovered this while implementing a CLI using tapipy. They found they needed to use id in the json for the tapipy createApp call and appId for the json in the tapipy putApp call.
Possibly the issue lies in the CLI implementation.
NOTE: This probably applies to Systems as well.
POST endpoint json request body uses field name id. PUT endpoint uses appId in the path and allows for field name id in the request body. For the PUT the id in the request body is ignored. This appears to cause a problem with tapipy. Possibly because tapipy is creating a single dictionary from path parameters and fields in the request body. Nathan Freeman and Tyler Clemens discovered this while implementing a CLI using tapipy. They found they needed to use id in the json for the tapipy createApp call and appId for the json in the tapipy putApp call. Possibly the issue lies in the CLI implementation. NOTE: This probably applies to Systems as well.
NOTE: Fixed by Tyler in CLI code