How to handle api keys in local development with visual studio docker support?
I just switched my project over to use visual studio docker support and it broke because the user secrets do not get added to the container image.
After some research I found this issue:
https://github.com/Microsoft/DockerTools/issues/24
This seems like a poor solution to have to directly map an explicit path from a file inside the repository that will change from developer to developer.
No one likes having a local file that can be committed by accident and break everyone's project if pulled.
Is this really the only solution or is there an alternative for managing secrets when using visual studio docker support?
0 comments:
Post a Comment