Hi there,
I'm trying to read a config file and read its contents into an ENV variable, however what I'm getting is an original config string partially interpreted. The 'stage' variable gets replaced properly but everything else is not.
Resulting function (you may notice how 'stage' was properly replaced with the correct value):
This exact ENV var definition works in a non-component based service, properly reading the file and putting its content as a ENV variable value. It appears that not all of the dynamic variables available for regular services can be used for component-based services. What are the best practices to solve this?
Got a reply to this in slack group basically confirming that this is an expected behaviour of a component-based service and not all of the dynamic variables are supported at this time. Closing this for now 👍
Hi there, I'm trying to read a config file and read its contents into an ENV variable, however what I'm getting is an original config string partially interpreted. The 'stage' variable gets replaced properly but everything else is not.
Here's my template:
Resulting function (you may notice how 'stage' was properly replaced with the correct value):
This exact ENV var definition works in a non-component based service, properly reading the file and putting its content as a ENV variable value. It appears that not all of the dynamic variables available for regular services can be used for component-based services. What are the best practices to solve this?
Thanks in advance!