tribelt's session and visitor keys are generated in the cluster #446

Parent

#444

What to build

tribelt's session key and visitor HMAC key are generated in the cluster. The Estate repository composes with the deploy-kit release that has generated keys, and tribelt declares both keys as generated under tribelt-system, so they appear in Vault with no manual step. A new value ends existing sign-ins once.

Acceptance criteria

• toolkit.yml names the release with generated keys.
• tribelt's project file declares session_key and visitor_hmac_key as generated, and its pod reads them.
• The keys exist in Vault after a release with no manual step, and keep their values across the next release.

Blocked by

• Generated keys, written by the Vault policy job #445