Support for mixed-case keys

Feature Requests
1

Some infrastructure platforms use mixed-case keys for environment variables, and do case-sensitive checks. In order to support syncing secrets to these platforms, Doppler needs to support mixed-case keys.

While I understand wanting to only support UPPER_CASE keys to maintain cross-shell support, this makes Doppler unusable for some deployments. A warning when trying to inject an invalid secret for a shell that doesn’t support that casing could provide sufficient balance against the functionality gained.

In my case, I’m wanting to deploy an Azure Function App using secrets from Doppler. This requires a critical app setting under the name “AzureWebJobsStorage”. Without this setting existing under that exact casing, the whole deployment fails, and will kill any existing deployment.

See this Github issue: https://github.com/Azure/functions-action/issues/93.

As seen in this article, there are 11 settings that need mixed case keys.

2

Hi @nick,

Thanks for the feedback and that certainly is a compelling case (no pun intended) for supporting different naming conventions such as PascalCase.

I’ll add a task to our backlog for Engineering to review and will in touch once I know more.

1 Like
4

I could also use this. In my use-case I’m trying to use an RDS proxy, which looks for the database “username” and “password” keys in Secrets Manager. I’m syncing to Secrets Manager from Doppler but unfortunately I can only use the keys “USERNAME” and “PASSWORD”, which RDS does not recognize.