Ability to create multiple groups and tasks

[bogdanov1609]

Hey! Awesome project, thank you.
But what about support for multiple groups and tasks in that groups?

Our goal is to "stick" docker containers to datacenters, because of it in our case, we have one job, two groups - one per datacenter, and one task per that groups.

[ValFadeev]

Hi, thanks for checking it out!

I would like to be able to support more complex job structures, however, I could not think of a nice way of mapping those onto Rundeck UI. It does not seem to offer things like repeating panels, or elements that could be conditionally enabled (at least not in community edition).

A hacky way of achieving this would be to allow injecting arbitrary fragments of job definition in hcl/json. However, this would kind of destroy the purpose of the plugin.

I will think of it, being open to suggestions. In the meantime, would you consider the following workaround: create 2 separate jobs in Rundeck, one for each group/task and the third job referencing those 2 as workflow steps?

You could also encapsulate the common settings in a "base nomad job" and expose the variable parameters via options.

[ValFadeev]

On second thought, I will probably go the "hacky" way and implement a sub-plugin that will accept an arbitrarily complex job definition (in json). Those with simpler use cases could still use the driver-specific plugins, in return for early input validation.

[bogdanov1609]

Hmm, I think in common cases we only need to change versions in already created jobs.
If we will have opportunity to submit json/hcl job and after that just change version via api or ui, it's going to be wonderful.

[ValFadeev]

@bogdanov1609 you can pretty much achieve that with the current plugin, as long as the fact that each task group will run within a separate job does not pose a big trouble.
See a working example here which you can import in a test project.
I am still planning to support arbitrary templates, after a bit of refactoring.