You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As was decried previously, various API keys were listed in plain text in the repository, and deployed by cloning. The environment from the past was heavily secured, which is no longer going to be the case.
Determine the best strategy to inject keys easily so the same deployment of code might be used to connect through diverse keys; especially serving multiple organizations in various processes.
The text was updated successfully, but these errors were encountered:
I pointed this out in the earlier discussion as well but I think we can make a constants.yml file or even per environment (rails style ish) and have things load from there.
As was decried previously, various API keys were listed in plain text in the repository, and deployed by cloning. The environment from the past was heavily secured, which is no longer going to be the case.
Determine the best strategy to inject keys easily so the same deployment of code might be used to connect through diverse keys; especially serving multiple organizations in various processes.
The text was updated successfully, but these errors were encountered: