The initial version of providing cloud-init user-data is via a path reference. It would be convenient to expose a way for a job author to embed the entire static user-data file contents as a heredoc-style string into the job file.
Optionally I suppose some light templating could be applied, but I am unsure if that would be useful in practice. Perhaps in that case the user could use the consul-template integration to create the file from vars and write it out to a file to use the existing mechanism.
The initial version of providing cloud-init user-data is via a path reference. It would be convenient to expose a way for a job author to embed the entire static user-data file contents as a heredoc-style string into the job file.
Optionally I suppose some light templating could be applied, but I am unsure if that would be useful in practice. Perhaps in that case the user could use the consul-template integration to create the file from vars and write it out to a file to use the existing mechanism.