Stack <stack name> does not exist on deploy
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 224
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Description
When running the deploy function, it checks the bucket name and then creates the bucket correctly. But the deployment process fails and exits the installation process on the next step -
"aws cloudformation deploy --template-file /tmp/tmp. --stack-name "
I am currently using Python 2.4.6 if that makes a difference and I ran the command as ./deploy awspics-lambda without the stack name or editing the default stack name within the deploy app. Is there something different with the DescribeStackResource operation in python 2 or am I missing something?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the deploy function invoked by ./deploy and trace the transition from bucket creation to the AWS CloudFormation deploy command and DescribeStackResource operation. Reproduce the shown awspics-lambda invocation, checking the reported stack-name handling; done means deployment proceeds without the “Stack does not exist” failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript, python
- Domain
- cli, cloud, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100