This message was deleted.

Yes - you must use

require_secret

to ensure the value is treated as a secret as part of the deployment (not serialized into any statefile). We will in the future make it an error to use other config functions on a secret config value (this is supported today for compatibility with how things worked prior to having deployment support for secrets).

Thanks for the clarification. Is there currently a github issue for the above. I would love to follow along