hashicorp

Hi,

I have configured boundary with this configuration:

kms "awskms" {
  purpose    = "root"
  region     = "eu-west-1"
  kms_key_id = "13f71062-f9da-4397-8dca-XXXXXXXX"
}

And it gives the next error:

boundary         | Error parsing KMS configuration: error fetching AWS KMS wrapping key information: NoCredentialProviders: no valid providers in chain. Deprecated.
boun

Great new metric last_state, thanks!

We now have a monitoring rule is in place to watch for failed sync. A sync was failing so I deleted the ExternalSecret. However, last_state does not forget and continues to report -1 on the ExternalSecret that no longer exists. It continues to report success on deleted objects as well.

Clearly this is bad and last_state should stop reporting ExternalSecre

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.