If the idea is that user should be able to provide value via Dynatrace and your app should be able to use that value. I’d suggest to use the settings for that.
The App Settings API is purpose-built for this use case. It lets you define a schema and store key-value config (including secrets) scoped to the app itself.
How it works:
1. Define a schema in /settings/schemas/ in your app project:
const { data } = useSettingsV2({ schemaId: 'app:my-app:config' });
Why it’s ideal: Values live in Dynatrace (not the repo), are editable via the Settings UI, support secrets with masking, and work natively within App Engine without needing app context for credential vault.