Skip to content

Custom CloudFormation resources should gracefully handle stack creation rollbacks #237

@rbalman

Description

@rbalman

Is your feature request related to a problem? Please describe.
Whenever a lambda backed custom resource creation fails, "github.com/aws/aws-lambda-go/cfn" returns a physicalResourceID to CloudFormation which doesn't exist. Then when CloudFormation tries to DELETE non-existent resource it fails. I have to manually skip the deletion of that particular custom resource to delete the Stack.

Describe the solution you'd like
Custom CloudFormation Resource should be able to be deleted like other normal Resources even though the CREATE event was not successful

Additional context

####### Here My Custom Resource is returning some ID when failed to create
Screen Shot 2019-09-24 at 11 24 34 AM

####### Here AWS Security Group returning nothing when failed to create

Screen Shot 2019-09-24 at 11 29 49 AM

Related PR

remind101/empire#918

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions