Feb 12 2021 lamba-action@master inserting DRONE_COMMIT and overwriting lambda ENV
scottdavidreynolds opened this issue · comments
As of today our Lambda ENV is being overwritten by this line:
DRONE_COMMIT=<hash_of_github_action>
We see that the ENV setting has been added to lambda-action as of Feb 12th. This must be correlated. We do not specify ENV in our github actions workflow yaml files. These values are stored in the Lambda directly with KMS.
I have a forked version https://github.com/Meetiers/lambda-action that returns the server back to use 1.2.3 from October before there ENV functionality was added and now my deploys do not overwrite my lambda env.
I'm seeing this as well. You're wiping out my environment variables.
