Question

How to access environment variables defined in Function Settings tab?

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: {}

Submit an answer


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!

Sign In or Sign Up to Answer

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.

Bobby Iliev
Site Moderator
Site Moderator badge
November 6, 2022
Accepted Answer

Hi there,

By default, the doctl serverless deploy command will look for an .env file in the same directory as the project.yml file.

To fix the error that you are seeing, create a .env file and define the SECRET_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

    Try DigitalOcean for free

    Click below to sign up and get $200 of credit to try our products over 60 days!

    Sign up

    Become a contributor for community

    Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

    DigitalOcean Documentation

    Full documentation for every DigitalOcean product.

    Resources for startups and SMBs

    The Wave has everything you need to know about building a business, from raising funding to marketing your product.

    Get our newsletter

    Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.

    New accounts only. By submitting your email you agree to our Privacy Policy

    The developer cloud

    Scale up as you grow — whether you're running one virtual machine or ten thousand.

    Get started for free

    Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

    *This promotional offer applies to new accounts only.