Miserlou/Zappa

Add a pre-deployment sanity check

Open

#78 opened on May 11, 2016

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Python (11,903 stars) (1,286 forks)batch import
enhancementgood-ideahacktoberfesthelp wanted

Description

Just display warnings if the app_module doesn't exist to avoid the

 UnboundLocalError: local variable 'app_module' referenced before assignment

that happens from putting the wrong values in zappa_settings.

Contributor guide

Tech stack
python
Domain
devops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
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
Basic PythonFamiliarity with Zappa configuration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Examine the deploy management code in the Zappa repository, likely in `zappa/cli.py` or similar. Look for where `app module` is used and add a check before its first reference to ensure it exists to avoid UnboundLocalError. Review existing configuration validation patterns in the codebase to mimic the warning style.