Open tekumara opened 3 years ago
This was on a stack that I had created by importing resources. I updated the stack using another tool (parfait). The stack is now in a state that stackit is happy with, and stackit is no longer hanging.
Can reproduce this reliably by creating and executing an import change set, eg:
aws cloudformation create-change-set \
--stack-name $(stackname) --change-set-name $(LogicalResourceId)ImportChangeSet \
--change-set-type IMPORT \
--resources-to-import "[{\"ResourceType\":\"AWS::S3::Bucket\",\"LogicalResourceId\":\"$(LogicalResourceId)\",\"ResourceIdentifier\":{\"BucketName\":\"$(BucketName)\"}}]" \
--template-body file://infra/cloudformation/s3-buckets.yaml
aws cloudformation describe-change-set --change-set-name $(LogicalResourceId)ImportChangeSet --stack-name $(stackname)
aws cloudformation execute-change-set --change-set-name $(LogicalResourceId)ImportChangeSet --stack-name $(stackname)
And then try and run stackit as above.
stackit just hangs without any indication of what's happening: