jgreenemi/Parris

Add `no-clobber` option for Lambda function update.

Open

#4 opened on Jan 2, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (320 stars) (22 forks)batch import
good first issuehelp wanted

Description

Allow lambda-config.json to specify if this function should be replaced or not if setup.py is run and an existing function is found. At present it just overwrites whatever code is already there to make updates seamless, but user may not want to have their Lambda function be so easily overwritten.

Contributor guide

Tech stack
pythonaws
Domain
devopscloud
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
PythonAWS Lambda basicsJSON config handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Examine the codebase to find how `lambda config.json` is parsed and how the Lambda function update is currently performed. Look at files like `parris.py` or `lambda utils.py` for the existing update logic. The change involves adding a new key in the config that prevents overwriting when set to true. The implementation should check this flag before calling the update API.
Add `no-clobber` option for Lambda function update. · jgreenemi/Parris#4 | Good First Issue