brianneisler/gulp-cloudformation

Simple gulp plugin for deploying stack files to AWS cloudformation

Hi there 👋

gulp-cloudformation's Issues

Replace gulp-util (deprecated) with alternatives

This package still uses gulp-util which has been deprecated by the gulp team (https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5).

The blogpost outlines the following alternatives for the gulp-util functions found in this package:
log: https://www.npmjs.com/package/fancy-log
File: https://www.npmjs.com/package/vinyl

Setup docs to use Verb

https://www.npmjs.com/package/verb

getInstance means it's not possible to call with different options in a single gulpfile

I have a gulpfile that deploys to 2 different regions and in one of those regions to 2 different accounts. If I call each gulp task individually it works fine. But running multiple cloudformation() calls with different options just reuses the options of the first call. This is due to the caching of the GulpCloudformation instance in getInstance.js.

Given that it causes very confusing and unexpected results, and is probably not saving too much in terms of clock time, is this caching necessary?

allow StackName as a parameter

It would be helpful if the params object for the .deploy() function allowed me to specify the name of the CloudFormation stack. Currently it seems to pick based on the filename of the template file. This is an excellent default but doesn't allow you to run multiple CF stacks from the same template (e.g. for multiple environments dev/prod.)

This is what I get when I try passing StackName with a stack that already exists and template file cloudformation.yml:

ValidationError: Stack with id cloudformation does not exist