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
{{ message }}
This repository has been archived by the owner on Oct 1, 2020. It is now read-only.
I've been trying to use kinesis-firehose-cloudwatch-logs-processor as part of my kinesis firehose stack, but because all Serverless applications get deployed as nested stacks there is no easy way to reference the resources in the parent stack if there are no outputs. For instance, "serverlessrepo-auto-subscribe-log-group-to-arn" application has outputs and can be easily integrated. I strongly believe that before being published the applications need to have the resource outputs specified in the template.
Overall, I'm loving the Serverless Repo!
The text was updated successfully, but these errors were encountered:
I've been trying to use kinesis-firehose-cloudwatch-logs-processor as part of my kinesis firehose stack, but because all Serverless applications get deployed as nested stacks there is no easy way to reference the resources in the parent stack if there are no outputs. For instance, "serverlessrepo-auto-subscribe-log-group-to-arn" application has outputs and can be easily integrated.
I strongly believe that before being published the applications need to have the resource outputs specified in the template.
Overall, I'm loving the Serverless Repo!
The text was updated successfully, but these errors were encountered: