There is URI module present in Ansible which lets you invoke REST End Points and it works preety well.
Currently i have lot of JSON Objects and corresponding REST end points ofcourse for each.
Is it a good practice for each and every parameter inside a JSON object (which is model object for REST service) configurable via jinja template in Ansible rather than POSTing complete Payload to a base URL from a file?
I mean it can be huge parameters if we make each service payload parameter as variable in ansible.
Customer demand is : they want each and every parameter used for REST API configurable via Ansible.
I dont know is it good or bad, for me it is not good practice.
Thanks Andrew , but is it good to make each and every parameter of Rest api response as configurable using Ansible , considering we have huge parameters?
There is URI module present in Ansible which lets you invoke REST End Points and it works preety well.
Currently i have lot of JSON Objects and corresponding REST end points ofcourse for each.
Is it a good practice for each and every parameter inside a JSON object (which is model object for REST service) configurable via jinja template in Ansible rather than POSTing complete Payload to a base URL from a file?
Take a look at modules in Kubernetes space for handling module parameters.
I mean it can be huge parameters if we make each service payload parameter as variable in ansible.
Customer demand is : they want each and every parameter used for REST API configurable via Ansible.
I think purpose of httpapi plugin is different. Here I have my own API (say built in JAX-RS or Spring Boot), and list of REST ends points are of order (10-100) where each Resource have multiple parameters to deal with.
In that context , is it good to make each param configurable using ansible?