claudia destroy ignores --profile

[kdybicz]

• Expected behaviour:

I would assume that claudia destroy --profile private will cleanup all changes introduced by Claudia. This in my case includes removing Lambda function, all installed notification handlers, role and policies.

• What actually happens:

Unfortunately it's failing, because the --profile part seems to be ignored on https://github.com/claudiajs/claudia/blob/master/src/commands/destroy.js#L30 level and default profile is used. Which leads to situation where Lambda is properly removed, but roles and policies remain intact. I believe that there is also no code for notification handler/s removal.

AWS_PROFILE=private claudia destroy seems to be temporary workaround for that issue.

• Link to a minimal, executable project that demonstrates the problem:

Any project where different AWS profile than default is in use. I'm trying to use Claudia here: https://github.com/secretescapes/aws-lambda-image/tree/claudia-to-rule-them-all.

• Steps to install the project:

Clone that branch and replace private profile (in the package.json) with one that should be used. Be sure that default profile is invalid or to restrictive to allow Claudia to work properly.

Then just run npm run create.

• Steps to reproduce the problem:

npm destroy

[linshu]

I am having the same problem.

[gojko]

the most likely cause is this line

claudia/src/util/destroy-role.js

Line 2 in c3b837d

iam = new aws.IAM();

where IAM is initialised during module load instead of when the function is called. I should be able to patch and retest this soon.

[linshu]

You might need consider destroy a lambda which is created with an existing role (using --role option). I got this error while I destroyed a lambda with an existing role.

SJCMACD951FD56:rds_sns slin$ AWS_PROFILE=claudia claudia destroy
{ [DeleteConflict: Cannot delete entity, must detach all policies first.]
  message: 'Cannot delete entity, must detach all policies first.',
  code: 'DeleteConflict',
  time: Tue Feb 14 2017 13:24:18 GMT-0800 (PST),
  requestId: 'f1844792-f2fb-11e6-90ce-5d24be813fc8',
  statusCode: 409,
  retryable: false,
  retryDelay: 97.95927084051073 }

[kdybicz]

@linshu that's my bad. The actual working workaround is AWS_PROFILE=private claudia destroy --profile private. That one should also work for you.

[kdybicz]

👍

[gojko]

this is now on NPM as 2.8.0