Skip to content

Conversation

karikarshivani
Copy link
Contributor

@karikarshivani karikarshivani commented Jun 28, 2022

Moved INPUT_BUCKET environment variable with others

Signed-off-by: karikarshivani karikarshivani@gmail.com

Signed-off-by: karikarshivani <karikarshivani@gmail.com>
@karikarshivani karikarshivani self-assigned this Jun 28, 2022
@karikarshivani karikarshivani changed the title Set lambda trigger to an existing s3 bucket Semantic update for env var Jun 28, 2022
@em-c-rod em-c-rod requested a review from rgs1109 June 28, 2022 16:43
deploymentBucket: # Custom configuration for deployment bucket is unique and put here
deploymentBucket: # Custom configuration for deployment bucket
blockPublicAccess: true
environment:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@karikarshivani hi - quick question - was there an advantage to originally keeping this separate ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @rgs1109! Yes, the provider.environment section defines the environment variable globally (so all functions can access the value) and the functions.<function_name>.environment section defines the environment variable locally (so only that function can access the value). Hope that helps! :)

@karikarshivani karikarshivani requested a review from rgs1109 June 29, 2022 13:49
@em-c-rod em-c-rod merged commit ee5a6e3 into main Jun 29, 2022
@em-c-rod em-c-rod deleted the serverless branch June 29, 2022 17:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants