fix: use relative path as lambda function local package path #261
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To avoid unintentional state changes when working in multiple environments,
Use relative path as lambda function local package path.
Before:
As seen in
Before
, if the filename is set to an absolute path, the username is included, and the lambda function is updated even if it is the same source in another user's environment.After:
In
After
, setting the relative path based on cwd, update is attempted only when the actual source code is changed.PR of other related projects: