-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VpcConfig invalid when referencing other resources #57
Comments
Known bug. Related to #22. We are working on resolving this now. We will update this thread once its resolved |
I literally preprocess my templates inserting the proper info.
…-Joe
Sent via mobile.
On Feb 15, 2017 10:49 PM, "Denis Loginov" <notifications@github.com> wrote:
Is there any workaround for now? Perhaps substitution at a higher level?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#57 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA-bx8uv6ilyLaxUTslq762rDMRuCV5Iks5rc8c7gaJpZM4Le2dZ>
.
|
I'm doing everything through CodePipeline now and strangely, it doesn't appear to have this problem. EDIT: haven't tested with ImportValue though, it may be the only thing still not supported. EDIT2: Seems like deletion of ENI still doesn't work if there are referenced resources (even when references are resolved correctly), see #64 |
@dinvlad that's because we just recently deployed the fix :-) Intrinsic functions should just work, except for ImportValue specifically in a few places - https://github.com/awslabs/serverless-application-model/blob/master/HOWTO.md#using-intrinsic-functions |
Yep, working correctly now! |
Confirmed, now working. |
The following returns the error message
Resource with id [SampleFunction] is invalid. Type of property 'VpcConfig' is invalid.
though appears to be valid.When I modify the block to reference the actual values (as follows), template works as expected, thus this seems to be a transform issue.
The text was updated successfully, but these errors were encountered: