Thank your very much, for your response.
Okay, nice...I was thinking about an function-less service for the resources.
I'm not sure if I understand the documentation. What I figured:
1. create a service name resources and in the resource/serverless.yml define the something like
2. in the say they api/serverless.yaml I reference it like
Optionally I would define custom variables in the resources/serveless.yml so the path to reference is a little shorter.
Did I get that more or less correctly?
Kind regard, thomas
I'm coming from In serverless 0.5.6. There were the CloudFormation-Outputs which were stored in _meta and could be used and referenced as environment variables. Especially when ARNs are needed this comes in handy, right?
Does serverless-1.x handle it in a similar way? Or how do I get the details in to variables and into the environment of the other services?