Environment variables for testing

Environment variables for testing

In order to test your function in local debugging, either you can add the environmental variables in your local machine or you can add it in your .env file inside your functions folder and access the same.    In order to access the environment variables in development and production, you need to add

    • Related Articles

    • How to create a folder in the File Store in the production environment?

      You can create folders using Catalyst SDK’s only in the development environment. The folders cannot be created through Catalyst SDK methods in the production environment. Hence, we would suggest you to create the folders in the Filestore only from ...

    • Package not found error in production, although function works in development environment

      This means the packages aren't installed within the functions folder. In the local debugging environment, this issue doesn't occur because packages may be available globally. Please make sure packages are present within the respective functions ...

    • Catalyst Data Store : API Limit Reached - Error 403

      As the message indicates, you have reached the maximum limit for row count in your development environment. You can query the tables in order to find the count of rows in specific table in the ZCQL console. Also, the limit will be 5000 rows per table ...

    • How to invoke Circuit URL from Postman

      If you use a self client to generate the Grant token, then you need to use Postman to generate the access token for your usage. In postman, make a POST request to the following sample URL : ...

    • Catalyst Data Store tables are empty in production

      We would suggest you to use the Catalyst CLI/Bulk Write API to perform the bulk write operation in your table in the production environment. You can export the same from development and import it into production. Please check this link for more ...