sincecutoff.com
← all changes

KMS Autokey config supports project-level operations and key-resolution-mode

Introduced 2026-05-19 · score 0.95

HOW TO USE IT

To inspect a project Autokey configuration, run `gcloud beta kms autokey-config describe --project=<project-id>`. To update it, put the project resource name and desired `keyProjectResolutionMode` in a YAML config file, then run `gcloud beta kms autokey-config update <config-file> --project=<project-id>`.

gcloud beta kms autokey-config describe --project=<project-id>
# <config-file>.yaml name: projects/<project-id>/autokeyConfig keyProjectResolutionMode: RESOURCE_PROJECT keyProject: '' gcloud beta kms autokey-config update <config-file>.yaml --project=<project-id>

WHY THIS HELPS

Describe or update a project-level Autokey configuration, including its key resolution mode.

REQUIREMENTS AND LIMITATIONS

  • Availability: beta
  • --project=<project-id> (required): Project id for the configuration; describe requires exactly one of --project or --folder. It is also a gcloud-wide flag for update.
  • <config-file> (required): File containing the AutokeyConfig resource to update.
  • name (required): AutokeyConfig resource name, e.g. projects/<project-id>/autokeyConfig.
  • keyProjectResolutionMode: Mode for resolving the key project. Allowed values: DEDICATED_KEY_PROJECT, RESOURCE_PROJECT, DISABLED. Docs do not state these values are mutually exclusive; they are enum alternatives.
  • keyProject: Key project name. Empty value clears the configuration; guide's RESOURCE_PROJECT example leaves it empty.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card