Issue with beanstalk and cloudformation

[chaotang88]

Parden me if I'm asking dumb questions.

So for beanstalk, my current folder structure is like this: which the extension does is add https binding and add environment variable("Development, Staging etc"), now I manage to build out this structure through TeamCity. Somehow the breanstalk step package up the bundle and generates aws-windows-deployment-manifest.json by itself and not include my extension script which failed my deployment
, how can I fix this?

2nd question about cloudformation. My cloudformation template are nested, and I refer them in my main template: without uploading them to s3, how the create/update stack task knows where to find my sub-templates? What should I put on my bases3repo variable instead of my s3 bucket url(since it will be running on vsts build agent now)?

Thank you for your time.

[normj]

For the 1st question the task is written assuming the manifest needs to be created. Looks like we need to add support to check if the manifest file already exists.

And the second question the CloudFormation task is not yet advanced enough to manage nested tasks. I think what I would do is use the S3 Upload task to upload the nested templates to S3 and then pass those locations to where you upload as parameters when using the CloudFormation task to deploy the main template. There are definitely some feature ideas on task side for the future to make this process easier.

[chaotang88]

Thank you so much for your fast response. And really looking forward to those enhancements!

[PsiOps]

Hmm sadly not a lot of progress on issue number 2. The lack of support for nested stacks is quite the bummer.