AnthonyWC

+1 on skipping resources scanning in the beginning; also I don't think caching is working for me (on python 3.5). Where is the cache stored?

As a workaround I unselected aws-sdk plugin from the project configuration.

~Has anyone got this to work in 3.4.2?~ Edit: Somehow got it to work after I downgrade to 3.4.0 then upgrade to 3.4.2 works after I apply the patch.

> I find it strange that terraform doesn't natively better support importing and re-synching existing infrastructure. The functionality terraform provides natively is just sub-par and this project fills the gap!...

If you mean the order under plugins in serverless.yml; I wasn't aware that the order makes a difference (is that documented anywhere..) but I did try both as you suggested;...

ok good to know there is a workaround; although I am no longer using alias. And yes I am using the step-function from horike37.

Think the template should have been included as part of default installation, new users are very likely to miss that install portion all together which doesn't make for good user...

I got a similar error; in my case it is due to the serverless-pseudo-parameter changing region in Resource, e.g. us-east-1 => ${AWS::Region} For example, let's say you have any resource...

Reporting that it doesn't work even when 'use Watchfile' after atom reload (unless it requires reboot or unmount) ``` #apm -v apm 1.15.3 npm 3.10.5 node 4.4.5 x64 python 2.7.12...

Adding some data point.. ``` %env repl.go:1:1: expected statement, found '%' ```