-
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
CodeUri - FnSub #89
Comments
Yes, this is a known bug. Intrinsics are not yet supported. #22 will fix this. |
mndeveci
pushed a commit
that referenced
this issue
Nov 19, 2021
mndeveci
added a commit
that referenced
this issue
Nov 23, 2021
hawflau
added a commit
that referenced
this issue
Apr 6, 2022
* feat: Support for Lambda URL (#86) * feat: changed CorsConfig property to Cors (#89) * feat: add list of "unreleased" properties (#91) This change hides the unreleased properties from the "Globals" error message * Lambda URL integ test (#94) * remove functionUrlConfig from the unrelease properties (#97) * remove functionUrlConfig from the unrelease properties * updates * Function Url new changes (#109) * update to Function Url * first update * reverted to support autopublishing and added validation for AuthType values * adding Integration test * fix: fix paths IF intrinsic bug (#107) * fix: fix paths IF intrinsic bug * missed bit of code * add NoValue tests * review feedback and refactoring * naming fix * review feedback naming and comments * add missing test + add extra check for api key on tests * integration test updated (#122) Co-authored-by: jonife <79116465+jonife@users.noreply.github.com> Co-authored-by: Renato Valenzuela <37676028+valerena@users.noreply.github.com> Co-authored-by: Ruperto Torres <86501267+torresxb1@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It doesn't look like i am able to use aws intrinsic functions, specifically Fn::Sub, in the CodeUri property.
e.g.
CodeUri: !Sub "s3://${S3Bucket}/${S3Key}"
This will resolve properly in the description property e.g.
Description: !Sub "s3://${S3Bucket}/${S3Key}"
Is this something hat could be supported? I know the docs say it MUST be a valid s3 :)
The text was updated successfully, but these errors were encountered: