Another question. it seems like secrets are part o...
# seed
s
Another question. it seems like secrets are part of lambda’s deployment regardless if they are actually used as env variables on lambda function itself. Is this expected behaviour? I have this suspicion because I have couple of secrets that are concatenated as value for a secret manager resource I define in cloudformation template. The combined size for these env variables is larger than 4kb which triggers this error
Request must be smaller than 5120 bytes for the UpdateFunctionConfiguration operation
and I don’t use these secret at all as environment variables.
f
We are in the process of rolling out an option for ppl to pick and choose which secrets get set as Lambda environments.
We can roll out the option for your account now so that the secrets don’t get set as Lambda environments automatically, and you can set it manually using
${env:SOME_SECRET_ON_SEED}
Let me know if that’d work for you.
s
That’s awesome. Yes please.
f
Can you DM me the name of your org on Seed?