-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trouble getting this to deploy #25
Comments
The initial template is now too large to send via 'templatebody,' I haven't looked at fixing it but the hack I used was to source Inventory-Template from s3 (do so with |
That gets it partway - at least addresses fixing the Manifest directions. I think I'm having issues with the inventory zip file now. We'll see. I'll keep poking at it. |
I just discovered that issue with deploy_stack.rb not generating manifest files from the too-large template. I'm going to drop sample manifest files in the repo tonight. |
If you send me the output of the make package I'll see what's going wrong. Also apologies for the delayed response, I apparently never subscribed myself to notifications on this repo. |
I was able to cobble together a working CF stack - not exactly sure the steps but I'm good now. I can wait for a later revision to run again. |
I'm trying to follow the directions in INSTALL.md - I have all the pre-reqs set up.
I cloned the repo and created a config.env as specified. Then tried running the deploy_stack. Looks like that actually needs to run from inside the aws_inventory directory given the pathing in the command.
I tried to edit the Manifest file. Setting the StackName is unclear where and how to do that. I removed the pBucketName definition but pDeployBucket doesn't exist. Then I tried running the make command. It was looking for config.prod so a copied config.env to that. But the make fails. I get a couple of these errors:
*** No rule to make target
yaml', needed by
zipfile'. Stop.Any ideas?
The text was updated successfully, but these errors were encountered: