Closed amsand11 closed 1 year ago
Update: The problem is definitely between my ears.
It appears the root of the component service's execution in my example is actually at /my-cool-service
.
So my file variable references should look like this for my-cool-service
specific configuration:
provider:
environment:
ENV_FOO: ${file(serverless.localdev.yml):CONFIG_FOO}
and this to reference the project level configuration (config that might be shared across component services):
provider:
environment:
ENV_BAR: ${file(../global.localdev.yml):CONFIG_BAR}
Are you certain it's a bug?
Are you using the latest version?
Is there an existing issue for this?
Issue description
I have the following setup
And this yields the following error:
I would generally expect to have service specific config files, but thus far the only resolution I've been able to get working are files that live at the project root. This is a fine workaround for my limited/simple use case right now, but I often prefer to keep configuration items isolated to the specific "thing" (i.e. service) that needs them.
Service configuration (serverless-compose.yml) content
Command name and used flags
serverless my-cool-service:print --stage localdev
Command output