Possibility to require a prompt when using the nomad CLI for taking action (i.e. "are you sure? yes")

[msherman13]

Proposal

Add the option to require user-confirmation before applying changes with the nomad CLI. For example restarting a job. Read-only actions like listing jobs or services should not require the prompt.

Use-cases

Currently, it is quite easy to use the nomad CLI to take actions in the cluster, which we love. However, in our use-case, we have a staging cluster and a production cluster and they can both be modified from our development machines. It would be great for us if we could somehow configure the CLI to require a user-confirmation prompt before taking action on the production cluster, but not require it for the staging cluster.

Attempted Solutions

We have some bash scripts wrapping the CLI to do this, but we don't have any way to require its usage by devs.

[jrasell]

Hi @msherman13 and thanks for raising this issue.

If we were to add further confirmation prompts (we already have some on critical/dangerous CLI calls) they would likely be accompanied by a -y flag which automatically confirms the action for automated processes. In this case, developers could continue to bypass this by passing that flag in the same way they bypass using the CLI wrapper you have. Building it into the CLI would also not stop people performing direct API calls to bypass the logic.

I feel this would be better solved by gating production access via automated workflows and ACLs. Nomad Enterprise also includes functionality such as Sentinel and Audit Logging which can potentially help the situation you are experiencing.