In the current solution, we're updating main.py directly to insert raw credentials. Not good! It requires you to clean it up before taking the latest pull and the credentials shouldn't be put into an actual source code file.
The next approach is going to be:-
There will be an env.example file containing credential format and if the profile will be used actively for the next run.
The user will copy the env.example to .env file and insert their credentials there.
Running the main function will use .env to determine which profiles to use and collect credentials from .env for submission.
This can also be improved in the future, depending on the demand. Leave a comment if you think we should take a different path.
In the current solution, we're updating
main.py
directly to insert raw credentials. Not good! It requires you to clean it up before taking the latest pull and the credentials shouldn't be put into an actual source code file.The next approach is going to be:-
env.example
file containing credential format and if the profile will be used actively for the next run.env.example
to.env
file and insert their credentials there..env
to determine which profiles to use and collect credentials from.env
for submission.This can also be improved in the future, depending on the demand. Leave a comment if you think we should take a different path.