Force new revision when latest secrets are used in environment #4
Description
At the moment, when the latest version of secrets are exposed through the environment, this value is not updated to reflect the latest version. This will only happen on a cold start, and never if instances are kept warm. This is not an issue when mounting secrets as volumes.
There should be the functionality provided to force a new revision to be (optionally) created if any secrets using the latest version are exposed through environment variables.