I agree with Robert, that's why I still `+1` `brooklyn-cli` over `brooklyn-client`
I'm tempted to suggest `brooklyn-go-client`. What happens to the existing > Java client, which is not a CLI? Does it deserve its own repo too? What > about future language clients? > If the brooklyn rest API will be fully Swagger compliant I think a good documentation on how how to generate clients in different languages starting from the same YAML spec using swagger-codegen will be enough, I think. This will offer a good integration with other ecosystems and it will not require brooklyn community to support all the languages available out there. Cheers, Andrea
