We cannot get the Functions environment variables to work as described in the “templating” section of the “project.yml” reference documentation (https://docs.digitalocean.com/products/functions/reference/project-configuration/#templating). When we set an environment variable under the DO platform’s Functions > [NAMESPACE] > [FUNCTION_NAME] > Settings, then try to deploy the function from doctl with templating in the project.yml file, it throws this error:
"Error: The following substitutions could not be resolved: 'SECRET_KEY'"
(‘SECRET_KEY’ being the name of the variable that we want to keep only on the DO platform and not in some config file for obvious reasons).
Here is the project.yml
file for reference:
environment: {}
parameters: {}
packages:
- name: sample
environment: {}
parameters: {}
annotations: {}
functions:
- name: hello
binary: false
main: ''
runtime: 'python:default'
web: true
parameters: {}
environment:
SECRET_KEY: "${SECRET_KEY}"
annotations: {}
limits: {}
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hi there,
By default, the
doctl serverless deploy
command will look for an.env
file in the same directory as theproject.yml
file.To fix the error that you are seeing, create a
.env
file and define theSECRET_KEY
variable in there.Then you could also create a
.gitignore
file and define the.env
file in there, that way it will not be tracked by Git.Hope that this helps!
Best,
Bobby
This comment has been deleted