Unable to find logical ref resource for

[bboure]

@lightsofapollo

Since #65 was merged I get this kind of error all over the place.

Error: Unable to find logical ref resource for : AWS::Cognito::UserPool (custom.appSync.userPoolConfig.userPoolId.Ref)

The reason is that the implementation only supports DynamoDb resolution for now and throws an exception on any other resource.

This is a breaking change. Before this, userPoolId being a reference did not cause any problem since the emulator simply ignores/mocks authentication.

This error also occurs in any other resource referencing another, even if not even related to AppSync at all.

I suggest we change this line to fallback to the previous behaviour and simply return value untouched/unresolved, instead of throwing an exception.

[pianomansam]

I'm also experiencing this issue and didn't know where it was coming from.

…

On Wed, Apr 24, 2019, 7:51 AM Benoît Bouré ***@***.***> wrote: @lightsofapollo <https://github.com/lightsofapollo> Since #65 <#65> was merged I get this kind of error all over the place. Error: Unable to find logical ref resource for : AWS::Cognito::UserPool (custom.appSync.userPoolConfig.userPoolId.Ref) The reason is that the implementation only supports DynamoDb resolution for now and throws an exception on any other resource. This is a breaking change. Before this, userPoolId being a reference did not cause any problem since the emulator simply ignores/mocks authentication. This error also occurs in any other resource referencing another, even if not even related to AppSync at all. I suggest we change this line <https://github.com/ConduitVC/aws-utils/blob/master/packages/appsync-emulator-serverless/cloudFormationProcessor.js#L56> to fallback to the previous behaviour and simply return value untouched/unresolved, instead of throwing an exception. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#112>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGYBCB3IYLGYS7B3RF27JLPSBCURANCNFSM4HIDDVJA> .

[lightsofapollo]

@pianomansam This should be fixed in 0.12 onward. Can you confirm this works for you?

[pianomansam]

@lightsofapollo this appears to be fixed on 0.12