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
I have been using Fire for a while now and in the last few days, it struck me that it may be nice to have a way to read a required variable either as an argument or as an environment variable.
The example that made me think about this was a simple script I wrote to execute some tasks in Facebook's API. It needs to receive both the application id and secret. Sometimes I leave those as environment variables and sometimes I do not, depending on the machine that receives the deployed code.
I solved the issue by doing something like:
fromosimportenvironfromfireimportFireAPP_ID=environ.get('APP_ID')
defmain(app_id=None):
assertapp_idorAPP_ID, 'You need to provide the app ID either as a parameter or as an environment variable'if__name__=='__main__':
Fire(main())
This got me wondering if it would be nice or even useful to implement something like this directly into Fire's variable handling. If so, I would love to contribute.
Thank you all very much :D
The text was updated successfully, but these errors were encountered:
Oh, I didn't see that PR or issue #94. Later I was wondering if we could make this injection more generic and customizable. My point is that it may be useful to read those variables from config files in .ini, .json, .yaml formats and so on.
Before I elaborate any further, should we close this issue as a duplicate of #94 ?
Hello,
I have been using Fire for a while now and in the last few days, it struck me that it may be nice to have a way to read a required variable either as an argument or as an environment variable.
The example that made me think about this was a simple script I wrote to execute some tasks in Facebook's API. It needs to receive both the application id and secret. Sometimes I leave those as environment variables and sometimes I do not, depending on the machine that receives the deployed code.
I solved the issue by doing something like:
This got me wondering if it would be nice or even useful to implement something like this directly into Fire's variable handling. If so, I would love to contribute.
Thank you all very much :D
The text was updated successfully, but these errors were encountered: