Serverless Framework - How to combine module resources into cloud formation

Question

I'm having trouble merging my module/awsm.json into resources-cf.json . Nothing I'm trying to unify them. Here are my steps

• jaws project create
• cd new-project-name
• jaws module create greetings hello
• change greetings/awsm.json adding LambdaIamPolicyDocumentStatements and resources. Similar to https://github.com/dekz/awsm-users/blob/master/awsm.json .

" jaws deploy resources " does not update cloud formation and does not produce

 JAWS: Resources Deployer "dev": Deploying resources to region "us-west-2"... JAWS: Resources Deployer "dev - us-west-2": Performing Cloudformation stack update. This could take a while depending on how many resources you are updating... JAWS: Resources Deployer "dev - us-west-2": Cloud formation stack update failed because of the following error... { [ValidationError: No updates are to be performed.] cause: { [ValidationError: No updates are to be performed.] message: 'No updates are to be performed.', code: 'ValidationError', time: Sun Oct 11 2015 00:13:53 GMT-0700 (MST), statusCode: 400, retryable: false, retryDelay: 30 }, isOperational: true, code: 'ValidationError', time: Sun Oct 11 2015 00:13:53 GMT-0700 (MST), statusCode: 400, retryable: false, retryDelay: 30 } 

The redeployment of lambda and endpoint also does not update cloud formation resources.

What is the proper process to get changes to resources-cf.json and apply them on AWS?

Answer 1

There is currently no automation on 1.3.3 to generate resources-cf.json from awsm.json , as I expected, this will also be.

From your channel Gitter :

The resource part of the awsm module can update the main resource cf file during the first installation (a step after installation), but for now. There are currently no tools to do the same when you manually add changes to your module. At the moment, such changes must be manually transferred to the corresponding cf resource file. Future versions of JAWS should support commands that allow you to recover the resources-cf file from information stored in awsm modules, as some people requested this function.

Answer 2

I came across this question when I had a similar problem. In my case, setting the area and stage was specifically deployed successfully.

Are you sure that you did not deploy resources to another stage and / or region, and why AWS gives you a verification error (i.e., your stack has already been updated in this region / stage)

Here is what I ran:

jaws deploy resources staging us-east-1

After editing my cloudformation/staging/us-east-1/resources-cf.json .

I then confirmed through the AWS web console that the changes really worked.