aws lambda update-function-configuration: Add --env-file option

[franciscocpg]

often I have this boilerplate code in a shell script:

source .env

aws lambda update-function-configuration \
--region "$REGION" \
--function-name "$FUNCTION_NAME" \
--environment Variables="{\
VAR1=$VAR1,\
VAR2=$VAR2,\
VAR3=$VAR3,\
VAR4=$VAR4,\
(...)
}" > /dev/null

It would be nice if I could do this instead:

aws lambda update-function-configuration \
--region "$REGION" \
--function-name "$FUNCTION_NAME" \
--env-file .env

I'm not a python dev but if you are open to contributions and consider that this feature request makes sense I can propose a PR.

[justnance]

@franciscocpg - thanks for reaching out. In general, currently the CLI works with JSON formats. As such, there is a blog posting that goes into more detail regarding the feature you trying to work with:
Best Practices for Local File Parameters

Please advise if this works for you.

[franciscocpg]

Hi @justnance
Thanks for your response.

It does not work because the idea is to keep .env file (using its format) usable across multiples projects/frameworks.

Eg: The .env file with contents:

VAR1=Value1
VAR2=Value2

would be usable by my nodejs project, by docker-compose (https://docs.docker.com/compose/compose-file/#env_file) and by aws cli.

Since .env files are widely used across different projects/frameworks to define environment variables I thought that aws cli could support it too.

[justnance]

@franciscocpg - Thank you for your feedback. I am labeling this as a feature request pending additional 👍 .

[garrington]

+1

[moamenet]

+1

[tyronegroves]

+1

[fizz]

+1

[eschizoid]

+1

[ravinatesan]

+1

[machaerus]

+1