Tools do not check that EC2 environment variables are set
Bug #881138 reported by
Chris Bunch
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| AppScale |
Fix Committed
|
Medium
|
Chris Bunch | ||
Bug Description
In cloud deployments, EC2 environment variables related to keys and certs are needed, but the tools do not check if they exist before attempting to use them. The requested changes are:
1) Make sure that the four environment variables (EC2_CERT, EC2_PRIVATE_KEY, EC2_SECRET_KEY, EC2_ACCESS_KEY) needed are set, and abort if not.
2) Make sure that EC2_CERT and EC2_PRIVATE_KEY refer to files that actually exist.
3) If running in Euca, EC2_URL needs to be set (otherwise it defaults to localhost) - fail if it's not present
| Changed in appscale: | |
| status: | Expired → Fix Committed |
To post a comment you must log in.
