hashicorp

So there is currently an hvac.v1.Client.sys.list_mounted_secrets_engines() method.

However, for obvious reasons this will fail as it will attempt to list all mounted secrets engines (as it calls /v1/sys/mounts).

The web UI, however, shows what mounts the current token has access to.

While poking around the live API documentation the other day (`VAULT_BASE_URI/ui/vault/api-explorer

New Provider Request

Manage secrets from Mac keychain

Details

• URL: https://support.apple.com/en-il/guide/mac-help/mchlf375f392/mac
• Modes: read+write
• GitHub projects: https://github.com/keybase/go-keychain

I understand the nomad need to be start/restart as a 'root' user because many operation it runs, needs root privilege.

However as a system admin I would like to harden/limit the scope of 'sudo' access to specific tasks only. As far as I have analyzed the following will need sudo/become/root privilege's:

• handlers/main.yml: restart nomad
• tasks/main.yml: start nomad
• file & template oper

Description

With the changes introduced in #227, Noma API calls for job scaling operations were updated to permit stale reads. We should update the remainder of Nomad API calls for consistency and decreased load on the Nomad Servers.