Feature recommendation: Chef Resources for GoCD resources

[miroswan]

Since GoCD provides an API to manage some of its resources, it would make sense to have Chef resources that could manage these.

[tomzo]

Talking to GoCD API from ruby would basically require developing or using gocd-ruby-api. Something like this.

It is probably worth the effort to support backup/restore. Perhaps some of agent-related operations or user management.

However it is quite a lot of work. Personally I do not have a use case for such.

[tomzo]

I also wonder if such functionality should be included in this cookbook. It might be better if it could mature indepenently, without causing issues here.

[miroswan]

We don't necessarily need a resource for every single object. Could bring them in one by one. One LWRP per resource. the chef_gem resource could bring in the go api client for use within the resources.

[miroswan]

Once the cookbook gets to 1.0 I might submit a PR for a basic user resource and see what you think.

[willejs]

👍 for this. I think its essential to reproduce anything in code.
Currently we have built some tooling to push a bunch of json into the API to configure pipelines and get chef to run it.
Its something ive just started looking at and could easily be made into a custom resource.

[tomzo]

@willejs If you agree that pipelines should be configurable via source code rather than UI, then you might want to have a look at gocd/gocd#1133