You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
first of all: Thank you for your work on this plugin. We just started implementing a serverless api and need env-var support. Unfortunately, we need access to Cloudformation-Outputs inside of the env vars, e.g. for a Subnet-ID.
What we did so far is more of a workaround by specifying the env vars multiple times:
(no guarantees on correct indentation 😄 )
We would love to manage all of the env variables in their dedicated files and just have a ${env:dbHost} in the functions section without the ugly repetition in custom . Is there a way to achieve this?
Thanks in advance!
The text was updated successfully, but these errors were encountered:
Hey,
first of all: Thank you for your work on this plugin. We just started implementing a serverless api and need env-var support. Unfortunately, we need access to Cloudformation-Outputs inside of the env vars, e.g. for a Subnet-ID.
What we did so far is more of a workaround by specifying the env vars multiple times:
(no guarantees on correct indentation 😄 )
We would love to manage all of the env variables in their dedicated files and just have a
${env:dbHost}
in the functions section without the ugly repetition incustom
. Is there a way to achieve this?Thanks in advance!
The text was updated successfully, but these errors were encountered: