-
-
Notifications
You must be signed in to change notification settings - Fork 455
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
Can't concatenate in serverless.yml #530
Comments
Unfortunately I think you have to store the whole string in your environment file. |
This doesn't seem right. You can see in the official Serverless Components documentation here that there is string concatenation in the yaml file: https://github.com/serverless/components#variables
There is also an example of string concatenation in the serverless-nextjs-plugin yaml file here: https://github.com/serverless-nextjs/serverless-next.js/tree/master/packages/deprecated/serverless-plugin#overriding-page-configuration
It feels like something is wrong with how the component package is reading the yaml file.
|
Wrap them in quotes, |
That doesn't work either. So frustrating.
Then running
I get a domain of |
I have no explanation for this, but the trick is to set Working configuration
|
Invalid credentials or this AWS S3 bucket name may already be taken
error when trying to deploy
#289
I'm currently migrating from the plugin to the component.
In my existing serverless.yml I am able to do this sort of thing:
But in the component if I do this
Then it doesn't seem to concatenate.
Also with the lambda names:
In that case I just get the STAGE variable without the
-front-end
added on.If the syntax works in the old serverless.yml I'm surprised it doesn't work in the new serverless.yml.
Am I doing something wrong? I don't want to have to send
${SUBDOMAIN}
, ${LAMBDA_NAME}, ${API_LAMBDA_NAME}
, etc. when they're all just derivations off of${STAGE}
The text was updated successfully, but these errors were encountered: