-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Enhancement proposal] Configuration profiles #1068
Comments
Yes, good idea @aitorarjona |
The idea is to keep lithops:
backend: localhost
storage: localhost
localhost:
worker_processes: 1 for testing. Another profile for, for example, IBM Cloud in file lithops:
backend: ibm_cf
storage: ibm_cos
ibm_cf:
endpoint : ...
namespace : ...
api_key : ...
ibm_cos:
storage_bucket: ...
region : ... and to select this configuration profile: FunctionExecutor(config_profile="ibm") |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, Lithops can be configured:
The standard and most convenient is using a configuration file. The problem with having only one config file is that, for a multi-cloud configuration, all parameters reside in the same config file, potentially being a mess.
I propose to create configuration profiles. The "default profile" is the
~/.lithops/config
file, but users could create new config files with different names (e.g.~/.lithops/aws_lambda_testing
), and select the appropraite profile in the FunctionExecutor constructor (FunctionExecutor(config_profile="aws_lambda_testing")
).WDYT @JosepSampe
The text was updated successfully, but these errors were encountered: