Secrets with non-standard names

I have an existing container with some interesting environment variables:

$ fly secrets set DB:Password="foo"
Error Validation failed: Name only allows letters, numbers, and underscores

Am I totally out of luck to run this container unmodified?

Would the only way be to build on top of the container and script the mapping from DB_PASSWORD to DB:Password? Any other ideas?

I think an ENTRYPOINT script to map the env var names we accept to what you need is your best bet. We have some ideas for things that might improve this down the road, but you definitely don’t want to wait on our rando ideas we haven’t started working on yet.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.