More v1 migration feedback: My

KinesisStream

customer functions refused to upgrade, giving CloudFormation errors such as

adam-casa-iot-ingest-stateChange already exists in stack

. Tweaking the

functionName

slightly (I just appended a

2

) allowed the old function to be deleted and a new one created. I don't know why these were a problem but not my

API

or

Script

functions.

thanks! i just encountered this updating my db stack. the stream consumer got the ’already exists in stack` error, updating the name fixed it. perhaps removing the name would have worked too, but i didn’t try that.