"Role with name [my name]-executor already exists" on error

I ran:

claudia create --name storingInDynamo --region us-west-2 --api-module index

but forgot the files property. That trigger an excellent error message: package.json does not contain the files property

Great - but when I fixed that and ran the create-command again:

{ [EntityAlreadyExists: Role with name storingInDynamo-executor already exists.]
  cause: 
   { [EntityAlreadyExists: Role with name storingInDynamo-executor already exists.]
     message: 'Role with name storingInDynamo-executor already exists.',
     code: 'EntityAlreadyExists',
     time: Fri Feb 26 2016 14:24:46 GMT+0100 (CET),
     requestId: '4df7b6fb-dc8c-11e5-9b40-35d169b930d8',
     statusCode: 409,
     retryable: false,
     retryDelay: 72.52002414315939 },
  isOperational: true,
  code: 'EntityAlreadyExists',
  time: Fri Feb 26 2016 14:24:46 GMT+0100 (CET),
  requestId: '4df7b6fb-dc8c-11e5-9b40-35d169b930d8',
  statusCode: 409,
  retryable: false,
  retryDelay: 72.52002414315939 }

And now I don’t know how to fix this, except updating the name of the function (--name)

[thom-nic]

Did this cleanup function ever get implemented? calling aws iam delete-role is not so simple because you have to delete the inline log-writer policy first. So it seems you have to do

EDIT when I deleted the role but not the function, it created the role then failed to create the function, so I deleted the function but then when I ran create it failed because the role already exists… again.

So all steps:

aws iam delete-role-policy --role-name my-function-executor --policy-name log-writer
aws iam delete-role --role-name my-function-executor
aws lambda delete-function --function-name my-function

EDIT 2: I’ll mention I got into this situation because I changed my module entry point name from index.js to build/app.js (I started using babel precompilation.) I updated claudia.json but error messages seemed to indicate something was still attempting to import the old index.js so I deleted claudia.json and realized I had to delete the old lambda & role before it could create a new one with the same name.

[alpha-beta-soup]

Hmm, deleting the role in IAM doesn’t seem to be sufficient — I still get the error after doing so. Using the CLI has the same outcome. Is there something else that needs deleting? aws iam list-roles verifies that the role doesn’t exist.

I think these issues are the same or very similar:

• https://github.com/claudiajs/claudia/issues/169
• https://github.com/claudiajs/claudia/issues/190