We need a better way to bring nodes to live than using cURL.
I think that an IT-department will complain big time if they can't do all tasks needed to setup a server environment from the config-tool. To switch between config tool and cURL for the different tasks does not make sense.
Today we can handle trusting the nodes from the config tool, but we must add the possibility to push deployments and other tasks needed for the nodes too.
Why use two variants of tools when you could have everything in one centralized configuration tool?
Today I use both in my scripts and there is rarely any problems with the configuration from the config tool.
On the other hand, the tasks I use curl for are both brittle and hard to troubleshoot.
So we need to add tasks in the config tool for complete setup of the environment. cURL feels like a temporary option inhouse use but I doubt it will be a viable solution in production.
*Examples:*
*Important:*
* Install a service.
* Creating and editing routing rules
* Trigger upgrade of service (used when new packages been uploaded) - Like the old Webplayer Upgrade tool.
*Nice to have*
* Creating a resource pool (can be done when service is installed but would be useful to do separately as well)