Add orchestrator options

[tebriel]

This is a work in progress, to address:

feedback from @ProTip

For orchestrator config I'm a little concerned that the Terraform schema may stray from the API schema in a way that reduces the flexibility. Unlike notification which has "built in" notifications, email and webhook_urls, separate from a "plugin" config the orchestrator block is itself a "plugin" config. So its schema is pretty much the same as for the notification plugin block: https://github.com/terraform-providers/terraform-provider-rundeck/blob/master/rundeck/resource_job.go#L310-L323 .

The builtin orchestrator plugins happen to have one configuration key, however others could in theory have arbitrary configuration elements. It would reduce or make "validation" more tricky, but I'm wondering if it would be better to model the orchestrator schema after the notification plugin block?

[tebriel]

Okay, that's a good point, I'll make it mirror that config map to avoid future compatibility issues.

[fardin01]

Hi @tebriel. Just wondering if you ever had the time to get back to this? This would be a very cool feature to have. Let me know if there is anything I can do (bear in mind I have limited Goland skills). Thanks :)

[tebriel]

@fardin01 sorry, but I've left the Pindrop company and no longer have an environment where I manage rundeck. I wish you the best of luck if you want to pick this up!

[fdevans]

Closing. See #107