You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I am really interested in using a registry of nomad jobs, but I am not interested in deploying jobs through imperative commands such as nomad-pack run <pack>. I'd rather not deviate from my current flow where all my jobs are described in files, deployed thanks to Terraform -> everything as code.
Is there any plan to make nomad-pack available from either one of the following way?
Directly from Nomad jobspec files
From the Nomad Terraform provider
From a dedicated Nomad-pack Terraform provider
By the way, I would be glad to use the nomad-pack CLI for various other tasks such as consulting registry list, generating pack from template, and so on.
The text was updated successfully, but these errors were encountered:
Beside the user interface part, there is a serious problem on the current nomad-pack impl: if a job is removed from a pack, nomad-pack run xxx will not remove it from the deployment. (I've created a separate issue: #503)
But you don't need nomad-pack! It is possible to implement most nomad-pack features in Terraform's Nomad provider:
Declarative interface works
Removing jobs works
--preserve-counts DOES NOT WORK, pending upstream changes
Hello, I am really interested in using a registry of nomad jobs, but I am not interested in deploying jobs through imperative commands such as
nomad-pack run <pack>
. I'd rather not deviate from my current flow where all my jobs are described in files, deployed thanks to Terraform -> everything as code.Is there any plan to make nomad-pack available from either one of the following way?
By the way, I would be glad to use the nomad-pack CLI for various other tasks such as consulting registry list, generating pack from template, and so on.
The text was updated successfully, but these errors were encountered: