User wants a simpler way to handle short-lived secrets in Harness without storing them in Secret Manager.

Use case is that an SRE starts a deployment pipeline and enters two temporary sensitive values: an API Key ID and an API Key PEM. These values need to be passed securely to later steps or stages for authenticated API calls.

The main issue is that using Secret Manager for short-lived credentials creates extra work, since the secrets must be manually created, rotated, and deleted even though they are only needed for a short time.