flrent / grunt-cloudfront

AWS CloudFront cache invalidating grunt.js task based on node.js.

Hi there 👋

I am a Staff Software Engineer and tech lead based in San Francisco, California. I am currently working at Flickr, on front-end and data engineering projects.

I'm also currently researching and experimenting with LLMs and AI.

You can learn more about me here → florentlamoureux.fr

grunt-cloudfront's Issues

Fatal error: Cannot read property 'length' of null

I'm getting this error:

Fatal error: Cannot read property 'length' of null

Actually it says:

Invalidation succeeded. Please wait a few minutes.OK
{ 
Location: 'https://cloudfront.amazonaws.com/',
Id: ''
/** normal account data */
}
Fatal error: Cannot read property 'length' of null

I've checked from aws console, it is actually creating invalidation rule, but is not waiting for it to be completed.

Add a changelog generation

@payrollhero/devs,

We need a changelog generation so every update on S3 and CloudFront is logged. Already saw some cool grunt tasks, but none of them seems to integrate easily.
If anyone has an idea, please comment here.

devDependencies not install when running npm install

Step 1. Create a standard project
Step 2. Run npm install grunt-cloudfront --save-dev
Step 3. Look in the node_modules/grunt-cloudfront folder

There is no node_modules within the grunt-cloudfront dir. I'm not quite sure what's causing this bug? I've been getting round it by manually going to the node_modules/grunt-cloudfront directory and running npm install there.

Thanks

grunt-aws-s3 changed files

Any way of using grunt-aws-s3's aws_s3_changed as input?

Build invalidation batch from paths in configuration

Instead of having to include a valid invalidation batch, why not build the invalidation batch from a much simpler configuration?

Please see sspinc/grunt-cloudfront@30db42bd0290040392ea24ddd16da8adc82172d4 in our fork. This is the only difference and we would love to contribute this back in a backwards-compatible manner by checking the configuration whether it already includes Paths and CallerReference or it expects grunt-cloudfront to assemble it).

It would make it much easier to invalidate paths, especially if they are determined dynamically.

Working on directories

Did you know how can i invalidate each file on a virtual directory?

Example:

/builds/*.

Is there a way to ignore on dev?

Currently my package.json contains a postscript that runs grunt build once I run npm install.

I would like the option to ignore to run cloudfront if process.env.NODE_ENV === 'development'.

Is there a way to perform this task?